idle assignments

Death · 2004-08-06, 07:58

why???

07:51:23 NFSNET Client - $Revision: 1.17 $
07:51:23 Initializing...
07:51:23 Initialized.
07:51:23 Requesting assignment...
07:51:26 Received assignment (Longhorn 3_491P_3 35081623-35081624)...
07:51:26 Building .in file...
07:51:26 Updating project .in file with assigned range...
07:51:26 Launching siever...
07:52:41 Siever finished...
07:52:41 Submitting results...
07:52:42 Results successfully submitted...
07:52:42 Requesting assignment...
07:52:43 Received assignment (Longhorn 3_491P_3 35081624-35081625)...
07:52:43 Building .in file...
07:52:43 Updating project .in file with assigned range...
07:52:43 Launching siever...
07:53:39 Siever finished...
07:53:39 Submitting results...
07:53:43 Results successfully submitted...
07:53:43 Requesting assignment...
07:53:47 Received assignment ( IDLE 0-0)...

xilman · 2004-08-06, 08:30

Quote:

Originally Posted by Death

why???

07:51:23 NFSNET Client - $Revision: 1.17 $
07:51:23 Initializing...
07:51:23 Initialized.
07:51:23 Requesting assignment...
07:51:26 Received assignment (Longhorn 3_491P_3 35081623-35081624)...
07:51:26 Building .in file...
07:51:26 Updating project .in file with assigned range...
07:51:26 Launching siever...
07:52:41 Siever finished...
07:52:41 Submitting results...
07:52:42 Results successfully submitted...
07:52:42 Requesting assignment...
07:52:43 Received assignment (Longhorn 3_491P_3 35081624-35081625)...
07:52:43 Building .in file...
07:52:43 Updating project .in file with assigned range...
07:52:43 Launching siever...
07:53:39 Siever finished...
07:53:39 Submitting results...
07:53:43 Results successfully submitted...
07:53:43 Requesting assignment...
07:53:47 Received assignment ( IDLE 0-0)...

Good question, I'll see if I can find out.

By the way, Longhorn supports those clients which are still running obsolete software. I would strongly advise you to upgrade to the latest version. It's rather likely that Longhorn will go away in the next few weeks.

Paul

Death · 2004-08-06, 09:14

Quote:

Originally Posted by xilman

Good question, I'll see if I can find out.

By the way, Longhorn supports those clients which are still running obsolete software. I would strongly advise you to upgrade to the latest version. It's rather likely that Longhorn will go away in the next few weeks.

Paul

errrrmmmmmmmmmm.....

please tell me what version I'm running and what version you suggest?

Wacky · 2004-08-06, 09:52

I believe that you are running the latest version of the software against the wrong server. When you install a new version, you MUST do a CLEAN install. Please discard the entire NFSNET folder and reinstall from the tarball/zip file. Then run nfsnetinit and restart the client. You should end up in the "Texas" pool.

Death · 2004-08-06, 12:08

Yes, I know that I running l8st version =)

I doing like you suggest and it works now. thank you. but I think it was simpler to post this three lines
assignmentserver http://Texas.Server.NFSNet.Org/NFSNE...Dispatcher.cgi
libraryserver http://Texas.Server.NFSNet.Org/NFSNE.../Librarian.cgi
resultsserver http://Texas.Server.NFSNet.Org/NFSNE...ceptionist.cgi

thats too complex to rerun registration, replacing three line in details.txt was much simpler.. =))

well, nevermind, it works now....

Wacky · 2004-08-06, 12:11

You are only looking at the most visible aspects.

If you have bypassed the registration cycle, you will not have set up everything in the configuration, both in your client config file and on the servers.

I will disclaim any complaints about your stats.

Death · 2004-08-06, 12:25

well, if i was registered with old client, this registration will remain when I upgrading the client, right?

I will not complain about stats because I did as you say - reinstall clean client and rerun nfsinit. so all works fine.

Wacky · 2004-08-06, 14:16

One of the things that changed between the version of the siever that runs in "Texas" vs the older version that ran in "Longhorn" is the information that is collected and transmitted as a part of the registration procedure.
The parts of the registration that are common would carry over, but some things would not be correct.

As I understand the situation, you did do the appropriate upgrade. However, if others try to short-cut the system, they may not end up with a correct configuration file.

2004-08-06, 07:58	#1
Death Mar 2004 Ukraine, Kiev 56₈ Posts	idle assignments why??? 07:51:23 NFSNET Client - $Revision: 1.17 $ 07:51:23 Initializing... 07:51:23 Initialized. 07:51:23 Requesting assignment... 07:51:26 Received assignment (Longhorn 3_491P_3 35081623-35081624)... 07:51:26 Building .in file... 07:51:26 Updating project .in file with assigned range... 07:51:26 Launching siever... 07:52:41 Siever finished... 07:52:41 Submitting results... 07:52:42 Results successfully submitted... 07:52:42 Requesting assignment... 07:52:43 Received assignment (Longhorn 3_491P_3 35081624-35081625)... 07:52:43 Building .in file... 07:52:43 Updating project .in file with assigned range... 07:52:43 Launching siever... 07:53:39 Siever finished... 07:53:39 Submitting results... 07:53:43 Results successfully submitted... 07:53:43 Requesting assignment... 07:53:47 Received assignment ( IDLE 0-0)...

2004-08-06, 12:11	#6
Wacky Jun 2003 The Texas Hill Country 3²×11² Posts	You are only looking at the most visible aspects. If you have bypassed the registration cycle, you will not have set up everything in the configuration, both in your client config file and on the servers. I will disclaim any complaints about your stats. Last fiddled with by Wacky on 2004-08-06 at 12:17

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Idle	Unregistered	Information & Answers	1	2009-04-16 12:00
IDLE assignments	Jushi	NFSNET Discussion	1	2006-10-25 17:43
idle assignment	andi314	NFSNET Discussion	8	2004-11-01 09:34
drop idle temps 7-12C using this tweak	graysky	Hardware	3	2004-07-29 21:20
IDLE 0-0 assignments	TauCeti	NFSNET Discussion	7	2003-11-23 11:12

2004-08-06, 09:52	#4
Wacky Jun 2003 The Texas Hill Country 3²×11² Posts	I believe that you are running the latest version of the software against the wrong server. When you install a new version, you MUST do a CLEAN install. Please discard the entire NFSNET folder and reinstall from the tarball/zip file. Then run nfsnetinit and restart the client. You should end up in the "Texas" pool.

2004-08-06, 12:08	#5
Death Mar 2004 Ukraine, Kiev 2·23 Posts	Yes, I know that I running l8st version =) I doing like you suggest and it works now. thank you. but I think it was simpler to post this three lines assignmentserver http://Texas.Server.NFSNet.Org/NFSNE...Dispatcher.cgi libraryserver http://Texas.Server.NFSNet.Org/NFSNE.../Librarian.cgi resultsserver http://Texas.Server.NFSNet.Org/NFSNE...ceptionist.cgi thats too complex to rerun registration, replacing three line in details.txt was much simpler.. =)) well, nevermind, it works now....

2004-08-06, 12:25	#7
Death Mar 2004 Ukraine, Kiev 101110₂ Posts	well, if i was registered with old client, this registration will remain when I upgrading the client, right? I will not complain about stats because I did as you say - reinstall clean client and rerun nfsinit. so all works fine.

2004-08-06, 14:16	#8
Wacky Jun 2003 The Texas Hill Country 441₁₆ Posts	One of the things that changed between the version of the siever that runs in "Texas" vs the older version that ran in "Longhorn" is the information that is collected and transmitted as a part of the registration procedure. The parts of the registration that are common would carry over, but some things would not be correct. As I understand the situation, you did do the appropriate upgrade. However, if others try to short-cut the system, they may not end up with a correct configuration file.