Hi David,<div><br></div><div>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.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Mike</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 5, 2012 at 11:14 AM, David Beer <span dir="ltr"><<a href="mailto:dbeer@adaptivecomputing.com" target="_blank">dbeer@adaptivecomputing.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Matt,<div><br></div><div>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.</div>
<div><br></div><div>Cheers,</div><div><br></div><div>David<div><div class="h5"><br><br><div class="gmail_quote">On Mon, Nov 5, 2012 at 11:14 AM, Ezell, Matthew A. <span dir="ltr"><<a href="mailto:ezellma@ornl.gov" target="_blank">ezellma@ornl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 11/3/12 7:29 PM, "Mike Dacre" <<a href="mailto:mike.dacre@gmail.com" target="_blank">mike.dacre@gmail.com</a>> wrote:<br>
<br>
>John,<br>
>Thanks for that. Unfortunately, that probably means I need to move back<br>
>to version 3, since I can't use 4.1. Does anyone have any idea if the<br>
>hyphen-in-hostname problem is going to be fixed any time soon in 4.1?<br>
<br>
</div>4.1.2 definitely had problems with hostnames with dashes, but some fixes<br>
went into 4.1.3. I'm running 5 pbs_servers (4.1.3) on hosts that have<br>
dashes in them without any problems. Some other users have reported that<br>
issues persist in 4.1.3, but it works fine here. I would recommend trying<br>
4.1.3 before reverting to 3.x.<br>
<br>
Next time you see this serverdb corruption, save off a copy of the<br>
"broken" serverdb file. That might help find the source of the problem.<br>
<br>
~Matt<br>
<br>
---<br>
Matt Ezell<br>
HPC Systems Administrator<br>
Oak Ridge National Laboratory<br>
<div><div><br>
<br>
_______________________________________________<br>
torqueusers mailing list<br>
<a href="mailto:torqueusers@supercluster.org" target="_blank">torqueusers@supercluster.org</a><br>
<a href="http://www.supercluster.org/mailman/listinfo/torqueusers" target="_blank">http://www.supercluster.org/mailman/listinfo/torqueusers</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div>David Beer | Senior Software Engineer</div><div>Adaptive Computing</div><br>
</font></span></div>
<br>_______________________________________________<br>
torqueusers mailing list<br>
<a href="mailto:torqueusers@supercluster.org">torqueusers@supercluster.org</a><br>
<a href="http://www.supercluster.org/mailman/listinfo/torqueusers" target="_blank">http://www.supercluster.org/mailman/listinfo/torqueusers</a><br>
<br></blockquote></div><br></div>