Virtualmin/Webmin dying, one service at a time

2 posts / 0 new
Last post
#1 Tue, 10/23/2007 - 15:10
LauraTisoncik

Virtualmin/Webmin dying, one service at a time

I'm running Debian etch and Virtualmin Pro.

Mail once almost worked, once, even though I never got pop to work and there were some problems sending mail. Now supposedly nothing ever created via virtualmin appears in the virtual alias table (even when it apparently does appear in virtual alias tables) and so nothing is deliverable.

Then Bind no longer ran, according to Virtualmin/Webmin, with an "unknown error", except that one can grep named.pid, and connect to websites, and it was possible to find new subdomains that were created via webmin in named.conf.local and in subdomain.host, and connect to them. I managed to convince Webmin that Bind really does exist by pointing it at the pid, but still it's impossible to manage anything via Webmin's Bind module.

Now some of those domains have disappeared off the map, for reasons unknown. No changes were made in any of the config files, and the affected domains are registered, but they can't be pinged. One of the disappearing domains was the server domain itself: the two nameservers are alive (ns1.theprojectserver.org and ns2.theprojectserver.org), but "theprojectserver.org" itself has disappeared. Disappearing domains for no apparent reason is a tad bit unnerving.

Then updates stopped working with "unknown error". There were no apparent problems upgrading via command line.

I'm not sure that Virtualmin/Webmin are performing any function other than, at best, to complicate debugging problems, and at worst to create problems.

Do any of these problems sound familiar to anyone? Is there any solution to this situation short of giving up in favor of command line or asking my hosting company to reinstall everything including plesk?

Tue, 10/23/2007 - 15:51
Joe
Joe's picture

Howdy Laura,

Best best is to start figuring out what's going on with your system...none of these things are known issues.

For the mail problems, we'll want to see what's in the mail.log when problems occur. (And, I noticed while looking into your named problems that you're filtering the SMTP port on ns1.theprojectserver.info, so mail can't possible work if that's the server in question.)

For DNS, here's what we can know for sure:

[joe@delilah ~]$ whois theprojectserver.org
Name Server:NS1.THEPROJECTSERVER.INFO
Name Server:NS2.THEPROJECTSERVER.INFO

[joe@delilah ~]$ host theprojectserver.org NS1.THEPROJECTSERVER.INFO
Using domain server:
Name: NS1.THEPROJECTSERVER.INFO
Address: 66.79.190.50#53
Aliases:

[joe@delilah ~]$ host theprojectserver.org NS2.THEPROJECTSERVER.INFO
Using domain server:
Name: NS2.THEPROJECTSERVER.INFO
Address: 66.79.190.51#53
Aliases:

So, your registrar is pointing to ns1 and ns2 in theprojectserver.info domain. Neither of those name servers has information about this zone--are either of these (IP 66.79.190.50 and 66.79.190.51) the Virtualmin server? I can't really tell from here. So, getting the registrar glue records right, or getting those name servers knowing about your .org zone, would be step one. If the zone has actually gone missing in BIND, then it can be regenerated from Virtualmin without hassle (just turn off DNS service for the virtual server and then turn it back on).

I'd be happy to drop in and see about getting things sorted.

--

Check out the forum guidelines!

Topic locked