@automationgeek, I did the 3.1.8 PG3 upgrade today.  All of my NSs started except the August Lock NS.  It will not start and is not producing a log file so I can't provide any more information.  I've tried deleting it and re-installing but no luck.  Is anyone else experiencing this?

Thanks in advance for any suggestions.

When node servers don't start, the PG3 log will have more information on why they don't start. 

We just discovered an issue today where if a node server was installed during the early alpha test time frame (before there were multiple node server stores) it can now fail to start because it's missing information in the local database records telling PG3 what node server store it was originally installed from.  That's the working theory anyway.

If the PG3 log shows a failure with auto update, then it's the same problem.

I'm not sure how best to handle this.

1) it's not hard for me to add a check for this condition in PG3 and then assume the node server was installed from the production store.  However, there have been other similar changes so it may just fail later because some other piece of info is missing from the database.

2) you can try simply re-installing the node server.  With this version of PG3 you can simply click the "install" button in the store for this node server and you will have the option to re-install it to the same slot.  This will download the latest version of the node server and update everything.  The downside is that it will put the configuration parameters back to the default settings so you have to re-configure the node server.  But nothing on the ISY/IoP side will change so programs remain intact.  

Thanks @bpwwer, Here is a bit of the PG3 Log.  The only error I can see is:

9/19/2022, 17:05:07 [pg3] error: [August(10)] :: STDERR: python3: can't open file '/var/polyglot/pg3/ns/000db9561078_10/./august_poly.py': [Errno 2] No such file or directory

I already tried to re-install but no improvement.  Log attached

 

August NS restart.txt

@tmorse305If you refresh the store and try re-installing it should work now.   

@bpwwer, thank you!  Re-install was successful.