Posted: 2023-02-02 10:50 AM . Last Modified: 2023-02-02 10:54 AM
I am running PCNS 4.4.3 VMWare Appliance.
I am running it on a VMWare ESXI 8.0 Host.
I am aware that in the PCNS Manual it says that it isnt officially supported on anything higher than VMWare ESXI 7.0, but we already had ESXI 8.0 with new servers in place, before buying the APC UPS, so I have run the PCNS VM Appliance up on it anyway, as I didn't have much choice.
It is actually working fine on the ESXI 8.0, the only issue I have is that in the Event Log I get the following error message:
ERROR: The ini file is missing shutdownCommandFile key from section Shutdown
I am aware that it is a known issue in the release notes and I have added the "shutdownCommandFile =" to the shutdown section of pcnsconfig.ini.
Now when I add the line into the ini file and reboot the VM, the error message no longer appears in the Event Log.
However what has been happening, is that for some unknown reason, the "shutdownCommandFile = " line that I add gets removed/deleted from the pcnsconfig.ini by itself at some unknown point, whilst the PCNS VM Appliance is running, and then when the VM is restarted again, the error msg reappears in the Event Log again.
I have tried adding the "shutdownCommandFile =" line to both the pcnsconfig.ini and the pcnsconfig_backup.ini, but the same happens to both files and the "shutdownCommandFile =" is removed/deleted from both files at some unknown point, and the error msg reappears in the Event Log whenever the VM is restarted.
Whilst the PCNS VM Appliance is continually running and never shutdown/restarted, after adding in the "shutdownCommandFile =" line and starting it backup, the Error msg doesn't appear in the log.
Once restarted the error msg returns and when I check the "shutdownCommandFile =" is gone from the pcnsconfig & backup ini files.
I have also stopped the PowerChute service after the VM appliance has been running for a while, with no error msg in the Event Log and have checked the pcnsconfig & backup files and the "shutdownCommandFile =" is gone.
Does anyone know what is causing this line to be removed/deleted from the ini files on its own, as having to continually add it back in every time I restart the VM appliance is just frustrating?
Posted: 2023-02-08 09:54 AM
There are a few reasons why the error will be posted. We are looking at providing a fix in a future release.
NOTE: The error can be ignored as it is just a nuisance.
The possible causes are:
Posted: 2023-02-09 12:10 PM . Last Modified: 2023-02-09 12:12 PM
Thanks for your reply.
However I haven't done any of the four things you have listed.
I add the shtudownCommandFile = line to the ini file, save it and reboot as per the Readme Release Notes for PCNS, that mentions to do that if you get the Error message in the Event Log.
After restarting the PCNS VM. the error is gone.
Then at some unknown point, without changing a single thing in PCNS interface, the "shutdownCommandFile =" line just gets removed from the ini all by itself.
Definitely a bug of some sort and PCNS must be doing something on its own that changes the ini file and deletes the line.
Posted: 2023-02-12 11:21 AM . Last Modified: 2023-02-12 11:22 AM
As the "shutdownCommandFIle =" line just keeps getting removed from the ini file by itself, and the error msg in the Event Log was just annoying, a workaround I came up with, was to create a blank script file and put that path in the Run Command section of Shut Down settings in the PCNS interface.
This then adds the "shutdownCommandFile=" line into the ini with the path and filename, and then as it has a path and filename and is not just an equal sign with nothing after it, it no longer is being removed from the ini file and the Error no longer appears in the Event Log when restarting the PCNS VM Appliance.
As the script file is blank and does nothing, since I wasn't using a Command file on shutdown anyway, it doesn't do anything and has no affect on shutdown operation in the event of a power failure.
This workaround will do until APC fix the bug in PCNS for VMWare. Hope this helps anyone else having the same issue..