I've had the Polisy Pro for quite some time now and it is generally working well, but recently, I have noticed some generic problems (in the title) - (1) When I go to Settings->Polisy Configuration, it says "Please wait, getting configuration..." indefinitely.  I honestly forgot what the menu is supposed to look like if it ever updates, but I am pretty sure its not supposed to hang-  Also (2), when I go to System->Check for Polisy Update, it no longer displays a message indicating if an update is available or not.  It does display the green box saying that it "Sent upgrade check command to Polisy..." but there are no subsequent boxes displayed.

I was in the process of documenting my Polisy setup by pasting screen captures into a MS-Word document when I noticed these issues.  Running 10 nodeservers.  Thanks in advance for any suggestions.

Forgot to mention, running V2.2.9-5 on the Polisy and V5.3.0 on the ISY

Edited November 25, 20204 yr by JTsao
add detail

@JTsao,

These are usually related to browser cache. Please try a different browser or clear the cache for Polisy.

With kind regards,
Michel

Hi Michael,

Thanks for the reply - I did try clearing the cache and 3 different browsers but no luck - this problem has me stumped

 

Edited November 25, 20204 yr by JTsao

I am seeing the exact same issues, even using different browsers.

Recently did an update to 4 or 5 node servers... Polisy now seems to act normal, however, I cant stop or delete any node servers, nor are there any logs. I have rebooted it several times, also cleared my caches on my browser.. am remote so I cant unplug it..

 

UPDATE: Each activity I click on, the green bars shows up to acknowledge it, but nothing happens and ALL node servers are no longer working in the ISY.... after the last reboot, the polisy uptime is frozen. 

 

any suggestions? 

Edited November 25, 20204 yr by dbwarner5

3 minutes ago, peterskajr said:

I am seeing the exact same issues, even using different browsers.

Michel K. helped me to fix the problems - I hope he doesn't mind me sharing this here - you have to be somewhat technical

I use the program Putty for SSH - procedure is below:

1. Ssh to Polisy

2. curl -s https://pkg.isy.io/script/update121.sh | sudo bash

Then I followed the instructions to reboot after the script completed, performing a

"sudo shutdown -r now" (script will tell you what to type, I am guessing from memory - may be different)

This appeared to be an alternative means of updating the Polisy and it fixed both issues

@JTsao,

Thank you. This is a stopgap measure to upgrade the OS from 12.1 to 12.2 + make the OS itself into packages. Of course, there have been couple of instances where this has not worked and we are looking into them. Our upcoming udx package, will check the OS and then upgrade everything if necessary.

With kind regards,
Michel

@JTsao, thanks for the instructions.  It fixed my issue as well!

 

8 minutes ago, JTsao said:

Michel K. helped me to fix the problems - I hope he doesn't mind me sharing this here - you have to be somewhat technical

I use the program Putty for SSH - procedure is below:

1. Ssh to Polisy

2. curl -s https://pkg.isy.io/script/update121.sh | sudo bash

Then I followed the instructions to reboot after the script completed, performing a

"sudo shutdown -r now" (script will tell you what to type, I am guessing from memory - may be different)

This appeared to be an alternative means of updating the Polisy and it fixed both issues

Can you expand on this for those of us not technical? 

I havent used an SSH program in a long long time... on a Mac and remote..any suggestions of how to to do this? 

What is CURL.. and what do I do with line 2 if I am able to figure out how to SSH into polisy? 

thanks. need to fix this as I rely on this new connected device and the dozen node servers...

@dbwarner5,

On Mac, it's quite easy:

ssh admin@the-ip-address-for-polisy (replace with the actual ip). The default pwd is admin.

Curl is a url content tool. Copy/paste line to and hit enter.

With kind regards,
Michel

should I not be using my own id / password? also I am remote so am going through a dyndns server with a port number attached via a colon.  have tried several combos w/o luck yet.. will keep trying,. 

 

Just now, dbwarner5 said:

should I not be using my own id / password? also I am remote so am going through a dyndns server with a port number attached via a colon.  have tried several combos w/o luck yet.. will keep trying,. 

 

If you're remote then you won't be able to SSH to the box unless you are port forwarding port 22 to the public internet or you have a VPN connection.

Just now, simplextech said:

If you're remote then you won't be able to SSH to the box unless you are port forwarding port 22 to the public internet or you have a VPN connection.

so I have port forwarding os I can connect to my polisy remotely generally.. is this different for SSH connection? I am using a different port than 22 for my polisy. 

In my case,

I was in my house, on a PC on the same LAN as the Polisy

I just opened an SSH session to the IP address of the Polisy

I had to use the default username: admin password: admin

 

Just now, dbwarner5 said:

so I have port forwarding os I can connect to my polisy remotely generally.. is this different for SSH connection? I am using a different port than 22 for my polisy. 

Disclaimer.  Port forwarding is BAD!!!!!!

Did you reconfigure SSH to use a port other than 22?  If not then it's still the default port of 22 for SSH.

no.. I havent changed anything.. using terminal on Mac remotely, with an address to my home router with port forwarding to the Polisy at port xxx... did get one time an error from terminal about nothin at port 22.. 

so if I am understanding you correctly, when I get to my router via SSH, it is automatically going to port 22 which is not where the polisy is at, and that is my problem.. if so, then how do I specify a port for ssh that matches where my polisy is at? 

thanks

Found a site as to how to do it in terminal.. will try that.. thanks

 

5 minutes ago, dbwarner5 said:

Found a site as to how to do it in terminal.. will try that.. thanks

 

not working.. or over my head... lol if I remotely change my port forwarding for polisy to 22, it should work then to get into it and update it and then change the port forwarding back to where the isy knows where it is? 

1 hour ago, Michel Kohanim said:

@dbwarner5,

On Mac, it's quite easy:

ssh admin@the-ip-address-for-polisy (replace with the actual ip). The default pwd is admin.

Curl is a url content tool. Copy/paste line to and hit enter.

With kind regards,
Michel

ok.. I am into polisy now.. have run the curl command, its loading the update.. what is the reboot command? do I need to do anything else? 

Update: script tells you how to reboot.. 12.2 successfully loaded.. thanks everyone!! hope it solves my issues

FINAL UPDATE: All working now!  thanks as usual for all the support!

Edited November 25, 20204 yr by dbwarner5
update

I just checked the Polisy again and the problem has resurfaced.  I checked all the obvious things - cleared browser cache, rebooted the Polisy, logged out, logged in,etc.  The strange thing is that I have not updated the Polisy since applying the SSH fix a few days ago.  Anyone else seeing the two issues again?

 

Edited November 30, 20204 yr by JTsao
add info