Bug #39797 Permissions issue when installing from a directory with no write permission
Submitted: 1 Oct 2008 23:57 Modified: 28 Feb 2009 15:56
Reporter: Jonathon Coombes Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version:2.0.0.7049 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[1 Oct 2008 23:57] Jonathon Coombes
Description:
[user@host ~]$ sudo -u mysql /tmp/mysqlmonitoragent-2.0.0.7049-linux-glibc2.3-x86-64bit-installer.bin
Language Selection
 ....

----------------------------------------------------------------------------
Please wait while Setup installs MySQL Enteprise Monitor Agent on your computer.

Installing
0% ______________ 50% ______________ 100%
########################################
Error: There has been an error. A debug file has been created at:

/tmp/bitrock_debug_9130.xml

Please attach it to any bug report.
The application will exit now
Press [Enter] to continue :

The users home directory is where the command is run and because it is running sudo mysql, the mysql user does not have permission to write into the home directory.

How to repeat:
Run the installer from an directory which the installing user does not have permission to write. In this example it is the users home directory and because it is running sudo mysql, the mysql user does not have permission to write.

Suggested fix:
A simple workaround is to run it from a directory that the mysql user is able to write such as /tmp.
[2 Oct 2008 0:01] MySQL Verification Team
The main problem for the user is that instead of giving the appropriate permissions error, it gives a error dump for analysis and fails.
[3 Oct 2008 13:55] Keith Russell
Patch applied in versions => 2.0.0.7069.
[1 Mar 2009 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[18 Aug 2009 22:27] Andrii Nikitin
see also bug #42584 (and associated issues)