Smoking Room (Dec 30 2008)
Smoking Room (Dec 30 2008) |
|
| log in |
Message boards : Technical News : Smoking Room (Dec 30 2008)
| Author | Message |
|---|---|
 Matt LebofskyVolunteer moderator Project administrator Project developer Project scientist  Send message Joined: 1 Mar 99 Posts: 1375 Credit: 74,079 RAC: 0  | |
|
Yep, we had our usual Tuesday outage. Nothing special, except that the result table is vastly bloated due to the back-end queues being clogged for one reason or another. So the "compression" part of our outage took an extra hour (roughly). So be it. Hopefully the wheels were greased enough to continue letting these drain without much intervention on my or Jeff's part. In any case except a slightly painful recovery as we continue to catch up. We're also pulling up a bunch more unanalyzed raw data to keep the splitters happy during the long weekend. Other than that today.. a lot of planning and preparing for various bigger projects to tackle once the holidays are over and we're all back in the lab - adding yet more workunit storage, reconfiguring database/raw data storage, adding more stuff to the closet, upgrading OSes, retiring older machines, bringing newer ones on line already. That's all well and good, except that Eric, Jeff, and I have three separate higher-priority tasks to tackle before anything else if possible. Those are (a) wrapping up all radar blanking efforts (we still get too many result overflows due to missed and therefore unblanked radar), (b) noise shaping (the noise we're injecting to reduce the effect of the radar is causing predictable and removable but nevertheless messy analysis artifacts), and (c) the NTPCker (the real-time candidate finder/reporter - so we might have something positive to mention come our 10th year anniversary in May). | |
ID: 846958 ·  | |
|
| |
| ID: 846963 · | |
|
And wishing all the staff at Seti a very Kitty New Year....from | |
| ID: 846972 · | |
|
Have a well deserved New Year break! | |
| ID: 847078 · | |
|
Matt and crew, | |
| ID: 847296 · | |
|
Hi Matt, | |
| ID: 847496 · | |
|
Well it's now been over 24hrs since any of my pc's have been able to report completed work. :( | |
| ID: 847896 · | |
|
Gigabitethernet graphs show that the systems has taken a holiday :( | |
| ID: 847897 · | |
Well it's now been over 24hrs since any of my pc's have been able to report completed work. :( Checking the home page is often advised when you suspect server issues. At the moment, it says: December 31, 2008 Since the scheduling server also handles reported work, it stands to reason.... ____________ | |
| ID: 847917 · | |
|
Checking the "Home" page is helpfull, but the server status page shows that the scheduling server "anakin" is UP amd "running". I guess the human input is accurate as reporting results and new work downloads are responded to with "Scheduler request failed: HTTP gateway timeout". | |
| ID: 847926 · | |
Checking the "Home" page is helpfull, but the server status page shows that the scheduling server "anakin" is UP amd "running". I guess the human input is accurate as reporting results and new work downloads are responded to with "Scheduler request failed: HTTP gateway timeout". One thing to remember about the server status page is that it only checks to see if the server is actually running, but nothing about if all the processes are working or crashed as far as I know. | |
| ID: 848061 · | |
Checking the "Home" page is helpfull, but the server status page shows that the scheduling server "anakin" is UP amd "running". I guess the human input is accurate as reporting results and new work downloads are responded to with "Scheduler request failed: HTTP gateway timeout". That's correct. I remember reading about this once before.. the status page only sees if the process on the server is still running... kind of like looking in the task manager on Windows and seeing if svchost.exe (any one of the many) are still listed. If it is there, it is said to be running, regardless of what it is actually doing..or not doing. ____________  Linux laptop uptime: 1484d 22h 42m Ended due to UPS failure, found 14 hours after the fact | |
| ID: 848091 · | |
|
Happy Newyear to all of the staff and a well deserved weekend, too. | |
| ID: 848196 · | |
Checking the "Home" page is helpfull, but the server status page shows that the scheduling server "anakin" is UP amd "running". I guess the human input is accurate as reporting results and new work downloads are responded to with "Scheduler request failed: HTTP gateway timeout". It's also difficult to decide sometimes how to report "errors" -- if the scheduler was on last time, but you can't even find the server now, do you report it as "up" (last known state) or is the error due to some other issue (like network loading) that prevents the monitoring machine from even reaching the server. Either way, you can have "false ups" and "false downs." ____________ | |
| ID: 848274 · | |
Checking the "Home" page is helpfull, but the server status page shows that the scheduling server "anakin" is UP amd "running". I guess the human input is accurate as reporting results and new work downloads are responded to with "Scheduler request failed: HTTP gateway timeout". Of course it's not always that simple, when I was looking at the page, it was saying all was green, however the page had not updated for over an hour at that stage, but no one seemed to notice that. So if whatever updates the server status page stops, all bets are off!! Bernie :-) ____________  | |
| ID: 848327 · | |
Message boards : Technical News : Smoking Room (Dec 30 2008)
| Copyright © 2013 University of California |
