JTsao Posted December 16, 2020 Share Posted December 16, 2020 I did a Polisy: System->Check for Updates and I see that 100 Packages are available for update. Normally I try to keep the Polisy up to date,but I have never seen so many items to update - I am a bit concerned about breaking something when performing all of these updates - is anyone else seeing this? If so has anyone performed this massive update? Link to comment Share on other sites More sharing options...
simplextech Posted December 16, 2020 Share Posted December 16, 2020 3 minutes ago, JTsao said: I did a Polisy: System->Check for Updates and I see that 100 Packages are available for update. Normally I try to keep the Polisy up to date,but I have never seen so many items to update - I am a bit concerned about breaking something when performing all of these updates - is anyone else seeing this? If so has anyone performed this massive update? Only 100? nothing... Number of packages to be upgraded: 291 Most of them are FreeBSD system packages and dependencies. Link to comment Share on other sites More sharing options...
JTsao Posted December 17, 2020 Author Share Posted December 17, 2020 I guess 100 is not that big a number after all - I did the updates and everything looks OK so far... Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 18, 2020 Share Posted December 18, 2020 @JTsao et. Al, The reason for this is our migration to package based OS. In the upcoming releases, udx will automatically try and upgrade you to version 12.2 of the OS and packages. In the meantime, and if you feel like it: 1. ssh to Polisy 2. if the output of 'uname -a' is 12.1xx, then: curl -s https://pkg.isy.io/update121.sh | sudo curl 3. Afterwards, make sure 'uname -a' is 12.2xx With kind regards, Michel Link to comment Share on other sites More sharing options...
larryllix Posted December 18, 2020 Share Posted December 18, 2020 1 hour ago, Michel Kohanim said: @JTsao et. Al, The reason for this is our migration to package based OS. In the upcoming releases, udx will automatically try and upgrade you to version 12.2 of the OS and packages. In the meantime, and if you feel like it: 1. ssh to Polisy 2. if the output of 'uname -a' is 12.1xx, then: curl -s https://pkg.isy.io/update121.sh | sudo curl 3. Afterwards, make sure 'uname -a' is 12.2xx With kind regards, Michel curl: try 'curl --help' for more information which shows -s as a valid option. UPDATE: '| sudo curl' was English instruction, not bash script = all good now Link to comment Share on other sites More sharing options...
MrBill Posted December 18, 2020 Share Posted December 18, 2020 4 hours ago, Michel Kohanim said: @JTsao et. Al, The reason for this is our migration to package based OS. In the upcoming releases, udx will automatically try and upgrade you to version 12.2 of the OS and packages. In the meantime, and if you feel like it: 1. ssh to Polisy 2. if the output of 'uname -a' is 12.1xx, then: curl -s https://pkg.isy.io/update121.sh | sudo curl 3. Afterwards, make sure 'uname -a' is 12.2xx With kind regards, Michel Having just been through this with you i know that you meant to type: curl -s https://pkg.isy.io/update121.sh | sudo bash Link to comment Share on other sites More sharing options...
xlurkr Posted December 23, 2020 Share Posted December 23, 2020 Trying to do this right now. I get bash: line 1: html: No such file or directory bash: line 2: syntax error near unexpected token `<' 'ash: line 2: `<head><title>302 Found</title></head> -Tom Link to comment Share on other sites More sharing options...
xlurkr Posted December 24, 2020 Share Posted December 24, 2020 Here's what the curl returns: <html> <head><title>302 Found</title></head> <body> <center><h1>302 Found</h1></center> <hr><center>nginx/1.18.0</center> </body> </html> -Tom Link to comment Share on other sites More sharing options...
MrBill Posted December 24, 2020 Share Posted December 24, 2020 38 minutes ago, xlurkr said: Here's what the curl returns: <html> <head><title>302 Found</title></head> <body> <center><h1>302 Found</h1></center> <hr><center>nginx/1.18.0</center> </body> </html> -Tom Are you logging into your polisy via SSH? At a prompt that looks like this: [admin@polisy ~]$ type: curl -s https://pkg.isy.io/update121.sh | sudo bash the character between .sh and sudo is a vertical bar | which is often shift backslash or if not usually on the right side of the keyboard. Link to comment Share on other sites More sharing options...
xlurkr Posted December 24, 2020 Share Posted December 24, 2020 Yes, ssh in Terminal on a Mac. I am using the correct pipe character. I got the curl output I posted above by piping that to more. What do you get, right now, if you execute the curl command? -Tom Link to comment Share on other sites More sharing options...
DennisC Posted December 24, 2020 Share Posted December 24, 2020 When logging in to polish using ssh are you logging in using admin/admin? Link to comment Share on other sites More sharing options...
xlurkr Posted December 24, 2020 Share Posted December 24, 2020 Yes. Link to comment Share on other sites More sharing options...
MrBill Posted December 24, 2020 Share Posted December 24, 2020 45 minutes ago, xlurkr said: Yes, ssh in Terminal on a Mac. I am using the correct pipe character. I got the curl output I posted above by piping that to more. What do you get, right now, if you execute the curl command? -Tom The curl command gets an online script and pipes it to bash. What you should see is the output from the script... which is not html. perhaps you should open a ticket. support@universal-devices.com ps I can’t run the command now as both my policy’s have already been updated. Link to comment Share on other sites More sharing options...
xlurkr Posted December 24, 2020 Share Posted December 24, 2020 Couldn't you run the curl command and pipe it to more, like I did, just to see what you get? I wonder if that command returns something different now, compared to when you early upgraders did it. Michel said this was temporary, as he was moving to a new upgrade process, or something. I will open a ticket, once it looks like my situation is unique. -Tom Link to comment Share on other sites More sharing options...
mwester Posted December 24, 2020 Share Posted December 24, 2020 You can run the curl command at any computer that has curl installed, including WSL on Windows. Alternately, you can just open the URL part of the command in a browser on any computer. The response is a 302 -- a redirect. Not a shell script. UDI changed something, that URL is not useful any longer. Link to comment Share on other sites More sharing options...
xlurkr Posted December 24, 2020 Share Posted December 24, 2020 That's what I'm saying. Thanks for the the technical version. What I've been trying to do all day is run my first NS on my new Policy. The Policy is up-to-date, as far as it knows. The NS won't install correctly. Everyone trying to help me has already upgraded the OS to 12.2, so they told me to do so. I tried to and can't, apparently. I'm out of next moves. -Tom Link to comment Share on other sites More sharing options...
xlurkr Posted December 24, 2020 Share Posted December 24, 2020 Ticketed. -Tom Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 24, 2020 Share Posted December 24, 2020 @xlurkr, Thank you. I responded to your ticket. What you sent me had no resemblance to "curl -s https://pkg.isy.io/script/update121.sh | sudo bash". If it still does not work, please copy/paste the following command and send me the output: curl -s https://pkg.isy.io/script/update121.sh With kind regards, Michel Link to comment Share on other sites More sharing options...
xlurkr Posted December 24, 2020 Share Posted December 24, 2020 Michel: It is working this morning. It was not yesterday. Curl was returning HTML, not a bash script, and bash was choking on it. See my first post in this thread. I don't know what changed, but it was broken, and now it's not. Thank you. -Tom Link to comment Share on other sites More sharing options...
gzahar Posted December 24, 2020 Share Posted December 24, 2020 Just worked for me. FreeBSD 12.2-RELEASE-p2 r368666 POLISY Link to comment Share on other sites More sharing options...
mbking Posted February 8, 2021 Share Posted February 8, 2021 Using the following command, "curl -s https://pkg.isy.io/script/update121.sh | sudo bash", I updated Polisy to FreeBSD 12.2 based on some of the earlier discussions in this post. I too had seen a large number of update files and then suddenly the Update Check stopped working. Rebooting got it working for awhile, but it always returned 0 updates. I thought this FreeBSD update might help. The update completed normally and I'm now showing FreeBSD 12.2. I believe the release is P3. After rebooting Polisy, my 4 node servers appear to be working normally and I am getting the expected logs in those servers, but my overall Polisy log is no longer updating. The last lines in the log were posted about the time of the reboot after the FreeBSD upgrade. Has anyone else seen this or have any ideas how to correct it? Thanks. -Mark Link to comment Share on other sites More sharing options...
asbril Posted February 8, 2021 Share Posted February 8, 2021 I also noted that Polisy updates no longer appear. All my nodeservers work as desired and I assume that 3.X is around the corner and will resolve the issue. Link to comment Share on other sites More sharing options...
gviliunas Posted February 9, 2021 Share Posted February 9, 2021 @mbkingYes, I have same the same issue with the overall log. The individual NS logs are updating but the the main log stream has stopped. I think this was due to an update from this last Sunday 2/7 and not the 12.2 OS update. I've been running 12.2 for a few months. 2021-2-7 07:47:20 [polyglot] info: Caught SIGTERM/SIGINT Shutting down. 2021-2-7 07:47:20 [polyglot] error: MQTTS: clientError: ISY-Inventory read ECONNRESET 2021-2-7 07:47:20 [polyglot] error: MQTTS: clientError: HarmonyHub read ECONNRESET 2021-2-7 07:47:20 [polyglot] info: Ping(10): NodeServer Disconnected. 2021-2-7 07:47:20 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown at Function.MongoError.create (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/error.js:31:11) at /snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:497:72 at authenticateStragglers (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:443:16) at Connection.Pool.socketCount [as messageHandler] (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:477:5) at Socket.dataHandler (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/connection.js:333:22) at Socket.emit (events.js:159:13) Since all is working, I am going to wait for Polyglot 3.x I searched previous instances of the above mongo-db error and the solution seemed to be a factory reset on Polisy due to suspect db corruption. I'm going to wait for 3x before trying that as the current restore from a backup file requires lots of manual work and, as I stated, polisy NS functions are working. Link to comment Share on other sites More sharing options...
mbking Posted February 9, 2021 Share Posted February 9, 2021 1 hour ago, gviliunas said: @mbkingYes, I have same the same issue with the overall log. The individual NS logs are updating but the the main log stream has stopped. I think this was due to an update from this last Sunday 2/7 and not the 12.2 OS update. I've been running 12.2 for a few months. 2021-2-7 07:47:20 [polyglot] info: Caught SIGTERM/SIGINT Shutting down. 2021-2-7 07:47:20 [polyglot] error: MQTTS: clientError: ISY-Inventory read ECONNRESET 2021-2-7 07:47:20 [polyglot] error: MQTTS: clientError: HarmonyHub read ECONNRESET 2021-2-7 07:47:20 [polyglot] info: Ping(10): NodeServer Disconnected. 2021-2-7 07:47:20 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown at Function.MongoError.create (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/error.js:31:11) at /snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:497:72 at authenticateStragglers (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:443:16) at Connection.Pool.socketCount [as messageHandler] (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:477:5) at Socket.dataHandler (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/connection.js:333:22) at Socket.emit (events.js:159:13) Since all is working, I am going to wait for Polyglot 3.x I searched previous instances of the above mongo-db error and the solution seemed to be a factory reset on Polisy due to suspect db corruption. I'm going to wait for 3x before trying that as the current restore from a backup file requires lots of manual work and, as I stated, polisy NS functions are working. @gviliunas Thanks for the reply. Those are the same lines I see at the end of my overall log. I'm going to hope as well that 3x takes care of it. Thanks again. -Mark Link to comment Share on other sites More sharing options...
Jimbo.Automates Posted February 9, 2021 Share Posted February 9, 2021 There was a small update to Polyglotv2 recently and the log is still writing, just to a name that the UI doesn't see. It's fixed in an upcoming version that will hopefully be released soon.Sent from my Pixel 3 XL using Tapatalk Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.