franklin and kraken hostname identification conflicts

Create issue
Issue #770 closed
Roland Haas created an issue

The alias patterns used in franklin.ini


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.


Comments (5)

  1. Roland Haas reporter
    • removed comment

    actually it is not an alias but the `name` return value of `socket.gethostbyname_ex(hostname)` in line 37 that is 'nid16052'.

  2. Erik Schnetter
    • removed comment

    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?

  3. Roland Haas reporter
    • removed comment

    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

  4. Log in to comment