carteriii Posted Sunday at 08:25 PM Share Posted Sunday at 08:25 PM Running PG3x 3.2.27 with a brand new install on Polisy. Added ELK trial plugin. I entered config information that has been running on ISY994 (so I know what the user code it and it's right, and host is 192.168.1.15:2101 and I know 2101 is right and it still works from the ISY994 module). I did not enter a value for "outputs" since I haven't been sure what that is. ELK 3.10.15 shows disconnected, so I want to debug. I click the button/tab for "Log" and always see the message, "Starting events log", but never see any things displayed to the screen. I switch the log level to "Debug", and I have rebooted everything, including the Polisy itself. When I click to, "Download Log Package", I get a message that /var/polyglot/pg3/ns/000db9552474_1/logs/debug.log does not exist. I ssh to Polisy and found that the "logs" folder doesn't even exist: I'm clearly missing something, but have no idea what to try next. Why don't I even get any logs? Any suggestions? Thanks in advance. Quote Link to comment
Jimbo.Automates Posted Sunday at 09:49 PM Share Posted Sunday at 09:49 PM Probably a system issue, can you cat the install.log? Are you on the latest versions? Try "Upgrade Packges" in Admin Console, and when complete reboot, then delete and install Elk plugin again. If you are on the latest, then probably have to submit a support ticket, we have seen this issue before. Quote Link to comment
carteriii Posted Sunday at 11:50 PM Author Share Posted Sunday at 11:50 PM Thank you! Where in the install.log? I just looked in /var/log, /var/polyglot/log, and /var/polyglot/pg3/logs and do not see it anywhere. I should add that I've also restored a backup of my ISY994 to Polisy, and that obviously used the ELK module. Do I need to delete the module from IoX before trying to get the nodeserver running? I haven't seen any wiki doc or post suggesting that, and I'm obviously hoping not to have to re-do all my programs from the isy994 that currently reference elk zones & conditions. I ran the upgrade packages and according to that log, nothing had to be updated. I rebooted anyway and don't see any change. I did note that the logs include the question, "Is client running?" when it says that the log file doesn't exist. Below are the log lines from when I clicked to stop the ELK plugin and then start it again, and that "Is client running?" line is the last of this section that I've copied. 2024-09-15 14:44:06.234 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: stopNs 2024-09-15 14:44:06.260 [pg3] info: [ELK(1)]: Stopping Nodeserver 2024-09-15 14:44:06.261 [pg3] info: call_udx: Making request to socket with url /rest/pg3.stop.ns 2024-09-15 14:44:06.574 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 2024-09-15 14:44:06.582 [pg3] info: Getting Node Server store entry for nsid c7297a6e-f1c6-4c12-8b66-532a6721431a from store Production 2024-09-15 14:44:19.062 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: startNs 2024-09-15 14:44:19.073 [pg3] info: startNs:: ELK 2024-09-15 14:44:19.074 [pg3] info: startNs:: ELK is valid 2024-09-15 14:44:19.342 [pg3] info: checkLicense:: ELK Valid subscription license found. Expires: 2024-10-11T20:33:48.000Z 2024-09-15 14:44:19.356 [pg3] info: startNs:: ELK finished update check 2024-09-15 14:44:19.359 [pg3] info: startNs:: Starting ELK 2024-09-15 14:44:19.360 [pg3] info: call_udx: Making request to socket with url /rest/pg3.start.ns 2024-09-15 14:44:19.395 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 2024-09-15 14:44:19.402 [pg3] info: Getting Node Server store entry for nsid c7297a6e-f1c6-4c12-8b66-532a6721431a from store Production 2024-09-15 14:44:19.537 [pg3] info: startNs:: ELK starting polls 2024-09-15 14:44:19.543 [pg3] info: Starting ELK Expire Check timer 2024-09-15 14:44:19.545 [pg3] info: Checking if ELK has expired 2024-09-15 14:44:19.545 [pg3] info: Starting ELK Info timer 0 2024-09-15 14:44:19.558 [pg3] info: startNs:: ELK updating database (enabled, timestarted) 2024-09-15 14:44:19.559 [pg3] info: startNs:: ELK started. 2024-09-15 14:44:19.733 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 2024-09-15 14:44:19.740 [pg3] info: Getting Node Server store entry for nsid c7297a6e-f1c6-4c12-8b66-532a6721431a from store Production 2024-09-15 14:44:51.402 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: startLogging 2024-09-15 14:44:51.409 [pg3] info: Is client running? /var/polyglot/pg3/ns/000db9552474_1/logs/debug.log does not exist. Quote Link to comment
Jimbo.Automates Posted Monday at 12:09 AM Share Posted Monday at 12:09 AM The install.log is in your screenshot when you show the listing of the plugin directory.Sent from my Pixel 8 Pro using Tapatalk Quote Link to comment
carteriii Posted Monday at 01:41 AM Author Share Posted Monday at 01:41 AM Ah, duh! Sorry. I really did do a recursive "find", but that directory cannot be viewed by even admin without a sudo so it missed it. Sorry. So interestingly enough, it says pip3 (called from line2 of install.sh) cannot be found -------------------------------------------------- Installation date: Wed Sep 11 13:34:33 PDT 2024 ./install.sh: line 2: pip3: command not found -------------------------------------------------- Installation date: Sun Sep 15 12:23:08 PDT 2024 ./install.sh: line 2: pip3: command not found -------------------------------------------------- Installation date: Sun Sep 15 13:03:47 PDT 2024 ./install.sh: line 2: pip3: command not found -------------------------------------------------- Installation date: Sun Sep 15 16:12:50 PDT 2024 ./install.sh: line 2: pip3: command not found If it matters, the only command in install.sh is "pip3 install -r requirements.txt --user" That led me to find this post, in which someone mentioned the symbolic link from /usr/bin/pip3: That in turn points to /usr/local/bin/pip-3.11 (which does not exist). lrwxr-xr-x 1 root wheel 23 Sep 15 16:12 pip3 -> /usr/local/bin/pip-3.11 From the previous forum discussion, I tried the following, which did not create a new symbolic link or update anything. sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx I've also tried to "sudo pkg install pip311" and variants like pip3.11 but can't figure out the name of the package through the udi repository. I've searched all these forums and done some google searching, but can't figure it out. If anyone knows how to install pip3, that would seem to be the root cause of these current problems. Quote Link to comment
Solution Jimbo.Automates Posted Monday at 02:00 AM Solution Share Posted Monday at 02:00 AM There have been issues with Python installs during the updates. Please submit a support ticket and they'll get you fixed. I've not seen anyone with this issue post the solution and previously @Michel Kohanim just mentioned it was a Python install issue.Sent from my Pixel 8 Pro using Tapatalk Quote Link to comment
carteriii Posted Tuesday at 05:29 PM Author Share Posted Tuesday at 05:29 PM You (@Jimbo.Automates) were exactly correct that there were Python installation issues that support helped me address. The ELK plugin came up as connected as soon as everything was restarted, without needing to do anything else. I now see all the nodes for my system, and I am seeing logs. Now I need to finish my ISY994 migration, but the basic install & function seems to be working well. Thank you! 1 Quote Link to comment
Jimbo.Automates Posted Tuesday at 07:55 PM Share Posted Tuesday at 07:55 PM Awesome, glad it worked! Hope you are happy with the elk plugin, I know converting from the old method can be painful.Sent from my Pixel 8 Pro using Tapatalk Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.