[torqueusers] Major Problem with pbs_server database being corrupted
mike.dacre at gmail.com
Mon Nov 5 13:52:07 MST 2012
I can't risk running 4.1.3 right now as this is a production cluster with
active users. Right now I have gone back to 2.5.12 for stability. I would
love confirmation that 4.1.3 does not have a problem with 'hostnames with
dashes', as I would like to upgrade asap.
On Mon, Nov 5, 2012 at 11:14 AM, David Beer <dbeer at adaptivecomputing.com>wrote:
> Thanks for pointing that out. I am also wondering what the 'hostnames with
> dashes' problem is in 4.1.3. If anyone knows of the details of this issue,
> please create a bugzilla issue with the appropriate details so that we can
> resolve this.
> On Mon, Nov 5, 2012 at 11:14 AM, Ezell, Matthew A. <ezellma at ornl.gov>wrote:
>> On 11/3/12 7:29 PM, "Mike Dacre" <mike.dacre at gmail.com> wrote:
>> >Thanks for that. Unfortunately, that probably means I need to move back
>> >to version 3, since I can't use 4.1. Does anyone have any idea if the
>> >hyphen-in-hostname problem is going to be fixed any time soon in 4.1?
>> 4.1.2 definitely had problems with hostnames with dashes, but some fixes
>> went into 4.1.3. I'm running 5 pbs_servers (4.1.3) on hosts that have
>> dashes in them without any problems. Some other users have reported that
>> issues persist in 4.1.3, but it works fine here. I would recommend trying
>> 4.1.3 before reverting to 3.x.
>> Next time you see this serverdb corruption, save off a copy of the
>> "broken" serverdb file. That might help find the source of the problem.
>> Matt Ezell
>> HPC Systems Administrator
>> Oak Ridge National Laboratory
>> torqueusers mailing list
>> torqueusers at supercluster.org
> David Beer | Senior Software Engineer
> Adaptive Computing
> torqueusers mailing list
> torqueusers at supercluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the torqueusers