Upgrade... lost the database

Just did an upgrade to 2.2.12.

I have lost everything, all sites, users, database etc.

I did use the backup utility a while ago. (didn't before the upgrade) where does this get saved? Are there any auto backups done with the upgrade?

I still have my directories just no database.
Can I just start creating the same domains in the same order or is it going to delete those directories too?

Given all email and web is currently down, for our company, need to either recover what I can or start over very quickly.

Thanks.

 

Update

OK: I have been able to get email back up. Given I believe ISPConfig simply modifies the cfg files of the various applications.

We are not a big company, and the web items are not critical (as to have to have them now), so I would like to refine my question to this.

Can I enter the sites in the same order as they where entered before so I get web1, web2 the same, reenter the users and I will not break the working email applications?

Is there files I should manually back-up before I do this?

Thanks again. Stupid me not having a current database back-up.

 

uggh

No I did not do any special creation before rerunning the script.

It did not run correctly the first time, and reran it.

It then wipes out the database?

I do see backups in my tmp directory. But they do not appear large enough either.
I believe someone may have gotten access to the system and wiped out the databases, before I ran the upgrade.
With the assumption I do not have a database backup.

Can I recreate the hosts and users and be OK as long as the hosts are in the right order?

 

What's the output of

Code:

ls -la /tmp

and

Code:

df -h

?

 

ls -la /tmp
total 146128
drwxrwxrwt 14 root root 20480 May 3 07:38 .
drwxr-xr-x 24 root root 4096 May 3 06:57 ..
-rw------- 1 root root 747 May 2 12:59 existing_db_05_02_2007__12_59_09.sql
-rw------- 1 root root 304122 May 2 13:24 existing_db_05_02_2007__13_24_06.sql
-rw------- 1 root root 304122 May 2 13:51 existing_db_05_02_2007__13_51_18.sql
drwxrwxrwt 2 root root 4096 May 3 06:57 .font-unix
drwx------ 3 root root 4096 May 3 06:58 gconfd-root
-rw------- 1 root root 140 May 3 06:58 .gdm425WRT
srw-rw-rw- 1 root root 0 May 3 06:58 .gdm_socket
srwxr-xr-x 1 root root 0 May 3 07:27 gedit.root.3648525463
srwxr-xr-x 1 root root 0 May 2 11:46 gnome-system-monitor.root.2749371787
-rw------- 1 root root 31061993 May 2 12:45 home_admispconfig_05_02_2007__12_59_09.tar.gz
-rw------- 1 root root 31567970 May 2 13:07 home_admispconfig_05_02_2007__13_24_06.tar.gz
-rw------- 1 root root 31568166 May 2 13:36 home_admispconfig_05_02_2007__13_51_18.tar.gz
-rw-rw-r-- 1 apache apache 93 Apr 25 14:16 .htaccess
drwxrwxrwt 2 root root 4096 May 3 06:58 .ICE-unix
drwx------ 2 root root 4096 May 3 06:58 keyring-d6kiXX
drwx------ 2 root root 4096 Nov 15 11:56 keyring-jvDSdE
drwx------ 2 root root 4096 Jan 16 12:38 keyring-N5Jd6o
drwx------ 2 root root 4096 Jan 22 08:41 keyring-Ve8lvZ
drwx------ 2 root root 4096 Dec 5 10:06 keyring-W1Z4Ki
srwxr-xr-x 1 root root 0 May 3 06:58 mapping-root
drwx------ 2 root root 4096 May 3 07:37 orbit-root
srwxr-xr-x 1 root root 0 Nov 15 12:16 OSL_PIPE_0_SingleOfficeIPC_dff687f33e731547a7abecfd29de83
-rw------- 1 root root 18173252 May 2 12:44 root_ispconfig_05_02_2007__12_59_09.tar.gz
-rw------- 1 root root 18167292 May 2 13:07 root_ispconfig_05_02_2007__13_24_06.tar.gz
-rw------- 1 root root 18168069 May 2 13:36 root_ispconfig_05_02_2007__13_51_18.tar.gz
-rw------- 1 root root 0 May 3 07:01 sess_051d2a43936e2447bf49ee0e9de8be7f
-rw------- 1 admispconfig admispconfig 25 May 3 06:55 sess_17712bea37555506455fe13c353c28ee
-rw------- 1 root root 0 May 3 06:58 sess_23f6e5428abae52a939bb71be1822099
-rw------- 1 root root 0 May 3 03:15 sess_56a05ed8e19aa6e3f39c99990b357f7f
-rw------- 1 root root 0 May 3 04:00 sess_68656e9203fed00fa49e5d254925c733
-rw------- 1 admispconfig admispconfig 25 May 3 07:01 sess_a670dcbd86bfcbeeac905924d62b9bd4
-rw------- 1 root root 0 May 3 07:03 sess_be133183ab2a55e21dfdc8b74966cbce
drwx------ 2 root root 4096 May 3 06:58 ssh-UePMNE2959
drwx------ 2 root root 4096 May 3 06:58 virtual-root.Weq8PW
-r--r--r-- 1 root root 11 May 3 06:58 .X0-lock
drwxrwxrwt 2 root root 4096 May 3 06:58 .X11-unix

******************
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
143G 17G 119G 13% /
/dev/sda1 99M 17M 77M 18% /boot
tmpfs 999M 0 999M 0% /dev/shm

 

These are your ISPConfig database backups.

 

well I had a similar thing happen. But when I typed in

ls -la /tmp

I don't see anything similar to

-rw------- 1 root root 747 May 2 12:59 existing_db_05_02_2007__12_59_09.sql
-rw------- 1 root root 304122 May 2 13:24 existing_db_05_02_2007__13_24_06.sql
-rw------- 1 root root 304122 May 2 13:51 existing_db_05_02_2007__13_51_18.sql

What happened was I was doing the update via ssh, and I got preoccupied with something else, When I came back my session had timed out but it was to the point where it asked me for an email address for ISPConfig to use. I went back and tried to re-run the install but as soon as I noticed this was for a fresh install I canceled out.

The last backup of the ful database was last night with no changes made since then other than running the upgrade script. What is the best way for me to proceed?

Thanks

 

Till,

Thanks for the quick reply. I've tried that and I get


########## INSTALLATION ##########

Preparing files. Please wait a moment...
cp: cannot stat `/root/ispconfig/httpd/conf/ssl.*': No such file or directory


Any help would be much appreciated. I have the backup of my database but not a backup of the files.




EDIT: After letting it sit for about 20 mins it continued with the install. I'm going to watch it this time...

 

Well, the script finished and it said

Shutting down ISPConfig system...
/root/ispconfig/httpd/bin/apachectl stop: httpd (no pid file) not running
ISPConfig system stopped!
Starting ISPConfig system...
/root/ispconfig/httpd/bin/apachectl startssl: httpd could not be started
ISPConfig system is now up and running!
Congratulations! Your ISPConfig system is now installed. If you had to install quota, please take the steps described in the installation manual. Otherwise your system is now available without reboot.

but I am unable to access the admin page. Any help on where to look to fix this would be much appreciated. Oh and it never asked me for an email this time.

 

Well... I've been trying everything I can think of to get this working. After much searching, I am still at a loss. I can run apachectl start and then I can access the ISPConfig admin page at a http://xx.xxx.xxx.xxx:81 but there are a lot of errors. When I try apachectl startssl I get the same message as above "httpd could not be started" Any ideas on where to focus my efforts would be much appreciated.

Thanks.

EDIT: Here is what I'm getting.
root@server1:/# /root/ispconfig/httpd/bin/apachectl start
/root/ispconfig/httpd/bin/apachectl start: httpd started
root@server1:/# /root/ispconfig/httpd/bin/apachectl stop
/root/ispconfig/httpd/bin/apachectl stop: httpd stopped
root@server1:/# /root/ispconfig/httpd/bin/apachectl startssl
/root/ispconfig/httpd/bin/apachectl startssl: httpd could not be started

 

Ahhhh... I screwed it up... I had gone to try the update one more time like you had suggested earlier Till and this time while it's checking files I get a ton of errors like these:

for what looks like every file and then it ends with

I'm not going to touch anything else until I hear back. Am I to the point where I need to do a fresh install of ISPConfig? And if so, is there a topic anywhere about restoring a backup onto a fresh install? I haven't seen one yet.

Thanks.

 

Do the directories /root/ispconfig and /home/admispconfig and the ISPConfig database exist? If not, check your /tmp directory, there should be backups of both directories and a dump of the ISPConfig database from which you can restore your previous installation.

 

Well I think I figured out the problem. My root HD is full. In the /tmp directory I have

I have copied the 3 files to a different hard drive and cleared out some more space on the root. Then I'm going to untar the backup to /root/ispconfig Is this the right course of action with this?


EDIT: I Found the culprit... 4 months of daily database backups in the 300MB range each... they should be going to my backup hard drive, but for some reason they are on the root... I'll have to change that.

 

YES!!! It works. Thanks for the simple guidance Till and Falco, you guys Rock!