If you are going to use MyDNS on a VPS you must remove Bind first. It is preinstalled on most VPS images.
Install Dirvish, rsync and ssh on the backup server:
apt-get install dirvish ssh
/etc/dirvish/master.conf should look something like this:
bank: /data/backup Runall: expire-default: +15 days expire-rule: #MIN HR DOM MON DOW STRFTIME_FMT * * * * 1 +3 months * * 1-7 * 1 +1 year * * 1-7 1,4,7,10 1 * 10-20 * * * +4 days
Create a dirctory where all backup’s will be stored: Continue reading Backup Server with Ubuntu and Dirvish
Recently on our VPS servers there has been no admin group on a default Ubuntu install. Here is the solution.
Add an admin group to the Ubuntu install.
[cc lang=’bash’ ]addgroup admin[/cc]
Now you will need to add any users you want to have root privileges to the admin group.
[cc lang=’bash’ ]adduser cbrown admin[/cc]
Now go to the edit the sudoers file to include the admin group.
[cc lang=’bash’ ]nano /etc/sudoers[/cc]
and insert the following at the bottom of the file.
[cc lang=’bash’ ]# Members of the admin group may gain root privileges[/cc]
[cc lang=’bash’ ]%admin ALL=(ALL) ALL[/cc]
After fighting getting this setup on Tuesday and Wednesday I ended up succeeding and didn’t take any notes. So of course here I am this morning having the exact same problem and trying to go off memory.
Now lets review what has been done so far. I have had a VPS server imaged with Ubuntu 9.04 32-bit and the installed ISPConfig 3 from this tutorial. http://www.howtoforge.com/perfect-server-ubuntu-9.04-ispconfig-3-p3 (Start at page 3 if you have had your image installed.)
First after you have finished the ISPConfig tutorial go into the /etc/pure-ftpd/db folder and copy the file mysql.conf to a safe directory. I used /root.
This is important because the ISPConfig setup has already configured the file with your database username, password, table to be used, and etc. So it is easier to copy the file and use it after we have reinstalled PureFTP. Continue reading Setup PureFtp on VPS
The IntoVPS VPS server we purchased for MPL ended up not working out. The server ended up going down a couple different times within the first we acquired it. Obviously this is not expectable when dealing with multiple clients websites, including MPL’s own.
I ended up picking the VPS because it was actually rated better than the normal VPS company I use and had almost the same rates. The only problem I saw at the time is that they didn’t offer any unmetered bandwidth. This would could have been a problem if we decided to load the VPS down with sites. The server would have run out of bandwidth and possibly shut off in the middle of the month or we could have been charged for the bandwidth overages.
Anyway, we ended up choosing Fivebean, the most reliable I have come across so far. They do in fact offer an unmetered bandwidth option. This is fantastic and means we can still use our current backup system we have in place at the office.
It turns out that it is a great thing we ended up switching to this VPS. I ended up having to login to the Hostmonster account MPL uses for some smaller sites, and had a very disturbing warning message. The message said something along the lines that we had 9704 folders and were putting their server at risk and if we didn’t do something about it we were in jeopardy of getting our account turned off.
THIS IS EXACTLY WHY YOU SHOULDN’T USE SHARED HOSTING!!
Shared hosting might be ok for your average little site, but I guess they don’t like when you put 5 little sites on it. This was completely ridiculous, they claimed unlimited space and bandwidth, but neglect to tell you that there is a limit on the amount of files you can have. So my suggestion is to stay away from Hostmonster and all its variations (Bluehost and some others).
This leads be to moving all the sites from the Hostmonster account to the new VPS server and closing the Hostmonster account. I hope it keeps going smoothly….
I have finally got the new WNGG (http://www.wngg.net) server up and running. It was your typical linux server install until I ran into the problems about it being a VPS (Virtual Private Server). The problem happened to be with Pureftp, and how it does not like to work with virtualization. After many hours I found the solution, downloaded the source code for Pureftp, changed some variables and rebuilt the source. What do you, it worked. Although it took a fair amount of time to fix this problem, I am sure it will be useful again in the future.