[mythtv-users] Upgrade to 2.6.17-gentoo-r2/ivtv-0.7.0/mythtv-0.19_p9163-r1 and having problems

Mark Knecht markknecht at gmail.com
Sun Jul 16 20:40:12 UTC 2006


On 7/16/06, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> On 07/16/06 15:29, Mark Knecht wrote:
>
> >On 7/16/06, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> >
> >
> >>On 07/16/06 14:28, Mark Knecht wrote:
> >>
> >>>dragonfly ~ # mysql -u root mythconverg
> >>>ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> >>>'/var/run/mysqld/mysqld.sock' (111)
> >>>
> >>>
> >>Do you have the --skip-networking option in your commandline or in your
> >>MySQL configuration file?
> >>
> >I assume this is not a mysql permissions issue since I need to connect
> >to change permissions?
> >
> >skip-networking is commented out in both /etc/conf.d/mysql and
> >/etc/mysql/my.cnf
> >
>
> So, does the file /var/run/mysqld/mysqld.sock exist?  If not, make sure
> the user who's running mysqld has permissions to write to it and then
> restart mysql.
>
> Mike

The process is apparently owned by root:

dragonfly conf.d # ps aux | grep mysqld
root      8814  0.0  0.0   1564   488 pts/0    S+   13:38   0:00 grep mysqld
dragonfly conf.d #

The file does exist and continues to exist when mysql is stopped. I am
getting an error message on another file (mysqld:pid) which I filed a
bug report on Gentoo's site:

dragonfly conf.d # ls -al /var/run/mysqld/
total 8
drwxr-xr-x 2 mysql mysql 4096 Jul 16 13:05 .
drwxr-xr-x 6 root  root  4096 Jul 16 13:05 ..
srwxrwxrwx 1 mysql mysql    0 Jul 16 13:05 mysqld.sock
dragonfly conf.d # /etc/init.d/mysql stop
 * Stopping mysql ...
/etc/init.d/mysql: line 332: /var/run/mysqld/mysqld.pid: No such file
or directory
 * Stopping mysqld (0)
                            [ ok ]
dragonfly conf.d # ls -al /var/run/mysqld/
total 8
drwxr-xr-x 2 mysql mysql 4096 Jul 16 13:05 .
drwxr-xr-x 6 root  root  4096 Jul 16 13:32 ..
srwxrwxrwx 1 mysql mysql    0 Jul 16 13:05 mysqld.sock
dragonfly conf.d #

When I try to restart mysql I get a warning about the file already
existing. If I stop mysql, remove this file by hand, and then start
mysql I do not get the warning.

I'm curious as to whether the error when stopping was a mistake where
they should have removed this file but typed the wrong name in the
script? From /etc/init.d/mysql, which is very Gentoo specific and
Greek to me:

<SNIP>

        ebegin "Stopping ${myservice}"
        for shutdown_elem in ${shutdown_list} ; do
                runwhat=${shutdown_elem%%=*}
                pidfile=${shutdown_elem#*=}
                timeout=${STOPTIMEOUT:-"120"}
                PID=$(< "${pidfile}" )
                wdebug 3 "runwhat            ${runwhat}"
                wdebug 3 "pidfile            ${pidfile}"
                wdebug 3 "timeout            ${timeout}"
                wdebug 3 "PID                ${PID}"

                einfo "Stopping mysqld (${runwhat})"
<SNIP>

- Mark


More information about the mythtv-users mailing list