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

    cannot stop kopano-services

    Kopano Groupware Core
    3
    7
    733
    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.
    • klausguenter
      klausguenter last edited by klausguenter

      Hi there,

      I want to migrate Kopano 8.4.5 on Debian to a new machine.
      To make a backup of the database on the old machine I tried to stop the kopano-services first.
      kopano-server is stoppable without problems.
      But when I try to stop kopano-spooler, kopano-dagent, kopano-gateway etc I get the message:
      “Stopping spooler: kopano-spooler failed!”

      I dont find any reasons for this in the log-files.
      What could be the problem for this?

      Regards,
      KG

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

        Hi Klaus,
        sounds like a problem of the access rights?
        Did you stop the services as root user?
        regards
        Andreas

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

          Hi Andreas,
          yes, I was logged in as root.
          As far as I know there are some files handled by the Services.
          .pid-files or so?
          Maybe the processes have problems accessing these files. What are the normal rights for these files?

          Regards,
          KG

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

            Hi Klaus,
            yep you’re right, they are under:
            /var/run/kopano# ls -la
            insgesamt 20
            drwxrwxr-x 2 kopano kopano 240 Aug 29 22:46 .
            drwxr-xr-x 21 root root 660 Aug 26 17:56 …
            -rw-r–r-- 1 kopano kopano 6 Aug 29 22:46 dagent.pid
            -rw-r–r-- 1 kopano kopano 6 Aug 29 22:46 monitor.pid
            srw-rw---- 1 kopano kopano 0 Aug 29 22:46 prio.sock
            -rw-r–r-- 1 kopano kopano 6 Aug 29 22:46 search.pid
            -rw-rw-rw- 2 kopano kopano 0 Aug 29 22:46 search.pid.lock
            srwx------ 1 kopano kopano 0 Aug 29 22:46 search.sock
            -rw-r–r-- 1 kopano kopano 6 Aug 29 22:46 server.pid
            srw-rw-rw- 1 kopano kopano 0 Aug 29 22:46 server.sock
            -rw-r–r-- 1 kopano kopano 6 Aug 29 22:46 spooler.pid

            They normally belong to the user kopano - if activated in the .cfg files.
            do you find anything under /var/log/syslog oder /var/log/kopano/* ?

            best regards
            Andreas

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

              Hi Andreas,

              I think we come closer to the cause of the problem:
              before using kopano the system was a zarafa.

              In /var/run/kopano there is only
              srw-rw---- 1 root root 0 Aug 29 22:46 prio.sock
              -rw-r–r-- 1 root root 6 Aug 29 22:46 server.pid
              srw-rw-rw- 1 root root 0 Aug 29 22:46 server.sock

              (by the way: is it a big problem when it runs as root?)
              The server-process is the one I can stop without problems.

              The other .pid-files are under /var/run
              -rw-r–r-- 1 root root 6 Aug 29 22:46 zarafa-dagent.pid
              -rw-r–r-- 1 root root 6 Aug 29 22:46 zarafa-gateway.pid
              -rw-r–r-- 1 root root 6 Aug 29 22:46 zarafa-ical.pid
              -rw-r–r-- 1 root root 6 Aug 29 22:46 zarafa-monitor.pid
              -rw-r–r-- 1 root root 6 Aug 29 22:46 zarafa-search.pid
              -rw-r–r-- 1 root root 6 Aug 29 22:46 zarafa-search.pid.lock
              -rw-r–r-- 1 root root 6 Aug 29 22:46 zarafa-spooler.pid

              There are no .sock-files in that directory.
              Maybe they are created only when needed? Or is that the problem?
              (I only use groupware-calendar functionality via Outlook and Mobile Phones. There is no E-Mail traffic or anything else on this server)

              Regards,
              Markus

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

                Hi Markus.
                you should always run the services as non privileged user- for security reasons.
                Did you check the Migration manual? If you switch from zarafa to kopano you have to change the owner etc.
                Even If you “only” sync the calendar entries etc. your Z-push or webapp is pulic available :-).
                My suggestion is to remove to kill the processes and remove the PID Files.
                Than check the owner and try start stop with one single process.

                Best Regards
                Andreas

                p.s. do you know https://www.univention.com/ - If you want to run kopano without much care about administrations this is great :)

                1 Reply Last reply Reply Quote 0
                • marcus.bauch
                  marcus.bauch last edited by

                  Hej.

                  You say “old Debian machine” …which version of Debian is it you run Zarafa?

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