CLI Problem

[Ronin]

Ok, so I was transitioning my boxes over to the CLI instead of GUI, and I've run into an interesting problem. Basically, I've only gotten one box to be able to connect to Seti to download WU (granted, I set it up for 80 for the cache, but still...). I can't get 3 out of 4 to connect right now, and I'm not sure if it's because Seti is down or what (I was able to download all 80 WU to cache on the one box at the same time I was trying to bring the other boxes back online).

I'm running version 3.08 of the CLI (have to, per work) and the latest version of Seti Driver.

Anyone have any ideas what's going on? This is a bit frustrating and I'm missing valuable crunching time.

 

[IsOs]

I suggest that you point the one machine that is processing SETI to one of the public SETI Q and send your completed workunits to that Q. After your machine established a client account in that Q, point the other machine to this Q. If the Q doesn't provide workunits to your account, try to contact the Q operator and request that some workunits be moved to your client's account.

 

[Ronin]

Unfortunately, that requires me to wait to get set up. I guess I could go back to the GUI on the machines that aren't connecting at the moment, and then when there are WU to process, I'll shift over. Or, I'll set up my own Queue box and just send WU to myself

If anyone else has any other suggestions, lemme know, please.

 

[IsOs]

You can move some of those 80 workunits from that machine that was able to get workunits.

Example, move workunits 71-80 to a floppy by moving the numbered subdirectories. Rename these subdirectories to 1 to 10 and move them to second machine.

 

[Assimilator1]

The 1 box that is connecting ,is that by chance the only 1 thats directly connected to the net?
(no probs connecting to SETI here inccidentley)

What are your SETIDriver settings?
What error messages are you getting?

Btw having your own Q would be a good move anyway ,you can keep an eye on your own fleets stats

 

[Ronin]

The point here is, I can't connect to Seti to even set up my account (rather, obviously I have an account, but I can't connect to even get that process done). I moved the work units over, but processing them would be a waste of time if there's no account associated with them.

All boxes are connected to the net via an extensive network, and submitting and receiving WU on the GUI client is no problem, so I'm not sure how the CLI would change that.

I'm following the directions to the T via the directions listed here, which worked perfectly fine on the first box. Just every one after that hasn't... :|

I'm not getting any error messages. When I start Seti Driver, the icon is red. When I change the settings (the first 3 steps on that page), and click transmit, it goes green for about a second, then goes red again.

Yes, the box is connected to the net (all of them are...the ones that are exhibiting the problem, that is), so that's not the problem...

I don't see how someone can mess this up, but apparently somewhere along the line, I did....

 

[RaySun2Be]

Ronin, copy the USER.SAH file from one of the SETI subdirectories that SETIDRIVER creates (1, 2, 3, etc.) from the PC that was able to connect and download WUs, to all the SETI subfolders on the other PCs.

Would you mind sharing your SETIDRIVER settings? It would help with troubleshooting.

 

[Ronin]

Preliminary Seti Driver settings are exactly are what's dictated on the sigline page. Meaning:



Step 1: Place the CLI executable file and SetiDriver.exe in the same directory. For example, C:\Program Files\SETI@Home.


Step 2: Run SetiDriver.exe.


Step 3: Choose the following options:

Maximum Processes = Default (1)
Desired Cache Size = 1
Hide Processing = No
Auto Transmit = No
Display Transmit = Yes


Step 4: Now, click Save Config, and then Transmit (Do not click New Client). <----this is where I have my problem, as it refuses to transmit. Basically, it doesn't seem to want to connect.

 

[Ronin]

Well, it looks like things are working. I'm going from machine to machine and setting it up, and I'm getting my queue downloads and a nice green Seti icon, so I should be gtg. *crosses fingers*

I hope my totals don't suffer too much :|

 

[Assimilator1]

Wierd! ,hopefully its ok now?

Btw re error messages ,I was referring to any shown in the CLI window

 

[Ronin]

There was none, unfortunately. It simply wouldn't connect. Nothing else :|

 

[Ronin]

Ok, so all my boxes are up on CLI, and thus far, it looks like I got a 20% increase in output. No complaints Now, to get more boxes up!

 

[Wiz]

WTG!!!!!!!!!!!!!!!!!!!!!!

 

[Assimilator1]