No backend database support for type: = sqlite3

  • Post date

FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › No backend database support for type: = sqlite3

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • 26/09/2006 at 9:18 AM #633
    barnseyboy
    Participant

    i compiled the latest nightly as im trying to enable flac support (i had previously been using the mt-daapd_0.2.4-1_arm.deb package working sweetly)

    i configuured with –enable-flac and –enable-sqlite3

    make ran successfully

    i copied the relevant parts of the conf file (db_type and db_params) to my existing conf file

    i made sure that folder /usr/local/var/cache/mt-daapd exists and my runas is set to nobody (a previous post on here suggested that was their problem)

    however when i start mt-daapd i always get this error in the logs

    2006-09-26 10:11:06 (00004000): Starting with debuglevel 2
    
2006-09-26 10:11:06 (00004000): Starting rendezvous daemon
    
2006-09-26 10:11:06 (00004000): Starting signal handler
    
2006-09-26 10:11:06 (00004002): Signal handler started
    
2006-09-26 10:11:07 (00004000): Error opening db: No backend database support for type: = sqlite3
    
2006-09-26 10:11:07 (00004000): Stopping signal handler
    
2006-09-26 10:11:07 (00004002): Got shutdown signal. Notifying daap server.

    is there a way to get better information on what im missing, i do think that i have all the relevant sqlite3/libsqlite etc pacakges installed (im using debianslug)

    many thanks in advance .
    db

    26/09/2006 at 9:44 AM #6610
    fizze
    Participant

    isnt the switch just “–enable-sqlite” ?

    26/09/2006 at 10:22 AM #6611
    barnseyboy
    Participant

    ive just tried to reconfigure with –enable-sqlite and i got the following

    checking sqlite.h presence... no
    
checking for sqlite.h... no
    
configure: error: sqlite.h not found... Must have sqlite headers installed

    i then installed libsqlite0 and re-ran configure. all reported back ok (found sqlite.h etc)

    i then make copy the binary to /usr/sbin/ and run /etc/init.d/mt-daapd -start

    log reports same error

    2006-09-26 11:19:24 (00004000): Starting rendezvous daemon
    
2006-09-26 11:19:24 (00004000): Starting signal handler
    
2006-09-26 11:19:24 (00004002): Signal handler started
    
2006-09-26 11:19:25 (00004000): Error opening db: No backend database support for type: = sqlite
    
2006-09-26 11:19:25 (00004000): Stopping signal handler
    
2006-09-26 11:19:25 (00004002): Got shutdown signal. Notifying daap server.

    this is the first time i have tried to run using sqlite (previously using songs.gdb) do i need to do anything to ‘initialise the database file’ ? ive specified the db path (and it exists, but obviously no sqlite file is being created in there yet)

    and im presuming that gdb is no longer supports as when i compile without the flags i get this error

    Must use either --enable-sqlite or --enable-sqlite3

    i also tried running mt-daapd -force-reload which put the following in the log file

    2006-09-26 11:35:06 (00004000): Can't get db version. New database?
    
2006-09-26 11:35:06 (00004000): Initializing database
    
2006-09-26 11:35:06 (00004000): Error: enum_begin failed (error 1): ?
    
2006-09-26 11:35:06 (00004000): Error: enum_begin failed (error 1): ?
    
2006-09-26 11:35:06 (00004000): Full reload...
    
2006-09-26 11:35:06 (00004000): Starting mp3 scan
    
2006-09-26 11:35:06 (00004000): Error inserting file Track 01.mp3 in database
    
2006-09-26 11:35:06: Aborting
    26/09/2006 at 12:42 PM #6612
    barnseyboy
    Participant

    the solution specified here worked ..

    http://forums.fireflymediaserver.org/viewtopic.php?p=6210&sid=09081c1fbc981b4ca5c28092bc2186a6

    the /var/cache/mt-daapd was not writeable by the ‘runas’ user nobody.

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