Home › Forums › OS X Server and Client Discussion › Web › 10.4.8 and MySQL
- This topic has 5 replies, 4 voices, and was last updated 18 years, 6 months ago by
ElgertS.
-
AuthorPosts
-
September 30, 2006 at 1:28 pm #367161
ElgertS
ParticipantI just tried the 10.4.8 Server update on a server using MySQL 5, not the Apple MySQL installation that ships with the server. On reboot I could no longer connect to MySQL. Anyone know what Apple has changed in this regard with the latest release?
October 3, 2006 at 2:21 am #367180Waipouli
ParticipantDid you ever get a fix? I have a 10.4.7 server running 5.0.22 i’d like to upgrade to 10.4.8.
Thanks,
CoryOctober 3, 2006 at 11:46 pm #367186nerdtech
ParticipantWe ran into this exact same issue today – except with Mac OS X 10.4.8 client… I’ve been banging my head on my desk all day…
What error messages are you seeing? We’re seeming to be getting a strange UTF-8 related one. This is an installation of the latest official MySQL package for Mac OS X 10.4, 32-bit. We saw problems immediately after upgrading to 10.4.8 [repairing permissions before and after updating to 10.4.8]. We can’t even strip out MySQL and re-install it successfully. It still breaks.
Thanks in advance.
October 6, 2006 at 1:26 pm #367205zonko
ParticipantHello,
Has anyone managed to resolve this problem? We’re running OS X Server, and using the distribution of MySQL that comes with the system (4.1.13a). We updated to 10.4.8 yesterday, and now MySQL won’t start. The most helpful message we’ve found is in /var/mysql/
.err. It simply says “The Database could not be initialized”. Any suggestions? Thanks,
Kevin Graham
OIT Student Computing Services
Princeton UniversityOctober 6, 2006 at 8:18 pm #367212zonko
ParticipantHello,
I’m Kevin Graham, who posted earlier- I signed up for an account.
We managed to fix this problem by moving the /var/mysql/ib_logfile0 and ib_logfile1 files to a different location. We came up with this fix after discovering these entries in /var/mysql/servername.princeton.edu.err:
## here’s the previous successful shutdown/startup cycle
060928 6:18:12 InnoDB: Starting shutdown…
060928 6:18:17 InnoDB: Shutdown completed; log sequence number 0 268782
060928 6:18:17 [Note] /usr/libexec/mysqld: Shutdown complete060928 06:19:04 mysqld started
060928 6:19:04 [Warning] Setting lower_case_table_names=2 because file system for /var/mysql/ is case insensitive
060928 6:19:11 InnoDB: Started; log sequence number 0 268782
/usr/libexec/mysqld: ready for connections.
Version: ‘4.1.13a-log’ socket: ‘/var/mysql/mysql.sock’ port: 3306 Source distribution## We applied the 10.4.8 patch here, and it rebooted the system
061005 11:23:05 [Note] /usr/libexec/mysqld: Normal shutdown
061005 11:23:14 InnoDB: Starting shutdown…
061005 11:23:27 InnoDB: Shutdown completed; log sequence number 0 268837
061005 11:23:27 [Note] /usr/libexec/mysqld: Shutdown complete
061005 11:23:29 mysqld ended
****
061005 11:24:25 mysqld started
061005 11:24:25 [Warning] Setting lower_case_table_names=2 because file system for /var/mysql/ is case insensitive
061005 11:34:34 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
061005 11:34:34 [ERROR] Can’t init databases
061005 11:34:34 [ERROR] Aborting
061005 11:34:35 [Note] /usr/libexec/mysqld: Shutdown complete
061005 11:34:35 mysqld ended061005 12:47:02 mysqld started
061005 12:47:03 [Warning] Setting lower_case_table_names=2 because file system for /var/mysql/ is case insensitive
InnoDB: Error: log file ./ib_logfile1 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
061005 12:47:04 [ERROR] Can’t init databases
061005 12:47:04 [ERROR] AbortingSo first it complained because ib_logfile1 didn’t exist, but apparently it tried to create it. Then the next time it tried to start, it didn’t like the fact that it was 0 bytes. Once we got rid of both “ib_logfileX” files, it started happliy.
I hope that’s helpful to others.
October 21, 2006 at 12:00 am #367358ElgertS
ParticipantIn our case it was that the ownership for /var/mysql had changed to root. Changing it back to mysql fixed the problem.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed