@josefgabriel wrote:
Well I did just manage to get a log file and verify that the abort was the same two times. Here is the log:
2008-02-19 12:21:25 (023ce670): Starting with debuglevel 0
2008-02-19 12:21:25 (023ce670): Starting rendezvous daemon
2008-02-19 12:21:25 (023ce670): Initializing database
2008-02-19 12:21:35 (023ce670): Starting web server from C:Program FilesFirefly Media Serveradmin-root on port 9999
2008-02-19 12:21:35 (023ce670): Registering rendezvous names
2008-02-19 12:21:35 (023ce670): Serving 10903 songs. Startup complete in 10 seconds
2008-02-19 12:21:35 (023ce670): Rescanning database
2008-02-19 12:34:59 (023ce670): Starting playlist scan
2008-02-19 12:35:12 (023ce670): Scanned 10903 songs (was 10903) in 817 seconds
2008-02-19 12:45:14 (023ce670): Rescanning database
2008-02-19 12:59:00 (023ce670): Starting playlist scan
2008-02-19 12:59:10 (023ce670): Scanned 10903 songs (was 10903) in 836 seconds
2008-02-19 13:09:12 (023ce670): Rescanning database
2008-02-19 13:17:18 (023ce670): Query: INSERT INTO updated VALUES (4808)
2008-02-19 13:17:18 (023ce670): Error: unable to open database file
2008-02-19 13:17:18: AbortingSo this is a complete guess but it appears to be related around unable to open the database file that stores the scanned info. Anyone have any ideas or suggestions? Thanks again.
That usually means that the db file is locked by another program. might be a virus scanner. might be a realtime backup program… you can try a newer nightly (http://nightlies.fireflymediaserver.org) if you aren’t alrady — there are some fixes there for locks by av programs.
If you are on a newish nightly, and are still having the problem, see if you can figure out what 3rd party program is grabbing the database, and see if you can exclude it from whatever the application is doing.
— Ron