<pre>>Matthew Asplund wrote:<br>>><i> I rebooted my Ubuntu Dapper Drake/mythtv0.20 setup this morning, and it <br></i>><i><span style="font-style: italic;">></span> isn't restarting correctly. I cannot start up mythbackend because it
<br></i>><i><span style="font-style: italic;">></span> says that mysql is not running (which is correct). I try running <br></i>><i><span style="font-style: italic;">></span> /etc/init.d/mysql start and it times out starting msqladmin, because it
<br></i>><i><span style="font-style: italic;">></span> cannot connect to the socket. I try running mysqld as root, and (sudo <br></i>><i><span style="font-style: italic;">></span> /usr/sbin/msqld) and it says it cannot start because the port is already
<br></i>><i><span style="font-style: italic;">></span> bound to a process, and to check that a mysql server is already <br></i>><i><span style="font-style: italic;">></span> running. ps -aux | grep sql shows nothing running.
<br></i>><i><span style="font-style: italic;">></span> <br></i>><i>> I am not sure what to do. How do I find out what is blocking access to <br></i>><i>> the port? I have done several updates from binary .debs from the one
<br></i>><i>> apt repository (I cannot remember the address, and I am at work, so I <br></i>><i>> cannot look up the address, it may have been the iowa state one, but it <br></i>><i>> might have been another).
<br></i>><i>> <br></i>><i>> (This is only a crisis, because The Office is on tonight, and my son has <br></i>><i>> a concert, though I can record it another way if I have to.)<br></i>><i><span style="font-style: italic;">
></span> <br></i>><i>> Matthew Asplund<br></i><br>>what does<br>><br>>lsof | grep mysql<br>><br>>say?<br><br>>Tom<br><br>So here's the end of the story. I run a netstat, and nothing was listed as
<br>accessing port 3306. I run the lsof and nothing was using any mysql files. I <br>even rebooted in single user mode, and it still said that the port was not<br>available. Luckily at this point I had to take my son to a jazz band concert, and
<br>I was explaining what the problem was, when I realized that the problem was with <br>the IP address. Sure enough, when I re-booted the computer my linksys router<br>had given a different IP address then usual to the computer, and I had hard-coded
<br>the IP address of the server to be <a href="http://192.168.1.100">192.168.1.100</a>, but it had gotten <a href="http://192.168.1.103">192.168.1.103</a> <br>from DCHP. So I fixed the IP address and everything works now.
<br><br>Thanks for the help<br><br></pre>