FreeNAS 9.3 miniDLNA network issues

[Lyubomir B]

I have installed a month ago a minidlna server into an own jail based on the https://forums.freenas.org/index.php?threads/how-to-install-minidlna-on-freenas-9-3-prior-to-plugin.25395/

At first everything was working as expected. All of a sudden after a reboot the jail could not be reached over the network. Pinging the FreeNAS box was always successfull and the SSH granted but not for the jail itself. I found out that after every reboot i need to go to the network settings into the GUI of the NAS box hit the edit for the Network Adapter just hit OK again to restart the network adapter and then the Minidlna jail would be reacheable over the network. I admit stupid workaround but since i do not reboot the box ofter i wouldnt mind.

The second issue i got after the latest bugfix update for the FreeNAS. The minidlna server just stops working after a while. When i try to access it and play movies or music the CPU meter into top gets overloaded slowly but constantly up to 100% and the log from freenas shows : "sonewconn: pcb 0xfffffe000c32aab8: Listen queue overflow: 12 already in queue awaiting acceptance". And after a while the minidlna service would terminate of itself forcing me to restart it again.

Which wasnt the case before the update no matter if i was listening to music and streaming a movie at the same time.

 

[dlavigne]

Hardware? Anything in /var/log/messages?

 

[Lyubomir B]

Hardware? Anything in /var/log/messages?

So the Hardware is as follows:

CPU: Intel(R) Pentium(R) CPU G2030T @ 2.60GHz (2594.16-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
SMP: AP CPU #1 Launched!

FreeBSD 9.3-RELEASE-p12 amd64

16Gigs of RAM NON ECC@1666MHz
real memory = 17714642944 (16894 MB)
avail memory = 16429277184 (15668 MB)
agp0: aperture size is 256M, detected 65532k stolen memory

freenas-boot 14.4G 5.70G 8.67G - - 39% 1.00x ONLINE -
mypool 5.44T 1.54T 3.90T - 12% 28% 1.00x ONLINE /mnt


this is what i got from messages:

Mar 18 09:10:05 MiniDLNA syslogd: kernel boot file is /boot/kernel/kernel
Mar 28 18:20:07 MiniDLNA syslogd: kernel boot file is /boot/kernel/kernel
Mar 29 20:22:32 MiniDLNA syslogd: exiting on signal 15
Mar 29 20:25:42 MiniDLNA syslogd: kernel boot file is /boot/kernel/kernel
Mar 30 00:27:04 MiniDLNA root: /usr/sbin/service: WARNING: $svnserve_enable is not set properly - see rc.conf(5).
Mar 30 00:27:04 MiniDLNA root: /usr/sbin/service: WARNING: $pbid_enable is not set properly - see rc.conf(5).
Mar 30 00:27:04 MiniDLNA root: /usr/sbin/service: WARNING: $git_daemon_enable is not set properly - see rc.conf(5).
Mar 30 00:27:04 MiniDLNA root: /usr/sbin/service: WARNING: $ffserver_enable is not set properly - see rc.conf(5).
Mar 30 07:09:04 MiniDLNA reboot: rebooted by root
Mar 30 07:09:26 MiniDLNA syslogd: exiting on signal 15
Mar 30 07:11:52 MiniDLNA syslogd: kernel boot file is /boot/kernel/kernel

And i just checked into the jail structure under /usr/sbin/service there is no such file as rc.conf

Code:

root@MiniDLNA:/usr/sbin # locate rc.conf
/etc/defaults/rc.conf
/etc/rc.conf
/usr/local/etc/rc.conf.d
/usr/share/examples/etc/defaults/rc.conf
/usr/share/man/man5/rc.conf.5.gz
/usr/share/man/man5/rc.conf.local.5.gz
/usr/share/man/man5/src.conf.5.gz
/usr/src/crypto/openssh/contrib/suse/rc.config.sshd
/usr/src/etc/defaults/rc.conf
/usr/src/release/picobsd/floppy.tree/etc/rc.conf
/usr/src/release/picobsd/floppy.tree/etc/rc.conf.defaults
/usr/src/share/man/man5/rc.conf.5
/usr/src/share/man/man5/src.conf.5
/usr/src/tools/tools/nanobsd/gateworks/cfg/rc.conf
/usr/src/tools/tools/nanobsd/pcengines/Files/etc/rc.conf
/usr/src/tools/tools/tinybsd/conf/bridge/etc/rc.conf
/usr/src/tools/tools/tinybsd/conf/default/etc/rc.conf
/usr/src/tools/tools/tinybsd/conf/firewall/etc/rc.conf
/usr/src/tools/tools/tinybsd/conf/minimal/etc/rc.conf
/usr/src/tools/tools/tinybsd/conf/vpn/etc/rc.conf
/usr/src/tools/tools/tinybsd/conf/wireless/etc/rc.conf
/usr/src/tools/tools/tinybsd/conf/wrap/etc/rc.conf
/var/db/etcupdate/current/etc/defaults/rc.conf

 

[dlavigne]

rc.conf is in /etc (as expected), not in bin (as that is for binaries/executables). What driver is the NIC using (from ifconfig)? It looks like you are running into this: https://forums.freenas.org/index.php?threads/freenas-9-2-error-listen-queue-overflow.17774/.

 

[Lyubomir B]

rc.conf is in /etc (as expected), not in bin (as that is for binaries/executables). What driver is the NIC using (from ifconfig)? It looks like you are running into this: https://forums.freenas.org/index.php?threads/freenas-9-2-error-listen-queue-overflow.17774/.

Yes indeed i already stumbled upon this thread.
But my NIC is from Intel. And like i already mentioned before these three updates last week everything was running like in butter.

here the output of ifconfig command outside the jail in the root of freenas :

Code:

em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=42098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
  ether e0:69:95:91:7d:ef
  inet 192.168.1.91 netmask 0xffffff00 broadcast 192.168.1.255
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet autoselect (1000baseT <full-duplex>)
  status: active
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
  nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
  options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
  inet 127.0.0.1 netmask 0xff000000
  nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
  ether 02:98:d3:54:37:00
  inet 192.168.1.254 netmask 0xffffff00 broadcast 192.168.1.255
  nd6 options=9<PERFORMNUD,IFDISABLED>
  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
  member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 7 priority 128 path cost 2000
  member: epair6a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 13 priority 128 path cost 2000
  member: epair5a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 12 priority 128 path cost 2000
  member: epair4a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 11 priority 128 path cost 2000
  member: epair3a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 10 priority 128 path cost 2000
  member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 9 priority 128 path cost 2000
  member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 8 priority 128 path cost 2000
  member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
  ifmaxaddr 0 port 1 priority 128 path cost 20000
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:f4:74:00:08:0a
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:ea:74:00:09:0a
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair3a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:ec:74:00:0a:0a
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair4a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:4a:9d:00:0b:0a
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair5a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:08:3d:00:0c:0a
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair6a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:08:54:00:0d:0a
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
  options=8<VLAN_MTU>
  ether 02:b9:05:00:07:0a
  nd6 options=9<PERFORMNUD,IFDISABLED>
  media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
  status: active

and the funny thing is that in my rc.conf file there is nothing like these apperantly error messages

Code:

root@MiniDLNA:/ # cat /etc/rc.conf
portmap_enable="NO"
sshd_enable="NO"
sendmail_enable="NO"
sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"
hostname="MiniDLNA"
devfs_enable="YES"
devfs_system_ruleset="devfsrules_common"
inet6_enable="YES"
ip6addrctl_enable="YES"
minidlna_enable="YES"
pbid_enable="YES"
ffserver_enable="YES"
svnserve_enable="YES"

the last three lines after minidlna_enable="YES" i added yesterday manually with the hope to get the shit fixed but the minidlna daemon keeps closing after a while again for no reason.

Can you tell me how i could reinstall the minidlna package or at least try to upgrade it to a higher version may be this will solve the problem faster than doing additional headbanging.

cheers

 

[Lyubomir B]

Yesterday evening i was trying to upgrade the minidlna server package and noticed something strange. I was able to ping my hosts from the jail, but no host was able to ping the server itself. Looked once again into the ifconfig and everything was fine. Then tried to create a new jail with the idea to install the server there and tested first the connectivity. Ping was going in both directions which made me check the advanced options of the jail itself and found out that by all my other jails and the new one the NAT option was not selected and in addition the MAC address of the pair interface was also written down into the designated field. Then checked the configuration of my MiniDLNA jail and there was not the case so what i did is i deselected the NAT option and entered the MAC manually and saved and the connectivity was restored. I will observe if the server is going to stabelize and work properly like it was in the beginning. Why these options were changed i have no idea, because since i have created the jail never played with the advanced options.

Nope. The server kept closing on itself.
Deleted the jail and created a new one and followed the steps one by one from the MiniDLNA server again. And no success. It keeps closing on its own.

 

[dlavigne]

Were you able to get this sorted?

 

[Lyubomir B]

Were you able to get this sorted?

Hi dlavigne,

well i guess there ist a problem with the miniDLNA server refreshing my Folder dedicated for pictures. I have approximately round about 13 000 files there and this amount makes the server somehow crash. I deleted the entry from the config file so now my server is listing only my music database and my movies and everything runs smoothly.