PDA

View Full Version : Recycle bin will not empty.


begmarz
7th December 2006, 19:40
In the dns manager I deleted a Web site and tried to empty the recycle bin and it is a no go. I restarted the service - no go. I restarted the server - still I am unable to delete the site. I can restore the site and delete it but, when I attempt to empty the recycle bin it goes thru the "I'm working" phase then supposedly when it is done I find the items have not been removed.

I have done all I know to do HELP MEEE!!! :confused:

begmarz
8th December 2006, 01:15
I deleted the items in the db and that cleared them from the recycle bin list.
This is the screen shot for all the recycle bins.
What is going on?



The following error occurred:

The recycle bin cannot be accessed because the system is currently being updated. Please try again in a few minutes.

badgerbox76
8th December 2006, 05:48
I had the same problem once. Here is what you need to do, go into the recycle bin and try to delete the files if you get the error just stay logged into ispconfig but don't do anything for about 5min then try again is should work. I know it sounds strange but the computer is running some process at the moment that prevent it from deleting your files so if you let the process finish and try again it should work. Good luck

begmarz
8th December 2006, 21:43
I ended up going into the database and deleting the rows and then I deleted the associated files from the Linux /etc/www directory.

This is not what was required in the past. I went back into the ispconfig gui and refreshed the instance. The 'Recycle Bin' was empty however when the site was recreated the dns would not resolve when pinged.

falko
9th December 2006, 14:59
I ended up going into the database and deleting the rows and then I deleted the associated files from the Linux /etc/www directory.That's a bad idea. I guess you messed up your database... :(

This is not what was required in the past. I went back into the ispconfig gui and refreshed the instance. The 'Recycle Bin' was empty however when the site was recreated the dns would not resolve when pinged.Which distribution do you use? What's the output of ls -la /root/ispconfig?

begmarz
10th December 2006, 10:29
[root@ns1 /]# ls -la /root/ispconfig
total 104
drwxr-xr-x 9 root root 4096 Dec 7 15:36 .
drwxr-x--- 16 root root 4096 Dec 8 16:20 ..
-rwxr-xr-x 1 root root 33136 Oct 27 17:02 cronolog
-rwxr-xr-x 1 root root 9673 Oct 27 17:02 cronosplit
drwxr-xr-x 12 root root 4096 Oct 27 16:39 httpd
drwxr-xr-x 12 root root 4096 Oct 27 17:02 isp
-rw-r--r-- 1 root root 0 Dec 8 09:22 .ispconfig_lock
-rw-r--r-- 1 root root 8 Dec 8 09:22 .old_path_httpd_root
drwxr-xr-x 6 root root 4096 Oct 27 16:24 openssl
drwxr-xr-x 6 root root 4096 Oct 27 16:53 php
drwxr-xr-x 4 root root 4096 Dec 7 23:59 scripts
drwxr-xr-x 4 root root 4096 Oct 27 17:02 standard_cgis
drwxr-xr-x 2 root root 4096 Nov 17 11:34 sv
-rwx------ 1 root root 9389 Oct 27 17:02 uninstall

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxx
The database is ok I used sql to delete the rows from the db.

till
10th December 2006, 16:23
You deleted the rows manually in the db? Thats a really bad idea as it corrupts the database when you dont delete the corresponding records from the _dep and _nodes database tables.

begmarz
10th December 2006, 20:20
Having done the delete, how do I fix the corresponding entries in the _dep and _nodes database tables?

till
11th December 2006, 11:31
Having done the delete, how do I fix the corresponding entries in the _dep and _nodes database tables?

You can not fix it without knowing the unique ID numbers of the records that you deleted.

begmarz
11th December 2006, 19:18
So what should be done now? I must enable the dns on a clients web site. Which is were I started with all this. I had a conflict with creation of the web site (duplicates) in the recycle bin.

Is there a max number of sites in ispconfig? We have about 70 running now.
Attempts to create any new sites are not producing dns results.

till
11th December 2006, 19:21
There is no max. number of sites. Cna you craete the DNS records in the DNS-Manager?

begmarz
12th December 2006, 00:26
Yes we have but, once done we ping the URL and it does not resolve.

till
12th December 2006, 00:38
It may take up to 72 hours until new DNS-Records are propagated.

begmarz
12th December 2006, 01:29
Thanks we will give this a couple of days. . . and update this thread.

-Brad

till
12th December 2006, 11:51
You might also query your local server with:

dig @localhost yourdomain.com

If you get the correct result, the DNS zone configuration is ok on your server.