BIND 10 #530: msgq error message for unable to create socket
BIND 10 Development
do-not-reply at isc.org
Mon Jan 24 20:43:45 UTC 2011
#530: msgq error message for unable to create socket
------------------------------+---------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: msgq | Keywords:
Sensitive: 0 | Estimated Number of Hours: 0
Add Hours to Ticket: 0 | Billable?: 1
Total Hours: 0 | Internal?: 0
------------------------------+---------------------------------
{{{
File "/home/reed/opt/bind10/sbin/bind10", line 544, in startup
self.start_all_processes(c_channel_env)
File "/home/reed/opt/bind10/sbin/bind10", line 485, in
start_all_processes
self.start_msgq(c_channel_env)
File "/home/reed/opt/bind10/sbin/bind10", line 343, in start_msgq
raise CChannelConnectError("Unable to connect to c-channel after 5
seconds")
__main__.CChannelConnectError: Unable to connect to c-channel after 5
seconds
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/reed/opt/bind10/sbin/bind10", line 899, in <module>
main()
File "/home/reed/opt/bind10/sbin/bind10", line 838, in main
startup_result = boss_of_bind.startup()
File "/home/reed/opt/bind10/sbin/bind10", line 546, in startup
self.kill_started_processes()
File "/home/reed/opt/bind10/sbin/bind10", line 263, in
kill_started_processes
self.processes[pid].process.kill()
File "/usr/pkg/lib/python3.1/subprocess.py", line 1337, in kill
self.send_signal(signal.SIGKILL)
File "/usr/pkg/lib/python3.1/subprocess.py", line 1327, in send_signal
os.kill(self.pid, sig)
OSError: [Errno 3] No such process
}}}
Verbose mode gave me more information:
{{{
File "/home/reed/opt/bind10/libexec/bind10-devel/b10-msgq", line 156, in
setup_listener
self.listen_socket.bind(self.socket_file)
socket.error: [Errno 13] Permission denied
}}}
But didn't give me the path.
msgq should give a clear error message that says the path without the
python noise.
bind10 should also not have any traceback. It should say that the msgq
exited.
And why SIGKILL? (versus friendlier signal)
(I know the problem with msgq, but that is unrelated to this ticket.)
--
Ticket URL: <http://bind10.isc.org/ticket/530>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list