I just uninstalled it while logged in, and I can now see that the node servers directory is empty, unless something is hidden.  Just in case, I ran the rm command you suggested.

Reinstalled; same errors in the log.  Now that I'm logged in, are there any particular files you want me to look for?

-Tom

 

9 minutes ago, xlurkr said:

Reinstalled; same errors in the log.  Now that I'm logged in, are there any particular files you want me to look for?

Look at the NodeServer log.  It's in ISY-Inventory/logs/debug.log

See if the errors are the same as before.  If they are then for some reason it's not installing the modules on your Polisy.

Manually run the install.sh file.

/var/polyglot/nodeservers/ISY-Inventory
sudo -u polyglot ./install.sh

Post any errors from that.  If there's no errors then try to start the nodeserver from the UI

I had a similar issue, and found that I needed to upgrade the Polisy OS from 12.1 to 12.2 manually to correct it.
Steps taken:
Remove the offending node server(s) using the web interface
SSH to the Polisy
uname -r -------this shows the current version, mine started with 12.1
sudo curl -s https://pkg.isy.io/update121.sh | sudo bash
uname -r -------you should see that it is now 12.2
Install node server (s) using web interface

Sent from my Pixel 3 XL using Tapatalk

The logs/ directory doesn't appear to exist.

I will try Rob's suggestion next, since I tried running install.sh before he posted and got this:

ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6"

Collecting polyinterface

  Using cached polyinterface-2.1.0-py3-none-any.whl (13 kB)

Requirement already satisfied: requests in /usr/local/lib/python3.7/site-packages (from -r requirements.txt (line 2)) (2.22.0)

Collecting python-dotenv

  Using cached python_dotenv-0.15.0-py2.py3-none-any.whl (18 kB)

Requirement already satisfied: netifaces in /usr/local/lib/python3.7/site-packages (from polyinterface->-r requirements.txt (line 1)) (0.10.9)

Collecting markdown2

  Using cached markdown2-2.3.10-py2.py3-none-any.whl (34 kB)

Collecting paho-mqtt

  Using cached paho-mqtt-1.5.1.tar.gz (101 kB)

    ERROR: Command errored out with exit status 1:

     command: /usr/local/bin/python3.7 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-zygobz9e/paho-mqtt/setup.py'"'"'; __file__='"'"'/tmp/pip-install-zygobz9e/paho-mqtt/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-yzk5qby4

         cwd: /tmp/pip-install-zygobz9e/paho-mqtt/

    Complete output (1 lines):

    ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6"

    ----------------------------------------

ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

 

56 minutes ago, xlurkr said:

The logs/ directory doesn't appear to exist.

I will try Rob's suggestion next, since I tried running install.sh before he posted and got this:

ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6"

logs is created if/when the NS starts... which it isn't.

Looks like your system is messed up or needs updating.  Update the system and try again.  If it continues to fail open a ticket.

OK, the update fails.  Details are in the "100 Packages..." thread in Geek Batch.

-Tom

 

Something is not right.
Try
curl https://pkg.isy.io/update121.sh
chmod +x update121.sh
sudo ./update121.sh


Sent from my Pixel 3 XL using Tapatalk

OK, I will, but isn't curl returning the wrong thing?  What I got back doesn't look like a shell script to me.

-Tom

It is, which is why I'm asking you to eliminate the -s option, and save the result as a file to be executed locally instead of through the pipe

Sent from my Pixel 3 XL using Tapatalk

Can you try this yourself?  The curl command on its own, I mean.  I get back some html, not an install script.

-Tom

 

24 minutes ago, xlurkr said:

Can you try this yourself?  The curl command on its own, I mean.  I get back some html, not an install script.

-Tom

 

I get the same HTML output.  At this point I think you need to open a ticket with UDI

Tagging @Michel Kohanim for some visibility

It looks like that script moved, or is no longer accessible.

That must have happened in the past couple of days because I used it last week.

Sent from my Pixel 3 XL using Tapatalk

Ticketed.

-Tom

@xlurkr et. al,

This URL will not work with browsers. Please please please just copy/paste.

With kind regards,
Michel

This morning, the curl | bash command worked, and I successfully upgraded to 12.2.  The NS installed correctly.  After initial configuration, it's working fine.

Thanks to all for your help, especially Rob.  The most logical conclusion is that the current version of this NS requires version 12.2 of the OS.  I hope 12.2 doesn't break any of the other NSs, but I suppose if it does, the authors will fix them over time.

-Tom

 

Hmm.... the URL seems to be down again today??   Running the curl command with the -s option I'm getting the same return output that xlurker previously was getting:

[admin@polisy ~]$ curl https://pkg.isy.io/update121.sh

<html>

<head><title>302 Found</title></head>

<body>

<center><h1>302 Found</h1></center>

<hr><center>nginx/1.18.0</center>

</body>

</html>

[admin@polisy ~]$

Suggestions?   My Polisy is still on 12.1 (see following)   John

 

[admin@polisy ~]$ uname -a

FreeBSD polisy 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 r355229 POLISY  amd64

[admin@polisy ~]$

27 minutes ago, inovermyhead said:

Hmm.... the URL seems to be down again today??   Running the curl command with the -s option I'm getting the same return output that xlurker previously was getting:

likewise:

[admin@polisy ~]$ curl https://pkg.isy.io/update121.sh
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx/1.18.0</center>
</body>
</html>
[admin@polisy ~]$

 

Since 302 is a temp redirect, I checked and https://pkg.isy.io/update121.sh in a browser seems to redirect to https://www.universal-devices.com/

Whatever is happening it does seem to be @ the server.

 

3 hours ago, MrBill said:

I checked and https://pkg.isy.io/update121.sh in a browser seems to redirect to https://www.universal-devices.com/

Please see Polisy thread.  Michael commented that this does not work in a browser.  It worked for me on the Polisy.

That's the wrong url -- missing a folder between pkg.isy.io and update121.sh  -- see the other thread for the final posts that contain the full correct URL.  (i'd post it here, but i don't trust my memory, and this thread is confused enough!)

1 hour ago, gzahar said:

Please see Polisy thread.  Michael commented that this does not work in a browser.  It worked for me on the Polisy.

Please study my post.   The copy paste was not from a browser, it was from a polisy admin prompt.  Then since 302 is the http code for temporary redirect and curl apparently doesn't tell us where to THEN I used a browser to check that....

58 minutes ago, mwester said:

That's the wrong url -- missing a folder between pkg.isy.io and update121.sh  -- see the other thread for the final posts that contain the full correct URL.  (i'd post it here, but i don't trust my memory, and this thread is confused enough!)

good eye! 

Correct:

https://pkg.isy.io/script/update121.sh | sudo bash

On 12/27/2020 at 6:34 PM, MrBill said:

THEN I used a browser to check that....

Understood, but based on a number of people doing that exact thing, Michel commented that it was not valid (at least that was my interpretation). Anyway, glad it is worked out now.

Edited December 29, 20204 yr by gzahar

OK, all good now - 277 updates downloaded and installed - with the command:  curl https://pkg.isy.io/script/update121.sh | sudo bash

When I was having my problem, I copied Michel's command and pasted it into a ssh terminal session on the Policy.  I got the HTML response, and bash choked on it.

Two days later I did exactly the same thing, and it updated correctly.

I would say that the server destination has occasionally been borked.  Not sure how or why, but this isn't just about browsers or incorrect paths.

-Tom

 

@xlurkr,

Without the last ' | sudo bash' you will get a text response.

With kind regards,
Michel