Ad Widget

Collapse

1.4.1 zabbix-agentd not working on SLES 9.3

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • marc
    Senior Member
    • Oct 2004
    • 146

    #16
    if server is down, its working btw. so memory problem must be related with fetching active checks from server. unfortunately i had no time at the moment to build complete lab.

    Comment

    • fmtaylor2
      Member
      • May 2006
      • 66

      #17
      same here

      I don't have anything to add. 1.4.0 agent worked. 1.4.1 agent is borked.

      Comment

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

        #18
        Originally posted by fmtaylor2
        I don't have anything to add. 1.4.0 agent worked. 1.4.1 agent is borked.
        What is your platform?
        Alexei Vladishev
        Creator of Zabbix, Product manager
        New York | Tokyo | Riga
        My Twitter

        Comment

        • fmtaylor2
          Member
          • May 2006
          • 66

          #19
          RHEL5
          [root@boris zabbix-1.4]# uname -a
          Linux boris.itap.purdue.edu 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 x86_64 x86_64 GNU/Linux

          Also, I had the 1.4.0 agent still available on this system, which started and ran fine. The 1.4.1 agent will not (same error as indicated). Both compiled on the same system with the same config options.

          Comment

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

            #20
            Thanks for the additional details. I appreciate it very much!
            Alexei Vladishev
            Creator of Zabbix, Product manager
            New York | Tokyo | Riga
            My Twitter

            Comment

            • schiinke
              Junior Member
              • Jul 2007
              • 20

              #21
              Hi guys,

              I'm using Suse 9.3 and I got the message below:

              ./zabbix_agentd start
              : bad interpreter: No such file or directory
              I don't know why because the line . /etc/rc.status is already corrected with a one dot as described above.

              Please, see below my zabbix_agentd file:

              #! /bin/sh
              # Copyright (c) 07/2004 A.Tophofen, Germany
              # Modified for Zabbix 1.1alpha7 and SuSE Linux 9.2
              # April 2005, A. Kiepe, Switzerland
              #
              # init.d/zabbix_agentd
              #
              ### BEGIN INIT INFO
              # Provides: zabbix_agentd
              # Required-Start: $network $remote_fs $syslog
              # Required-Stop:
              # Default-Start: 3
              # Default-Stop:
              # Description: Starts Zabbix_Agentd
              ### END INIT INFO

              . /etc/rc.status
              rc_reset
              NAME="zabbix_agentd"
              CONFIG_FILE="/etc/zabbix/zabbix_agentd.conf"

              if [ ! -f ${CONFIG_FILE} ]; then
              echo -n "${NAME}configuration file ${CONFIG_FILE} does not exist. "
              # Tell the user this has skipped
              rc_status -s
              exit 6
              fi

              ZABBIX_BIN="/opt/zabbix/bin/zabbix_agentd"
              ZABBIX_PID="/var/tmp/zabbix_agentd.pid"


              if [ ! -x ${ZABBIX_BIN} ] ; then
              echo -n "${ZABBIX_BIN} not installed! "
              # Tell the user this has skipped
              rc_status -s
              exit 5
              fi


              export PATH=$PATH:/opt/zabbix/bin

              case "$1" in
              start)
              echo -n "Starting ${NAME} "
              checkproc -p ${ZABBIX_PID} ${ZABBIX_BIN}
              case $? in
              0) echo -n "- Warning: ${NAME} already running! " ;;
              1) echo -n "- Warning: ${ZABBIX_PID} exists! " ;;
              esac

              startproc -p ${ZABBIX_PID} -u zabbix ${ZABBIX_BIN}
              rc_status -v
              ;;
              stop)
              echo -n "Shutting down ${NAME}"
              checkproc -p ${ZABBIX_PID} ${ZABBIX_BIN} || echo -n "- Warning: ${NAME} not running! "
              killproc -p ${ZABBIX_PID} -TERM ${ZABBIX_BIN}
              rc_status -v
              ;;
              restart)
              $0 stop
              $0 start
              rc_status
              ;;
              *)
              echo "Usage: $0 {start|stop|restart}"
              exit 1
              ;;
              esac
              rc_exit

              Any light?

              Thanks,

              Comment

              Working...