after a backup replay, on a stratoserver, no cyrus contact.

Bond Sole blind at bonso-side.de
Sat Jan 31 17:25:09 CET 2015


Am 31.01.2015 16:15, schrieb Thomas Spuhler:
> On Saturday, January 31, 2015 10:46:17 AM Bond Sole wrote:
>> Am 31.01.2015 02:29, schrieb Jan Kowalsky:
>>>> i think the cyrus-master is running, i see under /var/run the cyrus-master.pid
>>>> and with /etc/init.d/cyrus-imapd start/stop it will change.
>>> I would try to restart cyrus anyway. sometimes it occurs that cyrus
>>> can't be shutdown gracefully. If not maybe you have to kill it with -9.
>>> Then start it again. Don't know if this helps.
>> it doesn't help
>>
>>>> and with cvt_cyrusdb i can work, but with the full command it will also run into
>>>> a segmentation fault.
>>> but can you dump your database?
>> yes with skiplist.py
>> /root/skiplist.py /var/lib/imap/mailboxes.db >mailboxes.txt
>>
>>
>> Die orginal Datenbank sichern:
>>
>>       mv /var/lib/imap/mailboxes.db /var/lib/imap/mailboxes.db.orig
>>
>>
>> Einspielen der korrigierten Datenbestände:
>>
>>       /usr/lib/cyrus-imapd/cvt_cyrusdb /root/mailboxes.txt flat
>> /var/lib/imap/mailboxes.db skiplist
>>
>>
>> Setzen der Zugriffsrechte
>>
>>       chown cyrus:mail /var/lib/imap/mailboxes.db
>>
>>
>>
>>
>> root at x:~# ls /var/lib/imap/
>> annotations.db    db.backup1  deliver.db    lock  mailboxes.db proc
>> quota  socket         tls_sessions.db
>> db        db.backup2  domain    log   msg        ptclient  sieve
>> statuscache.db  user
>> root at x:~# /root/skiplist.py /var/lib/imap/mailboxes.db >mailboxes.txt
>> root at x:~# vi mailboxes.txt
>> root at x:~# ls /var/lib/imap/
>> annotations.db    db.backup1  deliver.db    lock  mailboxes.db proc
>> quota  socket         tls_sessions.db
>> db        db.backup2  domain    log   msg        ptclient  sieve
>> statuscache.db  user
>> root at x:~# mv /var/lib/imap/mailboxes.db /var/lib/imap/mailboxes.db.orig
>> root at x:~# /usr/lib/cyrus-imapd/cvt_cyrusdb /root/mailboxes.txt flat
>> /var/lib/imap/mailboxes.db skiplist
>> Speicherzugriffsfehler
>> root at x:~# chown cyrus:mail /var/lib/imap/mailboxes.db
>> root at x:~# cp /var/lib/imap/mailboxes.db.orig /var/lib/imap/mailboxes.db
>> root at x:~# chown cyrus:mail /var/lib/imap/mailboxes.db
>> root at x:~# ls /var/run
>> amavis        crond.reboot     mount             saslauthd sshd
>>            utmp
>> apache2        dirsrv         mysqld             screen sshd.pid
>>        wallaced
>> apache2.pid    kolabd         network         sendmail      udev
>>        xinetd.pid
>> clamav        kolab-saslauthd  openvpn.server1.pid  sendsigs.omit.d
>> upstart-socket-bridge.pid
>> container_type    lock         openvpn.server1.status  shm
>> upstart-udev-bridge.pid
>> crond.pid    motd.dynamic     rsyslogd.pid         spamd.pid user
>> root at x:~# /etc/init.d/cyrus-imapd start
>> Starting : cyrus    30449  0.0  0.0  14048  1616 ?        S 09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30450  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30451  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30452  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30453  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30454  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30455  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30456  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30457  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30458  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30459  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30460  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30461  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30462  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30463  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30464  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> cyrus    30465  0.0  0.0  14048  1616 ?        S    09:59   0:00
>> /usr/lib/cyrus-imapd/cyrus-master -M /etc/cyrus.conf -C /etc/imapd.conf
>> -l 32 -d
>> /usr/lib/cyrus-imapd/cyrus-master already running.
>> root at x:~#
>>
>>
>> im  syslog i see this:
>> Jan 30 20:34:13 x master[2293]: setrlimit: Unable to set file
>> descriptors limit to -1: Operation not permitted
>> Jan 30 20:34:13 x master[2293]: retrying with 4096 (current max)
>> Jan 30 20:34:13 x master[2293]: process started
>> Jan 30 20:34:13 x master[2295]: about to exec
>> /usr/lib/cyrus-imapd/ctl_cyrusdb
>> Jan 30 20:34:13 x master[2293]: process 2295 exited, signaled to death by 11
>> Jan 30 20:34:13 x master[2296]: about to exec /usr/lib/cyrus-imapd/idled
>> Jan 30 20:34:13 x master[2293]: unable to setsocketopt(IP_TOS):
>> Operation not supported
>> Jan 30 20:34:13 x master[2293]: unable to setsocketopt(IP_TOS):
>> Operation not supported
>> Jan 30 20:34:13 x master[2293]: unable to setsocketopt(IP_TOS):
>> Operation not supported
>> Jan 30 20:34:13 x master[2293]: ready for work
>> Jan 30 20:34:13 x master[2299]: about to exec /usr/lib/cyrus-imapd/imapd
>> Jan 30 20:34:13 x master[2293]: process 2299 exited, signaled to death by 11
>> Jan 30 20:34:13 x master[2293]: service imap pid 2299 in READY state:
>> terminated abnormally
>> Jan 30 20:34:13 x master[2300]: about to exec /usr/lib/cyrus-imapd/imapd
>> Jan 30 20:34:13 x master[2301]: about to exec /usr/lib/cyrus-imapd/pop3d
>> Jan 30 20:34:13 x master[2293]: process 2301 exited, signaled to death by 11
>> Jan 30 20:34:13 x master[2293]: service pop3 pid 2301 in READY state:
>> terminated abnormally
>> Jan 30 20:34:13 x master[2302]: about to exec /usr/lib/cyrus-imapd/pop3d
>> Jan 30 20:34:13 x master[2293]: process 2302 exited, signaled to death by 11
>>
>> so my cyrus is running but does not work......
>>
>>
>>
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
>   does /usr/lib/cyrus-imapd/chk_cyrus
>
> give you any errors?
yes,
root at x:~# /usr/lib/cyrus-imapd/chk_cyrus
Speicherzugriffsfehler



More information about the users mailing list