Discover our Clipsal Smart Home packages as seen on The Block 2018

in location

OR

I'm looking for

  • Wholesalers
    • Uncheck All Check All
  • EXPERTISE
    • Expand
    • Expand
    • Expand
    • Uncheck All Check All
  • Switchboard Manufacturers
    • Uncheck All Check All
OR

The best way to see what Clipsal electric products can do for your home is seeing them in action at a Clipsal Display Centre.

Product stock may vary according to location. If you're after a specific product range, please check with your chosen location before visiting.

10 Results
    Load More Load Complete
    Change Location

    How to put PowerChute Network Shutdown version 3.1 and above into debug mode?

    Issue:
    Need to put PowerChute Network Shutdown version 3.1 and above into debug mode.

    Product:
    PowerChute Network Shutdown version 3.1 and above

    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.


     

    Didn’t find what you were looking for?

    Try Searching Again View Our Categories

    Need further assistance?

    Our Customer Care department provides total customer service solutions for our residential, industrial and commercial applications.

    Get Assistance