Opened 7 years ago

Closed 3 years ago

#360 closed defect (wontfix)

socket.error: AF_UNIX path too long

Reported by: jreed Owned by: UnAssigned
Priority: medium Milestone: Sprint-20131001
Component: ~msgq (obsolete) Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

bash-3.00$ ./install/libexec/bind10-devel/b10-msgq --verbose
[b10-msgq] MsgQ v20091030 (Paving the DNS Parking Lot)
Traceback (most recent call last):
  File "./install/libexec/bind10-devel/b10-msgq", line 436, in <module>
    setup_result = msgq.setup()
  File "./install/libexec/bind10-devel/b10-msgq", line 171, in setup
    self.setup_listener()
  File "./install/libexec/bind10-devel/b10-msgq", line 157, in setup_listener
    raise e
  File "./install/libexec/bind10-devel/b10-msgq", line 150, in setup_listener
    self.listen_socket.bind(self.socket_file)
socket.error: AF_UNIX path too long

(same with gcc or sunstudio build)

Subtickets

Change History (13)

comment:1 Changed 7 years ago by jreed

comment:2 Changed 7 years ago by jreed

$ echo -n  /export/home/users/jreed/builder/work/BIND10/20101004002000-Solaris10-sparc/install/var/bind10-devel/msgq_socket | wc -c
     112

(I added a simple write to the code to see this long path.)

comment:3 Changed 7 years ago by jreed

  • Summary changed from msqg on Solaris: socket.error: AF_UNIX path too long to socket.error: AF_UNIX path too long

Same issue on Mac OS X system:

File "/Local/Users?/jreed/builder/work/BIND10/20110224081500-MacOSX10.6-x86_64-GCC/install/libexec/bind10-devel/b10-msgq", line 174, in setup_listener

self.listen_socket.bind(self.socket_file)

socket.error: AF_UNIX path too long

comment:4 Changed 7 years ago by jreed

Also same problem on FreeBSD.

comment:5 Changed 6 years ago by jreed

  • Defect Severity set to N/A
  • Sub-Project set to DNS

Note this problem is for xfrout's socket also.

comment:6 Changed 6 years ago by jreed

We hit this issue again this week with the lettuce build. I worked around it by using less and shorter directory names.

Jelte suggested we can try to be smart and use a different filename or even a different path if the specified one is too long ("but that's against my 'do what i say' preference :)") and we can also try to detect it sooner if possible.

comment:7 Changed 6 years ago by jreed

Traceback (most recent call last):
  File "/home/jreed/builder/work/BIND10/20120213221701-DebianLinux-x86_64-GCC/install/libexec/bind10-devel/b10-xfrout", line 1040, in <module>
    xfrout_server = XfroutServer()
  File "/home/jreed/builder/work/BIND10/20120213221701-DebianLinux-x86_64-GCC/install/libexec/bind10-devel/b10-xfrout", line 924, in __init__
    self._start_xfr_query_listener()
  File "/home/jreed/builder/work/BIND10/20120213221701-DebianLinux-x86_64-GCC/install/libexec/bind10-devel/b10-xfrout", line 933, in _start_xfr_query_listener
    self._cc)
  File "/home/jreed/builder/work/BIND10/20120213221701-DebianLinux-x86_64-GCC/install/libexec/bind10-devel/b10-xfrout", line 634, in __init__
    ThreadingUnixStreamServer.__init__(self, sock_file, handle_class)
  File "/usr/lib/python3.2/socketserver.py", line 408, in __init__
    self.server_bind()
  File "/usr/lib/python3.2/socketserver.py", line 419, in server_bind
    self.socket.bind(self.server_address)
socket.error: AF_UNIX path too long

comment:8 Changed 4 years ago by muks

  • Milestone set to Sprint-20130903
  • Summary changed from socket.error: AF_UNIX path too long to [kean] socket.error: AF_UNIX path too long

comment:9 Changed 4 years ago by kean

  • Owner set to kean
  • Status changed from new to accepted

comment:10 Changed 4 years ago by kean

  • Milestone changed from Sprint-20131015 to Sprint-20131001
  • Owner changed from kean to UnAssigned
  • Status changed from accepted to reviewing

comment:11 Changed 4 years ago by kean

Changed configure to check the socket path length and produce an error if it is too long. Provided a --with-socket-directory option to allow the user to configure an alternate path if the default path is too long.

comment:12 Changed 4 years ago by jreed

  • Summary changed from [kean] socket.error: AF_UNIX path too long to socket.error: AF_UNIX path too long

comment:13 Changed 3 years ago by tomek

  • Resolution set to wontfix
  • Status changed from reviewing 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 http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.