ISPconfig Dovecot problem

Discussion in 'General' started by dolmax, Mar 14, 2008.

  1. dolmax

    dolmax New Member

    Hi everyone,

    I've installed ISPconfig on my Fedora Core 8 servers and really happy with the performance. One of my servers has been up and running for 2 months now, but I started facing a problem regarding Dovecot. Every morning when I get to my office, I see that the POP3 service is offline. If I try to restart the service by /etc/rc.d/init.d/dovecot restart I get a failure notice saying that the /etc/dovecot.conf is incorrect. In the same message I also receive another notification "dovecot is already running on PID XXXX". I basically reboot the system, and everything works like a charm.

    1. I could not find where the log files for dovecot are. Any pointers would be highly appreciated.
    2. What do you think the problem could be?
    3. Why did this happened over time? All I do is use yum to do full updates every now and then? Is this wrong?
    4. How do I restart ISPConfig while the system is running?
    5. How do I update ISPconfig services? Should I keep on using yum to update all installed appllications?

    Thank you all,
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    1) Dovecot should be logging to the file /var/log/maillog. But you might want to have a look into the dovecot.conf file if additional logging can be activated there.

    2) Not easy to say. First try to find the file were dovecot logs to. It might even be a hardware problem.

    3) Using yum frequently is fine and recommended.

    4) /etc/init.d/ispconfig_server restart

    But your problem is most likely not directly related to ispconfig, as ispconfig does not write configuration files for dovecot.

    5) Use yum and additionally update to the latest ispconfig version.
  3. dolmax

    dolmax New Member

    Till thank you for that response.

    I really don't know the methodology of ISPConfig yet, so I did not want to mess up the working system. I'll edit dovecot.conf to create a log path and see what I found. Strange but the server did not create the same problem today.

    I'll check and report if I find something about this problem.


Share This Page