View Single Post
  #7  
Old 30th April 2010, 16:37
GoremanX GoremanX is offline
Member
 
Join Date: Apr 2010
Posts: 50
Thanks: 2
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by till View Post
Then the cronjob must had been interrupted, e.g. killed manually which left the lock files there. The sysetm tries to repair itself if someone interuupted it after some time.
Can't imagine what woud've caused the cron job to die, ISPConfig 3 is the only thing I installed on that server. It wasn't doing anything else. I definitely never killed it myself.

Quote:
Originally Posted by till View Post
which is from your linux distribution and not ispconfig. As the error message states, the use of # for comments is deprecated. You can e.g. delete all lines starting with #
Thanks! I'll do that!

By the way, this may not be an ISPCOnfig 3 problem, but it's definitely a Perfect Setup Guide thing. Your guide purports to create a perfect server environment for running ISPConfig. Clearly this is not the case.

Quote:
Originally Posted by till View Post
There seems to be a problem with your harddisk layout. It looks as if /var/www and /var/run/.... are on separate partitions. This means that jails will not work as e.g. hardlinks from within the jail to the mysql socket are not possible. If you would have followed the perfect server guide to install your system, you would not have got this problem.
All of /var is on a separate partition. So /var/run and /var/www are on the same partition (/dev/sdf1 mounted as /var). The Perfect Setup guides specifically mention that I can choose a more advanced partition setup for my needs. There's certainly nothing advanced about placing /var on a separate partition. This is very common practice, especially for a server that hosts all vhosts in /var (which is most control panels I'm familiar with). If I can't have /var on a separate partition, then how am I supposed to expand hosting space with LVM in the future? I have /var mounted on an LVM LP.

Quote:
Originally Posted by till View Post
Most Linux commands do not add a timestamp to the error messages thats they send to stderr. ISPConfig is using system commands, it does not write a new linux distribution. If you want to know which lines get added, simply clear the log:

cat /dev/null > /var/log/ispconfig/cron.log
I must not spend enough time wading through log files. My apologies if you felt I was implying this was an ISPConfig problem. I was merely implying that this cron log file is useless in its current state.

Quote:
Originally Posted by till View Post
The cron.log is normally empty, I run here several servers in production use that were installed as described in the perfect setup guide and I dont get a single line in the cron.log. I guess there are more general problems with the way you installed ispconfig.
It's nice of you to blame me rather than the guide... especially since there's a post from someone else above who describes having the same problem as myself and proposes a functional solution.

Last edited by GoremanX; 1st May 2010 at 05:20.
Reply With Quote