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

[Paul Barker]

Mark Knecht wrote:
>
>
> 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 #
>   
Hmm, that output says to me no mysqld process is running. The grep is 
matching your grep process and not a mysqld process.

This is my out put ( from an FC5 box)

paul at gryffindor recordings]$ ps aux | grep mysqld
root      2248  0.0  0.1   4448   588 ?        S    Jun29   0:00 /bin/sh 
/usr/bin/mysqld_safe --defaults-file=/etc/my.cnf 
--pid-file=/var/run/mysqld/mysqld.pid --log-error=/var/log/mysqld.log
mysql     2281  0.0  2.7 142412 13276 ?        Sl   Jun29  18:38 
/usr/libexec/mysqld --defaults-file=/etc/my.cnf --basedir=/usr 
--datadir=/share/db --user=mysql --pid-file=/var/run/mysqld/mysqld.pid 
--skip-locking --socket=/var/lib/mysql/mysql.sock
paul     14056  0.0  0.1   3920   676 pts/2    S+   22:25   0:00 grep mysqld

Try ps aux | grep mysql | grep -v grep

So I guess mysql is starting and then bombing. Do you know where the 
mysql log file is ? On a FC box it's in /var/log. If not you can try to 
run it from the command line using the mysqld_safe command. On my Fedora 
box that's in /usr/bin but it should be where your mysql binaries are. 
It may give you more info about why mysql is choking.

Cheers
Paul