Bug 50949
Summary: | LAM fails to boot on localhost | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Joachim Frieben <jfrieben> |
Component: | lam | Assignee: | Trond Eivind Glomsrxd <teg> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | roswell | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-05 13:35:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joachim Frieben
2001-08-05 13:35:16 UTC
It works just fine for me... halden% tail -n 3 /etc/lam/lam-bhost.def # localhost cpu=2 halden% lamboot -d LAM 6.5.3/MPI 2 C++/ROMIO - University of Notre Dame lamboot: boot schema file: /etc/lam/lam-bhost.def lamboot: opening hostfile /etc/lam/lam-bhost.def lamboot: found the following hosts: lamboot: n0 localhost lamboot: found 1 host node(s) lamboot: origin node is 0 (halden.devel.redhat.com) lamboot: attempting to execute "hboot -t -c lam-conf.lam -d -I " -H 172.16.46.54 -P 39502 -n 0 -o 0 "" hboot: process schema = "/etc/lam/lam-conf.lam" hboot: found /usr/bin/lamd hboot: performing tkill hboot: tkill hboot: booting... hboot: fork /usr/bin/lamd [1] 353 lamd -H 172.16.46.54 -P 39502 -n 0 -o 0 -d hboot: attempting to execute lamboot completed successfully halden% lamnodes n0 halden.devel.redhat.com:2 halden% rpm -q lam lam-6.5.3-1 halden% Described behaviour was observed after -upgrading- from a working Red Hat Linux 7.1 installation. After doing a clean install of 'Roswell', lam worked as expected. |