copperstar Posted November 18, 2023 Share Posted November 18, 2023 (edited) After an upgrade packages run, the Elk nodeserver is having problems. After several restarts and even a restore to previous, I continue to get ; Controller:handler_start: Timed out waiting for handlers to startup Although the NodeServer in IoX displays connected, there is no data available from the Elk NodeServer. Any ideas on restoring the server? Thanks Full error log below; 2023-11-17 19:14:42,977 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-11-17 19:14:42,979 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-11-17 19:14:42,980 MainThread udi_interface INFO __init__:<module>: User=000db953d8b0_1 2023-11-17 19:14:42,980 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/000db953d8b0_1 2023-11-17 19:14:42,981 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/000db953d8b0_1 2023-11-17 19:14:42,982 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MGQ6Yjk6NTM6ZDg6YjAiLCJwcm9maWxlTnVtIjoxLCJsb2dMZXZlbCI6IkVSUk9SIiwidG9rZW4iOiI5dStoVm5hZHVYQURnJkx1IiwibXF0dEhvc3QiOiJsb2NhbGhvc3QiLCJtcXR0UG9ydCI6ODg4Mywic2VjdXJlIjoxLCJpc1BHM3giOnRydWUsInBnM1ZlcnNpb24iOiIzLjIuMTYiLCJpc3lWZXJzaW9uIjoiNS43LjEiLCJlZGl0aW9uIjoiU3RhbmRhcmQifQ== 2023-11-17 19:14:42,983 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-11-17 19:14:43,576 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-11-17 19:14:43,791 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-11-17 19:14:45,615 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-11-17 19:14:45,620 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-11-17 19:14:45,621 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-11-17 19:14:45,621 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-11-17 19:14:45,622 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-11-17 19:14:45,623 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.4 Starting... 2023-11-17 19:14:45,902 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.16 [ISY: 5.7.1, Slot: 1] 2023-11-17 19:14:45,904 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.0.19', 'netmask': '255.255.255.0', 'broadcast': '192.168.0.255'} 2023-11-17 19:14:45,908 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-11-17 19:14:45,914 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-11-17 19:14:45,915 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 000db953d8b0_1.cert key: 000db953d8b0_1.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-11-17 19:14:45,916 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-11-17 19:14:45,918 MainThread udi_interface.interface INFO interface:addNode: Adding node ELK Controller(controller) [None] 2023-11-17 19:14:45,919 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-11-17 19:14:46,017 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-11-17 19:14:46,020 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:d8:b0_1 - MID: 2 Result: 0 2023-11-17 19:14:46,066 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-11-17 19:14:46,149 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-11-17 19:14:57,444 Thread-8 udi_interface ERROR Controller:handler_start: Timed out waiting for handlers to startup 2023-11-17 19:14:57,448 Thread-8 udi_interface ERROR udi_interface:write: Exception in thread 2023-11-17 19:14:57,449 Thread-8 udi_interface ERROR udi_interface:write: Thread-8 2023-11-17 19:14:57,450 Thread-8 udi_interface ERROR udi_interface:write: : 2023-11-17 19:14:57,451 Thread-8 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-11-17 19:14:57,452 Thread-8 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-11-17 19:14:57,460 Thread-8 udi_interface ERROR udi_interface:write: self.run() 2023-11-17 19:14:57,462 Thread-8 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-11-17 19:14:57,472 Thread-8 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-11-17 19:14:57,483 Thread-8 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db953d8b0_1/nodes/Controller.py", line 167, in handler_start 2023-11-17 19:14:57,492 Thread-8 udi_interface ERROR udi_interface:write: self.exit() 2023-11-17 19:14:57,493 Thread-8 udi_interface ERROR udi_interface:write: AttributeError 2023-11-17 19:14:57,494 Thread-8 udi_interface ERROR udi_interface:write: : 2023-11-17 19:14:57,495 Thread-8 udi_interface ERROR udi_interface:write: 'Controller' object has no attribute 'exit' Edited November 18, 2023 by Jimbo.Automates Link to comment
Jimbo.Automates Posted November 18, 2023 Share Posted November 18, 2023 This looks like PG3 didn't send all the info the plugin was waiting for. I see you are on the latest release so I will upgrade and see if I have any issues. Link to comment
Jimbo.Automates Posted November 18, 2023 Share Posted November 18, 2023 I upgrade modules rebooted and no issues. Please set Log Level to Debug, restart, and when you see that error again please "Download Log Package" and PM that to me. Link to comment
Solution copperstar Posted November 18, 2023 Author Solution Share Posted November 18, 2023 Ended up deleting then reinstalling elk nodeserver and all is well. Must have been something that I did :). Thanks again for the great product and for trying to help. 1 Link to comment
Recommended Posts