Re: finished units upload probs ( Fixed )

Martin wrote:



Use ping and trace to check that you have the expected network connectivity.

Note that logrotate can sometimes cause problems when it shuts down some
system stuff while the logs are being rotated. Try restarting the
network services and then restart your firewall.

Also double check your file permissions.

Otherwise, try posting a few more details for more guesses.
(Not got infinite patience to do an infinity of brute force guessing (;-))

And there may be something subtly wrong with the .sah files. Note that
certain files and contents exist only at certain phases of operation...


Let us know what you find.

Good luck,
Martin

(And all's well with s@h winnt cli + SetiSpy + SetiQueue in wine on
Mandrake 9.1 Linux)


Hi Martin here is a cut and paste from another thread where I have tried to
explain what I have done so far, please bear with the long post some exciting
news just in at the bottom :(

<<<<---------start------>>>>>>>>>

Have checked all id`s and keys and all are correct ( hundreds of times just to
make sure that they are not getting corrupt before, during and after working
the unit)

Have tried the old client 3.03 which has worked fine and after logging in with
existing account it grabs a unit does its stuff then when it tries to return
it just sits there with no errors, this is from just cli or using ksetispy or
ksetiwatch, there is obviously communication with Seti as it will d/load a
new unit for ksetispies cache.

To eliminate the fact that it might be a Ksetispy or ksetiwatch prob I have
run using just the cli but still the same results.

So I tried with a newly d/loaded 3.08 client into a new dir with a different
name ( so not conflict ) and repeated the above and the result is the same as
with the 3.03 therefore eliminating the bad .sah`s as thay are new from
Seti@home when I d/loaded the first unit.

<<<<--Please note this part---->>>>>

I then copied the seti dir from another machine ( on the same lan so should
rule out firewall probs ) which is fine and has been returning results fine
all the way through this little prob, which shows that the files are all
correct.

Ran the existing part done unit on this machine and quess what no dice still
the same prob WTF!!! this is a self contained directory from a known working
good source but as soon as it is on this machine it dumps with no errors.

So I copy the dir back to good machine and voila! it sends the completed unit
and d/loads another unit.


So it is my conclusion it must be some global screwup on this machine that has
happened since the crash at Seti@home, it might just be coincidence or related
but I sure as h*ll cannot figure it out.

What I cannot understand is I now have 5 different dirs with 5 different
configs all seperate with newly d/loaded clients and new units, all my .sah
files have the right id`s and keys, but still no joy.

It might be just me and I am missing the most blindingly obvious cure.

I am now going to reboot my server and restart the firewall, I can`t see it
doing anything as the server and firewall has not been restarted for over 3
months and that was for dustbunny hunting���also�the�good�machine�goes
through the server and firewall as well , but as I have tried most other
things maybe a bit of lateral thinking may help :)

----------end---------------------

I am now waiting the completion of the next unit to see what happens as the
server/firewall has been rebooted and is working fine or I would not be able
to post this :)

Sorry I know it is somewhat bad form to be in 2 threads at the same time but
it is how this has worked out.

I can live with the situation that I can process the units on this machine and
d/load new units but have to copy finished units over to another machine to
send them as I will be wiping suse 8.1 off this system next week to install a
fresh new Suse 9.0 ( when it comes via the postman ) but it just irks me that
I cannot figure it out.


Seti is a self contained system in 1 directory so if it goes bad delete said
directory and renew with known good one and it should work- wrong!!!

install a fresh new d/load of client and unit making sure it is in a different
place with new different names so there should be no conflicts it should work
- Wrong!!!

It goes beyond my logic

<<<<<<<<<<<<<<<<<Note This>>>>>>>>>>>>>>>>>

Hang on it has just finished a unit will see what happens now...........

Well same thing happens it will not send the upload, log just hangs at
"Sending result - connecting to server" has been like that for 10 mins with
no net activity and no timeout and no errors, tried with cli and Ksetispy 

Seti@home sends a new unit to the cache so I must be sending something out for
them to reply

zip file, move to another machine on same lan unzip to cache dir of kseitspy
pressa da button bada bing bada boom all gone worky nice mister, and this is
using the .sah`s from this bad machine.


Anyone the wiser?



-- 
Mark
Twixt hill and high water.
N.Wales, UK.
Email is spam trap try baskitcaise at gmx dot co dot uk