I keep getting passthrough requests in my queue causing it to connect when it shouldn’t
1:48: Passthrough: SendRequest to shserver2.ssl.berkeley.edu failed: Connection Timeout
1:48: Passing through request send_result_get_user_stats
1:48: Queued passthrough request
How do i find out which client is causing it? 
Does it have:
11:07am: s@h_wrk Passthrough: Seti@home status: ErrorCode 0x00000064 100
In there as well?
If so, here is the answer…
Originally posted by Mulda
[B]Does it have:
11:07am: s@h_wrk Passthrough: Seti@home status: ErrorCode 0x00000064 100In there as well?
If so, here is the answer… [/B]
No :nono:
Is it fixed yet m8? Are you trying to add a new user to the queue? It seems that SETIQueue will “passthrough” requests from a new user to Berkeley in order to identify it.
No mate, its not fixed yet. Im getting it every few hours (Leave it Mincer;)) There are no new clients on my system. I have disabled pass through requests for now but I could do with finding out which client is causing it
I think ive just found the problem 
4:23: Returning passing through request response
4:23: Passthrough: Seti@home status: ErrorCode 0x00000064 100
4:23: Seti@home message: 'Corrupt user ID. Please exit SETI@Home, delete user_info.sah and result.sah and restart SETI@Hom...
4:23: Passing through request send_result_get_user_stats
4:21: Queued passthrough request
4:21: Sending result 10se03aa.6671.2753.311076.96
Now I just need to find out which client it is :wiggle:
Originally posted by Deaky
[B]I think ive just found the problem
4:23: Returning passing through request response 4:23: Passthrough: Seti@home status: ErrorCode 0x00000064 100 4:23: Seti@home message: 'Corrupt user ID. Please exit SETI@Home, delete user_info.sah and result.sah and restart SETI@Hom... 4:23: Passing through request send_result_get_user_stats 4:21: Queued passthrough request 4:21: Sending result 10se03aa.6671.2753.311076.96
Now I just need to find out which client it is :wiggle: [/B]
Might I offer you a :razz: and a “don’t be so hasty with your replies” 
Drop back a couple more lines in the log and you should see the inbound connection from the client.
Also monitor it for a while if you are using something like Seti Driver to cache on the clients, it took me a week or so to wheedle out all the culprits in my work Q because only 1 or 2 user_info files were corrupt in a large Driver cache.
Originally posted by Deaky
[B]
4:23: Passthrough: Seti@home status: ErrorCode 0x00000064 100
[/B]
Please accept my gracious appologies oh beardy one :hail:
/If anyone wants me I’ll be the one in the corner wearing :hat:
