I have to wait more than 10 minutes for ISPConfig to create a website?

Hey everyone. I've noticed I always have a problem adding new website into ISPConfig system. Whenever I make a new website, database for it, ftp for it and DNS zone, I always have to wait 15+ minutes, sometimes 30minutes? Why is that? Can I do anything to prevent this or speed it up or does ISPConfig normal take so long to process the data?

thanks in advance

 

I have the same problem on my servers.

The /usr/local/ispconfig/server/temp/.ispconfig_lock file was there. I removed it but no solution for the problem

Where can the debug guide be found?

 

THANK YOU till!!!

I did what you said and it only took around 10 seconds for the newly created website, ftp, database and DNS to become active!

PERFECT SOLUTION! (at least for me =))

Thanks again!

EDIT: ** Should I remove it more often? Or is this once in a year problem? =) I've been using ISPConfig for 6 months now.

 

Thank you for the information till, I was away that's why I didn't answer. You say I should debug this issue? Can you refer me to a guide or tutorial on how to debug such issues?

 

Hey,

You have to: ISPConfig -> System -> Server Config (take server which has problems) -> Server -> Loglevel = Debug

Afterwards you can do a

Code:

tail -f /var/log/ispconfig/ispconfig.log

 

Command "/usr/local/ispconfig/server/server.sh" returned:

Code:

PHP Warning:  PHP Startup: apc.shm_size now uses M/G suffixes, please update your ini files in Unknown on line 0

And after that "finish".

I bought this would affect the php in any way? Or is this serious?

NOTE: I tried to fix it, by adding "M" or "G" at the end of "apc.shm_size=512", how ever that didn't seem to make any effect.

 

I'm certain I installed apc "after" I installed the server via tutorial here on howtoforge.com, so basically the apc cannot be the reason why I had the ".ispconfig_lock" file. Other than apc I don't get any errors.

 

I want to disable it to see if the problems go away however I can't, since I have 50+ users using apc on RoundCube to send attachments. Any other suggestions?

Also, I was reading articles on the internet and it was never mentioned apc would destory/kill/hang apache process, in your words "system configuration that causes the server process to die", since apc is the only problem I got from debugging. Could there be anything else wrong?

 

Oh sorry, I have no idea how I missed that step, here is the output in which the lock file gets removed:

Code:

07.08.2012-09:37 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
07.08.2012-09:37 - DEBUG - No Updated records found, starting only the core.
07.08.2012-09:37 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
finished

 

This is what I got:

Code:

07.08.2012-09:55 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
07.08.2012-09:55 - DEBUG - No Updated records found, starting only the core.
/usr/sbin/mpt-status
/usr/bin/fail2ban-client
/sbin/iptables
/sbin/ip6tables
07.08.2012-09:55 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
finished.

Beside that output I still have the apc problem at the top of the output:

Code:

PHP Warning:  PHP Startup: apc.shm_size now uses M/G suffixes, please update your ini files in Unknown on line 0

 

Did you fix it in the correct place? PHP settings can be in php.ini or be set individually for a website (e.g. through ISPConfig or inside an .htaccess file).

 

So I went to check each and every .htaccess file on my server to see if there are any apc settings inside and I found nothing. So because I know that I'm using RoundCube that uses apc, I went to check some tutorials on where to find those .htaccess files, so I found them and there was no mentioning of apc.

So basically I have no idea why that error keeps poping up and my only solution to this problem would be to completely remove apc from my server.

If any of you guys come across any other ideas, please let me know.