#770: franklin and kraken hostname identification conflicts ------------------------+--------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- The alias patterns used in franklin.ini {{{ ^nid[0-9][0-9][0-9][0-9][0-9](.nersc.gov)?$ }}} matches one of the alias of a kraken head node. In particular I get aliases (on kraken-gsi4): {{{ ['c1-1c1s5n0', 'login16', 'logingsi4', 'krakenpf16', 'kraken-gsi4'] }}} which matches the nid pattern. I am not sure if franklin and kraken actually share head nodes or not. If not then a more restrictive alias pattern for franklin might help, though I have no access to it so cannot test it.
#770: franklin and kraken hostname identification conflicts -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Resolution: | Keywords: -------------------------+--------------------------------------------------
Comment (by rhaas):
actually it is not an alias but the {{{name}}} return value of {{{socket.gethostbyname_ex(hostname)}}} in simlib.py line 37 that is 'nid16052'.
#770: franklin and kraken hostname identification conflicts -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Resolution: | Keywords: -------------------------+--------------------------------------------------
Comment (by eschnett):
Franklin and Kraken are hosted by different agencies, and don't share login nodes. I assume that the nidNNN are Cray's naming scheme for compute nodes, and they conflict.
Franklin will be retired in six weeks, so this problem should solve itself soon.
Where do you see this problem? A compute node of Kraken? Or a Kraken head node?
#770: franklin and kraken hostname identification conflicts -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Resolution: | Keywords: -------------------------+--------------------------------------------------
Comment (by rhaas):
A workaround to get simfactory to work is to override its automatic detection mechanism by doing (on a kraken head node): {{{ echo kraken >$HOME/.hostname }}}
#770: franklin and kraken hostname identification conflicts -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: defect | Status: closed Priority: minor | Milestone: Component: SimFactory | Version: Resolution: fixed | Keywords: -------------------------+-------------------------------------------------- Changes (by eschnett):
* status: new => closed * resolution: => fixed
Comment:
Franklin does not exist any more. Closing this ticket.
trac@lists.einsteintoolkit.org
-
Einstein Toolkit