Re: [gentoo-user] MythTV (or possibly mysql) stopped working after a kernel rebuild
Sasha, I have since done this in the last hour. I had saved the kerenl config this morning before finding the i915 driver. I went back to that config, turned on i915 support, and rebooted, etc. I did that before I wrote this message. however something has caused the system tobe unhappy with either mythbackend or mysql. I'm still having trouble though and I'm at a loss to figure out what's causing it. Thanks, Mark On 4/25/05, Alexander Kirillov [EMAIL PROTECTED] wrote: Mark, You shouldn't start with the default config but rather with one known to be working with your hardware etc. (unless you know what you are doing:) Old kernel configs should remain in /etc/kernels. After make mrproper copy an old config to /usr/src/linux as .config and make the changes you need to support your graphics chip there. Sasha My kernel didn't call up the right stuff for X-Video support so I rebuilt it. After rebooting mysql no longer starts and hence mythbackend doesn't run. Is there anything about mysql that would be effected by building a new version of an existing kernel? I did start completely over with the kernel. (make clean/make mrpoper/etc.) Or is this just a coincidence and something else is the likely culprit? -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MythTV (or possibly mysql) stopped working after a kernel rebuild
On Mon, 25 Apr 2005, Mark Knecht wrote: Sasha, I have since done this in the last hour. I had saved the kerenl config this morning before finding the i915 driver. I went back to that config, turned on i915 support, and rebooted, etc. I did that before I wrote this message. however something has caused the system tobe unhappy with either mythbackend or mysql. I'm still having trouble though and I'm at a loss to figure out what's causing it. Is MySQL running? Run the usual mysql command and see if you can login. If MySQL is not running then do /etc/init.d/mysql start rc-update add mysql default -- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MythTV (or possibly mysql) stopped working after a kernel rebuild
If you have changed your kernel its highly likely your ivtv module will need rebuilding, and if thats not working mythbackend is probably not going to start. On Mon, 25 Apr 2005 13:50:15 -0700 Mark Knecht wrote: Sasha, I have since done this in the last hour. I had saved the kerenl config this morning before finding the i915 driver. I went back to that config, turned on i915 support, and rebooted, etc. I did that before I wrote this message. however something has caused the system tobe unhappy with either mythbackend or mysql. I'm still having trouble though and I'm at a loss to figure out what's causing it. Thanks, Mark On 4/25/05, Alexander Kirillov [EMAIL PROTECTED] wrote: Mark, You shouldn't start with the default config but rather with one known to be working with your hardware etc. (unless you know what you are doing:) Old kernel configs should remain in /etc/kernels. After make mrproper copy an old config to /usr/src/linux as .config and make the changes you need to support your graphics chip there. Sasha My kernel didn't call up the right stuff for X-Video support so I rebuilt it. After rebooting mysql no longer starts and hence mythbackend doesn't run. Is there anything about mysql that would be effected by building a new version of an existing kernel? I did start completely over with the kernel. (make clean/make mrpoper/etc.) Or is this just a coincidence and something else is the likely culprit? -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list -- Nick Rout Barrister Solicitor Christchurch http://www.rout.co.nz [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MythTV (or possibly mysql) stopped working after a kernel rebuild
I have since done this in the last hour. I had saved the kerenl config this morning before finding the i915 driver. I went back to that config, turned on i915 support, and rebooted, etc. I did that before I wrote this message. however something has caused the system tobe unhappy with either mythbackend or mysql. I'm still having trouble though and I'm at a loss to figure out what's causing it. Is MySQL running? Run the usual mysql command and see if you can login. If MySQL is not running then do /etc/init.d/mysql start rc-update add mysql default Check MySQL logs also. Usually found in /var/log/mysql -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MythTV (or possibly mysql) stopped working after a kernel rebuild
On 4/25/05, Nick Rout [EMAIL PROTECTED] wrote: If you have changed your kernel its highly likely your ivtv module will need rebuilding, and if thats not working mythbackend is probably not going to start. Yes, I rebuilt ivtv and tested that I couldrecord from the command line basically using something like: cat /dev/v4l/video0 test.mpg The mpeg file played fine in mplayer. The problem seems to be that mythfrontend cannot connect to mythbackend anymore and the mythbackend scripts are having trouble starting and stopping mythbackend. However even the mythbackend app comes up in a default mode askingme for my preferred language and terminal messages say it cannot connect to mysql. Does mysql require some sort of network protocol that mightnot be running? Samba, NFS, etc.? Thanks, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MythTV (or possibly mysql) stopped working after a kernel rebuild
On 4/25/05, Nick Rout [EMAIL PROTECTED] wrote:
On Mon, 25 Apr 2005 15:03:35 -0700
Mark Knecht wrote:
Does mysql require some sort of network protocol that mightnot be
running? Samba, NFS, etc.?
Thats what the startup scripts are for. They should automatically start
required scripts. If in doubt take a look at the init script. In my
/etc/init.d/mysql it says:
depend() {
use dns net
That means mysql will use the network and dns resolution operating, but
doesn't need them.
see http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2chap=4
As someone else said, look in your logs.
To check that mysql is actually running try the ps command.
ps ax|grep mysql
Thanks for the info.
OK, using ps aux | grep mysql returned nothing so it wasn't running.
To eliviate my frustration I rebuilt mysql along with all of MythTV,
or at least the parts I had installed before. I'm sure that was
overkill but now mysql and MythTV are starting to work again:
dragonfly ~ # ps aux | grep mysql
root 21769 0.0 0.2 2084 1048 ?Ss 16:10 0:00
/bin/sh /usr/bin/mysqld_safe
mysql21804 0.0 1.4 39200 7200 ?Sl 16:10 0:00
/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql
--pid-file=/var/run/mysqld/mysqld.pid --skip-locking --port=3306
--socket=/var/run/mysqld/mysqld.sock
root 21935 0.0 0.0 1476 464 pts/0R+ 16:19 0:00 grep mysql
dragonfly ~ #
and I can log in when on the backend machine:
dragonfly ~ # mysql -u root -p mythconverg
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 14 to server version: 4.0.24
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql quit
Bye
dragonfly ~ #
And I can also get into mythtv-setup and even the front end, to some extent.
The place I'm a bit stalled at right now, and I'm sure it's a config
issue only, is that I need mysql to be bound to the network address of
the machine it's running on (dragonfly) so that I can access the
mythbackend from other parts of the house. (XBox running Linux when
this works, but my laptop for now) To that end I changed
/etc/mysql/my.cnf like this:
# keep secure by default!
#bind-address= 127.0.0.1
bind-address= 192.168.10.55
port= 3306
# this can make it even more secure:
and restarted mysql. Now netstat shows it listening, I think:
dragonfly ~ # netstat -apn | grep mysql
tcp0 0 192.168.10.55:3306 0.0.0.0:*
LISTEN 21804/mysqld
unix 2 [ ACC ] STREAM LISTENING 90716 21804/mysqld
/var/run/mysqld/mysqld.sock
dragonfly ~ #
Nowever, when I try to log in from any machine on the network I don't
seem to be able to get in:
dragonfly ~ # mysql -h 192.168.10.55 -u root -p mythconverg
Enter password:
ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES)
dragonfly ~ #
I ran these commands within mysql to hopefully open it up to other
tcp/ip addresses:
dragonfly ~ # mysql -u root -p mythconverg
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 16 to server version: 4.0.24
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql grant all on mythconverg.* to mythtv@% identified by mythtv;
Query OK, 0 rows affected (0.00 sec)
mysql flush privileges;
Query OK, 0 rows affected (0.00 sec)
mysql quit
Bye
dragonfly ~ #
But it still doesn't let me in. Teh same thing happens in mythfrontend
judging from what I see in the terminal:
2005-04-25 16:14:11.368 Changing from None to None
2005-04-25 16:14:37.991 Writing settings file /home/mark/.mythtv/mysql.txt
2005-04-25 16:14:38.001 Connecting to backend server:
192.168.10.55:6543 (try 1 of 5)
Connection timed out.
You probably should modify the Master Server settings
in the setup program and set the proper IP address.
2005-04-25 16:15:08.192 Connecting to backend server:
192.168.10.55:6543 (try 1 of 5)
Connection timed out.
You probably should modify the Master Server settings
in the setup program and set the proper IP address.
2005-04-25 16:15:09.230 Changing from None to None
2005-04-25 16:15:13.607 Connecting to backend server:
192.168.10.55:6543 (try 1 of 5)
Connection timed out.
You probably should modify the Master Server settings
in the setup program and set the proper IP address.
[EMAIL PROTECTED] ~ $
/var/log/mysql/mysql.err shows only:
050425 16:10:45 mysqld started
/var/log/mysql/mysqld.log shows only:
/usr/sbin/mysqld: ready for connections.
Version: '4.0.24' socket: '/var/run/mysqld/mysqld.sock' port: 3306
Gentoo Linux mysql-4.0.24
Do I possibly just have the format of the remote login command wrong?
Any
