I’ve been getting this for a few weeks now, very randomly. I’m thinking it might be related to python bug https://bugs.python.org/issue38904. Anybody else seen this? My apologies for posting something so vague, I’m not sure what to try next - I suppose I could read up on signal.
Nov 25 07:14:39 nacho librenms-service.py[3166]: Traceback (most recent call last): Nov 25 07:14:39 nacho librenms-service.py[3166]: File "/opt/librenms/librenms-service.py", line 48, in Nov 25 07:14:39 nacho librenms-service.py[3166]: service.start() Nov 25 07:14:39 nacho librenms-service.py[3166]: File "/opt/librenms/LibreNMS/service.py", line 404, in start Nov 25 07:14:39 nacho librenms-service.py[3166]: sleep(self.config.master_resolution) Nov 25 07:14:39 nacho librenms-service.py[3166]: File "/opt/librenms/LibreNMS/service.py", line 550, in reap Nov 25 07:14:39 nacho librenms-service.py[3166]: handler = signal(SIGCHLD, SIG_DFL) Nov 25 07:14:39 nacho librenms-service.py[3166]: File "/usr/lib/python3.8/signal.py", line 47, in signal Nov 25 07:14:39 nacho librenms-service.py[3166]: handler = _signal.signal(_enum_to_int(signalnum), _enum_to_int(handler)) Nov 25 07:14:39 nacho librenms-service.py[3166]: TypeError: 'int' object is not callable