You are here: Home » Topic » startup on unslung 6.8

startup on unslung 6.8

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #560
    fizze
    Participant

    I have a unsling script on my slug, so that mt-daapd is started upon boot.
    I just realized, that is is defunct.
    There are lots of Zombified instances of mt-daapd left in memory, any clues how this might happen ?

    I know that the same script used to work as late as 900ish nightlies for sure.

    So the Q is, what has changed in mt-daapd since then that affects startup behavious ?
    Its really a nag, and the slug doesnt really reboot often, but if it happens, its nice not to have to turn a PC on and “fix” mt-daapd… 😉

    #6236
    rpedde
    Participant

    @fizze wrote:

    I have a unsling script on my slug, so that mt-daapd is started upon boot.
    I just realized, that is is defunct.
    There are lots of Zombified instances of mt-daapd left in memory, any clues how this might happen ?

    I know that the same script used to work as late as 900ish nightlies for sure.

    So the Q is, what has changed in mt-daapd since then that affects startup behavious ?
    Its really a nag, and the slug doesnt really reboot often, but if it happens, its nice not to have to turn a PC on and “fix” mt-daapd… 😉

    zombies happen because processes are terminated and not reaped. I’d check your syslog and see what’s up. You might be getting killed for oom condition.

    Maybe some of your gigantic oggs slipped into the db?

    #6237
    fizze
    Participant

    well I guess thats what I might have to do.
    The weird thing is, when I run the same script like 1min after the slug has booted it works fine of course.

    Just figured Id ask since there’s a bunch of slug users here 😉

    #6238
    fizze
    Participant

    Alright, finally had some time to bog this down.
    Seems that I start 2 instances 😛 Funny thing is, I never modified my unslung scripts. weirdness. Well, the second entry has to be somewhere 😉

    <25>Sep 19 17:32:04 mt-daapd[508]: Starting with debuglevel 0
    <25>Sep 19 17:32:04 mt-daapd[508]: Starting rendezvous daemon
    <25>Sep 19 17:32:04 mt-daapd[510]: Starting signal handler
    <25>Sep 19 17:32:05 mt-daapd[510]: Initializing database
    <25>Sep 19 17:32:07 mt-daapd[519]: Starting with debuglevel 0
    <25>Sep 19 17:32:07 mt-daapd[519]: Starting rendezvous daemon
    <25>Sep 19 17:32:07 mt-daapd[521]: Starting signal handler
    <25>Sep 19 17:32:07 mt-daapd[521]: Initializing database
    <25>Sep 19 17:34:55 mt-daapd[510]: Starting web server from /share/flash/conf/opt/share/mt-daapd/admin-root on port 3689
    <25>Sep 19 17:34:55 mt-daapd[521]: Starting web server from /share/flash/conf/opt/share/mt-daapd/admin-root on port 3689
    <25>Sep 19 17:34:55 mt-daapd[521]: Listen port: Address already in use
    <25>Sep 19 17:34:55 mt-daapd[521]: Error staring web server: Address already in use
    <25>Sep 19 17:34:55 mt-daapd[520]: Rendezvous socket closed (daap server crashed?) Aborting.

    Wow, funny. I had a rc.local~ in my /unslung dir. If the slug is dumb enough to execute this at bootup, Im gonna scream 🙄

    #6239
    rpedde
    Participant

    Wow, funny. I had a rc.local~ in my /unslung dir. If the slug is dumb enough to execute this at bootup, Im gonna scream 🙄

    wow.. that *is* super strange. Quick and dirty, I guess. 🙂

Viewing 5 posts - 1 through 5 (of 5 total)
  • The forum ‘Setup Issues’ is closed to new topics and replies.