First try with SetiQ- not having any luck :( HELP

Ben98SentraSE

Senior member
Aug 26, 2000
449
0
0
My Linux box has just finished a WU. SetiQ on a different box on my network is sitting there with

Seti Queue. Revision .78b Courtesy of: Ken Reneris
9/24 Sun 2:22am INI result_log=log
9/24 Sun 2:22am INI report_stats=yes
9/24 Sun 2:22am INI work_unit_adjust=1
9/24 Sun 2:22am INI min_limit=3
9/24 Sun 2:22am INI max_limit=8
9/24 Sun 2:22am INI max=8
9/24 Sun 2:22am INI sync_hour=3:10
9/24 Sun 2:22am INI queue_depth=4 days
9/24 Sun 2:22am INI max_poll=20 minutes
9/24 Sun 2:22am INI log_filesetiq.log hours=1
9/24 Sun 2:22am wu (rpd=0) Min:1 Max:8 Queued:0
9/24 Sun 2:22am SRV Initial install - can not get work-unit yet
9/24 Sun 2:22am SRV Waiting for s@h client to send initial WU request
9/24 Sun 2:22am SRV connecting to seti@home server
9/24 Sun 2:22am SRV get user_info

So I do a ./setiathome -verbose -proxy 204.248.217.6:5512 and get this:

Using proxy server 204.248.217.6:5512
Sending result - connecting to server.
recv fd=4 n=0, errno=2
Unexpected end of data from server

and the SetiQ window adds

9/24 Sun 2:29am sah 192.168.0.2 -> qresult.3 24h06m15s
9/24 Sun 2:29am sah 192.168.0.2 <- user_info
9/24 Sun 2:29am sah wake srv

Just sits there. Doesn't download anything. If I do a &quot;sq.exe local connect&quot; it tells me &quot;SetiQ already connected&quot; and the SetiQ window just says

9/24 Sun 2:31am CMD BEN2 -> Connect

and still sits there and does jack.

HELP!
 

Robor

Elite Member
Oct 9, 1999
16,979
0
76
No help, just a bump. I know nothing about Linux... I prefer Windoze! ;)

Rob
 

TwoFace

Golden Member
May 31, 2000
1,811
0
0
Uhm... seems to me that the SetiQ program can't connect to the internet... you are connected when you're doing this right?

Other than that I have no idea, as it seems to me like you're doing everything right... this'll serve as a ^ as well ;)

With love and respect your fellow TA member

Two-Face
 

Assimilator1

Elite Member
Nov 4, 1999
24,137
510
126
I don't know anything about Linux either but
1 thing that I did to get SETI CLi to work with SETIQ (on win 95)was to allow the SETI client to get its WU directly from SETI 1st ,after that I made it get its WU's from SETIQ (it wouldn't get it 1st WU from SETIQ ) which then worked.I've no idea why that worked though! :eek:

Another thing is that the author of SETIQ will respond to your E mail ,see if he can help you,I would give him at least 1 week to reply though (though he has responded to me in the past within a day or 2)
 

Tetsuo316

Golden Member
Mar 14, 2000
1,825
0
0
On my computer, in the Wsockhk.txt file in the SetiQ directory, I leave my IP address on there. On my computer with a dialup connection, I deleted the line of the address, and after that, it connected no problem.
 

Ben98SentraSE

Senior member
Aug 26, 2000
449
0
0
I understood your first sentence I think, but in the second sentence I am confused- where on the dialup box did you delete &quot;the line of the address?&quot; And how is you dialup box different from the box where SetiQ is?
 

Michael

Elite member
Nov 19, 1999
5,435
234
106
How does your network connect to the internet?

Michael

ps - check your PM, I can spare a few WU's from my Q
 

ColinP

Golden Member
Oct 10, 1999
1,359
0
0
Ben,

the linux box is fine, you SETIQ box can't get a WU.
I think the SETIQ server is as below.
shserver.ssl.berkeley.edu
128.32.18.166
SETIQ should automatically pick up your modem connection and dial out.
Are you sure the S@H servers were up when you were trying ??

cheers,

Col.
 

Ben98SentraSE

Senior member
Aug 26, 2000
449
0
0
I know the Seti servers were up at that time cuz I was playing with the Setiq config files and kept trying to connect my linux box to my Setiq server and it wasn't working. I gave up and immediately made my linux box go straight to the seti servers and it worked.

Seems that the servers are sorta back up now so will see what I can do...
 

Ben98SentraSE

Senior member
Aug 26, 2000
449
0
0
I *think* I've got it. The linux box was sitting there waiting for Seti@home (not setiq) to send it a WU as it was finally able to send it the results and was sitting there with &quot;Getting data - connecting to server.&quot; So I thought I'd kill it and start it over with SetiQ. What I did with SetiQ was CollinP's advice of commenting out the &quot;qseti_server=X.X.X.X&quot; line in both Wsockhk.txt's in \Seti@home and \Seti@home\setiq and it doesn't kill the client anymore, just sitting there the same like before I just fixed SetiQ.

Now SetiQ is sitting there with &quot;192.168.0.2 waiting for a work unit&quot; as it probably should since the Seti servers are still acting funky. Thanks CollinP and I hope that completely solves it.
 

artemedes

Senior member
Nov 3, 1999
778
0
0
Hey ben. It sounds like you figured it out, but I thought I would comment on something. If I remember right, SetiQ will not contact Berkeley until the clients contact SetiQ. It also averages the times and can figure out how many WUs you need for the number of days that you specify in the qseti.txt file. I was having similar difficulties when I was setting up one computer that had never done seti before. I needed setiq on it because it is on a dialup and infrequently connnected to Internet. I had to be on the internet, allow the cli client to connect using default settings (directly from berkeley) then after it had a work unit to use, change the client settings to use setiq (setipatch in this case) then it sent the completed WU to setiQ. SetiQ then took it from there and it has been running great since.:)
 

Darkone

Senior member
Feb 26, 2000
320
0
0
one other thing... your Q is on a registered IP address and your Linux box isn't...

Is there a slight chance that your Q machine can not see back into the private network to send information back ?? just a thought ......

D
 

Ben98SentraSE

Senior member
Aug 26, 2000
449
0
0
Nope that didn't do it. I got up this morning to find the Linux box sitting there not crapped out, but just waiting for a WU. Also one of my Win98 boxes was the same way. SetiQ just seems to not want to download any WU's! Here's the output SetiQ had:

Seti Queue. Revision .78b Courtesy of: Ken Reneris
9/25 Mon 10:52am INI result_log=log
9/25 Mon 10:52am INI report_stats=yes
9/25 Mon 10:52am INI work_unit_adjust=1
9/25 Mon 10:52am INI min_limit=3
9/25 Mon 10:52am INI max_limit=8
9/25 Mon 10:52am INI max=8
9/25 Mon 10:52am INI sync_hour=3:30
9/25 Mon 10:52am INI queue_depth=4 days
9/25 Mon 10:52am INI max_poll=20 minutes
9/25 Mon 10:52am INI log_filesetiq.log hours=1
9/25 Mon 10:52am ave 192.168.0.2 23h03m15s
9/25 Mon 10:52am wu (rpd=1) Min:1 Max:8 Queued:0
9/25 Mon 10:52am SRV connecting to seti@home server
9/25 Mon 10:52am SRV get user_info
9/25 Mon 10:52am sah ME WuAdjust: 2
9/25 Mon 10:52am sah ME -> qresult.7 31h40m38s
9/25 Mon 10:52am sah ME <- user_info
9/25 Mon 10:52am sah wake srv
9/25 Mon 10:52am sah duplicate result ignored
9/25 Mon 10:52am sah ME <- user_info
9/25 Mon 10:52am sah wake srv

It always seems to just sit there on &quot;wake srv&quot; if some system has tried to request a WU or if it has yet it to it sits there at &quot;get user_info.&quot; Again both of my Wsockhk.txt's have all the lines commented out (the one in \Seti@home and \Seti@home\setiq) and here is my qseti.txt below:


# work_unit_adjust sets the number of seti@home.exe client apps
# that are processing work units. This number is used to determine
# how many work units are really outstanding (which is the # in
# the queue, plus the number of clients working on work units)
work_unit_adjust=1

# sync_hour is the hour to connect the seti server to send all
# outstanding results, and to acquire new work units. By default the queuing
# app picks the minute of the hour at random. (The hour is picked
# at randmon as well if the following line is commented out)
sync_hour=3
#sync_min=0

# setting autoconnect to 'no' will stop setiq from attempting to
# automatically contact the seti server. To connect you must use
# sq.exe tools. E.g: sq local connect
autoconnect=yes

# startupconnect causes setiq to transfer work when first started.
# Setting this value to 'no' will disable this.
startupconnect=yes

# max_poll is the longest amount of time to wait when polling the
# setiserver. This value is in minutes. If setiqueue can not connect
# to seti server, it retries in 1 second and doubles that amount
# each time the connection fails, up to max_poll. This value
# may be set from 5 to 2880.
max_poll=20

# if there are abort_retry_count *consecutive* failures in trying
# to perform an operation to seti server, setiq will disconnect
# and disable autoconnecting either permanently or until the
# next sync time as determined by the retry_at_sync_time flag.
#abort_retry_count=8
#retry_at_sync_time=no

# queue_depth is the number of days worth of work units to queue.
# the min is 1, the max is 30. This number to queue fluctuates a bit
# as min &amp; max are computed by the rpd (result per day) which is
# tallied as the number of results submitted to the queuing app
# over the last 24 hours.
queue_depth=4

# ave_over is the number of days to average the results over
# to determine the number of work units being completed per day.
# This setting must be within the number of days setiq has been
# running.
ave_over=1

# min_limit limits the minimum queue threshold.
# max_limit limits the maxumum queue threshold. These are used if
# for some reason the queuing app is downloading too many work units.
# This allows an override to reduce the numbers.
min_limit=3
max_limit=8

# This setting will increase the upper limit of the queue size
# to be at least 'max'. The maximum value for this setting is 200.
max=8

# response_delay sets a delay in seconds that setiqueue will wait
# before responding to receiving a new result from a client. Set
# this value to 5 if you are using the seti monitor app. This will
# give the app enough time to see the result.sah file.
# response_delay=5

# result_log provides the location to keep a copy of all results
# ever completed. The file result.log (in the setiqueue directory)
# can be used to see which local machine completed which result.
# Comment this line out if you do not wish to keep a logged copy
# of all results sent. Note the results are logged when clients
# complete, not when they are sent to the seti server
result_log=log

# report_stats disables the reporting of statistics to setiq server.
# At some point I will put a link to get setiq stats on my website, but
# have not completed the web site code to do this yet. The stats also
# are useful when I send mail to s@h to indicate how many seti users
# are using/depending on setiq. And finaly I can send update notices
# to active users whom are reporting statistics when a change is
# made to setiq.exe
#report_stats=no

# After stats are reported an optional local job can be dispatched
# with job=
#job=C:\W2K\system32\cmd.exe /c e:\backup\backup

# log_file sets a filename where setiq output should be logged.
# log_days indicates how many hours to keep in the log before starting a new one
log_file=setiq.log
log_hours=1

# proxy_server is used if the non-queued clients normally work
# through a proxy server. By supplying proxy_server the connection
# setiqueue makes will be through the proxy server &amp; port
# information.
#
# Note: This setting is under testing.
#
#proxy_server=204.248.217.6
#proxy_port=80


The computer is ALWAYS connected via dialup networking. I almost NEVER get kicked off and at all these times I was testing I was connected.

Help?
 

Ben98SentraSE

Senior member
Aug 26, 2000
449
0
0
To answer Darkone's question, I've tried setting the proxy IP to the external and internal IP's of that box to no avail. :(
 

blade47

Golden Member
Dec 12, 1999
1,353
0
0
This may be a stupid question but do you connect to the internet through a proxy server? If so you'd need to remove the # in front of the proxy settings in setiQ:

#proxy_server=204.248.217.6
#proxy_port=80

and change them to whatever you normally use to access the internet.

The rest of the qseti.txt file looks fine.

You may already know this but I'll ask anyway. You didn't patch the remote clients did you?

 

Ben98SentraSE

Senior member
Aug 26, 2000
449
0
0
Now I don't know the exact definition of a proxy server in this sense so let me explain. I have 4 computers, 1 running Win98SE with Internet Connection Sharing and 3 running DHCP. (Static internal IPs work as well, just haven't got around to messing with them yet) The internet connection sharing box does separate the 3 boxes from the net so you can't see them, so is that considered a &quot;proxy server?&quot; Or is it simply a &quot;gateway?&quot; I mean I don't have to setup IE or anything to route through this box, they just do through DHCP.

I *think* I tried setting it this way before (as you can see I put my static external IP in there) but it didn't work. I probably have reconfigured things since then so I guess it wouldn't hurt, but I don't see why that setting would be necessary since all the other 3 boxes know to go through that box to get out to the net anyways. And the other thing I didn't understand was why that setting was defaulted to port 80.

And no I have not patch the clients on the other boxes, just the one on same box with SetiQ (which also will not work the same way the other boxes will not work).