Firefly daap server crash?

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #2528
    Anonymous
    Inactive

    Appolopgies for re-threading this, but I have had no response

    Firefly has been starting up nightly without problem for a couple of weeks, but last night it failed, and looking in the messages file I see:

    ‘Rendezvous socket closed (daap server crashed?) Aborting.’

    What has happened, why (if anyone can answer) but more importantly, how do I recover?

    OK, still having problems here and I cannot get debug to work at all, so I do not have any pointers.

    I am using Firefly 0.2.4.2 on an NSLU2 with unslung 6.8

    I did earlier try to download one of the later nightlies, but I got various install errors to do with missing dependancies?

    If you need any more info to try and help or offer suggestions let me know

    Mike

    #17328
    EVILRipper
    Participant

    In what debuglevel are you running?
    Try setting it to 9. Maybe you will encounter new warnings/messages which can give better clues on what’s wrong.

    #17329
    Anonymous
    Inactive

    @EVILRipper wrote:

    In what debuglevel are you running?
    Try setting it to 9. Maybe you will encounter new warnings/messages which can give better clues on what’s wrong.

    Thanks for the response, unfortunately I cannot get debug to run at all. My config file is:

    web_root /opt/share/mt-daapd/admin-root
    port 3689
    admin_pw mt-daapd
    mp3_dir /share/flash/data/public/music
    servername NSLU2 Music
    runas guest
    playlist /opt/etc/mt-daapd/mt-daapd.playlist
    extensions .mp3,.m4a,.m4p
    logfile = var/log/mt-daapd.log
    db_dir /opt/var/mt-daapd
    rescan_interval 600
    scan_type 0
    debuglevel = 5
    always_scan 0
    process_m3u 0
    compress

    but get the error when trying to start Firefly:

    Invalid config directive: debuglevel

    Now what have I done, or not…?

    Mike

    #17330
    stretch
    Participant

    This is my config file with the comments removed.

    web_root = /opt/share/mt-daapd/admin-root
    port = 3689
    admin_pw = :)
    db_type = sqlite3
    db_parms = /opt/var/mt-daapd
    mp3_dir = /share/flash/data/music
    servername = NSLU2 Music
    runas = guest
    playlist = /opt/etc/mt-daapd/mt-daapd.playlist
    extensions = .m4a,.flac
    ssc_codectypes = ogg,flac,alac
    ssc_prog = /opt/sbin/mt-daapd-ssc.sh
    logfile = /var/log/mt-daapd.log
    rescan_interval = 3600
    always_scan = 0
    scan_type = 0
    debuglevel = 0
    password = music
    [plugins]
    plugin_dir = /opt/share/mt-daapd/plugins
    plugins = rsp.so,ssc-script.so

    Notice the difference?

    The *=* is mising from most of your config file entries
    Hope this fixes it 😉

    Note: I’m using svn-1696 on the slug so there may be some extra config stuff not applicable to 0.2.4.2

    #17331
    Anonymous
    Inactive

    @stretch wrote:

    This is my config file with the comments removed.

    web_root = /opt/share/mt-daapd/admin-root
    port = 3689
    admin_pw = :)
    db_type = sqlite3
    db_parms = /opt/var/mt-daapd
    mp3_dir = /share/flash/data/music
    servername = NSLU2 Music
    runas = guest
    playlist = /opt/etc/mt-daapd/mt-daapd.playlist
    extensions = .m4a,.flac
    ssc_codectypes = ogg,flac,alac
    ssc_prog = /opt/sbin/mt-daapd-ssc.sh
    logfile = /var/log/mt-daapd.log
    rescan_interval = 3600
    always_scan = 0
    scan_type = 0
    debuglevel = 0
    password = music
    [plugins]
    plugin_dir = /opt/share/mt-daapd/plugins
    plugins = rsp.so,ssc-script.so

    Notice the difference?

    The *=* is mising from most of your config file entries
    Hope this fixes it 😉

    Note: I’m using svn-1696 on the slug so there may be some extra config stuff not applicable to 0.2.4.2

    I noticed that too, but apart from my additions of log file and debuglevel, the rest was as edited and saved by the Firefly web interface, and works correctly without my additions?

    Mike

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