Hi admin folks,

First I get an automated email:

"Your sensor connected to host 8073 currently runs in debug mode."

I check and debug mode is disabled. So I don't know why I get the email.

Then I check the WUs. This set-up is normally unmonitored so I don't watch the WUs come in and go out. Apparently they have been running for very short times (I did have the task length set to 24 hours) and I'm getting no credit for them, even though data is being recorded.

So, I unplug the sensor, plug it back in and it is still running short times (I now set the WU length to one hour). I'm getting credit but I have no idea why this is all happening as I hadn't adjusted anything for months.

Has my sensor malfunctioned?

To add to the weirdness, I just looked through some of the Marked as Invalid WUs and found some very odd entries like this one:

3765694 3746410 8073 3 Sep 2014 | 7:23:44 UTC 3 Sep 2014 | 7:24:22 UTC Completed, marked as invalid 112,006.00 112,006.00 0.00 Radioactivity Monitor v1.77 (nci)


Turnaround time was 38 seconds yet somehow I clocked up 112,006 CPU seconds. Did I just invent time travel?

Looks like your sensor stops working after the first few readings (the cpm drops to zero). Or your USB port goes into power-saving mode maybe?

I don't know what this means though:

"claimed interface, could not get bound driver: No data available,0"

I don't get that in my stderr output.

Edit: You haven't got a BU asic on the same MB USB port have you? That'll be sucking you dry (if you will).
____________

Looks like your sensor stops working after the first few readings (the cpm drops to zero). Or your USB port goes into power-saving mode maybe?

I don't know what this means though:

"claimed interface, could not get bound driver: No data available,0"

I don't get that in my stderr output.

Edit: You haven't got a BU asic on the same MB USB port have you? That'll be sucking you dry (if you will).