Bug 47022 - Wrong interface name in Samba config
Wrong interface name in Samba config
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-16 16:34 CEST by Nico Stöckigt
Modified: 2021-05-14 16:34 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.034
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018041821000191
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2018-05-16 16:34:12 CEST
In a customer's environment I struggled on the following warning while facing issues with samba internal dns resolution.

============================================================
[2018/05/16 23:14:22.313696,  3, pid=20964, effective(0, 0), real(0, 0)] ../lib/util/util_net.c:256(interpret_string_addr_internal)
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.  interpret_string_addr_internal: getaddrinfo failed for name eth0_1 (flags 32) [Name or service not known]
[2018/05/16 23:14:22.313764,  2, pid=20964, effective(0, 0), real(0, 0)] ../source4/lib/socket/interface.c:195(interpret_interface)
  interpret_interface: Can't find address for eth0_1
============================================================

The give interface is known as eth0:1 to the system

============================================================
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:03:34:bd brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.20/24 brd 192.168.11.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.11.10/24 brd 192.168.11.255 scope global secondary eth0:1
       valid_lft forever preferred_lft forever
============================================================

This seems simply to be wrong.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:41:55 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.