Server Crash on svn-1677

[rcoundon]

On WinXP SP2 I connect to the server.
Browse Artists and play a track. The server immediately crashes with the error

2007-10-20 12:37:49 (0d0a4aa2): Query: INSERT INTO updated VALUES (4611)
2007-10-20 12:37:49 (0d0a4aa2): Error: no such table: updated
2007-10-20 12:37:49: Aborting

I also see peppered through the log file the message

2007-10-20 12:35:28 (7a517a52): Couldn’t set socket to blocking

I have tried with a few different types of files but the same happens.

Cheers,
Ross

[rcoundon]

I think I’ve identified the problem.
It would seem that the database table structure must have changed recently and installing the latest nightly ‘over the top’ of an existing installation doesn’t upgrade the database.
Therefore, in order to get this working I deleted my original sqlite3 db and allowed Firefly to build a new one and all is working fine.

Cheers,

Ross

[belu]

Don’t know whether that’s the right place to report, but here it is:

hundreds of lines

“2007-10-20 16:27:15 (93be5bf6): Couldn’t set socket to blocking”

per second in the log (playing flac).

more than 200MB for firefly and always 100% of CPU-Usage.

BeLU

WinXP Sp2, FF 1677)

[rcoundon]

Yeah, I’m getting loads of those too. Eventually, the server crashes altogether and has to be restarted.

Ross

[rcoundon]

Something else I’ve noticed (apologies for delivering this piece-meal)
is that the last entry in the event log is an error that states:

Could not alloc buffer in io_printf

[rpedde]

@rcoundon wrote:

I think I’ve identified the problem.
It would seem that the database table structure must have changed recently and installing the latest nightly ‘over the top’ of an existing installation doesn’t upgrade the database.
Therefore, in order to get this working I deleted my original sqlite3 db and allowed Firefly to build a new one and all is working fine.

Cheers,

Ross

actually hasn’t changed in a log time, and even over the top installs should update the db schema if it needs to, so somethere else was going on there. I wonder if this was related to the sqlite problems I was having on unix. I’ll have to look closer at this.

— Ron

[Author]

Posts