Ad Widget

Collapse

cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • just2blue4u
    Senior Member
    • Apr 2006
    • 347

    #1

    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)

    Hi Forum!

    When zabbix server (and agentd) v1.1beta8 are started (on Fedora Core 4), i get this errors into console:
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
    Krusty told me to check the rights in the logdir, but that's ok there:
    [root@dori zabbix]# ll
    insgesamt 8312
    -rw-rw-rw- 1 zabbix zabbix 1512 7. Apr 09:33 agentd.log
    -rw-r--r-- 1 zabbix zabbix 36309 7. Apr 09:35 server.log
    -rw-rw-rw- 1 zabbix zabbix 8449105 7. Apr 09:34 server.log.old
    -rw-rw-rw- 1 zabbix zabbix 606 6. Apr 14:17 zabbix_trapperd.log
    I didn't find any logfiles containing that errormessage.
    When turning zabbix off, the errors don't appear...

    Can somebody please help ?

    thx,
    j2b4u
    Big ZABBIX is watching you!
    (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)
  • xaitax
    Member
    • Apr 2006
    • 39

    #2
    Console-Errors like this appear if you have some commands executing in zabbix_agentd.conf as items, wich are not correctly.

    What does
    Code:
    # grep "cat" /$path/zabbix_agentd.conf
    tell you?

    P.S: german-languaged linux'es are bad!
    I rememeber in
    Code:
    /dev/hdx ist eingehaengt auf ...
    messages.

    - xai
    Last edited by xaitax; 07-04-2006, 09:58.

    Comment

    • just2blue4u
      Senior Member
      • Apr 2006
      • 347

      #3
      [root@dori zabbix]# grep "cat" /etc/zabbix/zabbix_agentd.conf
      [root@dori zabbix]# grep "cat" /etc/zabbix/zabbix_agent.conf
      [root@dori zabbix]#
      i didn't add / activate anything in ####### USER-DEFINED MONITORED PARAMETERS #######...


      ...

      and yes, you're right! Denglish-Linux sometimes talks bullshit! :P
      Big ZABBIX is watching you!
      (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

      Comment

      • xaitax
        Member
        • Apr 2006
        • 39

        #4
        Strange...
        Did u use precompiled binaries or did u compiled them yourself?

        - xai

        Comment

        • just2blue4u
          Senior Member
          • Apr 2006
          • 347

          #5
          i compiled them by myself (no zabbix RPMs later than 1.0.2 for Fedora core 4 available)
          Big ZABBIX is watching you!
          (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

          Comment

          • xaitax
            Member
            • Apr 2006
            • 39

            #6
            Last idea I have:

            Do you use relative or abosulte path for logging to file in zabbix_agentd.log?

            - xai

            Comment

            • just2blue4u
              Senior Member
              • Apr 2006
              • 347

              #7
              cat /etc/zabbix/zabbix_agentd.conf | grep log
              # Name of log file.
              # If not set, syslog will be used
              #LogFile=/tmp/zabbix_agentd.log
              LogFile=/var/log/zabbix/agentd.log
              [root@dori zabbix-1.1beta8]#
              sorry, absolute paths.

              I turned the log level to absolute verbosity (4), but even the agentd.log doesn't show any mysterious lines...
              Big ZABBIX is watching you!
              (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

              Comment

              • xaitax
                Member
                • Apr 2006
                • 39

                #8
                Let him try logging to syslog -> so we see if error still occurs.
                If so, we can exclude, logging engine fails.

                - xai

                Comment

                • just2blue4u
                  Senior Member
                  • Apr 2006
                  • 347

                  #9
                  i commented the logfile-line in conf while staying in loglevel 4, but i don't get anything onto console...
                  Big ZABBIX is watching you!
                  (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

                  Comment

                  Working...