You are here: Home » Topic » database error on svn-1463

database error on svn-1463

This topic contains 5 replies, has 1 voice, and was last updated by  fizze 10 years, 11 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #908

    dreamer
    $ sudo mt-daapd -f
    Config entry general/db_dir is deprecated. Please review the sample config
    Firefly Version svn-1463: Starting with debuglevel 2
    Starting rendezvous daemon
    Starting signal handler
    Initializing database
    Starting web server from /usr/share/mt-daapd/admin-root on port 3689
    Registering rendezvous names
    Serving 79 songs. Startup complete in 0 seconds
    Rescanning database
    Signal handler started
    Starting playlist scan
    Query: delete from songs where id not in (select id from updated)
    Error: attempt to write a readonly database
    Aborting
    Rendezvous socket closed (daap server crashed?) Aborting.
    Aborting
    #8034

    fizze
    Participant

    erm, your config file is deprecated.
    Then your db_param is maybe even missing, or the db_param defaults to the current dir, which seems like its not readable to the user mt-daapd revokes to.

    besides, use CODE to format log outputs. its a lot nicer.

    #8035

    dreamer

    I’m sory, but I’m not sure what you mean.

    #8036

    fizze
    Participant

    the config file (mt-daapd.conf) is an OLD one.
    reinstall from that ipkg, and tell it to overwrite your config with the default one.

    You will have to edit the mp3_dir, and probably other things.
    But then you will have a new, “clean” config file.

    #8037

    dreamer

    @fizze wrote:

    reinstall from that ipkg, and tell it to overwrite your config with the default one.

    Ok, noob here. I don’t get how to do this.

    #8038

    fizze
    Participant

    Well, however you installed that version of firefly, do that again.
    When you are asked to overwrite anything answer with yes 😉

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.