Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    [solved] kopano-server[8727]: An error occurred: no access (0xffffff9f)

    Kopano Groupware Core
    2
    3
    284
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dev107
      dev107 last edited by dev107

      Hey there,

      as I had a few difficulties with Kopano (with dagent and spooler), I was trying to fix it with an upgrade to the latest night build (8.7.83.94.5d57d3872-0+45.2) on Debian 9.X

      Now I’m not able to start kopano-server anymore due to the following:

      Sep 30 23:10:45 srv kopano-server[8727]: Starting kopano-server version 8.7.83 (pid 8727 uid 0)
      Sep 30 23:10:45 srv kopano-server[8727]: Using epoll events
      Sep 30 23:10:45 srv kopano-server[8727]: An error occurred: no access (0xffffff9f). Please check logfile syslog:/var/log/kopano/server.log for details.
      Sep 30 23:10:45 srv systemd[1]: kopano-server.service: Main process exited, code=exited, status=255/n/a
      Sep 30 23:10:45 srv systemd[1]: kopano-server.service: Unit entered failed state.
      Sep 30 23:10:45 srv systemd[1]: kopano-server.service: Failed with result 'exit-code'.
      

      Does anybody knows this issue and can help?

      1 Reply Last reply Reply Quote 0
      • jengelh
        jengelh Banned last edited by jengelh

        This can happen if the server_listen (or any related directive) contains unrecognized content.—At least that is one case where I observed it and which needs fixing. Though, that gives me An error occurred: no access (0xffffffea), not fff9f.
        (Adressed by commit kopanocore-8.7.83-101-gb71f17d7e)

        1 Reply Last reply Reply Quote 0
        • dev107
          dev107 last edited by

          @jengelh was a good direction. Actually the cause was that I’ve IPv6 deactivated. I was finally activating IPv6 and it was working.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post