Ticket #54 (assigned defect)

Opened 3 years ago

Last modified 1 year ago

(mod_rrdtool.c.390) rrdtool-write: failed Device not configured

Reported by: anonymous Assigned to: jan (accepted)
Priority: normal Milestone:
Component: mod_rrdtool Version: 1.3.15
Severity: normal Keywords: rrdtool mod_rrdtool freebsd dragonfly
Cc: Blocking:
Need Feedback:

Description

Installed 1.3.12 by manually replacing SIGCLD with SIGCHLD and starting it:

2005-03-03 11:18:32: (log.c.67) server started 2005-03-03 11:19:00: (mod_rrdtool.c.390) rrdtool-write: failed Device not configured 2005-03-03 11:19:00: (server.c.790) one of the triggers failed

It works, but rrd part doesnt.

Attachments

Change History

03/03/2005 12:23:36 PM changed by jan

  • status changed from new to assigned.

Can you provide some more information about the OS you are using ?

If possible generate a strace/ktrace/truss of the startup phase.

03/08/2005 03:10:32 PM changed by tomaz.borstnar@over.net

  • keywords changed from rrdtool mod_rrdtool to rrdtool mod_rrdtool freebsd dragonfly.

FreeBSD 4.11 and DragonFlyBSD (enhanced FreeBSD4-derivative). Tried both from ports and manually and always the same. In both cases.

I even tried removing the old rrd file to see if the problem lies there:

2005-03-08 16:08:23: (log.c.67) server started 2005-03-08 16:09:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:09:00: (server.c.790) one of the triggers failed

So no luck. I will try to get some useful truss output (hopefully).

03/08/2005 03:31:52 PM changed by tomaz.borstnar@over.net

2005-03-08 16:25:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:25:00: (server.c.790) one of the triggers failed 2005-03-08 16:26:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:26:00: (server.c.790) one of the triggers failed 2005-03-08 16:27:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:27:00: (server.c.790) one of the triggers failed 2005-03-08 16:28:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:28:00: (server.c.790) one of the triggers failed 2005-03-08 16:29:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:29:00: (server.c.790) one of the triggers failed 2005-03-08 16:30:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:30:00: (server.c.790) one of the triggers failed 2005-03-08 16:31:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 2005-03-08 16:31:00: (server.c.790) one of the triggers failed

04/20/2005 06:22:37 PM changed by sit@amsterdam.lcs.mit.edu

Here's a snippet from ktrace on FreeBSD 4.8 machine running 1.3.13, and using freebsd-kqueue: 

 57754 rrdtool  0.000011 RET   mmap 1746669568/0x681c1000
 57754 rrdtool  0.000026 CALL  break(0x804d000)
 57754 rrdtool  0.000011 RET   break 0
 57754 rrdtool  0.000025 CALL  break(0x8051000)
 57754 rrdtool  0.000009 RET   break 0
 57754 rrdtool  0.000012 CALL  read(0,0x804d000,0x4000)
 57754 rrdtool  0.000011 GIO   fd 0 read 0 bytes
       ""
 57754 rrdtool  0.000008 RET   read 0
 57754 rrdtool  0.000024 CALL  exit(0)
 57753 lighttpd 0.000344 PSIG  SIGCHLD caught handler=0x804c358 mask=0x0 code=0x0
 57753 lighttpd 0.000018 RET   kevent -1 errno 4 Interrupted system call
 57753 lighttpd 0.000011 CALL  sigreturn(0xbfbff510)
 57753 lighttpd 0.000020 RET   sigreturn JUSTRETURN
 57753 lighttpd 0.000096 CALL  write(0x2,0xbfbfef88,0x4d)
 57753 lighttpd 0.000020 GIO   fd 2 wrote 77 bytes
       "fdevent_freebsd_kqueue.c.104: kqueue failed polling: Interrupted system call
       "
 57753 lighttpd 0.000011 RET   write 77/0x4d
 57753 lighttpd 0.000012 CALL  gettimeofday(0xbfbff6e8,0)
 57753 lighttpd 0.000011 RET   gettimeofday 0
 57753 lighttpd 0.000012 CALL  kevent(0x7,0,0,0x807f000,0x2b58,0xbfbff6c8)
 57753 lighttpd 1.000487 RET   kevent 0
...
 57753 lighttpd 1.000945 RET   kevent 0
 57753 lighttpd 0.000042 CALL  gettimeofday(0xbfbff6e8,0)
 57753 lighttpd 0.000013 RET   gettimeofday 0
 57753 lighttpd 0.000038 CALL  stat(0x80b7780,0xbfbff610)
 57753 lighttpd 0.000011 NAMI  "/var/log/httpd/lighttpd.rrd"
 57753 lighttpd 0.000035 RET   stat -1 errno 2 No such file or directory
 57753 lighttpd 0.000038 CALL  break(0x80ba000)
 57753 lighttpd 0.000016 RET   break 0
 57753 lighttpd 0.000051 CALL  write(0x7,0x80b9000,0x176)
 57753 lighttpd 0.000010 RET   write -1 errno 6 Device not configured
 57753 lighttpd 0.000071 CALL  write(0xa,0x8070780,0x56)
 57753 lighttpd 0.000023 GIO   fd 10 wrote 86 bytes
       "2005-04-20 14:18:00: (mod_rrdtool.c.217) rrdtool-write: failed Device not configured 
       "
 57753 lighttpd 0.000012 RET   write 86/0x56
 57753 lighttpd 0.000010 CALL  write(0xa,0x8070780,0x40)
 57753 lighttpd 0.000011 GIO   fd 10 wrote 64 bytes
       "2005-04-20 14:18:00: (server.c.791) one of the triggers failed 
       "
 57753 lighttpd 0.000011 RET   write 64/0x40
 57753 lighttpd 0.000009 CALL  kevent(0x7,0,0,0x807f000,0x2b58,0xbfbff6c8)

06/11/2005 12:24:21 PM changed by md@hudora.de

I see the same behaviour with 1.3.13 on FreeBSD 5.3-RELEASE-p2. On al Linux box the same configuration (but without kqueue) works.

06/21/2005 10:36:05 PM changed by bwolf@antbear.org

  • version changed from 1.3.12 to 1.3.13.

I also encounter this problem here on FreeBSD 5.4-RELEASE-p2.

06/21/2005 11:19:58 PM changed by bwolf@antbear.org

To conclude: this only happens for me with freebsd-kqueue.

07/02/2005 12:25:52 AM changed by matt at haught.org

  • version changed from 1.3.13 to 1.3.14.

I also have this problem on FreeBSD 6-CURRENT, but I have oddly and accidently found that if I run it in the forground with the -D option it works!

Add/Change #54 ((mod_rrdtool.c.390) rrdtool-write: failed Device not configured)




Change Properties