• 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.

SeitQ problem - static IP fixed - Thanks Smoke - New Problem now!

W

Wiz

Diamond Member
I just got a static IP for my Q machine (for a different reason 😉) and thought it would be nice to be able to put that online for my machines that are not local.

I fiddled around and got that working, but now the only one that does not get an error is the machine its running on. The other machines try to connect to the Q but you can see the command window and it does connect but ends with an error and then disappears.

Please help!
 
Check your settings.

Settings for the TeAm Enterprise Q:

IP & Subnet Mask 0.0.0.0, 0.0.0.0
Port Number 5517
Connect Type WinINetDirect
 
Thanks, I will try that & see if I can see it from work 😉

(do you have a static IP on that one?)
 
Not static ... I use DNS2GO.

Don't forget your port forwarding! 🙂


/smoke ducks before wiz gives him a back-hand .... "damn rookies"/ lol
 
Thank you, my master. 😉
When we first met it was me helping you, now the tables have turned...
You could say as another famous character once said:

I've been waiting for you, Obi-Wan. We meet again, at last. The circle is now complete. When I met you I was but the learner. Now, *I* am the master.
Click to expand...
😉 😛
Thanks Greg, I can see it from work and I see one of the machines on my LAN sent a WU through already!




edit:
geez, this job at the library is getting to me... I'm like waxing all eloquent & stuff...
 
Now this is weird, I see WU's transmit from a work box but I don't see them in my Q history...

What would cause that???
 
Do you see them in the results queued to be sent to the Seti@Home server?

Do you need to clear your browser cache?
 
no, the name of this computer isn't showing up

I do see it change when other machines send in new units - so its not a cache problem.
 
looks like the WU's are being counted @ Seti@Home but not showing up in my Q.
This machine never downloaded anything from the Q so is there something I need to do to set it up for a new machine connecting from the Internet?
 
Look in your LOGS.

You should see an entry saying something like, "WU Received but not distributed from this SetiQueue." I currently don't have any such entrees in my Q so I am only going by what I've seen in the paste. The words may be different but their meaning will be the same.

When WUs distributed by your Q start coming back they will appear in history ... I guess. It's been so long since I've seen this action I could be wrong.

edit: It appears the final steps are taking place to end Seti-Classic so I wouldn't worry too much about this. 😉
 
Originally posted by: Smoke
Look in your LOGS.

You should see an entry saying something like, "WU Received but not distributed from this SetiQueue." I currently don't have any such entrees in my Q so I am only going by what I've seen in the paste. The words may be different but their meaning will be the same.

When WUs distributed by your Q start coming back they will appear in history ... I guess. It's been so long since I've seen this action I could be wrong.

edit: It appears the final steps are taking place to end Seti-Classic so I wouldn't worry too much about this. 😉
Click to expand...
i believ you are correct Greg( As best my old mind remembers)

 
nope, not showing in the logs either...

this is twilight zone material here...

I just send a few more through, the command window opens, it sais its connecting to the right IP & port, it sends & receives & closes the window and seti driver shows one less in the "need to fill" number. 😕

...to complicate matters, these units were originally downloaded to a machine on my lan - then transported here via memory card...
 
Read the "ALL" log, it contains everything that happens in the Q. The logs are truncated when they run out of the space you have allocated. Increase the size of the "Report Size Limit" and you will see far enough back to find the appropriate area. There should be something there.
 
Thanks Smoke, I will look at it again. 😉

I see some things that I can turn on, debug logging.
I will try that for a while and see what happens.
 
I am thinking that it counsiders this a "Passthrough operation" and it simply passes the WU's through. I can't see any mention of them even with all the debug logging on.
Weird. There was a remote WU sent in during this time period - see what th log says:

10:50am: Server Socket(32c) closed
10:50am: Server Socket(32c) response sent. Closing connection
10:50am: Server Socket(32c) write (len 181, wrote 181)
10:50am: Server Socket(32c) write (len 171, wrote 171)
10:50am: Server Http Image: b.gif
10:50am: Server socket(32c) Dispatch Http Request
10:50am: Server socket(32c) 70.89.119.245: Content length: 0
10:50am: Server Socket(32c) Read len: 529
10:50am: Server Socket(32c) accept: 198.104.0.100
10:50am: Server Socket(32c) closed
10:50am: Server Socket(32c) response sent. Closing connection
10:50am: Server Socket(32c) write (len 181, wrote 181)
10:50am: Server Socket(32c) write (len 171, wrote 171)
10:50am: Server Http Image: b.gif
10:50am: Server socket(32c) Dispatch Http Request
10:50am: Server socket(32c) 70.89.119.245: Content length: 0
10:50am: Server Socket(32c) Read len: 524
10:50am: Server Socket(32c) accept: 198.104.0.100
10:50am: Server Socket(32c) closed
10:50am: Server Socket(32c) response sent. Closing connection
10:50am: Server Socket(32c) write (len 2208, wrote 2208)
10:50am: Server Socket(32c) write (len 172, wrote 172)
10:50am: Server Http Image: setiq.gif
10:50am: Server socket(32c) Dispatch Http Request
10:50am: Server socket(32c) 70.89.119.245: Content length: 0
10:50am: Server Socket(32c) Read len: 522
10:50am: Server Socket(32c) accept: 198.104.0.100
10:50am: Server Socket(32c) closed
10:50am: Server Socket(32c) response sent. Closing connection
10:50am: Server Socket(32c) write (len 357, wrote 357)
10:50am: Server Socket(32c) write (len 357, wrote -1)
10:50am: Server Socket(32c) write (len 2046, wrote 2046)
10:50am: Server Socket(32c) async op with no event mask
10:50am: Server Socket(32c) write (len 2046, wrote -1)
10:50am: Server Socket(32c) write (len 2014, wrote 2014)
10:50am: Server Socket(32c) write (len 2014, wrote -1)
10:50am: Server Socket(32c) write (len 2013, wrote 2013)
10:50am: Server Socket(32c) write (len 1998, wrote 1998)
10:50am: Server Socket(32c) write (len 1998, wrote -1)
10:50am: Server Socket(32c) write (len 2032, wrote 2032)
10:50am: Server Socket(32c) write (len 2032, wrote -1)
10:50am: Server Socket(32c) write (len 2010, wrote 2010)
10:50am: Server Socket(214) closed
10:50am: Server Socket(214) response sent. Closing connection
10:50am: Server Socket(214) write (len 182, wrote 182)
10:50am: Server Socket(214) write (len 171, wrote 171)
10:50am: Server Http Image: b.gif
10:50am: Server socket(214) Dispatch Http Request
10:50am: Server socket(214) 70.89.119.245: Content length: 0
10:50am: Server Socket(214) Read len: 524
10:50am: Server Socket(32c) write (len 2010, wrote -1)
10:50am: Server Socket(32c) write (len 2017, wrote 2017)
10:50am: Server Socket(32c) async op with no event mask
10:50am: Server Socket(214) accept: 198.104.0.100
10:50am: Server Socket(32c) write (len 2017, wrote -1)
10:50am: Server Socket(32c) write (len 2004, wrote 2004)
10:50am: Server Socket(32c) write (len 2004, wrote -1)
10:50am: Server Socket(32c) write (len 2039, wrote 2039)
10:50am: Server Socket(32c) write (len 2039, wrote -1)
10:50am: Server Socket(32c) write (len 2048, wrote 2048)
10:50am: Server Socket(32c) write (len 2048, wrote -1)
10:50am: Server Socket(32c) write (len 1992, wrote 1992)
10:50am: Server Socket(32c) write (len 1992, wrote -1)
10:50am: Server Socket(32c) write (len 2025, wrote 2025)
10:50am: Server Socket(32c) write (len 2025, wrote -1)
10:50am: Server Socket(32c) write (len 2017, wrote 2017)
10:50am: Server Socket(32c) write (len 2017, wrote -1)
10:50am: Server Socket(32c) write (len 2043, wrote 2043)
10:50am: Server Socket(32c) write (len 2043, wrote -1)
10:50am: Server Socket(32c) write (len 2024, wrote 2024)
10:50am: Server Socket(32c) write (len 2024, wrote -1)
10:50am: Server Socket(32c) write (len 2031, wrote 2031)
10:50am: Server Socket(32c) write (len 2031, wrote -1)
10:50am: Server Socket(32c) write (len 2040, wrote 2040)
10:50am: Server Socket(32c) write (len 1994, wrote 1994)
10:50am: Server Socket(32c) write (len 2033, wrote 2033)
10:50am: Server Socket(32c) write (len 1988, wrote 1988)
10:50am: Server Socket(32c) write (len 173, wrote 173)
10:50am: Server Http: 198.104.0.100 serverlog.htm
10:50am: Server socket(32c) Dispatch Http Request
10:50am: Server socket(32c) 70.89.119.245: Content length: 0
10:50am: Server Socket(32c) Read len: 636
10:50am: Server Socket(32c) accept: 198.104.0.100
10:50am: Server Socket(32c) closed
10:50am: Server Socket(32c) response sent. Closing connection
10:50am: Server Socket(32c) write (len 181, wrote 181)
10:50am: Server Socket(32c) write (len 171, wrote 171)
10:50am: Server Http Image: b.gif
10:50am: Server socket(32c) Dispatch Http Request
10:50am: Server socket(32c) 70.89.119.245: Content length: 0
10:50am: Server Socket(32c) Read len: 555
10:50am: Server Socket(32c) accept: 198.104.0.100
10:50am: Server Socket(32c) closed
10:50am: Server Socket(32c) response sent. Closing connection
10:50am: Server Socket(32c) write (len 181, wrote 181)
10:50am: Server Socket(32c) write (len 171, wrote 171)
10:50am: Server Http Image: b.gif
10:50am: Server socket(32c) Dispatch Http Request
10:50am: Server socket(32c) 70.89.119.245: Content length: 0
10:50am: Server Socket(32c) Read len: 550
10:50am: Server Socket(32c) accept: 198.104.0.100
10:50am: Server Socket(32c) closed
10:50am: Server Socket(32c) response sent. Closing connection
10:50am: Server Socket(32c) write (len 2208, wrote 2208)
10:50am: Server Socket(32c) write (len 172, wrote 172)
10:50am: Server Http Image: setiq.gif
10:50am: Server socket(32c) Dispatch Http Request
10:50am: Server socket(32c) 70.89.119.245: Content length: 0
10:50am: Server Socket(32c) Read len: 548
10:50am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 182, wrote 182)
10:49am: Server Socket(32c) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 550
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 1355, wrote 1355)
10:49am: Server Socket(32c) write (len 1983, wrote 1983)
10:49am: Server Socket(32c) write (len 2033, wrote 2033)
10:49am: Server Socket(32c) write (len 1988, wrote 1988)
10:49am: Server Socket(32c) write (len 172, wrote 172)
10:49am: Server Http: 198.104.0.100 clientlog.htm
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 660
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 181, wrote 181)
10:49am: Server Socket(32c) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 555
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 181, wrote 181)
10:49am: Server Socket(32c) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 550
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 2208, wrote 2208)
10:49am: Server Socket(32c) write (len 172, wrote 172)
10:49am: Server Http Image: setiq.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 548
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 182, wrote 182)
10:49am: Server Socket(32c) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 550
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 1355, wrote 1355)
10:49am: Server Socket(32c) write (len 1983, wrote 1983)
10:49am: Server Socket(32c) write (len 2033, wrote 2033)
10:49am: Server Socket(32c) write (len 1988, wrote 1988)
10:49am: Server Socket(32c) write (len 172, wrote 172)
10:49am: Server Http: 198.104.0.100 clientlog.htm
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 660
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 181, wrote 181)
10:49am: Server Socket(32c) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 555
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 181, wrote 181)
10:49am: Server Socket(32c) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 550
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 2208, wrote 2208)
10:49am: Server Socket(32c) write (len 172, wrote 172)
10:49am: Server Http Image: setiq.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 548
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 182, wrote 182)
10:49am: Server Socket(32c) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 550
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(32c) closed
10:49am: Server Socket(32c) response sent. Closing connection
10:49am: Server Socket(32c) write (len 1355, wrote 1355)
10:49am: Server Socket(32c) write (len 1983, wrote 1983)
10:49am: Server Socket(32c) write (len 2033, wrote 2033)
10:49am: Server Socket(32c) write (len 1988, wrote 1988)
10:49am: Server Socket(32c) write (len 172, wrote 172)
10:49am: Server Http: 198.104.0.100 clientlog.htm
10:49am: Server socket(32c) Dispatch Http Request
10:49am: Server socket(32c) 70.89.119.245: Content length: 0
10:49am: Server Socket(32c) Read len: 660
10:49am: Server Socket(32c) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 555
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 2208, wrote 2208)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http Image: setiq.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 548
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 182, wrote 182)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 1355, wrote 1355)
10:49am: Server Socket(328) write (len 1983, wrote 1983)
10:49am: Server Socket(328) write (len 2033, wrote 2033)
10:49am: Server Socket(328) write (len 1988, wrote 1988)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http: 198.104.0.100 clientlog.htm
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 660
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 555
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 2208, wrote 2208)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http Image: setiq.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 548
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 182, wrote 182)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 1355, wrote 1355)
10:49am: Server Socket(328) write (len 1983, wrote 1983)
10:49am: Server Socket(328) write (len 2033, wrote 2033)
10:49am: Server Socket(328) write (len 1988, wrote 1988)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http: 198.104.0.100 clientlog.htm
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 660
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 555
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 2208, wrote 2208)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http Image: setiq.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 548
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 182, wrote 182)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 1355, wrote 1355)
10:49am: Server Socket(328) write (len 1983, wrote 1983)
10:49am: Server Socket(328) write (len 2033, wrote 2033)
10:49am: Server Socket(328) write (len 1988, wrote 1988)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http: 198.104.0.100 clientlog.htm
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 660
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 555
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 181, wrote 181)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 2208, wrote 2208)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http Image: setiq.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 548
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 182, wrote 182)
10:49am: Server Socket(328) write (len 171, wrote 171)
10:49am: Server Http Image: b.gif
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 550
10:49am: Server Socket(328) accept: 198.104.0.100
10:49am: Server Socket(328) closed
10:49am: Server Socket(328) response sent. Closing connection
10:49am: Server Socket(328) write (len 1355, wrote 1355)
10:49am: Server Socket(328) write (len 1983, wrote 1983)
10:49am: Server Socket(328) write (len 2033, wrote 2033)
10:49am: Server Socket(328) write (len 1988, wrote 1988)
10:49am: Server Socket(328) write (len 172, wrote 172)
10:49am: Server Http: 198.104.0.100 clientlog.htm
10:49am: Server socket(328) Dispatch Http Request
10:49am: Server socket(328) 70.89.119.245: Content length: 0
10:49am: Server Socket(328) Read len: 660
10:49am: Server Socket(328) accept: 198.104.0.100
Click to expand...
 
Do you have successful transactions in the logs. They should look like the following:

{Read from the bottom up for the correct time line}

2:17pm: Q0002 Work Unit 03my04aa.20051.25346.442312.134 added to the queue
2:17pm: Server Socket(40c) closed
2:17pm: Server Socket(40c) response sent. Closing connection
2:17pm: Server Socket(40c) write (len 356417, wrote 356417)
2:17pm: Server Socket(40c) write (len 188, wrote 188)
2:17pm: Q0002 Work unit 04no03aa.16415.32320.165886.70 given to Cisco
2:17pm: Server Socket(40c) Read len: 232
2:17pm: Server socket(40c) shserver2.ssl.berkeley.edu: Content length: 232
2:17pm: Server Socket(40c) Read len: 175
2:17pm: Server Socket(40c) accept: 24.117.36.239
2:17pm: s@h_wrk Sending result 02se03ab.1043.25906.742326.184
2:17pm: Server Socket(3b0) closed
2:17pm: Server Socket(3b0) response sent. Closing connection
2:17pm: Server Socket(3b0) write (len 405, wrote 405)
2:17pm: Server Socket(3b0) write (len 185, wrote 185)
2:17pm: Q0002 Result 02se03ab.1043.25906.742326.184 completed by Cisco [2h27m]
2:17pm: Server Socket(3b0) Read len: 8612
2:17pm: Server Socket(3b0) Read len: 7260
2:17pm: Server Socket(3b0) Read len: 5808
2:17pm: Server Socket(3b0) Read len: 4356
2:17pm: Server Socket(3b0) Read len: 2904
2:17pm: Server Socket(3b0) Read len: 1452
2:17pm: Server socket(3b0) shserver2.ssl.berkeley.edu: Content length: 8612
2:17pm: Server Socket(3b0) Read len: 176
2:17pm: Server Socket(3b0) accept: 24.117.36.239
 
I see those when a WU goes from my LAN but I think it is just doing a "passthrough" with the remote WU's.

3:12pm: s@h_wrk Waiting (idle)
3:12pm: Q0002 Work Unit 04no03aa.16415.15458.17324.44 added to the queue
3:12pm: s@h_wrk Download new work unit
3:11pm: s@h_wrk Waiting for WorkUnit delay gap. Waiting 59s
3:11pm: Q0002 Work Unit 04no03aa.16415.15297.92334.124 added to the queue
3:11pm: Server Socket(310) closed
3:11pm: Server Socket(310) response sent. Closing connection
3:11pm: Server Socket(310) write (len 356418, wrote 356418)
3:11pm: Server Socket(310) write (len 188, wrote 188)
3:11pm: Q0002 Work unit 03my04aa.20051.25105.29822.134 given to BLACKY
3:11pm: Q0002 New GetWorkUnit.sah saved
3:11pm: Server socket(310) client name: blacky
3:11pm: Server socket(310) shserver2.ssl.berkeley.edu: Content length: 230
3:11pm: Server Socket(310) Read len: 405
3:11pm: Server Socket(310) accept: 70.89.119.245
3:11pm: Check Stats Date
3:11pm: s@h_wrk Download new work unit
3:11pm: Check Stats Date
3:11pm: s@h_wrk Sending result 02se03ab.1043.21874.479804.54
3:11pm: Server Socket(32c) closed
3:11pm: Q0002 Send user info to BLACKY
3:11pm: Server Socket(32c) response sent. Closing connection
3:11pm: Server Socket(32c) write (len 418, wrote 418)
3:11pm: Server Socket(32c) write (len 185, wrote 185)
3:11pm: Q0002 Result 02se03ab.1043.21874.479804.54 completed by BLACKY [1h51m]
3:11pm: s@h_wrk Save result 02se03ab.1043.21874.479804.54
3:11pm: Server socket(32c) client name: blacky
3:11pm: Server Socket(32c) Read len: 3023
3:11pm: Server socket(32c) shserver2.ssl.berkeley.edu: Content length: 3023
3:11pm: Server Socket(32c) Read len: 176
3:11pm: Server Socket(32c) accept: 70.89.119.245
Click to expand...
 
I think I know what's going on.

All of these WUs belong to you ... not a different account, right.

Does the machine that you do not see getting any credit live on the same IP ADDRESS as another of your Seti computers?

If it does, SetiQueue is throwing the results into one of the "other" machine's CLIENT account. Unless you are using specific ports for each machine this will happen.

To get around this problem I have had to setup a new CLIENT using my BellSouth Dial-Up account (gets a different IP ADDRESS {dynamic} than the one recently used by my other Seti machines). Once the new CLIENT is created I give it a specific port number on the SetiQueue and then of course change the port number on the specific machines SetiDriver.

If this is not done, any new computer setup on the same LAN (IP ADDRESS) will be recognized by SetiQueue as the computer last reporting a WU.

Am I getting the water cloudy? 😛
 
that machine is on a completely different network in a different town

IP's are not even close ( I am pretty sure, but I will doublecheck in the morning) 😉
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top