When attempting to disable DEBUG logging, we see the error:Error: Could not update logging settings using JBoss Client CLI connecting on port 9990
search cancel

When attempting to disable DEBUG logging, we see the error:Error: Could not update logging settings using JBoss Client CLI connecting on port 9990

book

Article ID: 221483

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

When attempting to disable DEBUG logging, we see the error:

Error: Could not update logging settings using JBoss Client CLI connecting on port 9990

https://api-broadcom-ca-user.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=svpbm8mi8l2buh3Xh4Vxug==

Environment

Release : 6.3.0

Component :

Resolution

You can disable DEBUG manually by updating the standalone.xml in the <install dir>/jboss/standalone/configuration/ directory.

 

1. Make a copy of the current file.

 

2. Edit the file and change DEBUG to INFO for the specific loggers you wish to change.

For example below are for the AlertGenerator, AlertDistributorImpl, AlertVendorImpl, JawsSendSnmpTrap, and JawsMibVars loggers.

 

 <logger category="com.termalabs.server.alerting.AlertGenerator">
                <level name="DEBUG"/>
            </logger>
            <logger category="com.termalabs.server.alerting.AlertDistributorImpl">
                <level name="DEBUG"/>
            </logger>
            <logger category="com.termalabs.server.cache.AlertVendorImpl">
                <level name="DEBUG"/>
            </logger>
            <logger category="com.termalabs.server.JawsSendSnmpTrap">
                <level name="DEBUG"/>
            </logger>
            <logger category="com.termalabs.server.JawsMibVars">
                <level name="DEBUG"/>

 

3. After making the changes you will need to restart the service for the logging to be set back to INFO.

 

4. Launch the configuration tool again and verify the logging is set back to INFO level.