[Rocks-Discuss] Rocks 5: unable to contact qmaster using port 536

Philip Papadopoulos philip.papadopoulos at gmail.com
Thu May 29 22:08:01 PDT 2008

Even if your IP address is given to you via DHCP  -- the public address and
hostname must be defined statically
during installation. Naming is extremely sensitive for various systems, and
what we have works across
a number of services.  You almost certainly need to reinstall your frontend
to get the public and private hostname
propagated properly to various pieces of configuration.


On Thu, May 29, 2008 at 9:03 PM, Jens Hannemann <j.hannemann at ieee.org>

> Hi folks,
> I have a fresh install of Rocks 5.
> Unfortunately, the sge_qmaster fails to start. It immediately bailed out on
> me as the external hostname (in our case efrafa.audio, configured originally
> by DHCP during the install) as returned by the hostname command did not
> match the internal hostname (efrafa.local) that has been written to
> /opt/gridengine/default/common/act_qmaster .
> I fixed that by using the internal hostname in /etc/sysconfig/network.
> Now, the script gets along further, but then reports the following:
> --- snip ---
> -bash-3.1# service sgemaster start
>   starting sge_qmaster
> sge_qmaster didn't start!
> Please check the messages file
>   starting sge_schedd
> error: commlib error: can't connect to service (Connection refused)
> error: getting configuration: unable to contact qmaster using port 536 on
> host "efrafa.local"
> error: can't get configuration from qmaster -- backgrounding
> --- snap ---
> Any thoughts on that? And should I file a bug report on the first issue?
> Thanks,
> Jens

Philip Papadopoulos, PhD
University of California, San Diego
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20080529/37844bae/attachment.html 

More information about the npaci-rocks-discussion mailing list