Tagged: 

Viewing 2 reply threads
  • Author
    Posts
    • #15412
      Stefano Grespan
      Participant

        Hello, since some weeks we receive many notifications email with this message: “Error: Timeout of 600 seconds reached, killing child process!”
        It happens about every ten minutes but emails seem correctly fetched so I cannot understand what is the root cause. I’ve checked the communication page and it lists many connections without end time but it is not solved even after a reboot (see image below).

        Version: 10.5

        Thanks

         

      • #15414
        Stefan Abel
        Moderator

          Hello,

          It looks as if the connection to the mail server is set up correctly and receiving mails works, but the mail server doesn’t tell when it ends the connection, so OTOBO doesn’t know it’s done and then it runs into the timeout.

          Cheers
          Stefan

        • #15427
          Stefano Grespan
          Participant

            Thanks for your reply. Do you know if there’s a way to reset all those existing communications? Now Otobo cannot fetch emails anymore and if we try manually the error message is “Email account fetch already fetched by another process”

            We’ve tested from command line:

            docker_admin> docker exec -t -u otobo otobo_web_1 bin/otobo.Console.pl Maint::PostMaster::MailAccountFetch

            Error: unable to register the process in the database. Is another instance still running?

            Using the switch –force-pid the commend runs but necver exits.

            Here are some screenshots:

            Connection-Error
            Connections
            Fetch-Error

            Thanks for your help

        Viewing 2 reply threads
        • You must be logged in to reply to this topic.