cant open /shm_beostat

Roger Williams R.Williams at gns.cri.nz
Tue Jul 24 05:15:10 EDT 2001




Nicholas Henke wrote:

>when I try to do a linpack run from the commands line, I get an error
>stating that it couldnt open shared memory file /shm/beostat
>Any ideas on what is causing this? I am running scyld

and I didn't see anyone reply. While I don't have any trouble running the
supplied linpack script on my trial Scyld 27bz-7 cluster (5 x PII 166!!) I
have seen a similar message and would also like to know its cause.

shmblk_open: Couldn't open shared memory file: /shm_beostat
shmblk_open failed

[1]+  Exit 1                  beostatus

As you can see, the error precedes/follows a termination of beostatus
(which I have displayed across the network to my Sun workstation) and
happens after everything's been sitting idle for hours/days.

Also, I see these messages fairly regularly - again when the Scyld cluster
is idle.

beostat_req: beostat_lib.c: 100  Connection failed: Connection refused
beostat_req: beostat_lib.c: 100  Connection failed: Connection refused

What are these from?

--
Roger Williams, Institute of Geological & Nuclear Sciences, New Zealand
R.Williams at gns.cri.nz : Lotus Notes v4.6



_______________________________________________
Beowulf mailing list, Beowulf at beowulf.org
To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf



More information about the Beowulf mailing list