General Troubleshooting

The PowerChute service does not start if m11.cfg file is missing

If the m11.cfg file is moved, renamed, or deleted, the PowerChute service cannot start. If the m11.bak file is present, PowerChute will restore the m11.cfg file using this backup file when the PowerChute service is started. However, you will need to start the PowerChute service again after the m11.cfg file is restored.

If both the m11.cfg and m11.bak files are not present, you must uninstall and reinstall PowerChute.

Administrator access is required on all operating systems to open and edit the m11.cfg file. Ensure that the m11.cfg file is not modified in any way.

Parallel UPS Configuration is not possible with Easy UPS

Several SRV UPS devices with capacities of 10 kVA and above can be configured into a parallel configuration through the use of external hardware, such as an SRV Parallel Board.

Network Management Card(s) deployed within this configuration cannot detect this parallel configuration. PowerChute, which relies on Network Management Card data, is also not capable of recognizing this configuration as a parallel UPS setup.

The PowerChute service does not start if invalid PowerChute credentials are provided before deploying the virtual appliance

When deploying the PowerChute virtual appliance, the Customize template page allows you to specify some settings for the virtual appliance before deployment. The PowerChute Username and PowerChute Password are both required fields.

The OVF Deployment Wizard only validates the length of the PowerChute Web UI username and password. If the password provided does not meet the password requirements, an error message is displayed in the virtual appliance Console stating that PowerChute services are disabled due to invalid credentials. To resolve this issue:

  1. Open the pcnsconfig.ini file using an ASCII text editor.
  2. In the [NetworkManagementCard] section of the INI file, set the following lines with your new valid values:

    username= new user name

    password= new password

  3. Save the pcnsconfig.ini file.
  4. Enable and start the PowerChute service using the following commands:

     systemctl enable PowerChute

     systemctl start PowerChute

Enabling the PowerChute service without providing a username or password via the pcnsconfig.ini file will start the service in an unconfigured state. This may result in denial of service if an untrusted user can access the PowerChute configuration wizard before credentials are set.