Ad Widget

Collapse

Problems with suckerd on OpenBSD 3.8

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • slk
    Junior Member
    • Jan 2006
    • 1

    #1

    Problems with suckerd on OpenBSD 3.8

    Hi There,

    I'm trying out Zabbix for the first time and have run into some problems. Hoping someone can help me out.
    My setup is as follows:
    * OpenBSD 3.8
    * PostgreSQL 8.0.3
    * PHP 4.4.1
    * Zabbix 1.0

    I ran into a couple of problems
    1. make would fail due to it not being able to find the Postgres library+header files. configure wouldn't use the CPPFLAGS/LDFLAGS environment variable to add the correct directories. I solved this by editing the configure file by hand There must be a cleaner way to do this...
    2. PHP parser complained: [error] PHP Warning: Call-time pass-by-reference has been deprecated - argument passed by value; - I fixed this by setting the allow_call_time_pass_reference variable in php.ini. The web interface is now working.

    3. I'm now struggling with the following error in zabbix_suckerd:

    018766:20060126:155451 Starting zabbix_suckerd...
    018766:20060126:155451 zabbix_suckerd #0 started [Housekeeper]
    021451:20060126:155451 zabbix_suckerd #2 started [nodata() calculator]
    009979:20060126:155452 zabbix_suckerd #1 started [Alerter]
    026045:20060126:155452 zabbix_suckerd #3 started [ICMP pinger]
    004940:20060126:155452 zabbix_suckerd #4 started [Sucker. SNMP:ON]
    009979:20060126:155452 Query::select a.alertid,a.mediatypeid,a.sendto,a.subject,a.messa ge,a.status,a.retries,mt.mediatypeid,mt.type,mt.de scription,mt.smtp_server,mt.smtp_helo,mt.smtp_emai l,mt.exec_path from alerts a,media_type mt where a.status=0 and a.retries<3 and a.mediatypeid=mt.mediatypeid order by a.clock
    009979:20060126:155452 Query failed:PGRES_FATAL_ERROR
    018766:20060126:155452 One child process died. Exiting ...
    018766:20060126:155452 Cannot kill process. PID=[9979] [No such process]
    021451:20060126:155452 Got QUIT or INT or TERM or PIPE signal. Exiting...
    026045:20060126:155452 Got QUIT or INT or TERM or PIPE signal. Exiting...
    004940:20060126:155452 Got QUIT or INT or TERM or PIPE signal. Exiting...

    The Postgres log shows the following:
    LOG: could not send data to client: Broken pipe
    LOG: unexpected EOF on client connection

    The first few times I tried to start suckerd, I got these errors. It finally started and ran for a few hours, and it's now back to not starting at all. Any ideas on how to proceed troubleshooting this would be appreciated.

    thanks,
    -Stephen
    Last edited by slk; 27-01-2006, 17:53. Reason: wrong word
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    It looks like Postgresql was unable to process the query because of some unknown reason. I would suggest to check Postgresql logs to see if there are any issues.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    Working...