Search FAQs
How to put PowerChute Network Shutdown versions 3.1, 4.0, 4.1, or 4.2 into debug mode?
Issue:
Need to put PowerChute Network Shutdown version v3.1, v4.0, v4.1, v4.2 into debug mode.
Product:
PowerChute Network Shutdown v3.1, v4.0, v4.1, v4.2
Environment:
All supported OS
Cause:
Troubleshooting
Solution:
Windows
1. Stop the PowerChute service via the services console in Windows, or from a command prompt, type:
net stop PCNS1
2. Open [path to Program Files] \APC\PowerChute\group1
3. Create a backup of error.log by copying it to another directory on your PC and renaming it to error.log.backup
4. Create a backup of log4j.xml or log4j2.xml by copying it to another directory on your PC and renaming it to log4j.xml.backup or log4j2.xml.backup
5. Using a text editor, edit log4j.xml or log4j2.xml and change the line
Root level="error"
To
Root level="debug"
6. Restart the PowerChute service via the services console in Windows, or from a command prompt, type:
net start PCNS1
When PowerChute is restarted it will write debug information to error.log file.
When debugging is completed, stop the PowerChute service, copy the contents of log4j.xml.backup or log4j2.xml.backup into log4j.xml or log4j2.xml (to reset the values changed in step 5) and backup error.log by copying it to a new file naming it error-debug.log..
Restart the PowerChute service and review error-debug.log for errors. Contact Technical Support for more information on any errors present.
Linux/Unix
1. Stop the PowerChute daemon. In the command prompt, type:
service PowerChute stop or sudo service PowerChute stop
2. Navigate to: /opt/APC/PowerChute/group1
3. Create a backup of error.log by copying it to another directory and renaming it to error.log.backup
4. Create a backup of log4j.xml or log4j2.xml by copying it to another directory on your PC and renaming it to log4j.xml.backup or log4j2.xml.backup
5. Using a text editor, edit log4j.xml or log4j2.xml and change the line
Root level="error"
To
Root level="debug"
6. Restart the PowerChute daemon. In the command prompt, type:
service PowerChute start or sudo service PowerChute start
When PowerChute is restarted it will write debug information to error.log file.
When debugging is completed, stop the PowerChute daemon, copy the contents of log4j.xml.backup or log4j2.xml.backup into log4j.xml or log4j2.xml (to reset the values changed in step 5) and backup error.log by copying it to a new file naming it error-debug.log.
Restart the PowerChute daemon and review error-debug.log for errors. Contact Technical Support for more information on any errors present.
NOTE: PowerChute Network Shutdown v4.3+ is in debug mode by default.
Need to put PowerChute Network Shutdown version v3.1, v4.0, v4.1, v4.2 into debug mode.
Product:
PowerChute Network Shutdown v3.1, v4.0, v4.1, v4.2
Environment:
All supported OS
Cause:
Troubleshooting
Solution:
Windows
1. Stop the PowerChute service via the services console in Windows, or from a command prompt, type:
net stop PCNS1
2. Open [path to Program Files] \APC\PowerChute\group1
3. Create a backup of error.log by copying it to another directory on your PC and renaming it to error.log.backup
4. Create a backup of log4j.xml or log4j2.xml by copying it to another directory on your PC and renaming it to log4j.xml.backup or log4j2.xml.backup
5. Using a text editor, edit log4j.xml or log4j2.xml and change the line
Root level="error"
To
Root level="debug"
6. Restart the PowerChute service via the services console in Windows, or from a command prompt, type:
net start PCNS1
When PowerChute is restarted it will write debug information to error.log file.
When debugging is completed, stop the PowerChute service, copy the contents of log4j.xml.backup or log4j2.xml.backup into log4j.xml or log4j2.xml (to reset the values changed in step 5) and backup error.log by copying it to a new file naming it error-debug.log..
Restart the PowerChute service and review error-debug.log for errors. Contact Technical Support for more information on any errors present.
Linux/Unix
1. Stop the PowerChute daemon. In the command prompt, type:
service PowerChute stop or sudo service PowerChute stop
2. Navigate to: /opt/APC/PowerChute/group1
3. Create a backup of error.log by copying it to another directory and renaming it to error.log.backup
4. Create a backup of log4j.xml or log4j2.xml by copying it to another directory on your PC and renaming it to log4j.xml.backup or log4j2.xml.backup
5. Using a text editor, edit log4j.xml or log4j2.xml and change the line
Root level="error"
To
Root level="debug"
6. Restart the PowerChute daemon. In the command prompt, type:
service PowerChute start or sudo service PowerChute start
When PowerChute is restarted it will write debug information to error.log file.
When debugging is completed, stop the PowerChute daemon, copy the contents of log4j.xml.backup or log4j2.xml.backup into log4j.xml or log4j2.xml (to reset the values changed in step 5) and backup error.log by copying it to a new file naming it error-debug.log.
Restart the PowerChute daemon and review error-debug.log for errors. Contact Technical Support for more information on any errors present.
NOTE: PowerChute Network Shutdown v4.3+ is in debug mode by default.
Released for:APC United Kingdom
Explore more
Category:
Explore more
Category:
