Yup, It finally worked.
Thanks very much for your help!
On Thu, Oct 15, 2015 at 3:48 PM, Reuti wrote:
> They must run as root to allow switching to any user to run a job.
>
> reuti@node:~> ps -eo user,ruser,command | grep sge
> sgeadmin root /usr/sge/bin/lx24-amd64/sge_execd
>
>
> > Am 15.1
They must run as root to allow switching to any user to run a job.
reuti@node:~> ps -eo user,ruser,command | grep sge
sgeadmin root /usr/sge/bin/lx24-amd64/sge_execd
> Am 15.10.2015 um 15:43 schrieb Hatem Elshazly :
>
> No. the daemon process is owned by the user:
> ehpcuser 5842 0.0 0.0
No. the daemon process is owned by the user:
ehpcuser 5842 0.0 0.0 61376 1748 ?Sl 13:22 0:00
/opt/sge6/bin/linux-x64/sge_execd
On Thu, Oct 15, 2015 at 3:32 PM, Reuti wrote:
>
> > Am 15.10.2015 um 15:21 schrieb Hatem Elshazly :
> >
> > Exactly!
> > I found this message in a exec
> Am 15.10.2015 um 15:21 schrieb Hatem Elshazly :
>
> Exactly!
> I found this message in a execd log file:
> 10/15/2015 12:28:02| main|ip-172-31-49-241|E|getting configuration: denied:
> request for user "ehpcuser" does not match credentials for connection
>
> Does this mean that this user s
Exactly!
I found this message in a execd log file:
10/15/2015 12:28:02| main|ip-172-31-49-241|E|getting configuration:
denied: request for user "ehpcuser" does not match credentials for
connection wrote:
> The spool directory is created when the execd starts. I.e. it can also be
> removed in cas
Exactly!
I found this message in the log under /tmp:
On Thu, Oct 15, 2015 at 2:56 PM, Reuti wrote:
> The spool directory is created when the execd starts. I.e. it can also be
> removed in case of problems in this spool directory and with the next
> restart it's recreated.
>
> Is there any file i
The spool directory is created when the execd starts. I.e. it can also be
removed in case of problems in this spool directory and with the next restart
it's recreated.
Is there any file in /tmp on the exechost having execd in its name? If execd
runs into problems during startup, it's the only o
Yes it is.
Why do you think that the exec dirs weren't created? all the permissions
and ownerships are granted.
I'm using this script: inst_sge_sc to make the installation on ec2
instances not using apt-get gridengine-exec because I want to make the
installation in noninteractive mode but it seems
> Am 15.10.2015 um 14:33 schrieb Hatem Elshazly :
>
> It is in state qw.
>
> home directory is mounted.
>
> I used qalter command it produces this output:
> instance "node" dropped because it is temporarily not available
> I checked the firewalls and all of them are dropped and daemons are list
It is in state qw.
home directory is mounted.
I used qalter command it produces this output:
instance "node" dropped because it is temporarily not available
I checked the firewalls and all of them are dropped and daemons are listing
on the ports on the master and executions nodes.
I noticed that
Hi,
> Am 15.10.2015 um 01:16 schrieb Hatem Elshazly :
>
> Hi there,
>
> I'm having a problem getting an execution host to work. The master node seems
> it can't sense the execution node, when I submit a job it stalls in the queue.
Is it in state "qw" or "t"?
$ qalter -w v
will check whether
Hi there,
I'm having a problem getting an execution host to work. The master node
seems it can't sense the execution node, when I submit a job it stalls in
the queue.
Both daemons are running on master and executing node, I added the
execution node to the queue and made sure the ports are open an
12 matches
Mail list logo
