These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for quantal update killed my server on the new forum.
Tonight virtualmin had a kernel update and quantal. Trusting the default package I let it update now nothing works. It still says precise but the kernel seems to have changed.
When I start the server I get this.
Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 3.5.0-39-generic x86_64)
So that's not quantal.
WTF? This is the second time an update has fried me.
webmin won't start. apache won't start
This is what I get when I try to restart apache
$ sudo /etc/init.d/apache2 restart
sudo: unable to resolve host (none)
* Restarting web server htcacheclean ...not running
apache2: apr_sockaddr_info_get() failed for (none)
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
apache2: apr_sockaddr_info_get() failed for (none)
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
Howdy,
I wouldn't actually recommend upgrading to Ubuntu 12.10 Quantal... that would require a significant jump, and Virtualmin doesn't actually support that distro.
It does look like you're correctly using Ubuntu 12.04, that's good. I don't think the Ubuntu kernel update caused the issue you're seeing though.
It appears that Apache is running from the output you shared above... if you're saying it's not working properly, we may need to look into what's preventing Apache from working even though it's running.
It appears that the hostname on your server isn't set.... what output do you receive if you run the command "hostname"?
You'd normally want that to be a name in the "host.domain.tld" format. If that's not what you see, you can set a new hostname with this command:
hostname host.domain.tld
After doing that -- what happens if you run these commands:
/etc/init.d/apache2 stop
killall -9 apache2
/etc/init.d/apache2 start
Are your websites available after that?
If not -- are you running on a VPS, or dedicated server? If a VPS, is it OpenVZ? If so, can you paste in the contents of your /proc/user_beancounters file?
-Eric
I was able to get it working. First of all, i don't think running virtual min updates should bust a server. Some how, nginx startup process was put in there even though it's not actually installed. It was listening on 80 so apache couldn't get the port. Also networking no longer auto started. For some reason, just by doing the update, ufw was now blocking the webmin ports. Also the I see no reason why the hostname would be removed by an update. It just seemed sloppy to me. I am afraid to reboot my server now or restart apache. lol
I wasn't trying to upgrade to quantal. The files that virtualmin informed me needed update all said Quantal in them.
I was pretty disappointed in the process.
Howdy,
Virtualmin is simply using apt to pull in the packages that your distro says are available... it's not doing anything unusual.
The Apache and networking tools aren't provided by Virtualmin, those come from your disto's software repository.
I'm curious, what is the output of this command:
find /etc/apt/ -name "*.list" | xargs cat
That will show what repositories are setup on your system.
-Eric
I just did a fresh install not to long ago so I'm not sure how anything else would get in there.
any idea what this is all about when I click on the memcached server?
Yeah, I agree, I don't see anything that appears out of place in the various apt sources there.
However, Ubuntu 12.04 is one of the most popular distros in use for Virtualmin servers, and you're the only one to ever describe these symptoms.
Virtualmin doesn't modify the init scripts, Ubuntu packages do that. There's no reason Virtualmin would have added an init script for Nginx (even Virtualmin's Nginx module doesn't add that).
One thing you may want to verify is to make sure Nginx didn't inadvertently get installed somehow -- there's no reason it should be running if it's not installed.
What's the output of these two commands:
dpkg -l 'nginx*'
zgrep nginx /var/log/dpkg.log.*
As far as the memcache module you asked about -- that's a third party module it looks like, it doesn't come with Webmin... and I'm unfortunately not familiar with it. However, it appears that it requires Perl's "Cache::Memcached" module to work properly, which I believe is available in Ubuntu's "libcache-memcached-perl" package.
-Eric