Sites are still stucking here is there still any work on the servers now ?
Had much probles with loading the stats.....

Don't think there is much wrong at WCG HQ. Your client operates and decides based on a number of dynamic control parameters to ask for work. If it's not asking for work as you can see in the message log, then investigation is in order, the first value to check being the Duration Correction Factor. I've got my config set so it prints it out after completion of each task which includes a correction to this factor based on the last task actual versus estimate. (flops in header of task form basis for estimation with the benchmark values as a function of that calculation).

Here's the one flag <sched_op_debug> set in cc_config.xml and causes me to be informed on DCF and work fetch plus history when perusing the stdoutdae.txt file. From an older log:

11-Jun-2010 20:46:13 [World Community Grid] Computation for task X0000070450149200606261618_0 finished
11-Jun-2010 20:46:13 [World Community Grid] [dcf] DCF: 1.053681->1.059201, raw_ratio 1.108880, adj_ratio 1.052387
11-Jun-2010 20:46:15 [World Community Grid] Started upload of X0000070450149200606261618_0_0
11-Jun-2010 20:46:20 [World Community Grid] Finished upload of X0000070450149200606261618_0_0
11-Jun-2010 20:46:24 [World Community Grid] [sched_op_debug] Starting scheduler request
11-Jun-2010 20:46:24 [World Community Grid] Sending scheduler request: To report completed tasks.
11-Jun-2010 20:46:24 [World Community Grid] Reporting 1 completed tasks, not requesting new tasks
11-Jun-2010 20:46:24 [World Community Grid] [sched_op_debug] CPU work request: 0.00 seconds; 0.00 CPUs
11-Jun-2010 20:46:26 [World Community Grid] Scheduler request completed
11-Jun-2010 20:46:26 [World Community Grid] [sched_op_debug] Server version 601
11-Jun-2010 20:46:26 [World Community Grid] Project requested delay of 11 seconds

Takes out of a few things out of the guessing where the issue may be... and do keep in mind the recent uptime. That goes into the work fetch equation.

This one has a discussed cause from several weeks ago. The system will shut down parts automatically (and restart later) when momentary loads are too high, the first bit closed being the file uploading. Maybe WCG might have to contemplate after all to combine multiple HCC tasks in one same as was done with DDDT1.