Error Unable To Contact Qmaster Using Port 536 On Host
Contents |
unable to contact qmaster using port 536 on host Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Unable To Contact Qmaster Using Port 6444
[ The following text is in the "UTF-8" character set. ] [ unable to send message to qmaster using port 6444 on host Your display is set for the "ISO-8859-10" character set. ] [ Some characters may be displayed incorrectly. ] Hi, Thanks for Christian's reply. The qmaster host resolve the new exec01.host as follow, and the new exec01.host also can resolve the qmaster host by these 2 command. [root at qmaster ~]# /usr/local/sge/utilbin/lx24-amd64/gethostbyname exec01.host Hostname: exec01.host Aliases: Host Address(es): 10.0.5.81 [root at qmaster ~]# /usr/local/sge/utilbin/lx24-amd64/gethostbyaddr 10.0.5.81 Hostname: exec01.host Aliases: Host Address(es): 10.0.5.81 [root at qmaster ~]# nslookup exec01.host Server: 10.0.2.247 Address: 10.0.2.247#53 Name: exec01.host Address: 10.0.5.81 [root at qmaster ~]# nslookup 10.0.5.81 Server: 10.0.2.247 Address: 10.0.2.247#53 81.5.0.10.in-addr.arpa name = exec01.host. But when I install sge on new exec01.host, the error message as follow. Checking hostname resolving --------------------------- Cannot contact qmaster. The command failed: ./bin/lx24-amd64/qconf -sh The error message was: error: commlib error: access denied (server host resolves source host "exec01.host" as "(HOST_NOT_RESOLVABLE)") ERROR: unable to contact qmaster using port 536 on host "qmaster.server" 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] >> n Installation failed [root at exec01 sge]# ./bin/lx24-amd64/qconf -sh error: commlib error: access denied (server host resolves source host "exec01.host" as "(HOST_NOT_RESOLVABLE)") ERROR: unable to contact qmaster using port 536 on host "qmaster.server" Check the qmster process [root at qmaster ~]# ps axuw | grep qmaster root 2496 0.0 0.0 61096 708 pts/0 S+ 15:26 0:00 grep qmaster [root at qmaster ~]# qconf -sh | grep exec01.host exec01.host Thanks a lot. Best Regards, Lu Christian Reissmann ??: > Hi, > > for me it is not clear if you already have checked that the qmaster > host can resolve the new execd: > > So please use the tools gethost
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can https://arc.liv.ac.uk/pipermail/gridengine-users/2008-August/019876.html ask a question Anybody can answer The best answers are voted up and rise to the top installing Grid Engine “cannot reach qmaster” up vote 0 down vote favorite I want to install Grid Engine on my laptop. I am using Ubuntu 11.10 under VirtualBox 4.1.6. (The purpose of installing Grid Engine is not to compute anything, I just want a working http://superuser.com/questions/404315/installing-grid-engine-cannot-reach-qmaster Grid Engine environment to be able try out bash scripting for array jobs etc. The jobs which I would run would just do "sleep", so the cluster would consist of only one single node. My laptop has a dualcore CPU but I don't know if that's relevant here.) I am following the instructions from http://astoryworthtelling.wordpress.com/2009/08/25/installing-sge-on-ubuntu-single-machine-local-install/ and have tried to install Grid Engine like this: sudo apt-get install gridengine-master gridengine-exec gridengine-client gridengine-qmon gridengine-common Then I start qmon with sudo. The GUI starts alright, I click on "Queue Control". What then happens is that a window pops up saying "cannot reach qmaster": If I click "Retry" I get another popup which is slightly more informative, "Unable to contact qmaster using port 6444 on host "anton-VirtualBox": My question is, how can I fix this? Help to get Grid Engine running and fixing this would be very much appreciated, thank you. P.S.: One more thing, maybe it helps to help track down the error. When I try to use qstat from within bash, I get this message: anton@anton-VirtualBox:~$ qstat error: commlib error: access denied (client IP resolved to host name
Sign in Pricing Blog Support Search GitHub This repository Watch 1 Star 12 Fork 4 gawbul/docker-sge Code Issues 2 https://github.com/gawbul/docker-sge/issues/3 Pull requests 3 Projects 0 Pulse Graphs New issue error: unable to send message to qmaster using port 6444 on host "66be2f8db7c1": can't resolve host name #3 Closed http://marc.info/?t=134749385200006&r=1&w=2 gawbul opened this Issue Dec 10, 2014 · 3 comments Projects None yet Labels bug Milestone No milestone Assignees No one assigned 1 participant unable to Owner gawbul commented Dec 10, 2014 Hostname changes during docker build and settings written to /opt/sge reference wrong hostname. gawbul added the bug label Dec 10, 2014 Owner gawbul commented Dec 10, 2014 Aiming to fix with echo `hostname` > ~/sge_hostname during the SGE install and then echo "`hostname -i` `cat ~/sge_hostname`" >> /etc/hosts at the qmaster using port end of the Dockerfile. gawbul referenced this issue in bionode/bionode-sge Dec 10, 2014 Closed Docker image for development and testing #1 Owner gawbul commented Dec 10, 2014 Previous fix attempt didn't work. Docker applies hostname on docker run as the container id. Can override with docker run -h docker-sge. Best way to fix this, I think, is to run a script on execution of the container to change the hostname in SGE config to that of the running container? Owner gawbul commented Dec 12, 2014 Fixed this in b007111. gawbul closed this Dec 12, 2014 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
npaci-rocks-discussion 2016-10-01 - 2016-11-01 (87 messages) 1. 2012-09-13 Re: [Rocks-Discuss] ERROR: unable to send message to npaci-roc Guillermo Marco Pu 2. 2012-09-13 Re: [Rocks-Discuss] ERROR: unable to send message to npaci-roc Luca Clementi 3. 2012-09-12 [Rocks-Discuss] ERROR: unable to send message to qmas npaci-roc yang_yi Configure | About | News | Addalist | SponsoredbyKoreLogic