OK I am running Fedora Core3, Kernel kernel-2.6.9-1.724_FC3 along with
MySQL-server 4.1.8-0.i386.
No matter what I do MySQL the process will not start.  This happens to me on
a couple of boxes.
One of the boxes which was upgraded from Fedora Core2 to Core3 does work
with the exact same versions of everything.
 
Here are the versions I installed via RPM:
-rw-r--r--  1 root root 3.1M Dec 23 10:03 MySQL-bench-4.1.8-0.i386.rpm
-rw-r--r--  1 root root 5.3M Dec 23 10:05 MySQL-client-4.1.8-0.i386.rpm
-rw-r--r--  1 root root 2.7M Dec 16 03:43 MySQL-devel-4.1.8-0.i386.rpm
-rw-r--r--  1 root root 2.7M Dec 16 03:43 MySQL-embedded-4.1.8-0.i386.rpm
-rw-r--r--  1 root root  15M Dec 23 10:23 MySQL-server-4.1.8-0.i386.rpm
-rw-r--r--  1 root root 1.1M Dec 16 03:43 MySQL-shared-4.1.8-0.i386.rpm
-rw-r--r--  1 root root 1.3M Dec 16 14:41
MySQL-shared-compat-4.1.8-0.i386.rpm
 
When I start mysql with /etc/rc.d/init.d/mysql start I don't get the typical
OK, and the mysql log shows this:
/usr/sbin/mysqld, Version: 4.1.8-standard-log. started with:
Tcp port: 3306  Unix socket: /var/lib/mysql/mysql.sock
Time                 Id Command    Argument
 
Making it look like everything is OK.  Nothing is in /var/log/messages.
 
I have read several posts on the web and found similar issues with no
resolve.
I have seen people try to run mysqld but of course get a security issue
because it's not supposed to run as root, and that seems to be a popular
problem which is not really the heart of the issue.
 
When I su mysql and run mysqld I get this:
050107 14:09:12 [Warning] Asked for 196608 thread stack, but got 126976
mysqld: Can't create/write to file '/tmp/ib5ArcLz' (Errcode: 13)
050107 14:09:12  InnoDB: Error: unable to create temporary file; errno: 13
050107 14:09:12 [ERROR] Can't init databases
050107 14:09:12 [ERROR] Aborting
 
050107 14:09:12 [Note] mysqld: Shutdown complete
 
 
I hope this helps as I have already created a flat spot on my head from
banging it against the wall, and look forward to a more relaxing weekend.
Any help appreciated...
 
Joey
 
 

Reply via email to