#56 MiniDLNA crashes on system startup

open
None
5
2011-02-17
2011-02-17
No

I have MiniDLNA configured to start automatically on Linux startup via the /etc/init.d/minidlna script. However, it never actually starts. I get this error message in /var/log/syslog:

~ $ cat /var/log/syslog | grep "minidlna"
Feb 16 20:40:16 work-laptop kernel: [ 6564.862493] BUG: soft lockup - CPU#1 stuck for 61s! [minidlna:24464]
Feb 16 20:40:16 work-laptop kernel: [ 6564.862503] Pid: 24464, comm: minidlna Not tainted 2.6.32-28-generic #55-Ubuntu NV58 Series
Feb 16 20:41:22 work-laptop kernel: [ 6630.362493] BUG: soft lockup - CPU#1 stuck for 61s! [minidlna:24464]
Feb 16 20:41:22 work-laptop kernel: [ 6630.362503] Pid: 24464, comm: minidlna Not tainted 2.6.32-28-generic #55-Ubuntu NV58 Series
Feb 16 20:42:27 work-laptop kernel: [ 6695.862492] BUG: soft lockup - CPU#1 stuck for 61s! [minidlna:24464]
Feb 16 20:42:27 work-laptop kernel: [ 6695.862503] Pid: 24464, comm: minidlna Not tainted 2.6.32-28-generic #55-Ubuntu NV58 Series

I'm running MiniDLNA over my WiFi network, (not specifed in config file, that's just how I use it) could that be a part of the problem?

Discussion

  • Justin Maggard

    Justin Maggard - 2011-02-17
    • assigned_to: nobody --> jmaggard
     
  • Justin Maggard

    Justin Maggard - 2011-02-17

    I'm not able to reproduce that issue. Is pid 24464 still running? Is there anything in the minidlna log?

     
  • Jesse Badwal

    Jesse Badwal - 2011-03-10

    im also have an issue at boot..

    after each reboot I have to explicitly type

    sudo service minidlna stop
    sudo service minidlna start

    running 'sudo service minidlna restart' how doesnt work either..

     
  • Tyler Kocheran

    Tyler Kocheran - 2011-03-11

    I just worked around the issue by writing an Upstart script that started MiniDLNA after networking comes up. Works like a charm.

    By the way, where is this "minidlna log?"

     
  • Jesse Badwal

    Jesse Badwal - 2011-03-11

    the log is in /var/log/minidlna.log

    i create two scripts .. if-up and if-down..

    #!/bin/sh

    MINIDLNA=/etc/init.d/minidlna

    if [ ! -x $MINIDLNA ]; then
    exit 0
    fi

    if [ -n "$IF_MINIDLNA" ]; then
    $MINIDLNA stop
    fi

    and for if up

    #!/bin/sh

    MINIDLNA=/etc/init.d/minidlna

    if [ ! -x $MINIDLNA ]; then
    exit 0
    fi

    if [ -n "$IF_MINIDLNA" ]; then
    $MINIDLNA stop
    $MINIDLNA start
    fi

    dont know if this is what you did ? but it makes more sense to have minidlna start and stop with networking rather than on startup itself..

     
  • Justin Maggard

    Justin Maggard - 2011-03-12

    So do we still have a problem? Is there still a repeatable crash? Minidlna wants to get stated after the network is up, but still it shouldn't crash.

     
  • Jesse Badwal

    Jesse Badwal - 2011-03-12

    There is a problem.. its the fact that on reboot.. even though minidlna starts up.. it needs to be stopped and then restarted in order to start working.. if I reboot and then hit the xbox for example.. the device shows but no content.. if I explicitly stop and then start. it works.. as well if I restart .. it still doesnt work..

    I think two scripts.. for if-up and if-down to start and stop minidlna would be perfect.. the two scripts i posted are working great for me..

     

Log in to post a comment.