You are here: Home » Reply » Reply To: startup on unslung 6.8

Reply To: startup on unslung 6.8

#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 🙄