Ubuntu
eucalyptus package

eucalyptus-cc and nc init scripts do not clear /dev/shm before 'start' or after 'stop'

Bug #338866 reported by Daniel Nurmi
2
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

if an NC/CC needs to be fully restarted (if changes are made to the eucalyptus.conf, for example), then /dev/shm/*eucalyptus* should be cleared out (shared memory segments and semaphores). If the user wants to just shutdown/restart the process itself (without losing state), then /dev/shm/*eucalyptus* should be left while the process is restarted.

Revision history for this message
Soren Hansen (soren) wrote :

I'm not sure how to do this now that each component has its own init script. What should be removed for the NC and the CC, respectively?

Changed in eucalyptus (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel Nurmi (nurmi) wrote :

for the NC; /dev/shm/sem.eucalyptus-* will clear up NC semaphores.
for the CC; /dev/shm/*eucalyptusCC* will clear up CC semaphores and shared memory state

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

This looks fix-released to me. I'm looking at the init scripts, and I see:

eucalyptus-cc.in: rm -f /dev/shm/*eucalyptusCC*
eucalyptus-cc.in: rm -f /dev/shm/*eucalyptusCC*
eucalyptus-cc.in: rm -f /dev/shm/*eucalyptusCC*
eucalyptus-cc.in: rm -f /dev/shm/*eucalyptusCC*
eucalyptus-cc.in: rm -f /dev/shm/*eucalyptusCC*
eucalyptus-cc.in: rm -f /dev/shm/*eucalyptusCC*
eucalyptus-nc.in: rm -f /dev/shm/sem.eucalyptus-nc* /dev/shm/sem.eucalyptus-st*
eucalyptus-nc.in: rm -f /dev/shm/sem.eucalyptus-nc* /dev/shm/sem.eucalyptus-st*

:-Dustin

Changed in eucalyptus (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.