amavis does suicide

Discussion in 'Installation/Configuration' started by dynamind, Dec 13, 2011.

  1. dynamind

    dynamind Member

    Good Day,

    today I noticed I could not send mails, so I checked the logs in the panel, it shows:

    Dec 13 08:51:41 server amavis[28558]: (!!)TROUBLE in child_init_hook: BDB no dbS: Lock table is out of available locker entries, . at (eval 97) line 27.
    Dec 13 08:51:41 server amavis[28558]: (!)_DIE: Suicide in child_init_hook: BDB no dbS: Lock table is out of available locker entries, . at (eval 97) line 27.
    Dec 13 08:51:42 server amavis[28607]: (!)rundown_child on spam scanner SpamAssassin failed: Can't call method "call_plugins" on an undefined value at (eval 107) line 323 during global destruction.
    Dec 13 08:51:42 server amavis[28619]: (!)rundown_child on spam scanner SpamAssassin failed: Can't call method "call_plugins" on an undefined value at (eval 107) line 323 during global destruction.
    Dec 13 08:52:58 server postfix/postfix-script[1607]: fatal: the Postfix mail system is not running
    Dec 13 08:55:10 server postfix/postfix-script[1530]: fatal: the Postfix mail system is not running
    Dec 13 08:58:46 server amavis[1622]: (01622-02) (!)TempDir removal: tempdir is to be PRESERVED: /var/lib/amavis/tmp/amavis-20111213T085542-01622
    Dec 13 08:58:46 server amavis[1623]: (01623-01) (!)TempDir removal: tempdir is to be PRESERVED: /var/lib/amavis/tmp/amavis-20111213T085845-01623

    So I restarted postfix, but I made no changes/updates before which lead to this error.
    Do you have any idea what's up suddenly with the mailserver? The mailqueue gets worked soo slow, I'll get some coffee now : )
     
    Last edited: Dec 13, 2011
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Please check with:

    df -h

    that you have enough free space and with:

    top

    if the RAM is not fully used.
     
  3. dynamind

    dynamind Member

    Hello Till,

    thanks for your fast reply:


    Dateisystem Size Used Avail Use% Eingehängt auf
    /dev/hda1 76G 8,5G 64G 12% /
    tmpfs 1,5G 8,0K 1,5G 1% /lib/init/rw
    udev 1,5G 84K 1,5G 1% /dev
    tmpfs 1,5G 0 1,5G 0% /dev/shm

    free space looks ok. cat /proc/meminfo shows:


    MemTotal: 3083376 kB
    MemFree: 1604828 kB
    Buffers: 27288 kB
    Cached: 795600 kB
    SwapCached: 0 kB
    Active: 838596 kB
    Inactive: 582120 kB
    Active(anon): 597996 kB
    Inactive(anon): 2040 kB
    Active(file): 240600 kB
    Inactive(file): 580080 kB
    Unevictable: 0 kB
    Mlocked: 0 kB
    HighTotal: 2207688 kB
    HighFree: 803760 kB
    LowTotal: 875688 kB
    LowFree: 801068 kB
    SwapTotal: 3442684 kB
    SwapFree: 3442684 kB
    Dirty: 416 kB
    Writeback: 0 kB
    AnonPages: 598080 kB
    Mapped: 37888 kB
    Shmem: 2104 kB
    Slab: 38096 kB
    SReclaimable: 27868 kB
    SUnreclaim: 10228 kB
    KernelStack: 1936 kB
    PageTables: 5980 kB
    NFS_Unstable: 0 kB
    Bounce: 0 kB
    WritebackTmp: 0 kB
    CommitLimit: 4984372 kB
    Committed_AS: 1464920 kB
    VmallocTotal: 122880 kB
    VmallocUsed: 2244 kB
    VmallocChunk: 114508 kB
    HardwareCorrupted: 0 kB
    HugePages_Total: 0
    HugePages_Free: 0
    HugePages_Rsvd: 0
    HugePages_Surp: 0
    Hugepagesize: 2048 kB
    DirectMap4k: 8184 kB
    DirectMap2M: 903168 kB

    should I try to fsck at next reboot?

    okay I see, the filesystem is damaged:


    fsck from util-linux-ng 2.17.2
    e2fsck 1.41.12 (17-May-2010)
    Warnung! /dev/hda1 ist eingehängt.
    Warnung: Überspringe Journal-Wiederherstellung, da das Dateisystem im Nur-Lesen-Modus ist.
    /dev/hda1 enthält ein fehlerhaftes Dateisystem, Prüfung erzwungen. >STRG+C > touch /forcefsck > reboot, let's see
     
    Last edited: Dec 13, 2011
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes, thats the reason for the problem. The filesystem is currently in readonly modeso that amavis can not wrte to it even if there is free space.
     
  5. dynamind

    dynamind Member

    /dev/hda1 on / type ext3 (rw,noatime,nodiratime,user_xattr,errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)
    tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
    proc on /proc type proc (rw,noexec,nosuid,nodev)
    sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
    udev on /dev type tmpfs (rw,mode=0755)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
    fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)

    now it should be fixed, no error messages for the moment.

    thanks Till, have a nice day + christmas time
     

Share This Page