From: jance <powerjance@(email surpressed)>
Subject: Re: Macs not picking up
   Date: Mon, 31 Oct 2005 18:47:29 -0800
Msg# 1074
View Complete Thread (7 articles) | All Threads
Last Next
In article <1073-rush decimal general at seriss decimal com>,
 Greg Ercolano <erco@(email surpressed)> wrote:

> 	by www.3dsite.com (8.12.8/8.12.8) with SMTP id jA11UhFH025644
> 
> 	for <rush decimal general at seriss decimal com>; Mon, 31 Oct 2005 17:30:43 -0800
> Received: (qmail 21440 invoked from network); 1 Nov 2005 01:31:32 -0000
> Received: from unknown (HELO ?192.168.0.9?) (unknown)
> 
>   by unknown with SMTP; 1 Nov 2005 01:31:32 -0000
> X-pair-Authenticated: 24.205.66.40
> Organization: Seriss Inc.
> User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
> X-Accept-Language: en-us, en
> MIME-Version: 1.0
> To: rush decimal general at seriss decimal com
> In-Reply-To: <1072-rush decimal general at seriss decimal com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> Path: 3dsite.com
> Xref: 3dsite.com rush.general:1073
> NNTP-Posting-Host: localhost
> 
> Hi Jance,
> 
> 	I believe that's the problem in the "Cpus" report for the job:
> 
> > CPUSPEC[HOST]          STATE       FRAME   PID     JOBTID  PRI   ELAPSED  
> > JOBID          NOTES
> > +any=14@1[forworkone]  Idle/Nak    -       -       785     1     00:00:00 
> > speedybeast.13 unknown uid 100
> > +any=14@1[forworkone]  Idle/Nak    -       -       786     1     00:00:00 
> > speedybeast.13 unknown uid 100
>                                                                               
>                                               ^^^^^^^^^^^^^^^
> 
> 	From the FAQ:
> 	
> http://www.seriss.com/rush-current/rush/rush-admin-faq.html#ADMINFAQ-UNKNOWNUI
> D
> 
> 	Basically, I think you just need to make some user on the Macs to map the 
> Windows
> 	submitted jobs to, ie. make a 'rush' user on the macs, and whatever uid/gid 
> pair
> 	you use for that user, configure it in the global rush.conf file.
> 
> 	When the dameons pick up this change to the rush.conf file (use 'rush -push 
> rush.conf +any'
> 	to push the changes to the network), and submit new jobs, that should solve 
> it.
> 
> 	BTW, I'd be surprised if these errors weren't showing up in the rushd.log on 
> the macs..
> 	weren't they?

That worked!  We already had a user, we just had to put the uid/gid in 
the rush.conf.

And sorry, we hadn't even looked at the rushd.log.  It looks like those 
errors were showing up, but we wouldn't have known what they meant.

Thanks so much.

- Jance

Last Next