Amavis - TCP port 10024

Discussion in 'Installation/Configuration' started by stef157, Dec 29, 2015.

  1. stef157

    stef157 Member

    Hi all,
    I'm in trouble - again.

    I try to restart amavis and I get a failed message.
    So I check in the log and I see this :

    An idea of what I can do ?

    netstat -tulpn
    Thanks !
     
  2. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    That seems odd, amavis normally listens on port 10024 (and your netstat confirms that it is), it doesn't connect to that port. Check your amavis config and see if it is trying to forward to 10024, eg. this is from /etc/amavis/conf.d/50-user on an ispconfig 3.1 dev box:

    Code:
    $inet_socket_port = [10024,10026];
    
    # *:* = send to IP/HOST:incoming Port + 1
    $forward_method = 'smtp:*:*';
     
  3. stef157

    stef157 Member

    Thanks for your feedback

    Here is de bottom of my 50-user.

    Exactly the same as an other server where amavis work fine.

     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you ry to restart the whole server? or kill the amavisd process that currentöy blocks the port?
     
    stef157 likes this.
  5. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    I don't have an ispconfig 3.0 box available right now, but I don't see anything obviously wrong there. Later config files overwrite settings from previous ones though, so maybe that's not only file affecting that; try "grep -R 10024 /etc/amavis/" and see if you find anything else.
     
  6. stef157

    stef157 Member

    Not restarted (fear) and not killed to… I'll try to make a "killall amavis" tomorrow.

    Thanks ;-)
     
  7. stef157

    stef157 Member

    Here is it :
     
  8. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    That looks fine. I think the "can't connect" message doesn't mean it can't connect(), but actually means it can't bind() or listen() (confirmed by a quick look at TCP.pm), so ignore everything I've said and just kill the running amavisd :)
     
    stef157 likes this.
  9. stef157

    stef157 Member

    Here is what I've done (trying to kill) and there is no way to kill amavis :-|

    Code:
    root@server1:/home/stef157# /etc/init.d/amavis status
    [FAIL] amavisd is not running ... failed!
    root@server1:/home/stef157# killall amavis
    amavis: aucun processus trouvé
    root@server1:/home/stef157# killall amavisd-new
    Display all 137 possibilities? (y or n)
    0                config           led_workqueue    scsi_eh_1
    0:0              cpuset           log              scsi_eh_2
    0:1              cron             logger           scsi_eh_3
    0:2              CRON             master           scsi_eh_4
    1                crypto           md               scsi_eh_5
    1:0              dbus-daemon      md2-8            scsi_eh_6
    1:1              dovecot          md2_raid1        scsi_eh_7
    2                ext4-dio-unwrit  md3-8            sed
    2:1              fcgi-pm          md3_raid1        sh
    2:2              flush-0:21       mdadm            showq
    3                flush-9:2        memcached        smartctl
    3:0              flush-9:3        monit            smtp
    3:2              freshclam        munin-node       smtpd
    4                fsnotify_mark    mysqld           sort
    4:0              gam_server       named            spamd
    4:2              getty            netns            spawn
    5                gzip             nfsiod           sshd
    5:0              hd-audio0        nfsv4.0-svc      ssl-params
    5:2              imap             ntpd             su
    6                imap-login       perl             sync_supers
    6:1              init             php-cgi          tar
    6:2              irqbalance       php-fpm          tlsmgr
    7                jfsCommit        pickup           trivial-rewrite
    7:0              jfsIO            pipe             u:6
    7:1              jfsSync          proxymap         u:7
    acpid            kblockd          ps               udevd
    amavisd-new      kdevtmpfs        pure-ftpd        vlogger
    anvil            khelper          python           webmincron.pl
    apache2          khubd            qmgr             xfsconvertd
    ata_sff          khugepaged       rpcbind          xfsdatad
    auth             khungtaskd       rpc.idmapd       xfslogd
    bash             kintegrityd      rpciod           xfs_mru_cache
    bdi-default      ksmd             rpc.statd       
    clamd            kswapd0          rsyslogd        
    cleanup          kthreadd         scsi_eh_0       
    root@server1:/home/stef157# killall amavisd-new
    amavisd-new: aucun processus trouvé
    root@server1:/home/stef157# service amavis start
    Starting amavisd: amavisd-new.
    root@server1:/home/stef157# service amavis status
    [FAIL] amavisd is not running ... failed!
     
  10. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    lsof -i :10024 will show you the process id. Maybe it's no longer running, but hour netstat output above shows both 10024 and 10026, which should both be amavis.
     
    stef157 likes this.
  11. stef157

    stef157 Member

    Right now, I've some PID… I've to kill the 6 PID.

    Code:
    root@server1:/home/stef157# lsof -i :10024
    COMMAND     PID   USER   FD   TYPE    DEVICE SIZE/OFF NODE NAME
    /usr/sbin  1441 amavis    5u  IPv4 732479365      0t0  TCP localhost.localdomain:10024 (LISTEN)
    /usr/sbin  4512 amavis    5u  IPv4 732479365      0t0  TCP localhost.localdomain:10024 (LISTEN)
    /usr/sbin 23199 amavis    5u  IPv4 732479365      0t0  TCP localhost.localdomain:10024 (LISTEN)
    /usr/sbin 23585 amavis    5u  IPv4 732479365      0t0  TCP localhost.localdomain:10024 (LISTEN)
    /usr/sbin 28161 amavis    5u  IPv4 732479365      0t0  TCP localhost.localdomain:10024 (LISTEN)
    /usr/sbin 30329 amavis    5u  IPv4 732479365      0t0  TCP localhost.localdomain:10024 (LISTEN)
    Allright… I was really stressed, now the process are killed… and well restarted.

    Tanks for your help !

    Kind regard,
    Stéphane.
     
    Last edited: Dec 29, 2015

Share This Page