Red Hat Bugzilla – Bug 948744
Some java exceptions are not logged to the log file
Last modified: 2016-02-10 14:40:46 EST
Description of problem: Some java exceptions are not logged and it prevents people from proper troubleshooting Version-Release number of selected component (if applicable): rhevm-3.1.0-43 How reproducible: Always for specific issues line adding new LUN to an existing storage domain. See the additional information. Steps to Reproduce: Actual results: No java stack trace is logged Expected results: We see the stack trace Additional info: 55434 2013-04-04 10:22:40,170 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand] (http-/0.0.0.0:8443-7) Failed in GetDeviceListVDS method, for vds: rhvdes1; host: 192.168.136.43 55435 2013-04-04 10:22:40,170 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (http-/0.0.0.0:8443-7) Command GetDeviceListVDS execution failed. Exception: NullPointerException: 55436 2013-04-04 10:22:40,170 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (http-/0.0.0.0:8443-7) FINISH, GetDeviceListVDSCommand, log id: 3ea4c6d1 55437 2013-04-04 10:22:40,170 ERROR [org.ovirt.engine.core.bll.GetLunsByVgIdQuery] (http-/0.0.0.0:8443-7) Query GetLunsByVgIdQuery failed. Exception message is VdcBLLException: java.lang.NullPointerException
Failed to SnapshotVDS, error = Unexpected exception 2013-07-18 09:13:53,509 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand] (pool-5-thread-50) Detailed stacktrace:: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to SnapshotVDS, error = Unexpected exception at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createDefaultConcreteException(VdsBrokerCommand.java:61) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.createException(BrokerCommandBase.java:199) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.ProceedProxyReturnValue(BrokerCommandBase.java:185) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand.ExecuteVdsBrokerCommand(SnapshotVDSCommand.java:25) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:96) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:56) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:28) [dal.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:359) [vdsbroker.jar:] at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:1695) [bll.jar:] at org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand$3.runInTransaction(CreateAllSnapshotsFromVmCommand.java:322) [bll.jar:] at org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand$3.runInTransaction(CreateAllSnapshotsFromVmCommand.java:317) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:174) [utils.jar:] and it goes on and on...
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html