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

SETIQ Questions...

ericlp

Diamond Member
Anyone running a Linux Client with SetiQ?

I guess I should go over with you what kinda setup I got....

I'm running SetiQ on P4-2.66 Ghz machine. IP = 192.168.1.103:5517 (STATIC)

with 5 ECS MoBo's with AMD's 2200's on them and 1 stick of 128 Megs of RAM... Anyway....... I took down one board and to upgrade the ram in it to a faster stick. Anyway, it would have been nice to run all the IP's on static but linux router (boot floppy) only does DHCP.

Anyway... When I turned back on the seti box it acted like it couldn't find a network. I am thinking that the DHCP router reisued out the same IP and SetiQ thinking it was still connected to a client with the previous address didn't want it logging in again..................

So, anyway after shutting off the router and I guess the linux box just picked up a new IP address. But NOW setiQ thinks that the IP of 1.102 is still in use when the box that was using that is now on 1.108... 🙂

So if I look at the status it says I have 9 clients ... with the new 1.08 and the old 1.02... Dunno anyway of telling SetiQ to drop a client...

Thank you for your responses.


 
Originally posted by: Robor
A few days sounds kinda quick. What is the default time for SetiQ to drop a client?

Hmmm kinda Quck? 🙂 If there is no default to kill it or drop it in 20 mins or so I'll stop using it. Good for static IP's / no seti farms I guess... I'm not waiting 2 days just to get a client back on line and since I got 8 running with out a ups hooked up what's the point? I got cable so it's only good if for some reason seti's site is down.... I'll be doing some more research as I am sure there is a time out to drop a WU sooner.



 
Originally posted by: ericlp


So if I look at the status it says I have 9 clients ... with the new 1.08 and the old 1.02... Dunno anyway of telling SetiQ to drop a client...

Thank you for your responses.

Login to SetiQueue as ADMIN (or whatever you use?), enter your password and then go to TOOLS / DELETE A CLIENT.

Is this what you are looking for?

 
Client 192.168.1.102 being deleted

Yep... Thanks Smoke... Seems like someone does know somthing around here.

Some more fun stuff....

When SetiQueue is running (either the GUI or as service) you can also access the web interface of your Q by starting a new browser session and typing"http://localhost:5517" in the address bar. This will get you to the welcome screen of your Q.
On the navigation bar click on Settings to get an overview about the general settings of your SetiQueue.

See below for the settings of my SetiQueue. You will notice I needed to specify a proxy server for SetiQueue to connect to the Seti@Home web server at Berkeley. As this is my Queue at work, I masked the company's name for security reasons. The IP address of the computer my SetiQueue is running on is 192.168.16.129 also I changed the default port to 5512. I keep the logs for 2 days and specified my Queue to keep at least enough work units for 7 days without any connection to the Seti@Home web server before I run out of work units. As I set the "Max Queue Depth" to 9 days based on SetiQueue's computation, SetiQueue will fill the Queue up to the 9 days limit initially (in my case about 90 WU) and will start downloading new ones when the Queue is down to under 7 days. If the Queue is filled with WUs worth for 9 days, SetiQueue will not request new WUs from the Seti@Home web server at Berkeley when it is connecting, or the specified connection is exceeded.

General SetiQueue settings




Queue Size Settings



The second section displays the size settings for your Queue.
If a user's Queue contains only the amount of WUs specified in "Min Low Priority Queue Depth" his queue will be granted high priority to download WUs. If his Queue reaches the "Max Low Priority Queue Depth" amount of WUs the priority will be switched to normal again. The amount of WUs specified in "Max Low Priority Queue" allows an user who connects to your queue and is set on "low priortiy" to get the number of specified WU´s to download. The "Obsolete clients & pending WUs after" setting is used to kick a client from your Q after the given amount of days, if no result is returned by this client. The "Highlight items after" setting will change the color of the clients line (can be found under the topic RESULTS - CLIENTS) after the given amount of time if no result is received from the client in question. The next two settings are only of interest if you make your Queue publicly available over the internet, so that other users can connect and use your Queue. "New User Consolidate" will put all of it's clients into one line on the reports page and "New User Priority" allows you to set the priority of the users clients to LOW. If you set this to "Disabled Queues" the new user will not get any workunits from your Q. The user will change from LOW to NORMAL after about 10 days of actvity.


Queue Processing Settings



The third section displays the Queue processing settings of SetiQueue. I explained the "Inter-WU download gap" before, but the "Inter-WU VLAR gap" setting as well as the "Look for sweet WUs" option can only be found & configured from the web interface. VLAR units are units which take unusually longer than the average unit as they are recorded at Arecibo in a difficult angle. These workunits will take longer than the "normal" ones. If you specify an amount of time SetiQueue will wait this long after downloading the first one of these VLAR-units until it will download the next one to your Queue. 5 minutes should be enough to avoid downloading many of them at once.

Enabling the "Look for sweet WUs" option is highly recommended. A "sweet workunit" is analyzed much more faster than the average unit. If you enable this option SetiQueue will override the gap specified in "inter-WU download gap" after the first one is downloaded and will continue to download constantly new WUs until the next VLAR unit is discovered, after which it will return to use the "inter-WU download gap"


HTTP Server Settings



The last section shows if anyone can access your SetiQueue web server or only a user from a specific IP address. Mine is set to allow any IP address, though no one can change my settings as I specified an administration password. If you allow access to the SetiQueue web interface to anyone, the line "Allow any IP address" will read "enabled" otherwise it will display the IP address you specified.

To change any of the settings via the web interface you will have to log-in first. The log-in can be found on the left side right under the topic "Admin". Click on it and you will be prompted to enter a username admin and your password. After you logged in go back to the Settings page by clicking on Settings on the navigation bar. You will see a hyperlink at the top of the page "Click to edit settings". If you click on it the page will change to edit mode.

Now you can edit the settings. When finished click on the Submit button at the end of the page. As I said before you have more power over your Queue from this web interface than from the GUI. It makes everything more easy to administer and "get the big picture".

After you have submitted your changes switch to the Clients page by clicking on Clients on the navigation bar. You will see the netbios names of the computers where the Seti@Home clients are located on the left.




"RPD" shows the Results Per Day returned from this client to the SetiQueue.

"RY" shows the number of Results returned Yesterday.

"Avg CPU" displays the time the client needs for a work unit.

"Last Result" shows the time since the client last received a new WU to analyze from SetiQueue.

"AR" is the Angle Range of the work unit currently being processed by the client. Higher is generally faster. A number below 0.15 is likely to be a VLAR-unit, which takes longer than average to be processed.

"Est" shows the progress of the client. A green bar indicates that the client is well in time. A yellow bar (line 3) indicates that this client has already exceeded it's predicted processing time for a unit, but is not too much above it.
A red bar indicates that this client has exceeded it's predicted processing time for a WU way to much. You should check that client manually.

The times and averages are computed by SetiQueue on the last 14 day base. If you have a new setup, the computation useless until the client has returned some units. You can see that the client "testbox1" has a yellow bar although the average processing time for one unit is 21h26m, it hasn't returned a unit for the last 2 days 5h15m. This client isn't online regularly. SetiQueue will adjust the "Est" line according to the statistics gathered over the last 14 days.

You can edit a client while logged in with your Administrator password by clicking on the client's name and then clicking on "Click to edit settings" at the top of the client detail page


You can change the name for the client to be displayed on the Clients page by typing in a custom name for the client.
Setting the "Permanent client" option to enabled, the client will be displayed on the main Clients page although it might have become obsolete according to the "Obsolete Client After" option in the General Settings.
Dedicate a client port to a client if SetiQueue is not able to differ between two or more clients and is mixing up the statistics. Leave this empty if you do not encounter the a.m. problems.
Queue: The name of the Queue this client gets it's WUs from. You can have more than one Queue at a time.

The tools
When you are logged in with your Administrator password and click on the "Tools" topic on the navigation bar you can perform several useful tasks:




"Customize Summary Report" lets you decide what information shall be displayed on the Summary page of the web interface.
"Chart AR Performance" allows you to view a performance chart (time needed to complete a workunit) of up to 10 clients based on the processed angle range of the returned workunits.
"Delete/Recycle an overdue workunit" gives you the opportunity to delete workunits or recycle the workunit from a client
"Delete/Recycle any pending workunit" is the same as above, but also "green" workunits can be recycled/deleted from a client.
"Merge two client systems into one" - Imagine someone gave the computer the client is located on a new name. SetiQueue will acknowledge the new computername as a new client, abandoning the old one - you will have to merge those two to preserve correct statistics.
"Dedicate a TCP/IP port to a client" allows you to give a special port (differing from the default port 5517) to a client to connect to your Queue
"Move workunits from one Queue to another" - You have two Queues installed. One is almost empty, the other almost full. You don't want to or you are not able to connect to Berkeley to get new workunits, so you balance the load.
"Delete a batch of waiting workunits" - "This operation will remove all waiting work-units from all queues that are in the requested range. This operation is typically only used if for some reaon the Seti Server has provided a bunch of work-units that are in same way not interesting. E.g., obsolete." Uninteresting since the option to specify an angle range was removed.
"Delete a client" if you know that the client is no longer existing and it is still poisoning your statistics with an evil red bar
"Torch a user" the next time one of it's clients connect to your Queue. Will allow you to enter a custom message displayed on the clients screen.
If you are logged in you will notice another topic appearing under Admin, the Connect option. Click on it if you have set SetiQueue to connect manually if you want to send the finished WUs back to the server and receive new WUs in turn. Click on the "Connect button" and then click the desired "Minutes-Of-Connection button". You can also disconnect from here if you are connected and no more WUs shall be send/received or prior to the termination of your SetiQueue.

I personally have only use for the web interface of SetiQueue. You can manage it completely from there. You can install SetiQueue as a service for WinNT/2K/XP by starting the SetiQueue executable with the following parameter (from a DOS box): "setiqueue.exe -i". You will need Administrator Rights to do this. After installing it as a service the GUI won't be shown anymore. You can administer SetiQueue completely via the web interface. To uninstall the service just perform "setiqueue.exe -u".



 
I use SetiQueue here at home for my Windows based rigs. I have my Linksys Router set up to do DHCP as well, but that doesn't stop me from using static IPs. 😉 I have the Linksys issuing IPs starting at 192.168.1.101 and going up from there, up to 50 IPs. I have my SetiQueue server set up with a static IP of 192.168.1.145 with absolutely zero problems. And I will continue to have zero problems unless I somehow manage to get another 35 to 40 PCs running in here.. not likely, even with a LAN party. 😉

Each of the other PCs in the house is using DHCP and just get issued an IP starting at the beginning of the range - and thus .145 is completely safe. 🙂


 
Back
Top