ELK module won't connect after upgrade to PG3x 3.2.27

[plumcrazy426]

My Elk system refuses to connect after I updated my Eisy.

Eisy is running 5.8.4
PG3x is at 3.2.27
Elk Poly is 3.10.15
I updated via "Upgrade packages" in the Admin Console then updated the Elk NS in PG3x.
The elk module says it's running but also says "disconnected" The IP address is correct and the Elk system is online. (I can access it via RP2 and my phone)

This system has been running flawlessly for about a year until I upgraded.

I have tried both restarting and powering down the eisy. Same for the ELK M1XEP module. I have even deleted and reinstalled the elk NS in PG3x. All to no avail. I tried to get the log package but got an error message.

The following is the PG3x log that has the error message in it.
pg3_7-26-2024_113047_AM.zip

The following is a log package file from yesterday when it would let me download the error log.
ELK_7-25-2024_95146_AM.zip

Another thing noted is that when I go to the configuration page of the Node Server I don't get the instructions nor do I get the field pre-populated for light_nodes. When I first went in prior to upgrade. I got both of those items.

One more hint, when I went to the program summary page in admin console, all of the programs that were related to elk nodes had some sort of memory error message, They went away when I disabled the programs and I haven't been able to reproduce those messages.

I've been pulling my hair out trying to figure this out, but it doesn't seem that complicated.

Any help or insight would be appreciated.

[DennisC]

First, only one device can be connected at a time. Make sure you are not connected to your Elk via RP2 or your phone.

Next make sure the port on the plugin page is correct.

You will need the plugin debug package for specific help, so I suggest the following:

Run upgrade packages again and when completed, reboot.

If you still can not connect try changing the log to debug. If necessary, restart the plugin and after waiting awhile, download a log package.

If you can't download the log, try reinstalling again.

[plumcrazy426]

Thanks for the tips, I had tried/checked all of the above with the exception of changing the log type to debug.

I went through the steps in the order you suggested and no change. Still disconnected and still a "file not found" error when trying to download the NS log package.

I did download a pg3x log file that has some errors in it. They might mean something to someone. I did find some error number 61's in some log files that I was able to get after my initial update.

What I am really suspicious of if the configuration file page (attached) that I am getting now. When I was able to access the log files I saw a different page that had some pretty colored words with instructions as to how to fill out the fields. I also had a pre-populated entry for "light_nodes". The attached is what I get now. I am suspicious that I got a corrupted file or 2 and it is not reading the configuration properly.

[Jimbo.Automates]

Your original post didn't contain the PG3X log file.  Please PM it to me and I'll look.

If you can't download log package, then I suspect PG3 had an error installing the plugin.

 

[plumcrazy426]

After Jimbo.automates looked at my PG3x log file, He advised me to open a ticket with UD. They were extremely prompt in responding and remotely SSH'd into my eisy and had me up and running in just a few minutes. It appears that there were some missing files and all is well now.