another 6.1.12 switchserver owned my serverand restore broken thread [message #97695] |
Wed, 18 April 2012 01:40  |
|
After updating to 6.1.12 it updated fine i believe. After some higher than normal memory usage i decided to switch from bind to djbdns. Whats deceiving is once you restart djbdns theres no nindication regarding tinydns not running. It was until days later some potential customers couldnt order from my online store and lost a order because dns was down 4 days which is mostly my fault for not crontabbing my custom watchdog script to sms when my server is acting up.
Doing a search and reading recent posts regarding li tried locking down the /var/tinydns/env/IP but I forget what it broke, i think it was apache. Also the tinydns and djbdns for some reason didnt work right on my box and my domains was not resolvable. Switching back to bind from djbdns didnt fix the problem. Did the fixes and scripts from /scripts and i gave up when kloxo cp wouldnt load both 7777 and 7778, dns wouldnt resolv locally on the server, switching to lightty back to apache everything didnt work for me maybe my bad luck. So from previous issues with the last2 or 3 updates, i made sure i had full backups often ready for this situation.
So i reinstalled centos 5.8 64bit, kloxo, uploaded my full backup file to /home/lxlabs/client/admin/__backup folder and went and trieed to restore my backup. Most of the posts on the forum during my hunt for solutions were about kloxo complaining not able to unzip file. Well for my restore kloxo opens the restore file fine, shows a list of admins sites with checkboxes to select what to restore, and when i attempt to restore kloxo spits out a cannot connect to db server password incorrect. I checked kloxos pw and made sure it worked and it connects fine. i even used the /script kloxo pw reset and checked kloxo to see if the new pw added and it did. I tried doing the restore through ssh but same deal. The shell_exec log doesnt help its not verbose enough and i was unable to figure out how to restore the server. Luckily i backed up /var/lib/mysql notb long before the server went down and had to do a all nighter re adding all my websites creating emails installing wordpress and mysql db all manually and ujsing dump sql file to restore wordpress sites.
Since kloxo cant update any changes made say through cli manually which would be a great feature as i can easily write a script and do a lot of the manual restore a lot quicker.
I understand kloxo is open source and im not going to bit*h and complain because its free and the devs are working hard. Im looking for some recommendations on how/what i should backup manually using tar on a nightly basis so if my server takes a dump on me, i can simple do a fresh install and restore my nightly tar instead of kloxos backup/restore feature.
Anyone currently implements such a solution or similar? Besides tar what else would work better?
Also whats a safe dns server setup i can use in the meantime that wont affectkkloxo and uses low memory? I spent a lot of time getting my kloxo cp back in order and afraid to start switching bind to djbdns or apache to lighttpd.
|
|
|
|