Kopano-Server does not start



  • Hi,

    I just wanted to “migrate” move from Zarafa to Kopano. My setup splits servers between Samba AD, MTA (sendmail) and Kopano. I am quite familiar with Zarafa but new to Kopano, although most thinks looks quite similar ;-)

    Debian: 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux
    Kopano: Nightly build 8.4.90.103-0+18.1_amd64

    AD and MTA are working. Mysql (MariaDB) works as well, access rights set and tested. However, the clean setup (have not taken over any data yet) Kopano-server service does not start up with the following loglevel 6 error message say:

    server.log:
    Fri Aug 25 17:26:40 2017: [info   ] Audit logging not enabled.
    Fri Aug 25 17:26:40 2017: [info   ] Starting kopano-server version 8.4.90 (pid 7970)
    Fri Aug 25 17:26:40 2017: [info   ] Using epoll events
    Fri Aug 25 17:26:40 2017: [notice ] Listening for TCP connections on port 236
    Fri Aug 25 17:26:40 2017: [notice ] Listening for SSL connections on port 237
    Fri Aug 25 17:26:40 2017: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0.
    Fri Aug 25 17:26:40 2017: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock
    Fri Aug 25 17:26:40 2017: [notice ] Listening for pipe connections on /var/run/kopano/server.sock
    Fri Aug 25 17:26:40 2017: [notice ] Connection to database 'kopano' succeeded
    Fri Aug 25 17:26:40 2017: [error  ] Can´t update the database:
    Fri Aug 25 17:26:40 2017: [notice ] Waiting for mysql_server_end
    Fri Aug 25 17:26:40 2017: [notice ] Waiting for mysql_library_end
    Fri Aug 25 17:26:40 2017: [ notice] Server shutdown complete.
    

    Has anyone an idea? Thanks for any input!


  • Translator

    it may be worth checking in the server settings whether the default database is kopano or zarafa.

    If you set this to zarafa it will find your old database, otherwise it’s looking for a database called “kopano” which may not be available on your mysql server if you migrated from zarafa.

    At least I seem to remember that was the case when I did the migration myself.

    Unless of course you started with a completely clean database i.e. without porting over the old zarafa database in which case it should just work (i.e. a fresh installation).



  • thanks for the quick answer. It is set to “kopano”. I did not take over any files from zarafa, so it can be considered as a clean installation.


  • Translator

    @fixundfertig123

    so does it mean that the database is completely empty? I.e. a new freshly installed mysql server?



  • @mcostan yes it is a clean mysql installation.

    And my answer take at least 150 seconds (I just got informed by the system) since I just freshly registered and I can only post every 150 seconds ;-)


  • Translator

    then I am out of ideas, sorry…



  • @mcostan Thanks anyway!!!


  • Kopano

    Does your kopano database user have sufficient permissions on the database?

    The correct settings are described in the documentation: Configure KC Components



  • @bhuisman Did that already and tested access via “su”. As Kopano user I could create tables. So no indication of missing access rights. Thanks



  • Is Debian9 including MariaDB actually supported? The doc does not name Debian9 as supported, the community repo lists a non-testing Debian9?


  • Kopano

    @fixundfertig123 said in Kopano-Server does not start:

    Did that already and tested access via “su”. As Kopano user I could create tables. So no indication of missing access rights.

    The su part makes we wondering, are you actually referring the the system user or are you really speaking about the mysql/mariadb user? Can you show your database configuration in server.cfg?

    @fixundfertig123 said in Kopano-Server does not start:

    doc does not name Debian9 as supported

    The documentation refers to the release packages of Kopano and not the nightly community builds. For subscription holders Debian 9 is indeed not yet supported, but we aim to introduce support with the next mayor release (8.4).



  • Hi @fbartels,

    sorry for not being precise, my fault.

    The su part makes we wondering, are you actually referring the the system user or are you really speaking about the mysql/mariadb user?

    I switched to kopano system user and accessed the mysql / maria DB access then with a kopano DB user. Using this access rights I could create a test table without any problems.

    Attached my server.cfg extract:

    ##############################################################
    # SERVER SETTINGS
    
    # IP Address to bind to (empty for ANY)
    # Set to ::1 or 127.0.0.1 if connections should only come from localhost
    # and through the webserver proxy
    server_bind             = 172.16.1.19
    
    # Accept normal TCP connections (not recommended to disable)
    server_tcp_enabled      = yes
    
    # Port to bind to
    server_tcp_port         = 236
    
    # Accept Unix pipe connections (not recommended to disable)
    server_pipe_enabled     = yes
    
    # Unix socket location
    server_pipe_name        = /var/run/kopano/server.sock
    
    # Priority Unix socket location
    server_pipe_priority    = /var/run/kopano/prio.sock
    
    # Name for identifying the server in a multi-server environment
    server_name = Kopano
    
    # Override the hostname of this server, used by Kerberos SSO if enabled
    server_hostname =
    
    # Database engine (mysql)
    database_engine         = mysql
    
    # Allow connections from normal users through the Unix socket
    allow_local_users       = yes
    
    # local admin users who can connect to any store (use this for the kopano-dagent)
    # field is SPACE separated
    # eg: local_admin_users = root vmail
    local_admin_users       = root kopano
    
    # The user has full rights on a folder by default, uncomment the following line to disable this.
    # owner_auto_full_access = false
    owner_auto_full_access = true
    
    # e-mail address of the Kopano System user
    system_email_address    = postmaster@kopano.xxxxx
    
    # drop privileges and run the process as this user
    run_as_user             = kopano
    
    # drop privileges and run the process as this group
    run_as_group            = kopano
    
    # create a pid file for stopping the service via the init.d scripts
    pid_file                = /var/run/kopano/server.pid
    
    # run server in this path (when not using the -F switch)
    #running_path = /var/lib/kopano
    
    # Use given allocator library. Values like libtcmalloc.so.4,
    # libtcmalloc_minimal.so.4 and libjemalloc.so.2 would work.
    #allocator_library = default
    
    # create memory coredumps upon crash [no, systemdefault, yes]
    #coredump_enabled = systemdefault
    
    # session timeout for clients. Values lower than 300 will be upped to 300
    # automatically. If the server hears nothing from a client in session_timeout
    # seconds, then the session is killed.
    session_timeout         = 300
    
    # for temporary files
    # consider mounting a `tmpfs' underneath this path (wherever you
    # point it to)
    tmp_path = /tmp
    
    ##############################################################
    # MYSQL SETTINGS (for database_engine = mysql)
    
    # MySQL hostname to connect to for database access
    mysql_host              = 127.0.0.1
    
    # MySQL port to connect with (usually 3306)
    mysql_port              = 3306
    
    # The user under which we connect with MySQL
    mysql_user              = kopano
    
    # The password for the user (leave empty for no password)
    mysql_password          = xxxxxx
    
    # Override the default MySQL socket to access mysql locally
    # Works only if the mysql_host value is empty or 'localhost'
    mysql_socket            =
    
    # Database to connect to
    mysql_database          = kopano
    
    # Where to place attachments. Value can be 'database', 'files' or 's3'
    attachment_storage      = files
    
    # Enable fsync as method to make sure attachments are stored on disk where
    # supported and will not be buffered by OS and/or filesystem. Please note
    # this setting will lower attachment write performance depending on your
    # environment but enhances data safety with disaster recovery.
    # Only affects 'files' attachment storage backend.
    attachment_files_fsync  = yes
    
    # When attachment_storage is 'files', use this path to store the files
    # When attachment_storage is 's3', use this path to set a prefix to all
    # attachment data of a certain cluster, for example 'attach'
    attachment_path         = /var/lib/kopano/attachments
    

    Thanks for your effort.


Log in to reply
 

Looks like your connection to Kopano Community Forum was lost, please wait while we try to reconnect.