Submitting VMM Bug Reports

rated by 0 users
This post has 0 Replies | 0 Followers

Top 10 Contributor
Male
Points 116
Hyper9 Employee
Schley Andrew Kutz Posted: Thu, May 14 2009 9:37 AM | Locked

I would love to pretend that VMM is bug-free, but the fact is that there are probably a few lurking around. If you do run into a bug, here is how to notify me about it.

1. Ensure that DEBUG is turned on for the VMM log settings. This is configured in the vmm.properties file (in the conf directory). For example:

# log4j loggers
log4j.logger.com.hyper9.vmm.server=DEBUG, console
log4j.appender.console=org.apache.log4j.ConsoleAppender 
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=[%p] "%d{yyyy-MM-dd HH:mm:ss:SSS}" %m%n

log4j.logger.com.hyper9.vmm.server=DEBUG, vmmlog
log4j.appender.vmmlog=org.apache.log4j.RollingFileAppender
log4j.appender.vmmlog.File=/tmp/vmm-server.log
log4j.appender.vmmlog.MaxFileSize=100KB 
log4j.appender.vmmlog.layout=org.apache.log4j.PatternLayout
log4j.appender.vmmlog.layout.ConversionPattern=[%p] "%d{yyyy-MM-dd HH:mm:ss:SSS}" %m%n

Notice that the value for log4j.logger.com.hyper9.vmm.server is set to DEBUG.

2. Reproduce the bug (if you can).

3. Compress the VMM logs directory and the VMM server log (configured in the vmm.properties file). The important files are the catalina log files, the localhost log files, and the vmm-server.log file (or whatever you name it).

4. Create a new forum post under the Hyper9 VMM forums.

5. Describe the problem you are experiencing in the post and attach the log bundle to the post.

6. Be sure to mark the post as a question so we can mark it as answered :)

That's it! I've had some users in the past take the trouble to scrub their log files clean of what the think are encrypted passwords. For example:
[DEBUG] "2009-05-13 11:40:37:045" 127.0.0.1 "Administrator" HyperV evaqzjzxik8l 20090513114036926 compareServerObjects "vm02" "powerState is still ON"
[DEBUG] "2009-05-13 11:40:37:046" 127.0.0.1 "Administrator" HyperV evaqzjzxik8l 20090513114036926 compareServerObjects "vm02" "rSO has property perms=62"
[DEBUG] "2009-05-13 11:40:37:046" 127.0.0.1 "Administrator" HyperV evaqzjzxik8l 20090513114036926 compareServerObjects "vm02" "lSO has property perms=62"
[DEBUG] "2009-05-13 11:40:37:046" 127.0.0.1 "Administrator" HyperV evaqzjzxik8l 20090513114036926 compareServerObjects "vm02" "perms is still 62"
The fields "evaqzjzxik8l" and "20090513114036926" are the session ID and the transaction ID, neither of which have anything to do with the password. The session ID is also NOT the JSESSIONID, rather it is a randomly generated value that is used to ensure the security of RPC calls.

 

Page 1 of 1 (1 items) | RSS