Skip to content

Session 2 [ERR]: Invalid session to send RPCs. #11

Description

@jktjkt

This is a rather strange error that was observed once through netconf-cli-local:

/ietf-interfaces:interfaces/interface[name='lo']>
/ietf-interfaces:interfaces/interface[name='lo']> cd ietf-ip:ipv4/ietf-ip:address[ip=Session 2 [ERR]: Invalid session to send RPCs.
Error while completing: Failed to send RPC
                                                  cd ietf-ip:ipv4/ietf-ip:address[ip=
In line 1:
Error parsing key values here:
cd ietf-ip:ipv4/ietf-ip:address[ip=
___________________________________^_
/ietf-ip:address[ip= this was left of input
/ietf-interfaces:interfaces/interface[name='lo']> cd ietf-ip:ipv4/ietf-ip:address[ip=Session 2 [ERR]: Invalid session to send RPCs.
Error while completing: Failed to send RPC
Session 2 [ERR]: Invalid session to send RPCs.
Error while completing: Failed to send RPC
                                                  cd ietf-ip:ipv4/ietf-ip:address[ip=
In line 1:
Error parsing key values here:
cd ietf-ip:ipv4/ietf-ip:address[ip=
___________________________________^_
/ietf-ip:address[ip= this was left of input
/ietf-interfaces:interfaces/interface[name='lo']> cd ietf-ip:ipv4/ietf-ip:address[ip=Session 2 [ERR]: Invalid session to send RPCs.
Error while completing: Failed to send RPC
                                                  cd ietf-ip:ipv4/ietf-ip:address[ip=
In line 1:
Error parsing key values here:
cd ietf-ip:ipv4/ietf-ip:address[ip=
___________________________________^_
/ietf-ip:address[ip= this was left of input
/ietf-interfaces:interfaces/interface[name='lo']> cd ietf-ip:ipv4/ietf-ip:address[ip=

The netconf-cli-local talks NETCONF over a local UNIX socket. Maybe this happened because of a restart of netopeer2-server?

Activity

  1. jktjkt commented on Oct 9, 2025

    @jktjkt
    ContributorAuthor

    This is actually a server-side timeout:

    src/session_server.c:1866:        sprintf(msg, "Session idle timeout elapsed");
    

    It happens whenever the CLI is left idling for "too long". We should probably implement some keepalives, pings, whatever. Also, I'm getting this error message even when connected via the UNIX socket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions