CESNET
Call Home thread failed to wake up in a timely manner
hi:
We met a problem about netopeer2 recently. When the system is busy, netopeer2 maybe print "Call Home thread failed to wake up in a timely manner". Then after the system is not busy, netopeer2 can not call home again.
1)Following is detail log.
Nov 17 22:11:57 CTJ00000000000DDD netopeer2-server[2179]: 2020.Jan Could not set TCP_NODELAY socket option (Bad file descriptor). Nov 17 22:12:03 CTJ00000000000DDD netopeer2-server[2179]: 2020.Jan Could not set TCP_NODELAY socket option (Bad file descriptor). Nov 17 22:12:09 CTJ00000000000DDD netopeer2-server[2179]: 2020.Jan Could not set TCP_NODELAY socket option (Bad file descriptor). Nov 17 22:12:10 CTJ00000000000DDD netopeer2-server[2179]: SSH key exchange error (Received SSH_MSG_DISCONNECT: 9:Server key did not validate). Nov 17 22:12:12 CTJ00000000000DDD netopeer2-server[2179]: Session 6: SSH channel write failed. Nov 17 22:12:12 CTJ00000000000DDD netopeer2-server[2179]: Session 6: SSH channel poll error (Socket error: disconnected). Nov 17 22:12:12 CTJ00000000000DDD netopeer2-server[2179]: Session 7: invalid session to write to. Nov 17 22:12:12 CTJ00000000000DDD netopeer2-server[2179]: Session 7: failed to write reply. 2020.Jan Nov 17 22:12:15 CTJ00000000000DDD netopeer2-server[2179]: Session 6: ### _Call Home thread failed to wake up in a timely manner, fatal synchronization problem._
Following is version info: [root@CTJ00000000000DDD ~]# netopeer2-server -V netopeer2-server 0.7.0 compile time: Jul 29 2020, 15:26:26
[root@CTJ00000000000DDD ~]# sysrepod -v sysrepod - sysrepo daemon, version 0.7.8
Thank you very much. Wating for your reply.
You are using an obsolete version of sysrepo so I cannot provide much support but I think you can only increase NC_SESSION_FREE_LOCK_TIMEOUT in session_p.h. There is 1s currently, which I would expect is enough for a thread to wake up, but I suppose it depends on the scheduler.
