not initializing shared memory
Joseph Dixon asked what to do about the warning 'mt_shm_remove: may not have removed all/correct segments'. Respondents said leftover shared memory segments from an unclean shutdown can be listed with ipcs and removed with ipcrm, or onmode -ky retried, or the box rebooted. Mark Denham said it can largely be ignored unless client processes still hold segments.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
mt_shm_remove: WARNING: may not have removed all/correct segments what do you do about that?
your ids might not shut down correctly last time, so there are shm segments which have not been deleted. 1. reboot or 2. use ipcs to show segments and ipcrm to delete, make sure you hit the right segments. -----Ursprüngliche Nachricht----- Von: JOSEPH DIXON [mailto:jdixon@servnu.com] Gesendet: Donnerstag, 14. August 2003 16:23 An: ids@iiug.org Betreff: not initializing shared memory [1694] mt_shm_remove: WARNING: may not have removed all/correct segments what do you do about that?
Joseph
Use ipcs -m at command line to see existing shared memory segments. Try
onmode -ky a couple of time to see if they will remove (after ensuring allpossible connected sessions are terminated). If this doesn't work use ipcrm
-m 'segment id' to manually remove the shared memory segments. (If all else
fails bounce the box !!!)
Keith
-> -----Original Message-----
-> From: JOSEPH DIXON [mailto:jdixon@servnu.com]
-> Sent: Thursday, August 14, 2003 3:23 PM
-> To: ids@iiug.org
-> Subject: not initializing shared memory [1694]
->
->
-> mt_shm_remove: WARNING: may not have removed all/correct segments
->
-> what do you do about that?
->
********************************************************************************
**
This message is sent in strict confidence for the addressee only. It may
contain legally privileged information. The contents are not to be disclosed
to anyone other than the addressee. Unauthorised recipients are requested
to preserve this confidentiality and to advise the sender immediately of any
error in transmission.
This footnote also confirms that this email message has been swept for the
presence of computer viruses, however we cannot guarantee that this message
is free from such problems.
********************************************************************************
**
Joe: Check any pending/hanging shared memory and/or semaphore connections and remove it. You can find it using "ipcs | grep informix" remove using "ipcrm <sem id / shm id>". Once all removed successfully, you can restart Informix server without this error. Thank You Ramesh Vasudevan "JOSEPH DIXON" <jdixon@servnu.co To: ids@iiug.org m> cc: Sent by: Subject: not initializing shared memory [1694] forum.subscriber@ iiug.org 08/14/03 10:22 AM mt_shm_remove: WARNING: may not have removed all/correct segments what do you do about that?
Largely ignore it. You can run ipcs -m to see if there are any memory fragments still hanging about. This can happen if there are client processes that have not been killed off. Most often these memory fragments will show a capital D, in the flags col I think. If they are there you have to find the offending processes and remove them to release the fragments. Sometimes its as simple as running ipcs -mp and then using ps to see if the pids listed are still hanging around. Mark ----- Original Message ----- From: "JOSEPH DIXON" <jdixon@servnu.com> To: <ids@iiug.org> Sent: Thursday, August 14, 2003 10:22 Subject: not initializing shared memory [1694] > mt_shm_remove: WARNING: may not have removed all/correct segments > > what do you do about that? >