1696 caused 100% CPU usage on XP SP2

Viewing 7 posts - 16 through 22 (of 22 total)
  • Author
    Posts
  • #14205
    Anonymous
    Inactive

    I don’t know if this will help at all or if you’ve already got an idea of what’s going on but:
    I was just sitting around today and had noticed that one of the cores on my serving computer as doing the usual 100% use thing. A few minutes later I suddenly noticed it stopped and this was the error that occurred when it stopped:

    2007-11-16 19:06:50 (7d09ff67): Thread 20: could not read: unknown internal error

    The thread it is in reference to is:
    2007-11-16 17:36:00 (7d09ff67): Request: GET daap://146.244.184.248:9999/server-info HTTP/1.1
    2007-11-16 17:36:01 (7d09ff67): Request: GET /content-codes HTTP/1.1
    2007-11-16 17:36:01 (7d09ff67): Request: GET /databases HTTP/1.1
    2007-11-16 17:36:02 (7d09ff67): Request: GET /databases/1/items?type=music&meta=dmap.itemid,dmap.itemname, HTTP/1.1
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: daap.songalbumartist
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: daap.songcategory
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: daap.songextradata
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: daap.songcontentdescription
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: daap.songlongcontentdescription
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: daap.songkeywords
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.is-podcast
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.mediakind
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.series-name
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.network-name
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.episode-num-str
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.episode-sort
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.season-num
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: daap.songgapless
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.gapless-enc-del
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.gapless-heur
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.gapless-enc-dr
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.gapless-dur
    2007-11-16 17:36:02 (7d09ff67): Unknown meta code: com.apple.itunes.gapless-resy
    2007-11-16 17:36:03 (7d09ff67): Request: GET /databases/1/containers?meta=dmap.itemid,dmap.itemname, HTTP/1.1
    2007-11-16 17:36:03 (7d09ff67): Unknown meta code: com.apple.itunes.is-podcast-playlist
    2007-11-16 17:36:03 (7d09ff67): Unknown meta code: com.apple.itunes.special-playlist
    2007-11-16 17:36:04 (7d09ff67): Request: GET /databases/1/containers/1/items?type=music&meta=dmap.itemkind,dmap.itemid,dmap.containeritemid HTTP/1.1

    So a good hour and a half difference before the thread ending happened. I’m fairly certain that’s the exact error at the exact time it stopped, as when my cpu usage is at 100% the fan on my server kicks up, and it suddenly kicked down shortly after that error ending the thread.

    edit: just realized this was horribly table breaking

    #14206
    mbaker
    Participant

    Hiya. I’m having the same problem with this build but seeing some different symptoms in the log file.

    I’ve got debug set to 2 and am getting lots and lots of the following:

    ...
    2007-11-18 08:35:32 (d374dfdb): Updating playlists
    2007-11-18 08:35:33 (d374dfdb): Updating playlists
    2007-11-18 08:35:33 (d374dfdb): Updating playlists
    ...

    When I connect to it using my Roku, it’ll usually work briefly before crashing with the following error:

    2007-11-18 08:37:09 (7808c3cf): Error: enum_begin failed (error 1): Misc SQL Error: database is locked

    So basically, it’s dead Ron…

    Good luck with the DB rewrite! Interested to see that with this version you’ve upgraded to SQL3 (I’ve been running on an extremely stable 14xx version for months).

    #14207
    rpedde
    Participant

    @mbaker wrote:

    Hiya. I’m having the same problem with this build but seeing some different symptoms in the log file.

    I’ve got debug set to 2 and am getting lots and lots of the following:

    ...
    2007-11-18 08:35:32 (d374dfdb): Updating playlists
    2007-11-18 08:35:33 (d374dfdb): Updating playlists
    2007-11-18 08:35:33 (d374dfdb): Updating playlists
    ...

    When I connect to it using my Roku, it’ll usually work briefly before crashing with the following error:

    2007-11-18 08:37:09 (7808c3cf): Error: enum_begin failed (error 1): Misc SQL Error: database is locked

    So basically, it’s dead Ron…

    Good luck with the DB rewrite! Interested to see that with this version you’ve upgraded to SQL3 (I’ve been running on an extremely stable 14xx version for months).

    It’s supported sqlite2 and sqlite3 for a long time now. sqlite3 was kind of changing a moving target though, as they kept changing the threading rules.

    But mostly it’s stalbleish now.

    Is this a windows box? Because that looks more like virus scanner than anything else.

    – Ron

    #14208
    mbaker
    Participant

    It is a Windoze box, but it’s a server (Win Server 2003) without a virus scanner running. Haven’t had a problem like this up to now with any of the older nightlies (but then I haven’t upgraded in a long while).

    Have just moved the iTunes files from the local machine to a NAS (Terastation Live where I’m hoping to migrate Firefly to at some point soon so I can retire the server) but otherwise that’s the only change.

    I remember you commenting on the Sqllite 3 “moving target” previously. Glad to hear it’s settling. That I didn’t know shows how stable my 14xx has been!

    Did some more testing last night/today. Turned off scanning last night and then started Firefly and left it overnight without connecting. It burned hard on the startup scan generating loads of Updating Playlist messages. This morning I connected and it played 2 songs before dying like this.

    ...
    2007-11-18 19:35:56 (d374dfdb): Updating playlists
    2007-11-18 19:35:57 (d374dfdb): Updating playlists
    2007-11-18 19:36:02 (d374dfdb): Updating playlists
    2007-11-18 19:36:12 (d374dfdb): Scanned 14959 songs (was 14959) in 452 seconds
    2007-11-19 10:25:00 (e015e054): Session 0: Streaming file '01 Silver Lining.m4a' to 192.168.0.6 (offset 0)
    2007-11-19 10:28:21 (e016f916): Session 0: Streaming file '02 Close Call.m4a' to 192.168.0.6 (offset 0)
    2007-11-19 10:29:10 (d374dfdb): Rescanning database
    2007-11-19 10:29:11 (d374dfdb): Starting playlist scan
    2007-11-19 10:33:16 (5e28b214): Error: enum_begin failed (error 1): Misc SQL Error: database is locked

    It looks like it’s bumping into itself when trying to get a new song while scanning’s taking place. Seems pretty reproducible. Would a level 9 dump help?

    Cheers,
    Mark

    #14209
    rpedde
    Participant

    @mbaker wrote:

    It is a Windoze box, but it’s a server (Win Server 2003) without a virus scanner running. Haven’t had a problem like this up to now with any of the older nightlies (but then I haven’t upgraded in a long while).

    Have just moved the iTunes files from the local machine to a NAS (Terastation Live where I’m hoping to migrate Firefly to at some point soon so I can retire the server) but otherwise that’s the only change.

    I remember you commenting on the Sqllite 3 “moving target” previously. Glad to hear it’s settling. That I didn’t know shows how stable my 14xx has been!

    Did some more testing last night/today. Turned off scanning last night and then started Firefly and left it overnight without connecting. It burned hard on the startup scan generating loads of Updating Playlist messages. This morning I connected and it played 2 songs before dying like this.

    ...
    2007-11-18 19:35:56 (d374dfdb): Updating playlists
    2007-11-18 19:35:57 (d374dfdb): Updating playlists
    2007-11-18 19:36:02 (d374dfdb): Updating playlists
    2007-11-18 19:36:12 (d374dfdb): Scanned 14959 songs (was 14959) in 452 seconds
    2007-11-19 10:25:00 (e015e054): Session 0: Streaming file '01 Silver Lining.m4a' to 192.168.0.6 (offset 0)
    2007-11-19 10:28:21 (e016f916): Session 0: Streaming file '02 Close Call.m4a' to 192.168.0.6 (offset 0)
    2007-11-19 10:29:10 (d374dfdb): Rescanning database
    2007-11-19 10:29:11 (d374dfdb): Starting playlist scan
    2007-11-19 10:33:16 (5e28b214): Error: enum_begin failed (error 1): Misc SQL Error: database is locked

    It looks like it’s bumping into itself when trying to get a new song while scanning’s taking place. Seems pretty reproducible. Would a level 9 dump help?

    Cheers,
    Mark

    Actually, not really. I spend a whole day a couple weekends ago trying to find it and didn’t see it. I’m in the middle of completely redoing the db backend anyway right now, so by the time I’m done, the db stuff will be radically simplified and the problem will probably go away anyway. So I think it’s going to be a non-issue next nightlies anyway.

    Thanks for the offer of help, though.

    — Ron

    #14210
    mbaker
    Participant

    Sweet. Then I’ll leave you to it. Can’t wait for the new nightly!
    M

    #14211
    indierocksteve
    Participant

    I’ve been noticing this too, glad to hear some fixes are coming!

    thanks

Viewing 7 posts - 16 through 22 (of 22 total)
  • The forum ‘Nightlies Feedback’ is closed to new topics and replies.