I am seeing app weirdness for my Jetson Nano. Not getting any cpu work anymore. App is disappearing. No response from anyone yet as to why or if they are seeing a similar issue.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

2 of the handful of tasks it picked the wrong app for my machine resulted in error. I'm going to abort the rest of them that have been assigned to the wrong app. I have no idea why it did this, but hopefully it won't happen again. I post this in case anyone else experiences weirdness in app assignment and is curious.

The ones I got with the wrong app I got at
12 Oct 2019, 23:37:05 UTC

If you want to keep the server from sending the 32-bit App just install the SSE41 CPU App on that machine. It will only run the SSE41 App named in the app_info.xml and it will probably run the CPU tasks quite a bit faster than the stock CPU App. The server will automatically occasionally send other CPU Apps just to make sure the one you are running is the fastest App. There isn't anything you can do about it, except, install your own App with an app_info.xml.

TBar - Thanks for the information! It is nice to know that it used the other app (which caused errors) as a part of the normal functioning of the system. I thought something was broken. Glad it to know it is a feature not a bug (ha).

We got a few files added to the list
blc54_2bit_guppi_58642* (8-29) .

They will have to give us more before the weekend. Especially now that it has been reported that the Sunday morning crash problem has been fixed (look at panic thread)

We got a few files added to the list
blc54_2bit_guppi_58642* (8-29) .

They will have to give us more before the weekend. Especially now that it has been reported that the Sunday morning crash problem has been fixed (look at panic thread)

. . The report is that Eric thinks he has snared the Sunday morning gremlin.

. . In a few days we will know. Hopefully they are not a tribe ...

Stephen

? ?

We got a few files added to the list
blc54_2bit_guppi_58642* (8-29) .

They will have to give us more before the weekend. Especially now that it has been reported that the Sunday morning crash problem has been fixed (look at panic thread)

. . The report is that Eric thinks he has snared the Sunday morning gremlin.

. . In a few days we will know. Hopefully they are not a tribe ...

Stephen

? ?

Hi Stephen,

I believe Unixchick is correct. Here is the initial post from Mr. Kevvy in the Panic thread:

Dr. Korpela indicated that he just may have found and fixed the Sunday unresponsive scheduler issue. Let's hope we're back to merely one weekly outage...

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I believe Unixchick is correct. Here is the initial post from Mr. Kevvy in the Panic thread:

Dr. Korpela indicated that he just may have found and fixed the Sunday unresponsive scheduler issue. Let's hope we're back to merely one weekly outage...

That does sound like a significant change from the email I got very late on Sunday night:

And I think, maybe, I've found the problem.

I'm sure those of us who live in Europe (or other convenient timezones) will be watching closely on Sunday morning to see whether the fix has fixed it.

Hi Stephen,
I believe Unixchick is correct. Here is the initial post from Mr. Kevvy in the Panic thread:

Dr. Korpela indicated that he just may have found and fixed the Sunday unresponsive scheduler issue. Let's hope we're back to merely one weekly outage...

Have a great day! :)
Siran

. . You both seem to have skipped that very important part of the statement

Stephen

:)

. . You both seem to have skipped that very important part of the statement

There are three parts to the statement:

Found last Sunday
Fixed on Tuesday
Tested next Sunday

:-)

Ha. This discussion about the fix is really about who is an optimist and who is not. I saw the "may" in his statement, but lean toward I bet he did fix it.

The system overall just doesn't seem to be running as well as it used to though. The waiting for deletion is high for no good reason. Either they have changed the system (new normal) or something is broken. Seti also hasn't built up the RTS queue to its normal 600k+ level after the outage, and it isn't like the outage was that long.

It isn't a panic, as I'm sure seti will work through the deletions and build back the RTS and all will be just fine, but it is weird.

edit - I see Grant noticed the same thing and posted in the panic thread.

Ha. This discussion about the fix is really about who is an optimist and who is not. I saw the "may" in his statement, but lean toward I bet he did fix it.

. . OK call me a cynic ... but I have accepted that Murphy's Law is the most reliable ... :)

. . And I have the theory that software bugs are like cockroaches, they are rarely only one.

Stephen

:)

Ha. This discussion about the fix is really about who is an optimist and who is not. I saw the "may" in his statement, but lean toward I bet he did fix it.

. . OK call me a cynic ... but I have accepted that Murphy's Law is the most reliable ... :)

. . And I have the theory that software bugs are like cockroaches, they are rarely only one.

Stephen

:)

But, remember Murphy was an optimist ;-)

But, remember Murphy was an optimist ;-)

Yup, he was SURE things would go wrong...... :)

---

A proud member of the OFA (Old Farts Association).

We got some new files blc36_2bit_guppi_58643* (16 thru 98 with many gaps).
We are also getting old Aricebo files again to rerun.

I have a data related question. I was wondering how long on average it takes to process a petabyte of data? I could work it out with the work unit size but I thought it might not be quite that simple to get an accurate timing. TIA for information in regards to this.

---

Well, we've passed the witching hour of 12:00 UTC on a Sunday - and we still have a working scheduler. Kudos to Eric for a successful fix.

Well, we've passed the witching hour of 12:00 UTC on a Sunday - and we still have a working scheduler. Kudos to Eric for a successful fix.

+1

---

A proud member of the OFA (Old Farts Association).

Well, we've passed the witching hour of 12:00 UTC on a Sunday - and we still have a working scheduler. Kudos to Eric for a successful fix.

. . Operation Sunday sulk seems to be successful ... :)

Stephen

:)

Well, we've passed the witching hour of 12:00 UTC on a Sunday - and we still have a working scheduler. Kudos to Eric for a successful fix.

Fantastic!

Of course we will have to find something else to chat about and other excuses to go to the pub and/or burn hair.

Happy no outage Sunday to all my friends.

Well, we've passed the witching hour of 12:00 UTC on a Sunday - and we still have a working scheduler. Kudos to Eric for a successful fix.

Juan must be in mourning, he will have to fabricate a new reason to amble down to the pub.

---