Opened 8 years ago

Closed 7 years ago

#1449 closed defect (duplicate)

socket.error: [Errno 13] Permission denied

Reported by: jreed Owned by:
Priority: low Milestone:
Component: ~msgq (obsolete) Version:
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

Description (last modified by jreed)

BIND 10 should not be so noisy if --user user doesn't have permission:

2011-12-02 08:42:24.600 DEBUG [b10-boss.boss] BIND10_STARTED_PROCESS_PID started b10-msgq (PID 23167)
Traceback (most recent call last):
  File "/home/reed/builder/work/BIND10/20111201141511-NetBSD5-i386/install/libexec/bind10-devel/b10-msgq", line 545, in <module>
    setup_result = msgq.setup()
  File "/home/reed/builder/work/BIND10/20111201141511-NetBSD5-i386/install/libexec/bind10-devel/b10-msgq", line 194, in setup
    self.setup_listener()
  File "/home/reed/builder/work/BIND10/20111201141511-NetBSD5-i386/install/libexec/bind10-devel/b10-msgq", line 180, in setup_listener
    raise e
  File "/home/reed/builder/work/BIND10/20111201141511-NetBSD5-i386/install/libexec/bind10-devel/b10-msgq", line 173, in setup_listener
    self.listen_socket.bind(self.socket_file)
socket.error: [Errno 13] Permission denied
2011-12-02 08:42:29.771 ERROR [b10-boss.boss] BIND10_COMPONENT_START_EXCEPTION component msgq failed to start: Unable to connect to c-channel after 5 seconds
2011-12-02 08:42:29.771 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED component msgq (pid None) failed with unknown exit status

Instead of traceback it should have a clear BIND 10 log message.

By the way, why "unknown" exit status?

Subtickets

Change History (4)

comment:1 Changed 8 years ago by jreed

  • Description modified (diff)

comment:2 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Year 3 Task Backlog

The "unknown" exit status is no longer used in the latest code, as far as I can see.

Agree about the msgq traceback.

comment:3 Changed 8 years ago by jreed

This is similar to #1597.

comment:4 Changed 7 years ago by jinmei

  • Resolution set to duplicate
  • Status changed from new to closed

This should have been resolved in #2447.

Note: See TracTickets for help on using tickets.