Re: [gridengine users] Debugging a commlib error following reboot of exec host

Hi Joshua, Thank you for your reply. Please see my comments below. On Tue, Jul 03, 2018 at 11:30 AM PDT, Joshua Baker-LePain wrote: > On Tue, 26 Jun 2018 at 9:12am, Mun Johl wrote > > > We're using SGE 8.1.9 on CentOS 6.9 > > > > "All of the sudden" we've noticed that when we reboot an executi

Re: [gridengine users] Debugging a commlib error following reboot of exec host

On Tue, 26 Jun 2018 at 9:12am, Mun Johl wrote We're using SGE 8.1.9 on CentOS 6.9 "All of the sudden" we've noticed that when we reboot an execution host, any jobs sent to it within the first 10-15 min following boot-up will get stuck in the 't' state until deleted (sometimes that has to be don

[gridengine users] Debugging a commlib error following reboot of exec host

Hi, We're using SGE 8.1.9 on CentOS 6.9 "All of the sudden" we've noticed that when we reboot an execution host, any jobs sent to it within the first 10-15 min following boot-up will get stuck in the 't' state until deleted (sometimes that has to be done forcibly). However, after 10-ish minutes,

[gridengine users] Debugging a commlib error following reboot of exec host

Hi, We're using SGE 8.1.9 on CentOS 6.9 "All of the sudden" we've noticed that when we reboot an execution host, any jobs sent to it within the first 10-15 min following boot-up will get stuck in the 't' state until deleted (sometimes that has to be done forcibly). However, after 10-ish minutes,