MYSQL errors after upgrade to latest CURRENT version

mydomain

Well-Known Member
Aug 10, 2003
138
0
166
We are getting mySQL errors all over the place for customers' mysql databases after upgrading to the latest current version. Errors similar to:

Invalid SQL: Can't create/write to file '/tmp/#sql_69a9_0.MYI' (Errcode: 13)

Invalid SQL: Can't open file: 'asFaqQuestions.MYI'. (errno: 144)

Any ideas or assistance with this? We did notice some errors during hte /scripts/upcp process when it was wget'ing certain mySQL files - maybe these are incomplete on the server - is there a way to remove them and run /scripts/upcp again to download required tarballs again?
 

Rubas

Well-Known Member
Sep 15, 2003
125
0
166
Did you tried /scripts/upcp --force
I'm not sure if it reload also the mysql binaries ...

I had no problem with the mysql update so far.
 

mydomain

Well-Known Member
Aug 10, 2003
138
0
166
mysql.sock went missing and one point and PID file was also lost - resolved that by resetting the mysql root password etc.

As the errors referenced writing to /tmp I found out also that for some reason /tmp had lost its 1777 permissions - chmodded it back and no more errors.

The databases appear to be fine, no corruptions from what i can see...
 

jrehmer

Well-Known Member
Apr 10, 2003
286
0
166
Denver, CO
mydomain said:
mysql.sock went missing and one point and PID file was also lost - resolved that by resetting the mysql root password etc.

As the errors referenced writing to /tmp I found out also that for some reason /tmp had lost its 1777 permissions - chmodded it back and no more errors.

The databases appear to be fine, no corruptions from what i can see...
That didn't work for me I still have:

Code:
041031 11:15:45  mysqld started
041031 11:15:45 Warning: Asked for 196608 thread stack, but got 126976
/usr/sbin/mysqld: Can't create/write to file '/tmp/ibCimikU' (Errcode: 13)
041031 11:15:45  InnoDB: Error: unable to create temporary file; errno: 13
041031 11:15:45 Can't init databases
041031 11:15:45 Aborting

041031 11:15:45  InnoDB: Warning: shutting down a not properly started
                 InnoDB: or created database!
041031 11:15:45 /usr/sbin/mysqld: Shutdown Complete

041031 11:15:45  mysqld ended
NOTE: This is only on REBOOT, when i do a service mysql start it will start without the file permission error. I think this has SOMETHING to do with SECURETMP environments on startup......
 
Last edited: