general problems after installing dlna plugin

[tseeling]

Hallo,


I have installed and activated the DLNA plugin in my home NAS, but I've had no time yet to do any configuration, so it's just sitting there.
Presumably at the same time (I'm not quite sure) I started received strange error messages in my daily NAS mails.
Before I installed the plugin and got the first jail, my NAS was running fine for weeks after the 9.1.1 upgrade.

I'm an average unix guy but I have little experience in BSD systems management (I come from AIX and Solaris).
Where would I start looking for problems and log files? /var/cron/tabs is empty, root has no cron jobs, I'm lost somehow ;(

Please have a look at the mail from tonight: what especially strikes me odd is the plethora of different signals from which python dies.
The messages from "arp" are imho ok, it simply means a device is hopping from one AP to a different one.

A different error message comes from another shell script: Cron <root@nas> /bin/sh /root/save_rrds.sh
/usr/bin/tar: Undefined symbol "arkhive_entry_linkresolver_free"

What should/could I do there?

Code:

Checking for uids of 0:
root 0

Checking for passwordless accounts:

Checking login.conf permissions:

Checking for ports with mismatched checksums:

nas.***.local kernel log messages:
+++ /tmp/security.YYqSG6di	2013-10-25 03:01:01.000000000 +0200
+arp: 192.168.100.100 moved from 00:e0:7d:ad:d6:ba to 00:11:2f:b4:ab:b1 on epair0b
+pid 20996 (python2.7), uid 0: exited on signal 6
+pid 21162 (python2.7), uid 0: exited on signal 11
+pid 21621 (python2.7), uid 0: exited on signal 10
+pid 23265 (python2.7), uid 0: exited on signal 4
+pid 23700 (python2.7), uid 0: exited on signal 10
+pid 25436 (python2.7), uid 0: exited on signal 6
+pid 26013 (python2.7), uid 0: exited on signal 4
+pid 26028 (python2.7), uid 0: exited on signal 10
+pid 26183 (python2.7), uid 0: exited on signal 10
+pid 27583 (python2.7), uid 0: exited on signal 11
+pid 29436 (python2.7), uid 0: exited on signal 11
+pid 29541 (python2.7), uid 0: exited on signal 11
+pid 29646 (python2.7), uid 0: exited on signal 11
+pid 29809 (python2.7), uid 0: exited on signal 11
+pid 29899 (python2.7), uid 0: exited on signal 11
+pid 30000 (python2.7), uid 0: exited on signal 11
+pid 30141 (python2.7), uid 0: exited on signal 6
+pid 30314 (python2.7), uid 0: exited on signal 11
+pid 30579 (python2.7), uid 0: exited on signal 11
+pid 30704 (python2.7), uid 0: exited on signal 11
+pid 31295 (python2.7), uid 0: exited on signal 11
+pid 31314 (python2.7), uid 0: exited on signal 6
+pid 29267 (smbd), uid 0: exited on signal 6
+pid 31563 (python2.7), uid 0: exited on signal 11
+pid 32572 (python2.7), uid 0: exited on signal 11
+pid 32750 (python2.7), uid 0: exited on signal 10
+pid 33094 (python2.7), uid 0: exited on signal 11
+pid 33135 (python2.7), uid 0: exited on signal 11
+pid 34089 (python2.7), uid 0: exited on signal 6
+pid 34185 (python2.7), uid 0: exited on signal 10
+pid 34478 (python2.7), uid 0: exited on signal 11
+pid 34701 (python2.7), uid 0: exited on signal 4
+pid 34804 (python2.7), uid 0: exited on signal 11
+pid 34885 (python2.7), uid 0: exited on signal 11
+pid 35160 (python2.7), uid 0: exited on signal 11
+pid 35227 (python2.7), uid 0: exited on signal 10
+pid 35247 (python2.7), uid 0: exited on signal 11
+pid 35259 (python2.7), uid 0: exited on signal 11
+pid 35529 (python2.7), uid 0: exited on signal 11
+pid 35587 (python2.7), uid 0: exited on signal 11
+pid 35845 (python2.7), uid 0: exited on signal 11
+pid 36230 (python2.7), uid 0: exited on signal 10
+pid 36481 (python2.7), uid 0: exited on signal 11
+pid 36687 (python2.7), uid 0: exited on signal 11
+pid 36856 (python2.7), uid 0: exited on signal 11
+pid 37657 (python2.7), uid 0: exited on signal 11
+pid 39099 (python2.7), uid 0: exited on signal 10
+pid 39242 (python2.7), uid 0: exited on signal 10
+pid 39313 (python2.7), uid 0: exited on signal 11
+pid 39699 (python2.7), uid 0: exited on signal 11
+pid 40002 (python2.7), uid 0: exited on signal 11
+pid 40037 (python2.7), uid 0: exited on signal 11
+pid 40387 (python2.7), uid 0: exited on signal 11
+pid 40447 (python2.7), uid 0: exited on signal 6
+pid 40528 (python2.7), uid 0: exited on signal 11
+pid 41265 (python2.7), uid 0: exited on signal 11
+pid 41373 (python2.7), uid 0: exited on signal 11
+pid 41645 (python2.7), uid 0: exited on signal 6
+pid 41821 (python2.7), uid 0: exited on signal 11
+pid 41922 (python2.7), uid 0: exited on signal 11
+pid 42179 (python2.7), uid 0: exited on signal 11
+pid 42255 (python2.7), uid 0: exited on signal 10
+pid 42421 (python2.7), uid 0: exited on signal 10
+pid 42522 (python2.7), uid 0: exited on signal 6
+pid 42623 (python2.7), uid 0: exited on signal 10
+pid 42883 (python2.7), uid 0: exited on signal 4
+pid 42981 (python2.7), uid 0: exited on signal 11
+pid 43138 (python2.7), uid 0: exited on signal 11
+pid 43201 (python2.7), uid 0: exited on signal 10
+pid 43711 (python2.7), uid 0: exited on signal 10
+pid 43958 (python2.7), uid 0: exited on signal 11
+pid 44481 (python2.7), uid 0: exited on signal 10
+pid 44894 (python2.7), uid 0: exited on signal 11
+pid 44951 (python2.7), uid 0: exited on signal 11
+pid 45223 (python2.7), uid 0: exited on signal 11
+pid 45250 (python2.7), uid 0: exited on signal 11
+pid 45654 (python2.7), uid 0: exited on signal 11
+arp: 192.168.100.100 moved from 00:11:2f:b4:ab:b1 to 00:e0:7d:ad:d6:ba on epair0b

nas.***.local login failures:

nas.***.local refused connections:

-- End of security output --

Thanks for your insights,
Tschau...Thomas

 

[dlavigne]

Signal 11 is usually indicative of faulty hardware, typically RAM. Have you run a memtest on this system?

 

[cyberjock]

Try a RAM test.. memtest.org has a good ISO you can burn and boot from. 3 passes with no errors is typically considered "good".

 

[tseeling]

I thought about this, and Google found a few hints suggesting the same.
Only I was stymied because of the multitude of different signals, and strangely enough it seems to have gone away for now after I managed to delete the dlna plugin.
I will of course run a RAM test from a bootable USB stick as you suggest, that seems a good idea anyway to continue.
The system ran fine for over a year and my problems started only some days after upgrading to 9.1.1.