Panic Mode On (79) Server Problems?

Message boards : Number crunching : Panic Mode On (79) Server Problems?
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 . . . 22 · Next

AuthorMessage
Rolf

Send message
Joined: 16 Jun 09
Posts: 114
Credit: 7,817,146
RAC: 0
Switzerland
Message 1307905 - Posted: 19 Nov 2012, 22:13:15 UTC - in response to Message 1307890.  

11/19/2012 4:36:36 PM | SETI@home | Sending scheduler request: To fetch work.
11/19/2012 4:36:36 PM | SETI@home | Reporting 60 completed tasks
11/19/2012 4:36:36 PM | SETI@home | Requesting new tasks for NVIDIA
11/19/2012 4:36:40 PM | | Project communication failed: attempting access to reference site
11/19/2012 4:36:40 PM | SETI@home | Scheduler request failed: Server returned nothing (no headers, no data)
11/19/2012 4:36:42 PM | | Internet access OK - project servers may be temporarily down...

Pretty much the same thing here in Switzerland:

19.11.2012 23:05:52 | SETI@home | update requested by user
19.11.2012 23:05:52 | SETI@home | Sending scheduler request: Requested by user.
19.11.2012 23:05:52 | SETI@home | Not reporting or requesting tasks
19.11.2012 23:05:53 | SETI@home | Scheduler request failed: Server returned nothing (no headers, no data)
19.11.2012 23:05:57 | | Project communication failed: attempting access to reference site
19.11.2012 23:05:59 | | Internet access OK - project servers may be temporarily down.

N.B. times are UTC+1

ergo: SETI is off and Primegrid is running!!! It's so easy and simple!
ID: 1307905 · Report as offensive
juan BFP Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 16 Mar 07
Posts: 9786
Credit: 572,710,851
RAC: 3,799
Panama
Message 1307915 - Posted: 19 Nov 2012, 22:25:51 UTC

AP-Splitters are off... so everything works normal, but just for the few WU left on the Ready to send cache last update: 223,850 MB and 821 AP.

After that, if the splitters still offline, everything will return to the dryland...
ID: 1307915 · Report as offensive
MikeN

Send message
Joined: 24 Jan 11
Posts: 319
Credit: 64,719,409
RAC: 85
United Kingdom
Message 1307924 - Posted: 19 Nov 2012, 22:36:28 UTC - in response to Message 1307915.  

Amazingly one of my machines just managed to connect and nabbed 6 of those APs in one request. That will keep its CPUs happy for 3 days.
ID: 1307924 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14645
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1307955 - Posted: 19 Nov 2012, 23:40:30 UTC

On the other hand, I'm getting:

19/11/2012 23:37:13 | SETI@home | Sending scheduler request: Requested by user.
19/11/2012 23:37:13 | SETI@home | Reporting 48 completed tasks
19/11/2012 23:37:13 | SETI@home | Not requesting tasks: "no new tasks" requested via Manager
19/11/2012 23:37:13 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
19/11/2012 23:37:13 | SETI@home | [sched_op] NVIDIA work request: 0.00 seconds; 0.00 devices
19/11/2012 23:37:13 | SETI@home | [http] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
19/11/2012 23:37:13 | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
19/11/2012 23:37:14 | SETI@home | [http] [ID#1] Info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#0)
19/11/2012 23:37:14 | SETI@home | [http] [ID#1] Info: Trying 208.68.240.20...
19/11/2012 23:37:15 | SETI@home | [http] [ID#1] Info: Connection refused
19/11/2012 23:37:15 | SETI@home | [http] [ID#1] Info: Failed connect to setiboinc.ssl.berkeley.edu:80; No error
19/11/2012 23:37:15 | SETI@home | [http] [ID#1] Info: Closing connection #0
19/11/2012 23:37:15 | SETI@home | [http] HTTP error: Couldn't connect to server
19/11/2012 23:37:16 | SETI@home | Scheduler request failed: Couldn't connect to server

That's not good.
ID: 1307955 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1307958 - Posted: 19 Nov 2012, 23:49:01 UTC - in response to Message 1307955.  


Maybe That's good ;)

I think they maybe implemented something as 'Max simultaneous connected hosts'?

E.g. if the servers now process requests from 5000 computers any attempt to connect will be dropped immediately.
When some of those 5000 computers finish the request 1 'connection slot' will be free so next computer attempting a connection will be served?


 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1307958 · Report as offensive
Profile Bernie Vine
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 26 May 99
Posts: 9954
Credit: 103,452,613
RAC: 328
United Kingdom
Message 1307964 - Posted: 20 Nov 2012, 0:03:06 UTC

Cricket graph shows a dip that is just recovering.

Cricket
ID: 1307964 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14645
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1307966 - Posted: 20 Nov 2012, 0:09:46 UTC
Last modified: 20 Nov 2012, 0:18:39 UTC

Well, they're trying something new alright:

20/11/2012 00:05:53 | SETI@home | Sending scheduler request: Requested by user.
20/11/2012 00:05:53 | SETI@home | Reporting 49 completed tasks
20/11/2012 00:05:53 | SETI@home | Not requesting tasks: "no new tasks" requested via Manager
20/11/2012 00:05:53 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
20/11/2012 00:05:53 | SETI@home | [sched_op] NVIDIA work request: 0.00 seconds; 0.00 devices
20/11/2012 00:05:53 | SETI@home | [http] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/11/2012 00:05:53 | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
20/11/2012 00:05:53 | SETI@home | [http] [ID#1] Info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#0)
20/11/2012 00:05:53 | SETI@home | [http] [ID#1] Info: Trying 208.68.240.20...
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.20) port 80 (#0)
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.20) port 80 (#0)
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: POST /sah_cgi/cgi HTTP/1.1
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.0.38)
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Host: setiboinc.ssl.berkeley.edu
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Accept: */*
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Content-Length: 232400
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Expect: 100-continue
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server:
20/11/2012 00:05:55 | SETI@home | [http] [ID#1] Info: Done waiting for 100-continue
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: HTTP 1.0, assume close after body
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: HTTP/1.0 302 Found
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: the ioctl callback returned 0
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: Location: http://synergy.ssl.berkeley.edu:81/sah_cgi/cgi
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: Content-Type: text/html
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: Content-Length: 210
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server:
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: Closing connection #0
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: Issue another request to this URL: 'http://synergy.ssl.berkeley.edu:81/sah_cgi/cgi'
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: Violate RFC 2616/10.3.3 and switch from POST to GET
20/11/2012 00:06:10 | SETI@home | [http] [ID#1] Info: About to connect() to synergy.ssl.berkeley.edu port 81 (#0)
20/11/2012 00:06:10 | SETI@home | [http] [ID#1] Info: Trying 128.32.18.157...
20/11/2012 00:06:31 | SETI@home | [http] [ID#1] Info: Timed out
20/11/2012 00:06:31 | SETI@home | [http] [ID#1] Info: Failed connect to synergy.ssl.berkeley.edu:81; No error
20/11/2012 00:06:31 | SETI@home | [http] [ID#1] Info: Closing connection #0
20/11/2012 00:06:31 | SETI@home | [http] HTTP error: Couldn't connect to server
20/11/2012 00:06:32 | SETI@home | Scheduler request failed: Couldn't connect to server

That looks like an attempt to bounce me onto the Campus network port.

Edit: shortly afterwards, and after the same preamble, it went down the proper path:

20/11/2012 00:12:12 | SETI@home | [http] [ID#1] Info: Done waiting for 100-continue
20/11/2012 00:12:31 | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 200 OK
20/11/2012 00:12:31 | SETI@home | [http] [ID#1] Received header from server: Date: Tue, 20 Nov 2012 00:12:38 GMT
20/11/2012 00:12:31 | SETI@home | [http] [ID#1] Received header from server: Server: Apache/2.2.17 (Fedora)
20/11/2012 00:12:31 | SETI@home | [http] [ID#1] Received header from server: Connection: close
20/11/2012 00:12:31 | SETI@home | [http] [ID#1] Received header from server: Transfer-Encoding: chunked
20/11/2012 00:12:31 | SETI@home | [http] [ID#1] Received header from server: Content-Type: text/xml
20/11/2012 00:12:31 | SETI@home | [http] [ID#1] Received header from server:
20/11/2012 00:12:34 | SETI@home | [http] [ID#1] Info: Closing connection #0
20/11/2012 00:12:35 | SETI@home | Scheduler request completed
20/11/2012 00:12:35 | SETI@home | [sched_op] Server version 701
20/11/2012 00:12:35 | SETI@home | Project requested delay of 303 seconds
20/11/2012 00:12:35 | SETI@home | [sched_op] handle_scheduler_reply(): got ack for task 20au12ad.14321.244826.140733193388038.10.221_0

That's the way to do it.
ID: 1307966 · Report as offensive
Flipper

Send message
Joined: 31 Jul 10
Posts: 18
Credit: 117,656
RAC: 0
Australia
Message 1308005 - Posted: 20 Nov 2012, 2:38:46 UTC
Last modified: 20 Nov 2012, 3:32:36 UTC

Has anybody else been getting ghosts. i seem to have over 70 work units saying they were downloaded but they haven't. Any suggestions? Have they changed the way work units are downloaded. As in allocating x amount of WU's then downloading them in blocks of 20.
ID: 1308005 · Report as offensive
Profile Akio
Avatar

Send message
Joined: 18 May 11
Posts: 375
Credit: 32,129,242
RAC: 0
United States
Message 1308009 - Posted: 20 Nov 2012, 4:57:01 UTC

What's with all these current problems facing Seti@home as of late? (rhetorical). This is LAME! Love: me.
ID: 1308009 · Report as offensive
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1308013 - Posted: 20 Nov 2012, 5:21:22 UTC - in response to Message 1307966.  

Well, they're trying something new alright:

[quote]20/11/2012 00:05:53 | SETI@home | Sending scheduler request: Requested by user.
20/11/2012 00:05:53 | SETI@home | Reporting 49 completed tasks
20/11/2012 00:05:53 | SETI@home | Not requesting tasks: "no new tasks" requested via Manager
20/11/2012 00:05:53 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
20/11/2012 00:05:53 | SETI@home | [sched_op] NVIDIA work request: 0.00 seconds; 0.00 devices
20/11/2012 00:05:53 | SETI@home | [http] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/11/2012 00:05:53 | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
20/11/2012 00:05:53 | SETI@home | [http] [ID#1] Info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#0)
20/11/2012 00:05:53 | SETI@home | [http] [ID#1] Info: Trying 208.68.240.20...
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.20) port 80 (#0)
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.20) port 80 (#0)
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: POST /sah_cgi/cgi HTTP/1.1
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.0.38)
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Host: setiboinc.ssl.berkeley.edu
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Accept: */*
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Content-Length: 232400
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server: Expect: 100-continue
20/11/2012 00:05:54 | SETI@home | [http] [ID#1] Sent header to server:
20/11/2012 00:05:55 | SETI@home | [http] [ID#1] Info: Done waiting for 100-continue
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: HTTP 1.0, assume close after body
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: HTTP/1.0 302 Found
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: the ioctl callback returned 0
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: Location: http://synergy.ssl.berkeley.edu:81/sah_cgi/cgi
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: Content-Type: text/html
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server: Content-Length: 210
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Received header from server:
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: Closing connection #0
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: Issue another request to this URL: 'http://synergy.ssl.berkeley.edu:81/sah_cgi/cgi'
20/11/2012 00:06:09 | SETI@home | [http] [ID#1] Info: Violate RFC 2616/10.3.3 and switch from POST to GET
20/11/2012 00:06:10 | SETI@home | [http] [ID#1] Info: About to connect() to synergy.ssl.berkeley.edu port 81 (#0)
20/11/2012 00:06:10 | SETI@home | [http] [ID#1] Info: Trying 128.32.18.157...
20/11/2012 00:06:31 | SETI@home | [http] [ID#1] Info: Timed out
20/11/2012 00:06:31 | SETI@home | [http] [ID#1] Info: Failed connect to synergy.ssl.berkeley.edu:81; No error
20/11/2012 00:06:31 | SETI@home | [http] [ID#1] Info: Closing connection #0
20/11/2012 00:06:31 | SETI@home | [http] HTTP error: Couldn't connect to server
20/11/2012 00:06:32 | SETI@home | Scheduler request failed: Couldn't connect to server

That looks like an attempt to bounce me onto the Campus network port.

Edit: shortly afterwards, and after the same preamble, it went down the proper path:

With the trying it could be possible to extend the transaction not to time out pre-maturely.

ID: 1308013 · Report as offensive
Cosmic_Ocean
Avatar

Send message
Joined: 23 Dec 00
Posts: 3027
Credit: 13,516,867
RAC: 13
United States
Message 1308023 - Posted: 20 Nov 2012, 6:09:02 UTC

I finally got a bundle of completed APs reported a few minutes ago. I've been hitting the update button every 2-3 hours all day and it kept either doing time out or "no headers, no data."

On a side-note, Since switching from 6.2.19 to 6.10.58, I have noticed that my cache is not being processed in FIFO. It is all APs..about 17 days worth, and APs with a deadline four days sooner than the ones that keep getting picked to run next are still sitting there not getting started.

I know there are cache/queue changes along the way through the build history, but each WU has a 25-day deadline, so wouldn't it still make sense to run the soonest deadlines first (which also happen to be the ones that were acquired first)? I mean, it works out in the end I'm sure, but it's just weird.
Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)
ID: 1308023 · Report as offensive
Profile Brother Frank

Send message
Joined: 10 Dec 11
Posts: 26
Credit: 15,142,410
RAC: 0
United States
Message 1308028 - Posted: 20 Nov 2012, 6:25:37 UTC

SETI UPLOADS of finished work are slowly being retrieved. I had to turn off my proxy server activity and return to the normal BOINC communication channel first. First I used the Network Communication request to break out of a long time-out. Then I did manual update. I am going to try to let them all run by themselves now. A hint came later this afternoon when my little Toshiba Portege R705 with i3 processor and integrated graphics was able to send back its finished work.

My Intel i7 2600k based box with two Nvidia GTX 550 Ti cards was just able to send about 60 work units back over the last half hour. The first time in about a day. It had run out of work too. All day Sunday and Monday until mid-afternoon were very dry periods here. I also got new work units to process this evening. Other boxes with Nvidia cards are also slowing returning to life. I found that I could break out of the long timeouts and issue a manual update soon after I updated my i7 2670qm based notebook later this afternoon. Seti is not running right yet, because it is only sending gpu jobs to my i7 2670 qm notebook with one dedicated Nvidia 525m card, but no work at all for its other 7 processors. It's a start.

Thank you Seti at Home team working at the lab. Whatever changes you made are helping variety of windows 7 machines and my one core duo notebook using Windows Vista. All have 64 bit operating systems and are running Home Premium. My Core Duo desktop is running Windows 7 Ultimate. Brother Frank
Frank Elliott,Member of Carepages.com,a chronic illness support site. Was FrankLivingFully there.Free user name & pw needed. My Google+ Profile is:
https://profiles.google.com/u/0/10871372137584 Science,SF,Space,Astronomy,Medicine,Psyc Topics.
ID: 1308028 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13715
Credit: 208,696,464
RAC: 304
Australia
Message 1308034 - Posted: 20 Nov 2012, 7:32:58 UTC - in response to Message 1308028.  


Presently according to the Server Status page there are no splitters of either type running, nor any work ready to send.
Grant
Darwin NT
ID: 1308034 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14645
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1308048 - Posted: 20 Nov 2012, 9:08:55 UTC - in response to Message 1308034.  

Presently according to the Server Status page there are no splitters of either type running, nor any work ready to send.

And there have been none since about 01:00 UTC (AP) and 03:00 UTC (MB). (except a few resends from errors and timeouts, of course)

Yet the Cricket graph has been at maximum, throughout. What's all that data?
ID: 1308048 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13715
Credit: 208,696,464
RAC: 304
Australia
Message 1308050 - Posted: 20 Nov 2012, 9:16:55 UTC - in response to Message 1308048.  

What's all that data?

Scheduler responding "Project has no tasks available" to all the requests for work?

I noticed that too, and can't think of any reason why it would be that way unless they're archiving/retrieving from archives some data.
Grant
Darwin NT
ID: 1308050 · Report as offensive
juan BFP Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 16 Mar 07
Posts: 9786
Credit: 572,710,851
RAC: 3,799
Panama
Message 1308051 - Posted: 20 Nov 2012, 9:18:20 UTC
Last modified: 20 Nov 2012, 9:52:03 UTC

I don´t belive in witches, but the exist, exist...

A possible explanation, besides some "ghosts in the machine" (servers try to resend ghost units), i realy have no ideia...

Something else on the lab could actualy using the 100MB pipe... an "alien virus"?, another project experimental data?

I belive is easy to find that, tracing to where/from all data is sended/received... But that must be made by the people who have access to the lab.

That could be the source of our latest headaches...
ID: 1308051 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14645
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1308061 - Posted: 20 Nov 2012, 10:23:00 UTC - in response to Message 1308051.  

Yes, it could be ghosts being resent - some of my machines had developed a new crop of hauntings overnight. But it looks like it's beginning to decay now - this might be a good time to try manual updates, and help flush the remaining gremlins out of the system.
ID: 1308061 · Report as offensive
tbret
Volunteer tester
Avatar

Send message
Joined: 28 May 99
Posts: 3380
Credit: 296,162,071
RAC: 40
United States
Message 1308063 - Posted: 20 Nov 2012, 10:28:12 UTC - in response to Message 1308051.  

I don´t belive in witches, but the exist, exist...

A possible explanation, besides some "ghosts in the machine" (servers try to resend ghost units), i realy have no ideia...

Something else on the lab could actualy using the 100MB pipe... an "alien virus"?, another project experimental data?

I belive is easy to find that, tracing to where/from all data is sended/received... But that must be made by the people who have access to the lab.

That could be the source of our latest headaches...


Somethings loopy.

It's talking to itself even when it isn't saying anything.
ID: 1308063 · Report as offensive
juan BFP Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 16 Mar 07
Posts: 9786
Credit: 572,710,851
RAC: 3,799
Panama
Message 1308076 - Posted: 20 Nov 2012, 11:52:22 UTC - in response to Message 1308061.  

Yes, it could be ghosts being resent - some of my machines had developed a new crop of hauntings overnight. But it looks like it's beginning to decay now - this might be a good time to try manual updates, and help flush the remaining gremlins out of the system.

Maybe because the daylight, ghost don't like daylight.

ID: 1308076 · Report as offensive
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65690
Credit: 55,293,173
RAC: 49
United States
Message 1308096 - Posted: 20 Nov 2012, 13:57:07 UTC - in response to Message 1308061.  

Yes, it could be ghosts being resent - some of my machines had developed a new crop of hauntings overnight. But it looks like it's beginning to decay now - this might be a good time to try manual updates, and help flush the remaining gremlins out of the system.

Well as long as it's just Pocha Hauntis...
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 1308096 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 . . . 22 · Next

Message boards : Number crunching : Panic Mode On (79) Server Problems?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.