[gentoo-user] OT - mythbackend not binding to port. Why?
My mythbackend is screwing up. I called /usr/bin/mythbackend directly so that I could see what exactly the problem is. It gave me this: camille ~ # mythbackend 2006-10-05 14:08:36.085 Using runtime prefix = /usr 2006-10-05 14:08:36.120 New DB connection, total: 1 2006-10-05 14:08:36.127 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.139 Current Schema Version: 1123 Running as a slave backend. 2006-10-05 14:08:36.153 New DB connection, total: 2 2006-10-05 14:08:36.154 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.156 mythbackend: MythBackend started as a slave backend 2006-10-05 14:08:36.173 New DB connection, total: 3 2006-10-05 14:08:36.174 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.241 mythbackend version: 0.19.20060121-2 www.mythtv.org 2006-10-05 14:08:36.241 Enabled verbose msgs: important general 2006-10-05 14:08:36.242 AutoExpire: Found 1 recorders w/max rate of 72 MiB/min 2006-10-05 14:08:36.244 AutoExpire: Required Free Space: 1.1 GB w/freq: 10 min QServerSocket: failed to bind or listen to the socket 2006-10-05 14:08:36.247 Failed to bind port 6543. Exiting. I tried it with and without the firewall running and I got the same results. Why can't it bind to the port? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] OT - mythbackend not binding to port. Why?
On Thu, 2006-10-05 at 14:10 -0500, Michael Sullivan wrote: My mythbackend is screwing up. I called /usr/bin/mythbackend directly so that I could see what exactly the problem is. It gave me this: camille ~ # mythbackend 2006-10-05 14:08:36.085 Using runtime prefix = /usr 2006-10-05 14:08:36.120 New DB connection, total: 1 2006-10-05 14:08:36.127 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.139 Current Schema Version: 1123 Running as a slave backend. 2006-10-05 14:08:36.153 New DB connection, total: 2 2006-10-05 14:08:36.154 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.156 mythbackend: MythBackend started as a slave backend 2006-10-05 14:08:36.173 New DB connection, total: 3 2006-10-05 14:08:36.174 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.241 mythbackend version: 0.19.20060121-2 www.mythtv.org 2006-10-05 14:08:36.241 Enabled verbose msgs: important general 2006-10-05 14:08:36.242 AutoExpire: Found 1 recorders w/max rate of 72 MiB/min 2006-10-05 14:08:36.244 AutoExpire: Required Free Space: 1.1 GB w/freq: 10 min QServerSocket: failed to bind or listen to the socket 2006-10-05 14:08:36.247 Failed to bind port 6543. Exiting. I tried it with and without the firewall running and I got the same results. Why can't it bind to the port? I think I might have discovered one reason why mythbackend was screwing up. I rebooted my machine and tried mythbackend again after rebooting: camille ~ # mythbackend 2006-10-05 14:36:41.431 Using runtime prefix = /usr 2006-10-05 14:36:41.573 New DB connection, total: 1 2006-10-05 14:36:41.574 Unable to connect to database! 2006-10-05 14:36:41.574 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2006-10-05 14:36:41.633 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2006-10-05 14:36:41.688 Failed to init MythContext, exiting. So I tried mysql: camille ~ # /etc/init.d/mysql start * ... * Starting mysql (/etc/mysql/my.cnf) * MySQL NOT started (0) [ !! ] I looked for logs: camille ~ # ls /var/log/mysql camille ~ # camille ~ # cat /var/log/messages | grep 'mysql' Jun 16 08:43:44 camille groupadd[27649]: new group: name=mysql, gid=60 Jun 16 08:43:44 camille useradd[27713]: new user: name=mysql, uid=60, gid=60, home=/dev/null, shell=/bin/false Jun 18 17:01:18 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 18 17:08:13 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 19 16:15:21 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 20 14:23:09 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 25 20:29:49 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jul 10 13:52:29 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jul 20 11:26:56 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jul 27 08:55:43 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Aug 3 17:50:25 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Aug 8 19:07:39 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Aug 26 21:36:41 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Sep 8 23:02:08 camille usermod[24305]: delete `mythtv' from group `mysql' Sep 8 23:02:09 camille usermod[24305]: delete `mythtv' from shadow group `mysql' Sep 15 17:46:20 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Oct 2 13:13:00 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock camille ~ # I can't find any logs as to why mysql won't start. I can't make sense of the /etc/init.d/mysql script. Can anyone give me a hint as to why mysql is not starting? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] OT - mythbackend not binding to port. Why? [SOLVED]
On Thu, 2006-10-05 at 14:39 -0500, Michael Sullivan wrote: On Thu, 2006-10-05 at 14:10 -0500, Michael Sullivan wrote: My mythbackend is screwing up. I called /usr/bin/mythbackend directly so that I could see what exactly the problem is. It gave me this: camille ~ # mythbackend 2006-10-05 14:08:36.085 Using runtime prefix = /usr 2006-10-05 14:08:36.120 New DB connection, total: 1 2006-10-05 14:08:36.127 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.139 Current Schema Version: 1123 Running as a slave backend. 2006-10-05 14:08:36.153 New DB connection, total: 2 2006-10-05 14:08:36.154 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.156 mythbackend: MythBackend started as a slave backend 2006-10-05 14:08:36.173 New DB connection, total: 3 2006-10-05 14:08:36.174 Connected to database 'mythconverg' at host: localhost 2006-10-05 14:08:36.241 mythbackend version: 0.19.20060121-2 www.mythtv.org 2006-10-05 14:08:36.241 Enabled verbose msgs: important general 2006-10-05 14:08:36.242 AutoExpire: Found 1 recorders w/max rate of 72 MiB/min 2006-10-05 14:08:36.244 AutoExpire: Required Free Space: 1.1 GB w/freq: 10 min QServerSocket: failed to bind or listen to the socket 2006-10-05 14:08:36.247 Failed to bind port 6543. Exiting. I tried it with and without the firewall running and I got the same results. Why can't it bind to the port? I think I might have discovered one reason why mythbackend was screwing up. I rebooted my machine and tried mythbackend again after rebooting: camille ~ # mythbackend 2006-10-05 14:36:41.431 Using runtime prefix = /usr 2006-10-05 14:36:41.573 New DB connection, total: 1 2006-10-05 14:36:41.574 Unable to connect to database! 2006-10-05 14:36:41.574 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2006-10-05 14:36:41.633 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2006-10-05 14:36:41.688 Failed to init MythContext, exiting. So I tried mysql: camille ~ # /etc/init.d/mysql start * ... * Starting mysql (/etc/mysql/my.cnf) * MySQL NOT started (0) [ !! ] I looked for logs: camille ~ # ls /var/log/mysql camille ~ # camille ~ # cat /var/log/messages | grep 'mysql' Jun 16 08:43:44 camille groupadd[27649]: new group: name=mysql, gid=60 Jun 16 08:43:44 camille useradd[27713]: new user: name=mysql, uid=60, gid=60, home=/dev/null, shell=/bin/false Jun 18 17:01:18 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 18 17:08:13 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 19 16:15:21 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 20 14:23:09 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jun 25 20:29:49 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jul 10 13:52:29 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jul 20 11:26:56 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Jul 27 08:55:43 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Aug 3 17:50:25 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Aug 8 19:07:39 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Aug 26 21:36:41 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Sep 8 23:02:08 camille usermod[24305]: delete `mythtv' from group `mysql' Sep 8 23:02:09 camille usermod[24305]: delete `mythtv' from shadow group `mysql' Sep 15 17:46:20 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock Oct 2 13:13:00 camille rc-scripts: Strange, the socket file already exist in /var/run/mysqld/mysqld.sock camille ~ # I can't find any logs as to why mysql won't start. I can't make sense of the /etc/init.d/mysql script. Can anyone give me a hint as to why mysql is not starting? The mysql problem was because I forgot to update my bind-address in my.cnf. Myth is working now... -- gentoo-user@gentoo.org mailing list
