Bug #60721 | problem with mysql installation on linux.x64 | ||
---|---|---|---|
Submitted: | 1 Apr 2011 10:16 | Modified: | 24 Oct 2012 23:56 |
Reporter: | sowmya srinivasa | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S3 (Non-critical) |
Version: | 5.1.56 | OS: | Linux (installation fails) |
Assigned to: | CPU Architecture: | Any | |
Tags: | installation fails |
[1 Apr 2011 10:16]
sowmya srinivasa
[1 Apr 2011 10:22]
Valeriy Kravchuk
Please, send the output of: uname -a ls -l /var/lib/mysql Linux commands. Did you have any previous version of MySQL server installed on this system?
[1 Apr 2011 17:44]
sowmya srinivasa
Hi Valeriy, Here is the output requested. And yes, there was a mysql Db installedd before and i removed it using rpm -e command. sh-3.2# uname -a Linux adc6160580 2.6.18-164.0.0.0.1.el5xen #1 SMP Thu Sep 3 00:34:43 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux sh-3.2# ls -l /var/lib/mysql total 20548 -rw-rw---- 1 mysql mysql 10485760 Jan 4 02:08 ibdata1 -rw-rw---- 1 mysql mysql 5242880 Jan 4 02:08 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 Jan 4 02:08 ib_logfile1 drwx------ 2 mysql mysql 4096 Jan 4 23:52 master drwx------ 2 mysql mysql 4096 Apr 1 02:45 mysql srwxrwxrwx 1 mysql mysql 0 Jan 4 02:08 mysql.sock drwx------ 2 mysql mysql 12288 Jan 5 00:56 oratst -rw-r--r-- 1 mysql mysql 646 Apr 1 03:11 RPM_UPGRADE_HISTORY drwx------ 2 mysql mysql 4096 Jan 4 02:08 test sh-3.2# sh-3.2# sh-3.2# Thanks, Sowmya.
[3 Apr 2011 11:46]
Valeriy Kravchuk
You had removed binaries, but not datadir or my.cnf it seems. So, it looks like there is a problem with some of settings in my.cnf remained from the previous installation. Please, send the output of: find / -name my.cnf 2>/dev/null find / -name .my.cnf 2>/dev/null
[5 Apr 2011 9:00]
sowmya srinivasa
H, Output of the find command hangs. Its been 4 hours since I gave the command and I am still waiting for the output. Is there any work around for this? Thanks, Sowmya.
[5 Apr 2011 9:18]
Valeriy Kravchuk
Let's search in usual places. Kill your find command and try these: find /usr -name my.cnf 2>/dev/null find /etc -name my.cnf 2>/dev/null find /home -name .my.cnf 2>/dev/null
[6 Apr 2011 4:58]
sowmya srinivasa
Hi Valeriy, I did execute the commands what you told me to. The first two commands dint write anything to the file. But the command find /home -name .my.cnf 2>/tmp/null (used /tmp/null dir as /dev/null was saying its not a file when I opened it) gave the following output find: /home/sosriniv/.mozilla/sowmya: Permission denied find: /home/sosriniv/.mozilla/firefox: Permission denied find: /home/sosriniv/.mozilla/extensions: Permission denied find: /home/sosriniv/.mozilla/Default User: Permission denied find: /home/sosriniv/.autosave: Permission denied find: /home/sosriniv/.gnome/accels: Permission denied find: /home/sosriniv/.gnome/nautilus-scripts: Permission denied find: /home/sosriniv/.gnome/mime-info: Permission denied find: /home/sosriniv/.gnome2/keyrings: Permission denied find: /home/sosriniv/.gnome2/nautilus-scripts: Permission denied find: /home/sosriniv/.gnome2/panel2.d: Permission denied find: /home/sosriniv/.gnome2/file-roller: Permission denied find: /home/sosriniv/.gnome2_private: Permission denied find: /home/sosriniv/.gconf/apps: Permission denied find: /home/sosriniv/.gconf/system: Permission denied find: /home/sosriniv/oradiag_sosriniv/diag/clients/user_sosriniv/host_3574514837_80/incident/incdir_1: Permission denied find: /home/sosriniv/.sunw: Permission denied find: /home/sosriniv/.elinks: Permission denied find: /home/sosriniv/.java/.userPrefs: Permission denied find: /home/sosriniv/.kde/Autostart: Permission denied find: /home/sosriniv/.kde/share/fonts: Permission denied find: /home/sosriniv/.kde/share/apps: Permission denied find: /home/sosriniv/.kde/share/mimelnk: Permission denied find: /home/sosriniv/.kde/share/services: Permission denied find: Filesystem loop detected; `/home/sosriniv/.snapshot/nightly.0' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: Filesystem loop detected; `/home/sosriniv/.snapshot/nightly.1' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: Filesystem loop detected; `/home/sosriniv/.snapshot/nightly.2' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: Filesystem loop detected; `/home/sosriniv/.snapshot/nightly.3' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: Filesystem loop detected; `/home/sosriniv/.snapshot/nightly.4' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: Filesystem loop detected; `/home/sosriniv/.snapshot/nightly.5' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: Filesystem loop detected; `/home/sosriniv/.snapshot/weekly.0' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: Filesystem loop detected; `/home/sosriniv/.snapshot/weekly.1' has the same device number and inode as a directory which is 2 levels higher in the filesystem hierarchy. find: /home/sosriniv/.gnome_private: Permission denied find: /home/sosriniv/.metacity: Permission denied find: /home/sosriniv/.Trash: Permission denied find: /home/sosriniv/.dbus: Permission denied Thanks, Sowmya.
[12 Apr 2011 4:29]
sowmya srinivasa
Hi, I am not seeing any update now on this bug. Can you please take a look at this? Thanks, Sowmya.
[28 Jun 2012 13:05]
shalini P S
even i am also facing the same issue please tell how to come across
[24 Sep 2012 23:56]
MySQL Verification Team
Please check if the same issue than the bug: http://bugs.mysql.com/bug.php?id=66919 ?. Thanks.
[25 Oct 2012 1: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".