All Nodes Display - Install Status

[Teken]

Just logged in moments ago to see the latest updates within the Polisy. I was shocked to find that all of the installed nodes show up as *Install*?!?! I was thinking maybe this is a web browser caching issue so logged out of the Polisy and hard cleared the web browser - no dice! Selected the *Refresh* nodes and had the same results so I'm out of ideas. 

Anyone else seeing the entire list of Node Servers indicating *Install* when existing nodes are deployed??

[markv58]

I have found a Polyglot locked on occasion with no apparent reason, it's very rare though. Never checked to see what the nodeserver store had to say about it but if it happens again I will be sure to check.

[Teken]

So apparently this problem is much bigger than what I expected and may be related to the ongoing development of the Virtual Node Server as seen here: 

I invoked the restart Polyglot and saw the customary messages this action was being processed - It wasn't. Followed this up with rebooting the Polisy and the same customary message of completing this action was displayed - It wasn't.

I know this because the customary reboot beep was never heard . . .

I had to hard boot the entire system remotely through my APC managed PDU.

So, once again this affirms and highlights the importance of having the ability to remotely hard reboot a piece of hardware over the network. This also brings to the forefront of not relying on any kind of soft boot feature. It doesn't matter what flavor of OS from Unix, Linux, Windows, BSD, etc they all locked up and the reboot command has no ability to reset the system. I know this is easy for me to simply say this but there really needs a solid plan where different processes are isolated and contained where it doesn't impact the OS of the hardware.

As of this writing the Polisy has 14 Node Servers installed as part of a long term Beta trial and aren't doing anything besides running. There are no active programs calling upon any of these node servers. Yet on the surface it appears one node server was able to brick the Polisy where there was no ability to do anything besides hard booting the appliance.

This is why any system should have a real heart beat that can be pushed / pulled to know the true state of high vs low processes of the system. 

[markv58]

Hard to say what caused the brick, Virtual isn't really doing that much, the Blue Iris ns is on a 2 second update and that must eat up some processing time. I have 12 on Polisy including PiCamMonitor which is running 4 clones and have yet to have Polisy brick. A couple of RPi have bricked but again it's a very rare thing for me.

[Michel Kohanim]

@Teken,

I suspect something is filling up the log. Can you please login through ssh and do:

df -h

and paste the output?

With kind regards,
Michel

[Teken]

17 hours ago, Michel Kohanim said:

@Teken,

I suspect something is filling up the log. Can you please login through ssh and do:

df -h

and paste the output?

With kind regards,
Michel

Sure, here are the results of the final output:

 

[Michel Kohanim]

@Teken,

Thank you. I stand corrected. Can you please send /var/polyglot/log/debug.log (you can use the SCP command) to support@universal-devices.com?

With kind regards,
Michel

[Teken]

3 hours ago, Michel Kohanim said:

@Teken,

Thank you. I stand corrected. Can you please send /var/polyglot/log/debug.log (you can use the SCP command) to support@universal-devices.com?

With kind regards,
Michel

Hi Michel,

What is the password admin / Admin / My created password? None of the three work to allow access via SCP.

[Michel Kohanim]

Hi Teken,

Default password (which you should have changed) is admin/admin. So, SCP admin@polisy:/var/polyglot/log/debug.log polyglot.debug.log (<- destination file). When prompted, type admin for password.

With kind regards,
Michel