Folding Forum

I have 40 F@H 6.34 nodes still configured as -bigadv that were getting work units until this past weekend. They are still unable to get work units even if I remove the -bigadv flag and restart the client. Are folks still experiencing issues getting work units?

I'm still having problems with this host on multiple machines. I removed 7.1.52 and reinstalled 6.34 and pulled a work unit from another server just fine. Not sure why I'm getting so many HTTP_GATEWAY_TIMEOUTs for 129.74.85.15 when I can reach all the other F@H servers.

There may be a problem with the server or your connecting to it, but it is not from lack of work being available. The status reported on the server status page, http://fah-web.stanford.edu/pybeta/serverstat.html, has been "full" and "accepting" for over 24 hours into the past. T...

This was my first attempt reading the server status and your post clued me in. It appears I was reading it wrong. I cannot traceroute to the server from behind my NAT. foo.bar.com and x.x.x.x are my HTTP proxy. wget output follows: # wget http://129.74.85.15 --2012-07-31 12:10:13-- http://129.74.85....

Have you worked through the stickied Troubleshooting Tips ? Yes, that's how I figured out I was getting assigned to a server in "Active" status. If I'm reading this right, this server is not assigning new WUs, yet I'm getting sent to it anyway. My v7.1.52 client is configured for "ad...

My 7.1.52 Linux clients keep trying to get work units from 129.74.85.15 but server status shows "accept". Why am I getting assigned this server when it's not dishing out new work units? According to the status page, "Accept" means the server is only accepting WUs, not assigning. ...

I've been having problems with this server since yesterday and it's still taking place. I'm getting HTTP_GATEWAY_TIME_OUT across about 20 servers. I thought it might be an internal transparent proxy issue, but then I got assigned a different work server (171.67.108.60) for a couple of units and it w...