That's odd. My mysql.sock is chmod 777, which happened automatically. Check the startup script. Is it calling mysqld_safe? Are you using the regular startup script that came with mysql, or have you mucked with it?
Make sure when you chmod that the file is still a socket. Shouldn't be a problem. I don't really have much to add. a quick google search on "mysql.sock permissions" shows this bug: http://bugs.mysql.com/bug.php?id=11380 did you also upgrade mysql when you did the OS upgrade ? If so, backup your stuff and run mysql_install_db. That's the only suggestion I have, other than doing a google search as I did and look at more than the first 2 results (which was what I did to find that bug). -Sheeri On 2/19/06, Norman Walsh <[EMAIL PROTECTED]> wrote: > A couple of days ago, I decided to be brave (or crazy :-) and upgrade > my Ubuntu "Breezy" install to "Dapper". It was really remarkably > uneventful, I've just got a couple of rough edges to sort out. > > One is that dspam (3.4.9 built by me some months ago) can no longer > connect to mysql when I reboot the machine. The problem appears to be > permissions related. On boot, /var/run/mysqld is owned by mysql and in > the root group with 770 permissions. That means that dspam can't open > /var/run/mysqld/mysqld.sock to connect to the database. > > I've been fixing the problem with > > chgrp mysql /var/run/mysqld > chmod 775 /var/run/mysqld > > but (1) is that the safe and correct thing to do and (2) if it is, how > can I get mysql to do that by default when it starts? > > Be seeing you, > norm > > -- > Norman Walsh <[EMAIL PROTECTED]> | We have fewer friends than we imagine, > http://nwalsh.com/ | but more than we know.--Hugo Von > | Hofmannsthal > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
