[GE users] install execd clients

Reuti reuti at staff.uni-marburg.de
Mon Sep 15 13:37:29 BST 2008


Am 15.09.2008 um 14:11 schrieb Mag Gam:

> Reuti:
>
> Moving on, I will start using this  .
> $SGE_ROOT/default/common/settings.sh. Thanks for the tip.
>
> The machine is actually not the qmaster. I am running this on the 'to
> be' execution host.
> I ran the gethost* commands on both qmaster and client and everything
> looks right, but I am still getting this message.

Then the first step would be: is all running fine on the qmaster  
itself? - Reuti


> DNS looks good in the environment.
>
>
>
>
> On Mon, Sep 15, 2008 at 8:04 AM, Reuti <reuti at staff.uni-marburg.de>  
> wrote:
>> Am 15.09.2008 um 13:48 schrieb Mag Gam:
>>
>>> Sorry to pester, but now a new problem :-(
>>>
>>>
>>> Command failed: ./bin/lx24-amd64/qconf -sh
>>
>> When you source in your profile or system wide:
>>
>> . $SGE_ROOT/default/common/settings.sh
>>
>> you should get access to the binaries without the necessity to  
>> specify the
>> path. Also the correct architecture will be determined automatically.
>>
>>> Probably a permission problem. Please check file access permissions.
>>> Check read/write permission. Check if SGE daemons are running.
>>>
>>>
>>> This hostname is not known at qmaster as an administrative host.
>>>
>>> Real hostname of this machine:                     host, the  
>>> hostname
>>> resolving  on this host will most likely differ from\n
>>> Aliased hostname (if "host_aliases" file is used): the hostname
>>> resolving method on the qmaster machine\n
>>> Default domain ("none" means ignore):               
>>> mechengA.cs.unc.edu
>>> Ignore domain names:                               none
>>
>> What are the tools in $SGE_ROOT/utilbin/lx24-amd64 saying, i.e.
>> gethostbyname, gethostbyaddr, gethostname?
>>
>> The machine where you are issuing this command is also the qmaster?
>>
>> -- Reuti
>>
>>
>>>
>>> The resulting hostname is:              =========> true
>>>
>>> If you think that this host has already been added as an  
>>> administrative
>>>
>>> Please check and correct your >/etc/hosts< file and >/etc/ 
>>> nsswitch.conf<
>>> file on this host and on the qmaster machine.
>>>
>>> You can now add this host as an administrative host in a seperate
>>> terminal window and then continue with the installation  procedure.
>>>
>>>
>>> I have my /etc/services correct and the server is running the  
>>> correct
>>> deamons. Any ideas?
>>>
>>> I also added the client into the execution
>>>
>>> ./bin/lx24-amd64/qconf -sh shows the clien'ts FDQN  
>>> (mechengA.cs.unc.edu)
>>>
>>>
>>>
>>> On 9/15/08, Mag Gam <magawake at gmail.com> wrote:
>>>>
>>>> Disregard this. I fixed it by editing the /etc/services file
>>>>
>>>> On Mon, Sep 15, 2008 at 6:19 AM, Mag Gam <magawake at gmail.com>  
>>>> wrote:
>>>>>
>>>>> I am stuck here when trying to install execd
>>>>>
>>>>> Checking hostname resolving
>>>>> ---------------------------
>>>>>
>>>>> Cannot contact qmaster. The command failed:
>>>>>
>>>>>  ./bin/lx24-amd64/qconf -sh
>>>>>
>>>>> The error message was:
>>>>>
>>>>>  error: could not get environment variable SGE_QMASTER_PORT or
>>>>> service "sge_qmaster"
>>>>>
>>>>> You can fix the problem now or abort the installation  procedure.
>>>>> The problem can be:
>>>>>
>>>>>  - the qmaster is not running
>>>>>  - the qmaster host is down
>>>>>  - an active firewall blocks your request
>>>>>
>>>>> Contact qmaster again (y/n) ('n' will abort) [y] >>
>>>>>
>>>>> I am certain I added my client host, using "qconf -ah client".
>>>>> default/common/act_qmaster has my server listed.
>>>>>
>>>>> The server is running sge_qmaster and sge_schedd
>>>>>
>>>>> Any thoughts? or ideas?
>>>>>
>>>>> Also, I am certain there is no firewall.
>>>>>
>>>>>
>>>>> On 9/13/08, Rayson Ho <rayrayson at gmail.com> wrote:
>>>>>>
>>>>>> Actually, the SGE daemon (the qmaster) should write to that  
>>>>>> file when
>>>>>> it starts up. Can you check if the qmaster is running??
>>>>>>
>>>>>> The common/act_qmaster file is just clear text, and it should  
>>>>>> be OK to
>>>>>> just simply edit it with vi or any text editor.
>>>>>>
>>>>>> Rayson
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 9/13/08, Mag Gam <magawake at gmail.com> wrote:
>>>>>>>
>>>>>>> Rayson,
>>>>>>>
>>>>>>> Thanks for replying. I will try this and let you know.
>>>>>>>
>>>>>>> Also, is it a preferred method to edit files or execute a SGE  
>>>>>>> specific
>>>>>>> command to edit the file for me?
>>>>>>>
>>>>>>> TIA
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Sep 13, 2008 at 11:06 AM, Rayson Ho  
>>>>>>> <rayrayson at gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> The clients should share $SGE_ROOT, and the common/ 
>>>>>>>> act_qmaster file
>>>>>>>> in
>>>>>>>> the directory tells which machine the master is.
>>>>>>>>
>>>>>>>> Rayson
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 9/13/08, Mag Gam <magawake at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> I have successfully installed the master host but I am having
>>>>>>>>> trouble
>>>>>>>>> installing/configuring  the install execution hosts. I am  
>>>>>>>>> using a
>>>>>>>>> shared NFS filesystem for the spool and configuration so  
>>>>>>>>> finding the
>>>>>>>>> $SGE_ROOT and 'default' cell isn't too bad on the client.  
>>>>>>>>> But when
>>>>>>>>> trying to start up the client it says it can't find the  
>>>>>>>>> master. So
>>>>>>>>> how
>>>>>>>>> does the client know who the master is? Do I have to set an  
>>>>>>>>> env
>>>>>>>>> variable? Is it a good idea to have a shared file system  
>>>>>>>>> for cells?
>>>>>>>>>
>>>>>>>>> References:
>>>>>>>>> http://docs.sun.com/app/docs/doc/817-6118?q=N1GE
>>>>>>>>> http://docs.sun.com/app/docs/doc/817-6118/i999062? 
>>>>>>>>> q=N1GE&a=view
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Sorry for a newbie question.
>>>>>>>>> TIA
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -------------------------------------------------------------- 
>>>>>>>>> -------
>>>>>>>>> To unsubscribe, e-mail: users- 
>>>>>>>>> unsubscribe at gridengine.sunsource.net
>>>>>>>>> For additional commands, e-mail: users- 
>>>>>>>>> help at gridengine.sunsource.net
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --------------------------------------------------------------- 
>>>>>>>> ------
>>>>>>>> To unsubscribe, e-mail: users- 
>>>>>>>> unsubscribe at gridengine.sunsource.net
>>>>>>>> For additional commands, e-mail: users- 
>>>>>>>> help at gridengine.sunsource.net
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------- 
>>>>>>> -----
>>>>>>> To unsubscribe, e-mail: users- 
>>>>>>> unsubscribe at gridengine.sunsource.net
>>>>>>> For additional commands, e-mail: users- 
>>>>>>> help at gridengine.sunsource.net
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ----------------------------------------------------------------- 
>>>>>> ----
>>>>>> To unsubscribe, e-mail: users- 
>>>>>> unsubscribe at gridengine.sunsource.net
>>>>>> For additional commands, e-mail: users- 
>>>>>> help at gridengine.sunsource.net
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list