Any drive icons visible during the lockup?

During the 5 different solid lockups, I had either the normal spun up but not accessing, spun down, or the newer icon introduced in beta 11.

I've switched to port 81 to see if I can get the other lockups that seem to only affect the control of the player. Most of the time I probably won't notice though, as I rarley use the interface while here at work. Only when I am driving do I notice it when trying to change the volume, or do something else.

Haven't so far @Home have had it running short time on faux DC still haven't had any 'stuck jiffies'. I think it may have to do w/actually being in the car enviroment (power off/on/low/high) that might start it from when it happened to me. I do recall that when I started the car the error was there and nothing else but music was still playing, when I pulled the unit out It made my speakers pop, which I have had before w/o the error just shutting off ignition.

I'm not too concerned about it on startup, as a device driver (e.g. the IDE disk probe) could cause a brief "stuck jiffies" during boot. But if it occurs later on, that would be cause for concern.

Cheers

Well, after moving the http port to 81, I havent had another hard lock. Strangely enough I know that my port 80 is closed to the outside world so I'm a little confused how this has made a difference but it has. Unit has been running for over 7 hours without one lockup. Those stick persons are just dancing away.

That's still only 1116MB per month with triple the volume. If you ever need a mirror I'd put one up in a flash.

Would a flash be big enough? A hard drive of some sort might be better...

pca

khttpd: GET "/msadc/..%255c../..%255c../..%255c/..%c1%1c../..%c1%1c../..%c1%1c../winnt/system32/cmd.exe?/c+dir"

Hmm, I think I will leave the empeg up and running on my network at all times with Hijack.

Whatever you do, guys, don't fix this one. The empeg player is the perfect "canary in a coal mine" Nimda-detector.

Got any nasties running around inside the firewall?

Perhaps there's a bug in the ethernet path in the kernel..

Well an alert would be much better then the player locking. Especially on a Sunday when it's interrupting my music constantly.

My Nimda detector is a perl script that runs against the web logs of one of my servers here. IM should almost know the URL by heart now with as many times as I have given it to them. It shows total attacks, resolved name, IP, and type (Code Red 1, 2 Nimda). Came in real handy for telling a few coworkers they were infected. I'd offer the link, but it has since been turned into a "The End" page.

And I can't believe IIS is still vunerable to the same style quirks that I saw versions ago when I used to be an NT admin. (The whole encode some things into the URL to get the web server to play with files on the hard drive in the system folder).

No, Im clean inside the firewall. I have 2 machines with XP installed that are less than two weeks old and my wife's machine is running XP and all machines run NAV2002. Fortunately we've never had a virus. My wife is smart enough not to open attatchments.

Just to make sure I deep scanned all the PCs on the network and they're all clean so I think I'm virus free.

BTW, my firewall is actually a dual NIC linux box.

Alrighty... MkII, 2.0b11, Hijack v226. Whenever my buddy tries to connect via http to download a track, the player does a hard lock where the display freezes, no buttons work, and no http or ftp connections are accepted. I got him to do it twice repeatably, then i pulled up the Hijack Vitals 2.0b11 screen, and it keeps on truckin' while the display and everything else is frozen. This looks like the same bug KungFuCow and others are reporting. I've never seen this one myself, but it'd definitely different from the other button lockup. The jiffies are still going, and it's easily reproduced.

In reply to:

---

Alrighty... MkII, 2.0b11, Hijack v226. Whenever my buddy tries to connect via http to download a track, the player does a hard lock where the display freezes, no buttons work, and no http or ftp connections are accepted. I got him to do it twice repeatably, then i pulled up the Hijack Vitals 2.0b11 screen, and it keeps on truckin' while the display and everything else is frozen. This looks like the same bug KungFuCow and others are reporting. I've never seen this one myself, but it'd definitely different from the other button lockup. The jiffies are still going, and it's easily reproduced.

---

Well, maybe easy for you (or your buddy), but not for me here.

Can you detail your setup for me: eg. config.ini, using built-in playlist browser (or external XML?), and anything else you can think of?

-ml

Okay, config.ini has no modifications other than some IR_Translate stuff.
Using the standard Hijack HTML, no XML/XSL stuff.

I think we tracked it down. There's one song that is titled "100% Dundee" that seemed to kill it every time. Everything else downloads fine, even downloading 5 or 6 at a time, until you hit that track. Thinking the "%" was the culprit, i renamed the track, taking out the % sign, resynced, and he attempted to download again. It worked no lockups. I downloaded it from my machine as well, no lockups. I then readded the %, resynced, and sure enough, lock up immediately every time when you click on that song.

Could this be a sign of a bigger bug???

Not a major bug, they just forgot to escape the percent codes when enabling XML. Heh. I'm sure we'll see a 228 with escaped percents soon.

Well, it presents the exact same symptoms of the other http lockups... so there's the possiblilty of them being linked. and note this isn't using any XML, just the standard HTML Mark wrote up.

When I saw the nimda hack lock my player up it was requesting a URL which contained escaped characters. Unfortunately there was no debug information presented that would have indicated what request caused the problem, as the only thing on the serial connection were error messages indicating that requests had failed. Unless of corse the last failure also caused the lockup after displaying the error.

EXCELLENT!!!!!!!!!!!!!

Yup, obvious bug in that code.

Standby for v228

-ml