[SOLVED] Disk fills up, Zimbra breaks after fix?

[GoneWestCoast]

Greetings.

I had an install of Zimbra working on RHEL5, when the disk filled up. I've since fixed the disk related issue, but now Zimbra refuses to start correctly.

zimbra.log:
Jan 17 10:46:02 prmx055 zimbramon[3820]: 3820:info: 2008-01-17 10:46:01, STATUS: : Cannot: determine
Jan 17 10:46:02 prmx055 sendmail[3880]: m0HIk246003880: from=zimbra, size=375, class=0, nrcpts=1, msgid=<200801171846.m0HIk246003880@prmx055.ourdomain.com>, relay=zimbra@localhost
Jan 17 10:46:02 prmx055 sendmail[3880]: m0HIk246003880: to=zimbra, ctladdr=zimbra (1135/1135), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30375, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1]


startup.log:
Host email.ourdomain.com
Starting ldap...Done.
FAILED
Password:
Password:
Password:
Password:
Password:
Password:
Password:
Failed to start slapd. Attempting debug start to determine error.

I'd prefer not to start breaking the Zimbra internals until receiving guidance-- any thoughts?

[GoneWestCoast]

Digging a little deeper here. This appears incorrect; it shouldn't be asking me for a password:

[root@prmx055 /opt/zimbra/bin]# su zimbra -c './ldap start'
Password:
Password:

[jholder]

Your sudoers file is incorrect. Search the wiki on that term.

[GoneWestCoast]

Your sudoers file is incorrect. Search the wiki on that term.

You're correct; cfengine overwrote the sudoers file on its hourly run, and this wasn't noticed until we had to restart the service.

Thanks!

[jholder]

Cool!
Glad it's working