I have run into an odd issue with two domains on my server:
http://www.baltikarecords.com and
http://www.frozenplague.net
http://frozenplague.net points to /home/frozenpl
http://www.frozenplague.net SHOULD point to /home/frozenpl but it is going to /home/baltikar
baltika works fine no matter what you do.
frozen and baltika are on seperate IPs. DNS is all correct. httpd confs are all correct. I cannot for the life of me figure out what is causing this. Any ideas?
And apparently I’ve also lost that user’s mysql database.
Hi Adam,
For me, http://www.frozenplague.net and http://frozenplague.net both point to the same place.
Did you recently move frozenplague.net to a new IP address? It sounds like your ISP or your computer may have the old IP cached in their DNS cache, in which case you can just wait it out, or, manually edit the frozenplague.net.conf file, so it starts with
<VirtualHost 75.126.154.251:80 75.126.154.250:80>
instead of just
<VirtualHost 75.126.154.251:80>
That’ll make it listen on both the old and new IPs while the DNS change fully propogates. You’ll want to remove the .250 IP after a day or so, once dns propogation is complete.
Paul
[quote=IWorx-Paul;12912]Hi Adam,
For me, http://www.frozenplague.net and http://frozenplague.net both point to the same place.
Did you recently move frozenplague.net to a new IP address? It sounds like your ISP or your computer may have the old IP cached in their DNS cache, in which case you can just wait it out, or, manually edit the frozenplague.net.conf file, so it starts with
<VirtualHost 75.126.154.251:80 75.126.154.250:80>
instead of just
<VirtualHost 75.126.154.251:80>
That’ll make it listen on both the old and new IPs while the DNS change fully propogates. You’ll want to remove the .250 IP after a day or so, once dns propogation is complete.
Paul[/quote]
This has been on going for about… a week now, I’ve been diagnosing it since then. I did get it to work by doing exactly that… its currently listening on all of my shared IPs… however, this doesnt exactly make me feel good, because this err, doesnt exactly explain why it occurred in the first place or where the account’s things went. All the files are there, but email isnt… mysql database isnt… literally, any where to be found. I know the owner didnt delete it, hes currently asleep on the other side of the world, and has been angry as well since he hasnt been able to access his site from the www. address. Now I have to find his email and such, which mind you becomes a rather difficult process when well, in my using the backup/restore stuff in iworx, it seems to have only backed up the accounts i created under my nodeworx - not his reseller account (which I have to say, isn’t making me a very happy person right now.)
I can’t think of any reason an account’s email or database would just disappear. DNS appears to be set up correctly, frozenplague.net and www.frozenplague.net both point to the 251 ip.
If you’d like us to try to help see what’s going on with the missing data feel free to open a support ticket.
Paul
Honestly I cant think of any reason either. However, after looking for a very long time, I can absolutely say there exists no mailbox information or mysql information of any kind from that account. The domain, subdomains, dns, everything is still there - the mysql users, the databases, the actual data from those databases, and all of the mail is gone.
I’ve looked, no other accounts were affected. I checked to see if an account was deleted (logging on user deletes), and this is not the case either.
The access logs and error logs are all still dating back to when i originally created the account in february.
So, unless you can think of any other place that the mysql user information could have gone, I dont think there will be much solution there =/ (but thanks for the offer).
This is mildly troubling though.
Similar behavior with iptables firewall on my fresh CentOS 5 install- after yum update, no access to nodeworx and webmin- even though firewall ports for nodeworx and webmin were open AND I was accessing them fine before th update. Had to stop iptables.
Hi Hubbadubba. I’m not sure how your issue is related to the old thread this was posted in, maybe that was a mistake. Regardless, do you know what package was updated that caused the issue?
After I installed Iworx on a fresh CentOS5 I was unable to get to NodeWorx. I disabled APF via SSH and then was able to go into NodeWorx fine. I was then able to start APF back up and work normally.
So maybe doing a restart from SSH would fix the issue?
Hi Paul and Justec,
Don’t know if something is up with the date/time stamping on the forum posts or if I responded to Justec’s post last night but his is date/time posted 1:21 PM today.
That’s the explanation for the non-sequitur feel to my response. 
As for what package: I think it’s moot- I think I had my DNS messed up by bad IP addresses in resolv.conf.