Juan,
Ideally you shouldn't use 'kill -9' on the shrpcmonitor process ... doing so can end up with shared memory segments left live ...
To clean up the shared memory segments you first list the segments with 'ipcs -a'. The output will look like the following:
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 327680 root 777 139264 1
0x00000000 524289 dhenrich 600 393216 2 dest
0x00000000 14909442 dhenrich 600 393216 2 dest
0x00000000 589827 dhenrich 600 393216 2 dest
0x00000000 622596 dhenrich 600 393216 2 dest
0x4c02a47d 18644997 dhenrich 660 116604928 0
0x00000000 983046 dhenrich 600 393216 2 dest
0x00000000 720903 dhenrich 600 393216 2 dest
0x00000000 753672 dhenrich 600 393216 2 dest
0x00000000 786441 dhenrich 600 393216 2 dest
0x00000000 819210 dhenrich 600 393216 2 dest
0x4c02a47f 18677771 dhenrich 660 116359168 0
0x4c02a480 23592972 dhenrich 660 562249728 8
0x00000000 14942221 dhenrich 600 393216 2 dest
0x00000000 6520847 dhenrich 600 393216 2 dest
------ Semaphore Arrays --------
key semid owner perms nsems
0x4c02a47d 6225920 dhenrich 660 109
0x07b162d5 131073 dhenrich 600 1
0x4c02a47f 6258690 dhenrich 660 101
0x4c02a480 11173891 dhenrich 660 101
------ Message Queues --------
key msqid owner perms used-bytes messages
Then use 'ipcrm -m' to remove the "extra" hung segments:
ipcrm -m 23592972
There are a number of shared memory segments that don
t belong to GemStone so you don't want to remove things willy nilly:)
The best solution might be to reboot your server then make a note of what 'ipcs -a' looks like so if you need to do it again you'll have an idea which segments (and semaphores) belong to GemStone....
If you are running an appliance it can take a bit of time for the stone and related processes to shut down cleanly .... depends upon disk i/o ...
When I am nuking a running GemStone I try killing the stoned process first (you can use -9 on the stone process if you're not worried about potentially corrupting your extent ... like when you have backups) but using -9 on the shrpc monitor is not a good idea.
Dale
----- "Juan" <
[hidden email]> wrote:
| folks
|
| some times to press button labeled 'stop glass system'
| the cache light is not off and my process shows
|
| 6934 ? Sl 0:03 /opt/gemstone/product/sys/shrpcmonitor
| 'seaside@192.168.28.139' setlocationstr 8000 setnumpages 49
| 6970 ? S 0:00 /opt/gemstone/product/sys/pgsvrmain
| seaside@192.168.28.139 0 1 -1
|
| if i kill the process with kill -9 6934 ( for example)
|
| glass doesn't start anymore the error say something about cache
| problems.
| using appliance glass.
| any ideas?
| best regards
| MDC
Locked
