Big problem after "out of disk space"

Printable View

Show 40 post(s) from this thread on one page

01-15-2007, 07:07 AM
trapanator

Big problem after "out of disk space"

Hi, a situation I don't recommend to anyone.
My disk went full.
After I released some space, the Zimbra refuses to start.

I see that Postfix has launched postmap to recreate new aliases. So:

Code:

ls /etc/alias*

there is only the /etc/aliases and NOT the /etc/aliases.db !

Then I did:

Code:

newaliases

the command remains stucked (doesn't exit) and with a 'top' command:

Code:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10600 root 25 0 6500 1688 1324 R 98.5 0.1 3:17.09 postalias

with a :

Code:

ps exf | grep postalias

Code:

11002 pts/4 S+ 0:00 \_ grep postalias JAVA_JVM_VERSION=1.5 SHELL=/bin/bash TERM=xterm PERL5LIB=/opt/zimbra/zimbramon/lib/x86_64-linux-thread-multi:/opt/zimbra/zimbramon/lib:/opt/zimbra/zimbramon/lib/i386-linux-thread-multi:/opt/zimbra/zimbramon/lib/i486-linux-gnu-thread-multi:/opt/zimbra/zimbramon/lib/i586-linux-thread-multi:/opt/zimbra/zimbramon/lib/darwin-thread-multi-2level USER=zimbra LD_LIBRARY_PATH=/opt/zimbra/lib: SNMPCONFPATH=/opt/zimbra/conf USERNAME=zimbra MAIL=/var/mail/zimbra PATH=/opt/zimbra/bin:/opt/zimbra/zimbramon:/opt/zimbra/postfix-2.2.9/sbin:/opt/zimbra/openldap/bin:/opt/zimbra/java/bin:/opt/zimbra/snmp/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games PWD=/opt/zimbra/bin JAVA_HOME=/opt/zimbra/java LANG=CPERLLIB=/opt/zimbra/zimbramon/lib/x86_64-linux-thread-multi:/opt/zimbra/zimbramon/lib:/opt/zimbra/zimbramon/lib/i386-linux-thread-multi:/opt/zimbra/zimbramon/lib/i486-linux-gnu-thread-multi:/opt/zimbra/zimbramon/lib/i586-linux-thread-multi:/opt/zimbra/zimbramon/lib/darwin-thread-multi-2level SHLVL=1 HOME=/opt/zimbra LANGUAGE=it_IT:it:en_GB:en BASH_ENV=/opt/zimbra/.bashrc LOGNAME=zimbra ZIMBRA_HOME=/opt/zimbra _=/bin/grep OLDPWD=/opt/zimbra

how can I do?
01-15-2007, 07:09 AM
trapanator

I forgot the /etc/alias:

Code:

zimbra@grass:~/bin$ cat /etc/aliases # Added by installer for initial user

yes, it's empty.
01-15-2007, 07:19 AM
trapanator

I tried the command to recreate aliases.db with Verbose output:

Code:

zimbra@grass:~$ postmap -v /etc/aliases postmap: dict_eval: const mail postmap: dict_eval: const ipv4 postmap: name_mask: ipv4 postmap: dict_eval: const grass.intra.comune.trento.it postmap: dict_eval: const intra.comune.trento.it postmap: dict_eval: const Postfix postmap: dict_eval: const postfix postmap: dict_eval: const postfix postmap: dict_eval: const postdrop postmap: dict_eval: expand $myhostname, localhost.$mydomain, localhost -> grass.intra.comune.trento.it, localhost.intra.comune.trento.it, localhost postmap: dict_eval: expand $myhostname -> grass.intra.comune.trento.it postmap: dict_eval: const servertwo.intra.comune.trento.it postmap: dict_eval: const /opt/zimbra/postfix-2.2.9/libexec postmap: dict_eval: const /opt/zimbra/postfix-2.2.9/sbin postmap: dict_eval: const /opt/zimbra/postfix-2.2.9/spool postmap: dict_eval: const pid postmap: dict_eval: const all postmap: dict_eval: const postmap: dict_eval: const double-bounce postmap: dict_eval: const nobody postmap: dict_eval: const hash:/etc/aliases postmap: dict_eval: const 20060221 postmap: dict_eval: const 2.2.9 postmap: dict_eval: const hash postmap: dict_eval: const deferred, defer postmap: dict_eval: const postmap: dict_eval: expand $mydestination -> grass.intra.comune.trento.it, localhost.intra.comune.trento.it, localhost postmap: dict_eval: expand $relay_domains -> grass.intra.comune.trento.it, localhost.intra.comune.trento.it, localhost postmap: dict_eval: const TZ MAIL_CONFIG postmap: dict_eval: const MAIL_CONFIG MAIL_DEBUG MAIL_LOGTAG TZ XAUTHORITY DISPLAY postmap: dict_eval: const subnet postmap: dict_eval: const postmap: dict_eval: const += postmap: dict_eval: const -=+ postmap: dict_eval: const debug_peer_list,fast_flush_domains,mynetworks,permit_mx_backup_networks,qmqpd_authorized_clients,relay_domains,smtpd_access_maps postmap: dict_eval: const postmap: dict_eval: const bounce postmap: dict_eval: const cleanup postmap: dict_eval: const defer postmap: dict_eval: const pickup postmap: dict_eval: const qmgr postmap: dict_eval: const rewrite postmap: dict_eval: const showq postmap: dict_eval: const error postmap: dict_eval: const flush postmap: dict_eval: const verify postmap: dict_eval: const trace postmap: dict_eval: expand ${config_directory}/prng_exch -> /opt/zimbra/postfix-2.2.9/conf/prng_exch postmap: dict_eval: const /opt/zimbra/conf/smtpd.crt postmap: dict_eval: const /opt/zimbra/conf/smtpd.key postmap: dict_eval: const postmap: dict_eval: expand $smtpd_tls_dcert_file -> postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: expand $smtp_tls_cert_file -> postmap: dict_eval: const postmap: dict_eval: expand $smtp_tls_dcert_file -> postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const postmap: dict_eval: const 10240000 postmap: dict_eval: const 1 postmap: dict_eval: const yes postmap: dict_eval: const 100s postmap: dict_eval: const 100s postmap: dict_eval: const 100s postmap: dict_eval: const 100s postmap: dict_eval: const 3600s postmap: dict_eval: const 3600s postmap: dict_eval: const 100s postmap: dict_eval: const 100s postmap: dict_eval: const 1000s postmap: dict_eval: const 1000s postmap: dict_eval: const 10s postmap: dict_eval: const 10s postmap: dict_eval: const 1s postmap: dict_eval: const 1s postmap: dict_eval: const 1s postmap: dict_eval: const 1s postmap: dict_eval: const 500s postmap: dict_eval: const 500s postmap: dict_eval: const 3600s postmap: dict_eval: const 3600s postmap: dict_eval: const 3600s postmap: dict_eval: const 3600s postmap: dict_eval: const 18000s postmap: dict_eval: const 18000s postmap: dict_eval: const 1s postmap: dict_eval: const 1s postmap: name_mask: subnet postmap: inet_addr_local: configured 2 IPv4 addresses postmap: been_here: 127.0.0.0/8: 0 postmap: been_here: 192.168.13.0/24: 0 postmap: mynetworks: 127.0.0.0/8 192.168.13.0/24 postmap: dict_eval: const 127.0.0.0/8 192.168.13.0/24 postmap: open hash /etc/aliases

after "open hash /etc/aliases" line, the program doesn't exit forever.
01-17-2007, 01:28 AM
trapanator

Anybody ?
01-18-2007, 12:04 AM
trapanator

Up.... ..
01-18-2007, 11:19 AM
wickhamandrew

The same thing has happened to our server. I got a support ticket put in this morning and I believe they're working on fixing it.

I used the Zimbra VMware Appliance and they only provide you with 1.8Gbs worth of hard drive space. We got two users on there, each with 20Mbs of data, and then added a third with about 30Mbs of data and the server crashed and won't come back up. When tech support lets me know what to do I'll be sure to post it here.
01-21-2007, 11:07 PM
trapanator

wickhamandrew, any news?
01-22-2007, 02:36 AM
trapanator

I've filed the bug:

http://bugzilla.zimbra.com/show_bug.cgi?id=13951

please vote for it.
01-22-2007, 03:59 AM
wickhamandrew

Actually, on Friday, they said that I basically had to reinstall and try to restore from a backup. This isn't a solution to this problem. Once we get our Zimbra server, if we run out of disk space, I don't want to have to reinstall the whole suite just to get it back up and running. It is a ridiculous "solution."
03-19-2007, 08:48 AM
daceilo

You may have the same situation as myself ...

Did an strace on the postmap process (Using 100% of the cpu)...

It was stuck in this cycle:

stat64("/opt/zimbra/conf/postfix_header_checks.db", 0xbf848900) = -1 ENOENT (No such file or directory)
open("/opt/zimbra/conf/__db.postfix_header_checks.db", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0644) = -1 EEXIST (File exists)
open("/opt/zimbra/conf/__db.postfix_header_checks.db", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0644) = -1 EEXIST (File exists)
open("/opt/zimbra/conf/__db.postfix_header_checks.db", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0644) = -1 EEXIST (File exists)

Looks like it was looking for the one file, finding that it wasn't there, trying to create another file as a result (Which existed) and looped from there. I move the /opt/zimbra/conf/__db.postfix_header_checks.db to /opt/zimbra/conf/__db.postfix_header_checks.db.old after killing all the zimbra processes off and restarted and it started fine.

Show 40 post(s) from this thread on one page