Opened 8 years ago

Closed 6 years ago

#1734 closed defect (wontfix)

ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED component ... failed with 0 exit status

Reported by: jreed Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: ~Boss of BIND (obsolete) Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


I noticed this when I restart resolver and auth as in #1733.

I did:

> Resolver shutdown
> Auth shutdown

The logs showed:

2012-02-29 15:23:40.820 DEBUG [] CC_GROUP_SEND sending message '{  "command": [ "stopping", { "module_name": "Resolver" } ] }' to group 'ConfigManager'
2012-02-29 15:23:40.820 INFO  [b10-resolver.resolver] RESOLVER_SHUTDOWN resolver  shutdown complete
2012-02-29 15:23:40.827 DEBUG [b10-cmdctl.cmdctl] CMDCTL_COMMAND_SENT command 'shutdown' to module 'Resolver' was sent
2012-02-29 15:23:40.828 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process 11275 of b10-resolver ended with status 0
2012-02-29 15:23:40.828 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED component b10-resolver (pid 11275) failed with 0 exit status
2012-02-29 15:23:40.828 INFO  [b10-boss.boss] BIND10_COMPONENT_START component b10-resolver is starting

Notice the "ERROR" for 0 exit status. That seems wrong. I don't see any error here.


2012-02-29 15:23:45.847 DEBUG [b10-auth.datasrc] DATASRC_SQLITE_CLOSE closing SQLite database
2012-02-29 15:23:45.848 DEBUG [b10-auth.datasrc] DATASRC_CACHE_DESTROY destroying the hotspot cache
2012-02-29 15:23:45.848 DEBUG [b10-cmdctl.cmdctl] CMDCTL_COMMAND_SENT command 'shutdown' to module 'Auth' was sent
2012-02-29 15:23:45.868 INFO  [b10-boss.boss] BIND10_LOST_SOCKET_CONSUMER consumer 17 of sockets disconnected, considering all its sockets closed
2012-02-29 15:23:45.870 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED process 12084 of b10-auth ended with status 0
2012-02-29 15:23:45.870 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED component b10-auth (pid 12084) failed with 0 exit status
2012-02-29 15:23:45.870 INFO  [b10-boss.boss] BIND10_COMPONENT_START component b10-auth is starting

Same thing again: ERROR for 0 exit status.

These don't seem to be errors to me.


Change History (4)

comment:1 Changed 8 years ago by vorner

well, the resolver/auth peacefully exits after receiving the command. however, the boss does not know about the command and the process exits without it expecting it, therefore it thinks it failed. the error message is correct in that sense, because i did see a component to catch fatal exception and exit with 0 code (which is bug, of course, but the component still wants to be restarted, etc). so, there's nothing happening we wouldn't know about.

But I can see it is confusing for users, so we should do something about it. The long term would be making the shutdown command invisible, and making sure all the starting/stopping/restarting is done by Boss (which would have commands asking it to do it).

comment:2 Changed 8 years ago by shane

  • Milestone New Tasks deleted

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check

Closing ticket.

Note: See TracTickets for help on using tickets.