Server Crash on svn-1677

  • Post date

FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › Server Crash on svn-1677

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • 20/10/2007 at 11:41 AM #1833
    rcoundon
    Participant

    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

    20/10/2007 at 11:53 AM #12985
    rcoundon
    Participant

    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

    20/10/2007 at 2:37 PM #12986
    belu
    Participant

    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)

    20/10/2007 at 2:41 PM #12987
    rcoundon
    Participant

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

    Ross

    20/10/2007 at 3:36 PM #12988
    rcoundon
    Participant

    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

    20/10/2007 at 11:34 PM #12989
    rpedde
    Participant

    @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
Viewing 6 posts - 1 through 6 (of 6 total)
  • The forum ‘Nightlies Feedback’ is closed to new topics and replies.