Unable to bind to port 236: Name or service not known.


  • I’m trying to update from final version of Zarafa to Kopano, but I ran into following error when trying to start Kopano-server:

    Tue Sep 15 08:58:52 2020: [=======] Starting kopano-server version 8.5.5 (pid 34867)
    Tue Sep 15 08:58:52 2020: [crit   ] Unable to bind to port 236: Name or service not known. This is usually caused by another process (most likely another server) already using this port. This program will terminate now.
    

    According to netstat there are no services listening on port 236.

    There are also errors in syslog that might be related:

    Sep 15 08:58:52 kopano systemd[1]: Starting Kopano Server...
    Sep 15 08:58:52 kopano systemd[1]: Started Kopano Server.
    Sep 15 08:58:52 kopano kernel: [338127.159794] audit: type=1400 audit(1600149532.263:58): apparmor="DENIED" operation="exec" profile="/usr/sbin/kopano-server" name="/usr/sbin/kopano-server" pid=34867 comm="kopano-server" requested_mask="x" denied_mask="x" fsuid=0 ouid=0
    Sep 15 08:58:52 kopano kernel: [338127.162414] audit: type=1400 audit(1600149532.267:59): apparmor="DENIED" operation="open" profile="/usr/sbin/kopano-server" name="/etc/ssl/openssl.cnf" pid=34867 comm="kopano-server" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
    

    server_listen directive server.cfg currently looks like this:

    # infix for where the server should listen for connections.
    server_listen = *127.0.0.1:236
    #server_listen_tls =
    

    Any help would be appreciated.

  • Kopano

    @ilmix said in Unable to bind to port 236: Name or service not known.:

    *127.0.0.1:236

    Why that star infront of the ip?

    If you do not need to connect to the process over http you could also just comment that line altogether.


  • Thank you, I commented out the line and it helped. The star is there because according to Ubuntu manpage for server.cfg “the asterisk is the multi-protocol address wildcard.” and I wasn’t sure which protocol is used there.
    Now it is having problems with attachments directory.

    Tue Sep 15 13:58:47 2020: [=======] Starting kopano-server version 8.5.5 (pid 8289)
    Tue Sep 15 13:58:47 2020: [warning] setrlimit(RLIMIT_NOFILE, 8192) failed, you will only be able to connect up to 1024 sockets.
    Tue Sep 15 13:58:47 2020: [warning] WARNING: Either start the process as root, or increase user limits for open file descriptors.
    Tue Sep 15 13:58:47 2020: [error  ] Unable to write attachments to the directory '/data/zarafa/attachments' - Permission denied. Please check the directory and sub directories.
    Tue Sep 15 13:58:47 2020: [=======] Server shutdown complete.
    

    The permissions on that directory look ok, but for some reason it doesn’t work.

    test@kopano$ ls -l /data/zarafa/
    total 4
    drwxr-xr-x 12 kopano kopano 4096 Sep  9 09:27 attachments
    
  • Kopano

    @ilmix said in Unable to bind to port 236: Name or service not known.:

    “the asterisk is the multi-protocol address wildcard.” and I wasn’t sure which protocol is used there.

    yes, but that means *:236 and not *127.0.0.1:236.

    @ilmix said in Unable to bind to port 236: Name or service not known.:

    directory ‘/data/zarafa/attachments’ - Permission denied.

    That can either be accredited to appamor, systemd or your general system configuration. There was recently a topic on this forum and the general recommendation is to use the default paths.

    8.5.5 is also already a quite old, I would recommend to use a more recent version.