*New 11.3 series Release:
2019-10-19: XigmaNAS 11.3.0.4.7014 - released

*New 12.0 series Release:
2019-10-05: XigmaNAS 12.0.0.4.6928 - released!

*New 11.2 series Release:
2019-09-23: XigmaNAS 11.2.0.4.6881 - released!

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

Zeroconf mDNSResponder limited to 4 AFP shares??

NAS4Free & Apple Filing Protocol.
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
bafforosso
Starter
Starter
Posts: 18
Joined: 05 Jun 2013 23:01
Status: Offline

Zeroconf mDNSResponder limited to 4 AFP shares??

#1

Post by bafforosso » 24 Jun 2015 17:19

Hello,

while configuring a new Nas4Free server where multiple users (8 at the moment) need to backup their files from their own computer I hit a wall :
adding more than 4 AFP share would stop Zeroconf/Bonjour from working (with 4 share or less everything is fine)!?!

Digging a bit I found that mDNSResponderPosix would not start if there are more than 4 AFP shares defined in mdnsresponder.conf, it would read the 4 first shares defined, start the service, then read the definition of the 5th share and crash with an error (no kidding?). See here :

Code: Select all

nas4free: ~ # /usr/local/bin/mDNSResponderPosix -v 2 -f /var/etc/mdnsresponder.conf
[...]
Service name: "Backup Server"
Service type: "_adisk._tcp."
Service domain: "local"
Service port: 9
Text string: "sys=waMA=0,adVF=0x100"
Text string: "dk0=adVF=0xa1,adVN=Archived TM,adVU=182779de-8536-4db1-be96-1fb9fdc0f692"
Text string: "dk1=adVN=Test1,adVU=7e1047e1-850d-4547-b81a-0d72a7f68102"
Text string: "dk2=adVN=Test2,adVU=553341ef-daf3-470a-a2af-8358e9f72f3e"
Text string: "dk3=adVN=Videos,adVU=bd8b16ee-8ed6-4158-af5f-3215941faaa6"
mDNSResponderPosix: Registered service 4, name "Backup Server", type "_adisk._tcp.", domain "local",  port 9
Service name: "dk4=adVN=Test3,adVU=39690bc7-83f4-40a9-89da-21f697c19b8a"
mDNSResponderPosix: Error reading service file /var/etc/mdnsresponder.conf
Is this behaviour normal?

Is there some way to fix/bypass this???


P.S: I'm running Nas4Free beta 10.1.0.2.1665 on this machine.

Thanks,
Fred "Bafforosso"
System 1:
  • Case: Lian Li PC-Q25B Mini-ITX
    Motherboard + CPU: ASRock C2550D4I with Intel Quad-Core Avoton C2550 @2.4GHz
    RAM: 2x 8GB 1600MHz ECC DDR3L
    Hard Drives: 6x 2TB SATA3 in Raid-Z2

System 2:
  • Case: CoolerMaster Force 500
    Motherboard + CPU: SuperMicro X9SCL with Intel Xeon E3-1230 @ 3.2GHz
    RAM: 3x 4GB 1600MHz DDR3
    Hard Drives: 6x 3TB SATA3 in Raid-Z2

User avatar
zoon01
Developer
Developer
Posts: 768
Joined: 20 Jun 2012 21:06
Location: Netherlands
Contact:
Status: Offline

Re: Zeroconf mDNSResponder limited to 4 AFP shares??

#2

Post by zoon01 » 28 Jun 2015 00:46

Hi,

Try build 10.1.0.2.1701
That build should fix this problem.
System specs: XigmaNAS 11.2.0.4 -embedded on Samsung 860 EVO 256GB and Supermicro X10SL7-F w / Bios v3.2, IPMI v.03.84 / CPU E3-1241 v3 @ 3.50GHz - 32GB Crucial DDR3L 1600mhz ECC 1.35v , LSI 2308 on PH20.00.07.00 IT mode, Storage: 5x Western Digital Red (WD30EFRX) raidz

Development system is same system in virtualbox.

bafforosso
Starter
Starter
Posts: 18
Joined: 05 Jun 2013 23:01
Status: Offline

Re: Zeroconf mDNSResponder limited to 4 AFP shares??

#3

Post by bafforosso » 29 Jun 2015 11:41

thanks, but unfortunately still no luck on 10.1.0.2.1702 :

Code: Select all

 nas4free: ~# /usr/local/bin/mDNSResponderPosix -v 2 -f /var/etc/mdnsresponder.conf
[...]
Service name: "Backup Server"
Service type: "_adisk._tcp."
Service domain: "local"
Service port: 9
Text string: "sys=waMA=0,adVF=0x100"
Text string: "dk0=adVF=0xa1,adVN=Test1,adVU=3a5703a9-4716-4767-a5d3-8b56ee448aa4"
Text string: "dk1=adVF=0xa1,adVN=Test2,adVU=182779de-8536-4db1-be96-1fb9fdc0f692"
Text string: "dk2=adVF=0xa1,adVN=Test3,adVU=2853c7ae-451d-45ca-b4eb-a31decdc49ff"
Text string: "dk3=adVN=Test4,adVU=bd8b16ee-8ed6-4158-af5f-3215941faaa6"
mDNSResponderPosix: Registered service 3, name "Backup Server", type "_adisk._tcp.", domain "local",  port 9
Service name: "dk4=adVF=0xa1,adVN=Test5,adVU=a74ba523-ed4e-4991-8498-707c7af33370"
mDNSResponderPosix: Error reading service file /var/etc/mdnsresponder.conf

P.S: same results first with WebGUI upgrade from 10.1.0.2.1665 then with clean 10.1.0.2.1702 install.
System 1:
  • Case: Lian Li PC-Q25B Mini-ITX
    Motherboard + CPU: ASRock C2550D4I with Intel Quad-Core Avoton C2550 @2.4GHz
    RAM: 2x 8GB 1600MHz ECC DDR3L
    Hard Drives: 6x 2TB SATA3 in Raid-Z2

System 2:
  • Case: CoolerMaster Force 500
    Motherboard + CPU: SuperMicro X9SCL with Intel Xeon E3-1230 @ 3.2GHz
    RAM: 3x 4GB 1600MHz DDR3
    Hard Drives: 6x 3TB SATA3 in Raid-Z2

bafforosso
Starter
Starter
Posts: 18
Joined: 05 Jun 2013 23:01
Status: Offline

Re: Zeroconf mDNSResponder limited to 4 AFP shares??

#4

Post by bafforosso » 10 Jul 2015 15:49

Partly solved at commit r1703 :

works perfectly for an unlimited number of AFP shares without TimeMachine support, but still limited to 4 shares with TimeMachine support.
System 1:
  • Case: Lian Li PC-Q25B Mini-ITX
    Motherboard + CPU: ASRock C2550D4I with Intel Quad-Core Avoton C2550 @2.4GHz
    RAM: 2x 8GB 1600MHz ECC DDR3L
    Hard Drives: 6x 2TB SATA3 in Raid-Z2

System 2:
  • Case: CoolerMaster Force 500
    Motherboard + CPU: SuperMicro X9SCL with Intel Xeon E3-1230 @ 3.2GHz
    RAM: 3x 4GB 1600MHz DDR3
    Hard Drives: 6x 3TB SATA3 in Raid-Z2

User avatar
daoyama
Developer
Developer
Posts: 423
Joined: 25 Aug 2012 09:28
Location: Japan
Status: Offline

Re: Zeroconf mDNSResponder limited to 4 AFP shares??

#5

Post by daoyama » 10 Jul 2015 18:18

bafforosso wrote: works perfectly for an unlimited number of AFP shares without TimeMachine support, but still limited to 4 shares with TimeMachine support.
This is permanent restriction and never fixed.
Ticket #219:
https://sourceforge.net/p/nas4free/bugs/219/
NAS4Free 10.2.0.2.2115 (x64-embedded), 10.2.0.2.2258 (arm), 10.2.0.2.2258(dom0)
GIGABYTE 5YASV-RH, Celeron E3400 (Dual 2.6GHz), ECC 8GB, Intel ET/CT/82566DM (on-board), ZFS mirror (2TBx2)
ASRock E350M1/USB3, 16GB, Realtek 8111E (on-board), ZFS mirror (2TBx2)
MSI MS-9666, Core i7-860(Quad 2.8GHz/HT), 32GB, Mellanox ConnectX-2 EN/Intel 82578DM (on-board), ZFS mirror (3TBx2+L2ARC/ZIL:SSD128GB)
Develop/test environment:
VirtualBox 512MB VM, ESXi 512MB-8GB VM, Raspberry Pi, Pi2, ODROID-C1

bafforosso
Starter
Starter
Posts: 18
Joined: 05 Jun 2013 23:01
Status: Offline

Re: Zeroconf mDNSResponder limited to 4 AFP shares??

#6

Post by bafforosso » 13 Jul 2015 09:35

daoyama wrote:This is permanent restriction and never fixed.
Ticket #219:
https://sourceforge.net/p/nas4free/bugs/219/
Ok thanks for the info.

It may be a good idea to restrict maximum TimeMachine share to 4 in the WebGUI with a message to avoid confusion.
System 1:
  • Case: Lian Li PC-Q25B Mini-ITX
    Motherboard + CPU: ASRock C2550D4I with Intel Quad-Core Avoton C2550 @2.4GHz
    RAM: 2x 8GB 1600MHz ECC DDR3L
    Hard Drives: 6x 2TB SATA3 in Raid-Z2

System 2:
  • Case: CoolerMaster Force 500
    Motherboard + CPU: SuperMicro X9SCL with Intel Xeon E3-1230 @ 3.2GHz
    RAM: 3x 4GB 1600MHz DDR3
    Hard Drives: 6x 3TB SATA3 in Raid-Z2

Post Reply

Return to “AFP”