A bit more technical than my usual posting and most definitely over my own head. But, there will be those of you out there (if not now, soon) who will face this very problem:
I just upgraded all three of my Tiger Server boxes to 10.4.5 from 10.4.3.
All but one of them made the transition beautifully. The problem child has JBoss and MySQL driving a vertical search site pushing over 800,000 documents. Well, after reving to 10.4.5 this server decided to no longer respond as before. So, for those of of you out there who have yet to bite the bullet and go to 10.4.5 (or for those who are researching what has gone wrong after your upgrade) here’s what got me out of the weeds. A VERY SPECIAL THANKS TO MY MIRACLE WORKER – FRED TOTH! Who loves ya baby!?
Ok, so after your upgrade, jboss was reporting
“can’t connect…”, and “connection refused” when it tried to
talk to mysql.
mysql command line connections worked fine.
The java connection information (within the jboss config) looks like
Note that this specfies a TCP/IP connection to localhost, port 3306. Manually
testing that port also yielded “connection refused”.
However, on the dev system, I can connect to port 3306 with no problem.
I noticed in the process table that mysqld was running with “–skip-networking”.
That didn’t sound right! Documentation says “don’t listen to network ports at all”.
Again, the dev server did not have “–skip networking”.
So somehow the upgrade changed the mysqld startup options.
Finally, and partly by luck, I found the file “/etc/mysqlManager.plist”. It was timestamped
today and contained:
Changing the “no” to “yes” and rebooting (because I don’t know how to start/stop
mysqld) cured the problem.
This indeed, fixed the problem and all is well in my world again. And, I sincerely hope it serves to help some poor schmo out there wondering how he’s going to fare when his boss invariably delivers the evil eye. Never fear. Solution is here!