Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#1018 closed defect (fixed)

resolver will not start: RESOLVER_FAILED, resolver failed, reason: module_name missing in { }

Reported by: jreed Owned by: UnAssigned
Priority: very high Milestone: Sprint-20110628
Component: resolver Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Very High
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 2.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by jreed)

Trying to start BIND 10 as a resolver fails:

2011-06-16 10:23:05.993 DEBUG [b10-resolver.resolver] RESOLVER_QUSETUP, query setup
2011-06-16 10:23:06.002 FATAL [b10-resolver.resolver] RESOLVER_FAILED, resolver failed, reason: module_name missing in {  }

(This loops.)

My last running resolver was started on June 3, so some problem in past two weeks.

Maybe this ktrace output is useful?

 29455      1 b10-resolver CALL  sendmsg(5,0x7f7fffffc4a0,0)
 29455      1 b10-resolver MISC  msghdr: 48, 0000000000000000000000000000000050c0ffff7f7f0000010000000000000000000000000000000000000000000004
 29455      1 b10-resolver GIO   fd 5 wrote 66 bytes
       "{ \"command\": [ \"get_module_spec\", { \"module_name\": \"Logging\" }\
	 ] }"
 29455      1 b10-resolver RET   sendmsg 66/0x42
 29455      1 b10-resolver CALL  write(4,0x7f7fffffbafc,1)
 29455      1 b10-resolver GIO   fd 4 wrote 1 bytes
       "\0"
 29455      1 b10-resolver RET   write 1
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffbe60,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  write(4,0x7f7fffffbaff,1)
 29455      1 b10-resolver GIO   fd 4 wrote 1 bytes
       "\0"
 29455      1 b10-resolver RET   write 1
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb4e0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __select50(0xa,0x7f7fffffba10,0x7f7fffffba34,0x7f7fffffba58,0x7f7fffffba90)
 29455      1 b10-resolver RET   __select50 1
 29455      1 b10-resolver CALL  read(3,0x7f7fffffb610,0x400)
 29455      1 b10-resolver GIO   fd 3 read 6 bytes
       "\0\0\0\0\0\0"
 29455      1 b10-resolver RET   read 6
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb4e0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb4e0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __select50(0xa,0x7f7fffffba10,0x7f7fffffba34,0x7f7fffffba58,0x7f7fffffba90)
 29455      1 b10-resolver RET   __select50 1
 29455      1 b10-resolver CALL  recvmsg(5,0x7f7fffffb510,0)
 29455      1 b10-resolver MISC  msghdr: 48, 0000000000000000000000000000000040b5ffff7f7f0000010000000000000000000000000000000000000000000004
 29455      1 b10-resolver GIO   fd 5 read 4 bytes
       "\0\0\0\M-7"
 29455      1 b10-resolver MISC  msghdr: 48, 0000000000000000000000000000000040b5ffff7f7f0000010000000000000000000000000000000000000000000000
 29455      1 b10-resolver RET   recvmsg 4
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb4e0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __select50(0xa,0x7f7fffffba10,0x7f7fffffba34,0x7f7fffffba58,0x7f7fffffba90)
 29455      1 b10-resolver RET   __select50 0
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb4e0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  write(4,0x7f7fffffbcbc,1)
 29455      1 b10-resolver GIO   fd 4 wrote 1 bytes
       "\0"
 29455      1 b10-resolver RET   write 1
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffc020,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  write(4,0x7f7fffffbcbf,1)
 29455      1 b10-resolver GIO   fd 4 wrote 1 bytes
       "\0"
 29455      1 b10-resolver RET   write 1
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb6a0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __select50(0xa,0x7f7fffffbbd0,0x7f7fffffbbf4,0x7f7fffffbc18,0x7f7fffffbc50)
 29455      1 b10-resolver RET   __select50 2
 29455      1 b10-resolver CALL  read(3,0x7f7fffffb7d0,0x400)
 29455      1 b10-resolver GIO   fd 3 read 2 bytes
       "\0\0"
 29455      1 b10-resolver RET   read 2
 29455      1 b10-resolver CALL  recvmsg(5,0x7f7fffffb6d0,0)
 29455      1 b10-resolver MISC  msghdr: 48, 0000000000000000000000000000000000b7ffff7f7f0000010000000000000000000000000000000000000000000004
 29455      1 b10-resolver GIO   fd 5 read 2 bytes
       "\0\M-""
 29455      1 b10-resolver MISC  msghdr: 48, 0000000000000000000000000000000000b7ffff7f7f0000010000000000000000000000000000000000000000000000
 29455      1 b10-resolver RET   recvmsg 2
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb6a0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __select50(0xa,0x7f7fffffbbd0,0x7f7fffffbbf4,0x7f7fffffbc18,0x7f7fffffbc50)
 29455      1 b10-resolver RET   __select50 0
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb6a0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  write(4,0x7f7fffffbcbc,1)
 29455      1 b10-resolver GIO   fd 4 wrote 1 bytes
       "\0"
 29455      1 b10-resolver RET   write 1
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffc020,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  write(4,0x7f7fffffbcbf,1)
 29455      1 b10-resolver GIO   fd 4 wrote 1 bytes
       "\0"
 29455      1 b10-resolver RET   write 1
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb6a0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __select50(0xa,0x7f7fffffbbd0,0x7f7fffffbbf4,0x7f7fffffbc18,0x7f7fffffbc50)
 29455      1 b10-resolver RET   __select50 2
 29455      1 b10-resolver CALL  read(3,0x7f7fffffb7d0,0x400)
 29455      1 b10-resolver GIO   fd 3 read 2 bytes
       "\0\0"
 29455      1 b10-resolver RET   read 2
 29455      1 b10-resolver CALL  recvmsg(5,0x7f7fffffb6d0,0)
 29455      1 b10-resolver MISC  msghdr: 48, 0000000000000000000000000000000000b7ffff7f7f0000010000000000000000000000000000000000000000000004
 29455      1 b10-resolver GIO   fd 5 read 181 bytes
       "{\"instance\": \"*\", \"group\": \"ConfigManager\", \"seq\": 14, \"fro\
	m\": \"4dfa1f84_2@t1.m.reedmedia.net\", \"to\": \"4dfa1fd9_5@t1.m.reed\
	media.net\", \"reply\": 2, \"type\": \"send\"}{\"result\": [0, {}]}"
 29455      1 b10-resolver MISC  msghdr: 48, 0000000000000000000000000000000000b7ffff7f7f0000010000000000000000000000000000000000000000000000
 29455      1 b10-resolver RET   recvmsg 181/0xb5
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb6a0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __select50(0xa,0x7f7fffffbbd0,0x7f7fffffbbf4,0x7f7fffffbc18,0x7f7fffffbc50)
 29455      1 b10-resolver RET   __select50 0
 29455      1 b10-resolver CALL  __gettimeofday50(0x7f7fffffb6a0,0)
 29455      1 b10-resolver RET   __gettimeofday50 0
 29455      1 b10-resolver CALL  __clock_gettime50(0,0x7f7fffffd310)
 29455      1 b10-resolver RET   __clock_gettime50 0
 29455      1 b10-resolver CALL  write(2,0x7f7ffdb07ad8,0x17)
 29455      1 b10-resolver GIO   fd 2 wrote 23 bytes
       "2011-06-16 10:23:06.002"
 29455      1 b10-resolver RET   write 23/0x17
 29455      1 b10-resolver CALL  write(2,0x7f7ffdb02358,1)
 29455      1 b10-resolver GIO   fd 2 wrote 1 bytes
       " "
 29455      1 b10-resolver RET   write 1
 29455      1 b10-resolver CALL  write(2,0x7f7ffd744158,5)
 29455      1 b10-resolver GIO   fd 2 wrote 5 bytes
       "FATAL"
 29455      1 b10-resolver RET   write 5
 29455      1 b10-resolver CALL  write(2,0x7f7ffdb02378,2)
 29455      1 b10-resolver GIO   fd 2 wrote 2 bytes
       " ["
 29455      1 b10-resolver RET   write 2
 29455      1 b10-resolver CALL  write(2,0x7f7ffdb14388,0x15)
 29455      1 b10-resolver GIO   fd 2 wrote 21 bytes
       "b10-resolver.resolver"
 29455      1 b10-resolver RET   write 21/0x15
 29455      1 b10-resolver CALL  write(2,0x7f7ffdb02398,2)
 29455      1 b10-resolver GIO   fd 2 wrote 2 bytes
       "] "
 29455      1 b10-resolver RET   write 2
 29455      1 b10-resolver CALL  write(2,0x7f7ffdb0f878,0x45)
 29455      1 b10-resolver GIO   fd 2 wrote 69 bytes
       "RESOLVER_FAILED, resolver failed, reason: module_name missing in {  }"
 29455      1 b10-resolver RET   write 69/0x45

On a different note (maybe new ticket), we decided long ago to have unique log IDs. This log ID with

"RESOLVER_FAILED", "resolver failed, reason: %1"

generated by

} catch (const std::exception& ex) {
        LOG_FATAL(resolver_logger, RESOLVER_FAILED).arg(ex.what());

is not unique.

This is critical to me ... I am using b10-resolver for my home :)

Subtickets

Change History (10)

comment:1 Changed 8 years ago by jreed

  • Description modified (diff)

comment:2 Changed 8 years ago by jreed

What module_name? Where missing from? What actually has failure?

comment:3 Changed 8 years ago by jelte

  • Owner set to jelte
  • Status changed from new to assigned

comment:4 Changed 8 years ago by jelte

  • Owner changed from jelte to UnAssigned
  • Status changed from assigned to reviewing

fixed, I had forgotten to add logging config plugin and spec for cfgmgr to _DATA in the makefile; diff is:

diff --git a/src/bin/cfgmgr/plugins/Makefile.am b/src/bin/cfgmgr/plugins/Makefil
index 64f9dc3..d1e0f70 100644
--- a/src/bin/cfgmgr/plugins/Makefile.am
+++ b/src/bin/cfgmgr/plugins/Makefile.am
@@ -4,3 +4,4 @@ EXTRA_DIST += logging.spec b10logging.py
 
 config_plugindir = @prefix@/share/@PACKAGE@/config_plugins
 config_plugin_DATA = tsig_keys.py tsig_keys.spec
+config_plugin_DATA += b10logging.py logging.spec

(but also pushed to origin trac1018)

(*edit*: s/=/+=/ as noted by comment:5)

Last edited 8 years ago by jelte (previous) (diff)

comment:5 Changed 8 years ago by jreed

src/bin/cfgmgr/plugins/Makefile.am:6: ... `config_plugin_DATA' previously defined here

so use +=

comment:6 Changed 8 years ago by jreed

Okay that one line addition worked for me (using +=)

comment:7 Changed 8 years ago by jelte

  • Resolution set to fixed
  • Status changed from reviewing to closed

acked on jabber, merged, closing ticket (the exception/error is a more general issue imo)

comment:8 Changed 8 years ago by jreed

#1019 ticket is now opened for the exception/error .

comment:9 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Sprint-20110628

Put onto this sprint as it seems like this work was done during this sprint.

comment:10 Changed 8 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 2
Note: See TracTickets for help on using tickets.