| Bug #26879 | server install does not create debugtrace although specified on commandline | ||
|---|---|---|---|
| Submitted: | 6 Mar 2007 15:57 | Modified: | 12 Mar 2007 22:27 |
| Reporter: | Carsten Segieth | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Installing | Severity: | S3 (Non-critical) |
| Version: | 1.1.0.4876 | OS: | Linux (RH4) |
| Assigned to: | Carsten Segieth | CPU Architecture: | Any |
[7 Mar 2007 11:21]
BitRock Merlin
Hi Carsten, Could it be possible that you tried creating a debug trace file by running the installer and cancelling it by pressing CTRL+C. A debug trace will only be created when an error occurred, on successful installation or when the user clicks "Cancel" in GUI mode. It does not matter whether the given path is absolute or relative. If only a filename is given, the debug trace file will be created in the current directory. Please let us know if that is the case, if not we will continue investigating.
Description: using the command line /users/schilders/public_html/official_builds/official/archive/1.1.0.4876/service-manager/mysqlnetwork-1.1.0.4876-linux-installer.bin --debugtrace 1.1.0.4876_debug.trace no debug trace is created in current directory. Also using a different filename does not change the behaviour. Using ..INSTALLER.. --debugtrace /opt/mysql/network/${VERS}_debug.txt a file was created. How to repeat: see above Suggested fix: create trace file even if only a file name is given (= preferred!) or change help if a full path is needed.