CRITICAL EMERGENCY: rebooted system and now cannot bring up Cyrus server at all

2006-02-28 Thread Rob Tanner
Hi, I had to reboot the mail server and fsck the mail partition (280GB, 156GB of mail), and when I tried to bring up Cyrus, I get the following error: Feb 28 15:06:57 belgarath master[2702]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted This is the

Re: CRITICAL EMERGENCY: rebooted system and now cannot bring up Cyrus server at all

2006-02-28 Thread Andrew Morgan
On Tue, 28 Feb 2006, Rob Tanner wrote: Hi, I had to reboot the mail server and fsck the mail partition (280GB, 156GB of mail), and when I tried to bring up Cyrus, I get the following error: Feb 28 15:06:57 belgarath master[2702]: setrlimit: Unable to set file descriptors limit to -1:

Re: CRITICAL EMERGENCY: rebooted system and now cannot bring up Cyrus server at all

2006-02-28 Thread Andrew Morgan
On Tue, 28 Feb 2006, Rob Tanner wrote: I went back to check the logs so I could tell you exactly what came next, and I discovered that the imap daemons were now running. But it took 15 minutes for the first imap daemon to start up -- normally master starts up 5 right away. Not sure what to

Re: CRITICAL EMERGENCY: rebooted system and now cannot bring up Cyrus server at all

2006-02-28 Thread Daniel Renaud
Hi, Go to /etc/security/limits.conf and check with ulimit -a Before, the value -1 was for unlimited but since RHEL 4 and other OS, it doesn't work like this anymore. After the reboot, you had a problem with ulimit for open file descriptor so put unlimited (check the syntax to be sure)