Kernelpanic on Ubuntu Server 10.04.3 LTS

[thinksimple]

Hello, I'm new here. I used the search function but there was no simulare problem.
I hope someone can help me. I just bought the TwonkyServer TwonkyServer 6.0.34.

Here my system:
Linux HomeServer 2.6.32-33-generic-pae #71-Ubuntu SMP Wed Jul 20 18:46:41 UTC 2011 i686 GNU/Linux
Ubuntu 10.04.3 LTS

IP address for eth0: 10.10.1.10
IP address for eth0:1: 10.10.1.11
IP address for vmnet1: 172.16.83.1
IP address for vmnet8: 192.168.19.1

4GB RAM
Mainboard DG45FC
4x HDD Temp: 34°-38°

Here what I did to install TwonkyServer:

root@HomeServer:/opt/twonkyserver# cp /media/smb/Software/Software/Twonky/TwonkyServer\ 6.0.34/twonkymedia-i386-glibc-2.2.5-6.0.34.zip . root@HomeServer:/opt/twonkyserver# ls
twonkymedia-i386-glibc-2.2.5-6.0.34.zip
root@HomeServer:/opt/twonkyserver# unzip twonkymedia-i386-glibc-2.2.5-6.0.34.zip
Archive: twonkymedia-i386-glibc-2.2.5-6.0.34.zip
<---snip --->
inflating: RevisionHistory
inflating: Linux-HowTo.txt
....
inflating: twonkymedia-server-default.ini
<---/snip--->

root@HomeServer:/opt/twonkyserver# ls
cgi-bin plugins RevisionHistory twonkymediaserver
initial_keystore.dat radio.m3u twonkymedia twonkymedia-server-default.ini
Linux-HowTo.txt resources twonkymedia-i386-glibc-2.2.5-6.0.34.zip twonkymedia.sh
root@HomeServer:/opt/twonkyserver# rm twonkymedia-i386-glibc-2.2.5-6.0.34.zip
root@HomeServer:/opt/twonkyserver# chmod 700 twonkym* cgi-bin/* plugins/*
root@HomeServer:/opt/twonkyserver# ll
insgesamt 1716
drwxr-xr-x 5 root root 4096 2011-08-08 23:42 ./
drwxr-xr-x 14 root root 4096 2011-08-08 23:41 ../
drwxr-xr-x 2 root root 4096 2011-08-08 23:41 cgi-bin/
-rw-r--r-- 1 root root 193 2011-06-22 21:29 initial_keystore.dat
-rw-r--r-- 1 root root 2768 2011-06-22 21:29 Linux-HowTo.txt
drwxr-xr-x 2 root root 4096 2011-08-08 23:41 plugins/
-rw-r--r-- 1 root root 421 2011-06-22 21:29 radio.m3u
drwxr-xr-x 4 root root 4096 2011-06-23 02:44 resources/
-rw-r--r-- 1 root root 57677 2011-06-22 21:29 RevisionHistory
-rwx------ 1 root root 4744 2011-06-22 23:41 twonkymedia*
-rwx------ 1 root root 1643796 2011-06-22 23:41 twonkymediaserver*
-rwx------ 1 root root 153 2011-06-23 02:44 twonkymedia-server-default.ini*
-rwx------ 1 root root 3775 2011-06-22 21:29 twonkymedia.sh*
root@HomeServer:/opt/twonkyserver# route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
root@HomeServer:/opt/twonkyserver# service smbd stop
smbd stop/waiting
root@HomeServer:/opt/twonkyserver# service nmbd stop
nmbd stop/waiting
root@HomeServer:/opt/twonkyserver# /opt/twonkyserver/twonkymedia
root@HomeServer:/opt/twonkyserver# TwonkyMedia Version 6.0.34

For image conversion and scaling the TMS utilizes ImageMagick. For details on the license please see /opt/twonkyserver/cgi-bin/convert-readme.txt

KernelPanic ....

[thinksimple]

Hello, again
I started twonky server with a strace. But I didn't find anything: maybe someone else sees something:


root@HomeServer:/opt/twonkyserver# strace /opt/twonkyserver/twonkymedia
execve("/opt/twonkyserver/twonkymedia", ["/opt/twonkyserver/twonkymedia"], [/* 15 vars */]) = 0
brk(0) = 0x9213000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb773f000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=21885, ...}) = 0
mmap2(NULL, 21885, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7739000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/i686/cmov/libpthread.so.0", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 J\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=117086, ...}) = 0
mmap2(NULL, 98792, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7720000
mmap2(0xb7735000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x14) = 0xb7735000
mmap2(0xb7737000, 4584, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7737000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/i686/cmov/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0000m\1\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1405508, ...}) = 0
mmap2(NULL, 1415592, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb75c6000
mprotect(0xb7719000, 4096, PROT_NONE) = 0
mmap2(0xb771a000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x153) = 0xb771a000
mmap2(0xb771d000, 10664, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb771d000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb75c5000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb75c4000
set_thread_area({entry_number:-1 -> 6, base_addr:0xb75c46c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
mprotect(0xb771a000, 8192, PROT_READ) = 0
mprotect(0xb7735000, 4096, PROT_READ) = 0
mprotect(0xb775d000, 4096, PROT_READ) = 0
munmap(0xb7739000, 21885) = 0
set_tid_address(0xb75c4728) = 3467
set_robust_list(0xb75c4730, 0xc) = 0
futex(0xbfd5ecd0, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xbfd5ecd0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, NULL, bfd5ece0) = -1 EAGAIN (Resource temporarily unavailable)
rt_sigaction(SIGRTMIN, {0xb7724410, [], SA_SIGINFO}, NULL, = 0
rt_sigaction(SIGRT_1, {0xb77248f0, [], SA_RESTART|SA_SIGINFO}, NULL, = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, = 0
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0
uname({sys="Linux", node="HomeServer", ...}) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb75c4728) = 3468
exit_group(0) = ?
root@HomeServer:/opt/twonkyserver# TwonkyMedia Version 6.0.34

For image conversion and scaling the TMS utilizes ImageMagick. For details on the license please see /opt/twonkyserver/cgi-bin/convert-readme.txt

[parnott]

My suggeastion would be to start simple and get Twonky to bind to one specific ip address. All those virtual network adaptors are probably causing problems.

To get Twonky to bind to a specific ip address you modify the ip= paramter in the twonkymedia-server.ini file. In your example of the ehternet adaptors list, I would try-
ip=10.10.1.10

[thinksimple]

Hello parnott,

you were right. The multiple interfaces seem to be the problem. I created a twonkymedia-server.ini file and tried the option ip=127.0.0.1, 10.10.1.10
but this doesn't seem to work. Under Serverstatus he still lists all interfaces.

can I say something like bind-interfaces?

[parnott]

I think the ip= option only allows one ip address. If memory serves correctly 127.0.0.1 will always be bound. So you just need-
ip=10.10.1.10

There is no other option that I know of.

[thinksimple]

@all
the solution was to disable VMware NAT and Host network. Since I only use Bridging that's not a problem for me.

I think, for the future this bug should be solved.

[parnott]

Like what bug. As in your VM virtual adaptors causing a kernel panic when accessed? How is that a Twonky problem.

[thinksimple]

twonky shouldn't have any Problems with vmware Adapters. That's the bug

[parnott]

I don't wish to be argumentative. But if you are seeing a Kernel Panic (definition here http://en.wikipedia.org/wiki/Kernel_panic#Causes) then it is the OS failing not Twonky. All Twonky could be doing is enumerating the configured network adaptors and attempting to start broadcasting SSDP annoucements on each. It is difficult for a user space application to cause a Kernel Panic unless it was specially crafted to exploit a defect in the OS.

Have you looked in /var/log/messages or /var/log/kern.log to see if there is any relevant information?

[thinksimple]

I had a look in the syslog and the kern.log. There are no entries.
My suggestion is that twonky does something on/with/... the vmware adapterst which causes a Kernel Panic. It must be something Twonky initiates, as the system is running without twonky service started, smooth and stable. (It runs stabel now too, because the vmware host and nat adapter are not running)

I posted a strace earlier, that's the only hint I can give.

I don't want to argu any further. It leeds to nothing, and only causes uncomfortable "feelings".

But wat I want to say is: Thank you for your help! Now it is working!