I'm using static dhcp.
On 1/3/2012 5:19 PM, Gerard Henry wrote:
for instance, i have the same problem with a SGE master installed in a
virtualbox on a laptop. The problem arises when i swith laptop form
one network to another one. In this case, i restart the SGE master and
it's ok.
Why don't you use fixed adress in your dhcp config?
On 01/03/12 04:11 PM, Semi wrote:
My SGE_ROOT located on nfs, I also use dhcp and files (inetd.conf).
What can cause problem to access settings.sh?
may be there is any hint or trick or work around to solve this problem?
If you mean the daemon doesn't start at boot time, but does from a login
session, then it's likely the environment isn't set up correctly at boot
time, e.g. the init script isn't sourcing the right settings.sh.
On 1/2/2012 6:49 PM, Dave Love wrote:
Semi<[email protected]> writes:
Sometimes sgeexecd can't connect server, but after manual restart
succeeded.
How I can solve this problem?
Sometimes sgeexecd can't connect server, but after manual restart
succeeded. How I can solve this problem?
*
Spool logs*
tail sge92/messages
01/01/2012 16:21:51|execd|sge92|E|commlib error: can't connect to
service (Connection timed out)
01/01/2012 16:22:33|execd|sge92|E|getting configuration: unable to
contact qmaster using port 536 on host "sge01"
01/01/2012 16:25:45|execd|sge92|E|can't get configuration from qmaster
-- backgrounding
01/01/2012 16:26:16|execd|sge92|W|local configuration sge92 not defined
- using global configuration
01/01/2012 16:26:16|execd|sge92|I|starting up 6.0u8
01/01/2012 16:27:09|execd|sge92|I|controlled shutdown 6.0u8
01/01/2012 16:28:57|execd|sge92|E|commlib error: can't connect to
service (Connection timed out)
01/01/2012 16:29:39|execd|sge92|E|getting configuration: unable to
contact qmaster using port 536 on host "sge01"
01/01/2012 16:32:51|execd|sge92|E|can't get configuration from qmaster
-- backgrounding
01/01/2012 16:36:21|execd|sge92|W|local configuration sge92 not defined
- using global configuration
01/01/2012 16:36:21|execd|sge92|I|starting up 6.0u8
*
Executive node logs*
01/01/2012 16:28:57|execd|sge92|E|*commlib error: can't connect to
service* (Connection timed out)
01/01/2012 16:29:39|execd|sge92|E|getting configuration: unable to
contact qmaster using port 536 on host "sge01"
01/01/2012 16:32:51|execd|sge92|E|can't get configuration from qmaster
-- backgrounding
If you mean the daemon doesn't start at boot time, but does from a
login
session, then it's likely the environment isn't set up correctly at
boot
time, e.g. the init script isn't sourcing the right settings.sh.
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
