Ad Widget

Collapse

One child process died. Exiting ver 1.4.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • fmtaylor2
    Member
    • May 2006
    • 66

    #1

    One child process died. Exiting ver 1.4.2

    I have 1.4.0 installed and running fine (has been for a while now). The server, its database, and everything have been following the migration path since 1.1.x.

    I tried to upgrade to 1.4.2 today with no joy. Everything compiles just fine, but the server won't stay up. keeps giving me the classic "One child process died. Exiting".

    I applied the "ALTER TABLE trends MODIFY value_max double(24,4);" mysql fixes, but they didn't fix anything.

    Linux boris 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 GNU/Linux

    A roll back to 1.4.0 works fine. Any answers??
  • fmtaylor2
    Member
    • May 2006
    • 66

    #2
    More info

    I also tried the 1.4.3 build from today. It compiled ok, but has the same issue...

    Comment

    • Alexei
      Founder, CEO
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2004
      • 5654

      #3
      I am very interested in more details. Please increase Debug level to 4 and send the whole zabbix_server.log to a l e x @ z a b b i x . c o m after next crash.
      Alexei Vladishev
      Creator of Zabbix, Product manager
      New York | Tokyo | Riga
      My Twitter

      Comment

      • fmtaylor2
        Member
        • May 2006
        • 66

        #4
        done

        logs sent.

        Comment

        • Alexei
          Founder, CEO
          Zabbix Certified Trainer
          Zabbix Certified SpecialistZabbix Certified Professional
          • Sep 2004
          • 5654

          #5
          Thanks for the logs. This is a known (not yet fixed) problem with old syntax of aggreagated checks. As a workaround you may disable aggregate checks or update them to use new syntax described in ZABBIX Manual.
          Alexei Vladishev
          Creator of Zabbix, Product manager
          New York | Tokyo | Riga
          My Twitter

          Comment

          • cbidwell
            Senior Member
            • Aug 2006
            • 127

            #6
            I'm having this same issue. Not quite sure what you mean by disabling aggregate checks. Would that be "active" checks? Bare w/ me as I'm still fairly new to Zabbix. I'm trying to sell my team on Zabbix as opposed to Big Brother.

            Comment

            • fmtaylor2
              Member
              • May 2006
              • 66

              #7
              The short answer

              Originally posted by Alexei
              Thanks for the logs. This is a known (not yet fixed) problem with old syntax of aggreagated checks. As a workaround you may disable aggregate checks or update them to use new syntax described in ZABBIX Manual.
              Thanks, I finally got around to fixing this issue. For those who haven't figured it out yet, to fix your aggreagated checks, change parentheses to square brackets and change single quotes to double quotes and you should be good to go.

              Comment

              • twydyn
                Junior Member
                • Feb 2008
                • 4

                #8
                Can someone please tell me which file i need to edit in order to fix this? I am looking at the manual and i cannot find where i need to make the change. Any details on this issue will be greatly appreciated. thanks!

                Comment

                • twydyn
                  Junior Member
                  • Feb 2008
                  • 4

                  #9
                  nobody has the solution to this problem?

                  Does anyone have a howto for fixing this issue? Appears a few of us are affected but noone will give a detailed fix.

                  Thanks in advance.

                  Comment

                  • tahir.bhatti
                    Member
                    • Dec 2006
                    • 56

                    #10
                    Use zabbix-1.4.4, the problem will be solved.

                    Comment

                    • ashuji
                      Member
                      • Dec 2008
                      • 35

                      #11
                      I am using new syntax but still problem exist

                      Hi

                      I am using new syntax for grpsum but still this problem persisit, below here is the new syntax I have applied, please suggest if any change required:

                      grpsum["Job_Servers","jmx[PGiCOS:name=jobManager][TotalJobsProcessed]","last","0"]

                      Comment

                      • treelowa
                        Junior Member
                        • Apr 2010
                        • 6

                        #12
                        I am using a 1.8.2 and I get errors whenever I try enable monitoring via the admin/config/hosts web page. As soon as enable monitoring the zabbix_server processes die.

                        I am very very frustrated with this as I have come to a dead end now! I don't know where to turn. I think I may be moving to a different product if I cant get this resolved.

                        Comment

                        Working...