Ah, /dev/shm had root:root user writable only. Opening it up seems to have
kicked something the right way. Thanks folks.
John White
HPC Systems Engineer
(510) 486-7307
One Cyclotron Rd, MS: 50C-3209C
Lawrence Berkeley National Lab
Berkeley, CA 94720
On Apr 11, 2013, at 1:37 PM,
Yep, we've definitely got /dev/shm (this was done to fix an earlier problem).
John White
HPC Systems Engineer
(510) 486-7307
One Cyclotron Rd, MS: 50C-3209C
Lawrence Berkeley National Lab
Berkeley, CA 94720
On Mar 27, 2013, at 4:46 PM, Andrew Beekhof wrote:
> What about /dev/shm
ent is written with proper switch user
> environment and not rewriting my core pattern, enable world write on
> CRM_CCORE_DIR was the easy work around for it.
>
> Rainer
> Gesendet: Freitag, 29. März 2013 um 09:51 Uhr
> Von: "Jacek Konieczny"
> An: pacemaker@oss.clusterlabs
etreff: Re: [Pacemaker] issues when installing on pxe booted environment
On Fri, 29 Mar 2013 11:37:37 +1100
Andrew Beekhof wrote:
> On Thu, Mar 28, 2013 at 10:43 PM, Rainer Brestan
> wrote:
> > Hi John,
> > to get Corosync/Pacemaker running during anaconda installation, i
> >
On Fri, 29 Mar 2013 11:37:37 +1100
Andrew Beekhof wrote:
> On Thu, Mar 28, 2013 at 10:43 PM, Rainer Brestan
> wrote:
> > Hi John,
> > to get Corosync/Pacemaker running during anaconda installation, i
> > have created a configuration RPM package which does a few actions
> > before starting Corosy
gt;
> Rainer
>
> Gesendet: Donnerstag, 28. März 2013 um 00:46 Uhr
> Von: "Andrew Beekhof"
> An: "The Pacemaker cluster resource manager"
> Betreff: Re: [Pacemaker] issues when installing on pxe booted environment
> What about /dev/shm ?
> Libqb tries to
esource manager"
Betreff: Re: [Pacemaker] issues when installing on pxe booted environment
What about /dev/shm ?
Libqb tries to create some shared memory in that location by default.
On Thu, Mar 28, 2013 at 8:50 AM, John White wrote:
> Yup:
> -bash-4.1$ cd /var/run/crm/
> -bash-4.1$
What about /dev/shm ?
Libqb tries to create some shared memory in that location by default.
On Thu, Mar 28, 2013 at 8:50 AM, John White wrote:
> Yup:
> -bash-4.1$ cd /var/run/crm/
> -bash-4.1$ ls
> lost+found pcmk pengine st_callback st_command
> -bash-4.1$ touch blah
> -bash-4.1$ ls -l
> tot
Yup:
-bash-4.1$ cd /var/run/crm/
-bash-4.1$ ls
lost+found pcmk pengine st_callback st_command
-bash-4.1$ touch blah
-bash-4.1$ ls -l
total 16
-rw-r--r-- 1 hacluster haclient 0 Mar 27 14:50 blah
drwx-- 2 root root 16384 Mar 14 15:00 lost+found
srwxrwxrwx 1 root root
On 2013-03-22 19:31, John White wrote:
> Hello Folks,
> We're trying to get a corosync/pacemaker instance going on a 4 node
> cluster that boots via pxe. There have been a number of state/file system
> issues, but those appear to be *mostly* taken care of thus far. We're
> running into a
Hello Folks,
We're trying to get a corosync/pacemaker instance going on a 4 node
cluster that boots via pxe. There have been a number of state/file system
issues, but those appear to be *mostly* taken care of thus far. We're running
into an issue now where cib just isn't staying up wit
11 matches
Mail list logo