• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Problems connecting to any Team Proxy? -=Read This=-

MaxSiren

Senior member
Noticed a few new people tried downloading from my Queue today with no luck.

It turns out that when a user new to a certain Queue tries to download WUs for the first time, the Queue needs to contact Berkeley with that user's email address in order to find their Seti ID. This ID is needed because SetiQueue uses it to keep track of which WUs were sent to which user. So with Berkeley being unreliable today, the Queue wasn't able to get any new people's ID and just refused to send out WUs to them. It also seems that if SetiQueue can't contact Berkeley as soon as the new user connects, it doesn't try again later. What I found strange is that these incomplete queues were still filled with 10 WUs each, which seems kind of silly if you ask me. Chalk it up as a minor design flaw, I guess.

The lesson learned?

Proxy servers are very useful as a remote caching system for when Berkeley goes down, but only if you're using it BEFORE Berkeley goes down!!! 😉

Tip of the day?

Set at least one of your systems to use a TeAm proxy all the time. This will maintain an active account for you on that particular proxy.
 
Well I'm not how it happened but somebody connected and grabbed a Wu as well the Q its self filled up with default amount of Linux CLI. Go figure, If anyone already has account on one of the proxies go ahead and change all over to them. I still have 890+ Wu's available.












SHUX
 
Back
Top