Recycle bin will not empty.

Discussion in 'Installation/Configuration' started by begmarz, Dec 7, 2006.

  1. begmarz

    begmarz New Member

    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:
  2. begmarz

    begmarz New Member

    Now ispconfig is frozen on the msg below.

    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.
    Last edited: Dec 10, 2006
  3. badgerbox76

    badgerbox76 New Member

    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
  4. begmarz

    begmarz New Member

    I have done that.

    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.
  5. falko

    falko Super Moderator

    That's a bad idea. I guess you messed up your database... :(

    Which distribution do you use? What's the output of
    ls -la /root/ispconfig
  6. begmarz

    begmarz New Member

    This is the output.

    [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

    The database is ok I used sql to delete the rows from the db.
  7. till

    till Super Moderator

    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.
  8. begmarz

    begmarz New Member

    What causes the recycle to not empty? How do you fix it?

    Having done the delete, how do I fix the corresponding entries in the _dep and _nodes database tables?
  9. till

    till Super Moderator

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

    begmarz New Member

    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.
  11. till

    till Super Moderator

    There is no max. number of sites. Cna you craete the DNS records in the DNS-Manager?
  12. begmarz

    begmarz New Member

    Yes we have but, once done we ping the URL and it does not resolve.
  13. till

    till Super Moderator

    It may take up to 72 hours until new DNS-Records are propagated.
  14. begmarz

    begmarz New Member

    Thanks we will give this a couple of days. . . and update this thread.

  15. till

    till Super Moderator

    You might also query your local server with:

    dig @localhost

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

Share This Page