Jimbo.Automates Posted August 23, 2022 Author Share Posted August 23, 2022 I updated to elk Node server 3.4.9 The elk Node server status in PG3 shows disconnected. When I try and access the log file using the PG3 GUI, I get a 404 not found error. I have tried to delete and recreate the elk Node server. I have rebooted my polisy box. I have tried all these things repeatedly. Now all of my node servers (not just elk) are showing disconnected status in the PG3 GUI. I am running PG3 3.0.63, and IoP 5.4.4 I have made sure there were no pending updates on my polisy box as shown below. Something is seriously wrong here but I don't know how to proceed: [admin@polisy ~]$ sudo pkg update Password: Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. [admin@polisy ~]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy ~]$ sudo service udx status udx is running as pid 1148. [admin@polisy ~]$ sudo service isy status isy is running as pid 1216. [admin@polisy ~]$ sudo service pg3 status pg3 is running as pid 794. You should not be using pkg upgrade, only use Upgrade Packages in the admin console. Send a support ticket using the URL Michel has in his signature.Sent from my Pixel 6 Pro using Tapatalk 1 Link to comment
wmcneil Posted August 23, 2022 Share Posted August 23, 2022 12 hours ago, JimboAutomates said: You should not be using pkg upgrade, only use Upgrade Packages in the admin console. Send a support ticket using the URL Michel has in his signature. Sent from my Pixel 6 Pro using Tapatalk I have opened a ticket. I'll post back here when I am able to make progress. Link to comment
wmcneil Posted August 23, 2022 Share Posted August 23, 2022 16 minutes ago, wmcneil said: I have opened a ticket. I'll post back here when I am able to make progress. I pressed the "Upgrade Packages" button in the AC, and waited until it appeared changes were complete. (I never got 4 beeps, but waited until only the far left LED on the polisy box was illuminated. ) I then restarted PG3, and many things seem to be now working correctly once again, including Elk Node server 3.4.9 1 Link to comment
garybixler Posted August 25, 2022 Share Posted August 25, 2022 Just thought I would pass this error along. Doesn't seem to affect the operation. Thanks Gary 2022-08-25 08:37:33,515 Thread-2163 udi_interface DEBUG Controller:shortPoll: done 2022-08-25 08:37:36,713 ELK-21607 udi_interface INFO Controller:callback: ELK Controller: cs={'real_time_clock': '3537085250822110'} 2022-08-25 08:37:36,714 ELK-21607 udi_interface INFO Controller:callback: real_time_clock=3537085250822110 2022-08-25 08:37:38,524 ELK-21607 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message ZV!!! 2022-08-25 08:37:38,526 ELK-21607 udi_interface.node DEBUG node:setDriver: controller:ELK Controller Reporting set ERR to 1 to Polyglot 2022-08-25 08:37:38,527 ELK-21607 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-08-25 08:37:38,527 ELK-21607 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'ERR', 'value': '1', 'uom': 56}]} 2022-08-25 08:37:38,529 ELK-21607 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: ns_error = ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!! ...saving 2022-08-25 08:37:38,530 ELK-21607 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-08-25 08:37:38,531 ELK-21607 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {'ns_error': 'ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!!'}}]} 2022-08-25 08:37:38,533 ELK-21607 udi_interface DEBUG Controller:set_st: ELK Controller: elk_st=1 st=6 2022-08-25 08:37:38,534 ELK-21607 udi_interface.node DEBUG node:setDriver: controller:ELK Controller Reporting set GV1 to 6 to Polyglot 2022-08-25 08:37:38,535 ELK-21607 udi_interface.node DEBUG node:reportDriver: Updating value to 6 2022-08-25 08:37:38,535 ELK-21607 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV1', 'value': '6', 'uom': 25}]} 2022-08-25 08:37:38,685 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2022-08-25 08:37:38,687 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2022-08-25 08:37:38,688 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'ns_error': 'ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!!'} 2022-08-25 08:37:38,689 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking ns_error / ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!! 2022-08-25 08:37:38,728 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ERR to 1 UOM 56 2022-08-25 08:37:38,730 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2022-08-25 08:37:38,810 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV1 to 6 UOM 25 2022-08-25 08:37:40,203 ELK-21607 udi_interface INFO Zone:callback: zone_8:Outside Temp: changeset={'voltage': 0.7} 2022-08-25 08:37:40,204 ELK-21607 udi_interface DEBUG Zone:_set_voltage: zone_8:Outside Temp: val=0.7 2022-08-25 08:37:40,204 ELK-21607 udi_interface DEBUG BaseNode:set_driver: zone_8:Outside Temp: CV,0.7 default=None force=False,report=True Link to comment
Recommended Posts