| Bug #28192 | ??? | ||
|---|---|---|---|
| Submitted: | 2 May 2007 4:00 | Modified: | 8 Jun 2007 4:05 |
| Reporter: | fgbfvb gfbfsgbf | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.37-0 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
[2 May 2007 4:00]
fgbfvb gfbfsgbf
[2 May 2007 7:19]
Valeriy Kravchuk
Thank you for a problem report. What Linux distribution do you use? What exact RPM(s) you had installed (give URLs or full names)?
[3 May 2007 23:58]
fgbfvb gfbfsgbf
MySQL-client-community-5.0.37-0.rhel4.i386 - Red Hat Enterprise Linux 4 RPM (x86) Server 5.0.37.0 and i have installed Client 5.0.37.0
[3 May 2007 23:58]
fgbfvb gfbfsgbf
MySQL-client-community-5.0.37-0.rhel4.i386 - Red Hat Enterprise Linux 4 RPM (x86) Server 5.0.37.0 and i have installed Client 5.0.37.0 http://dev.mysql.com/downloads/mysql/5.0.html#linux-rhel4-x86-32bit-rpms
[4 May 2007 0:09]
fgbfvb gfbfsgbf
Error: [On Start up] Starting MySQL... etc/RC5.d/S64MySQL: Line 151 kill: (2209) Procedure could not be found. [On Shut down] Kill: Stoping MySQL... Manager or Server PID file could not be found. I'm using Fedora core 5
[8 May 2007 2:10]
fgbfvb gfbfsgbf
I suppose the main issue i'm having in fixing MySQL is:
- I looked at the error i'm getting on start up which points me to the file "etc/RC5.d/S64MySQL: Line 151". I've looked at that file and found the instruction which states # If you install MySQL on some other places than /, then you
# have to do one of the following things for this script to work:
And thats fair enough but all i did was run the RPM from the desktop. At no point did the RPM ask for me to specify any information, unlike other server RPM's i've installed in Linux. I do not know where the RPM has set the data directory or the any directory for that matter.
Was i supposed to run the RPM from a specific location maybe... ?
[8 May 2007 4:05]
Valeriy Kravchuk
Do you have SELinux enabled? Please, try to start MySQL server with mysqld_safe & command, and inform about the results.
[8 Jun 2007 23: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".
