When apcupsd starts, I get the following error: “attach_shmarea: cannot get shm area: Identifier removed.\ What is the problem?
This problem and the problem of cannot create shm area are due to the fact that the shared memory key that apcupsd wants to use is already in use. This happens most frequently when there is an old zombie apcupsd process still in the system. The solution is to remove the old process. You can often see what is going on by doing a: ipcs command as root when apcupsd is not running. If you see a segment with the key 0x10feed01, you can be sure there is some old apcupsd process still using it. If you cannot kill the old process, you can try using ipcrm (see the man pages). Recent versions of apcupsd starting with apcupsd-3.8.2Beta6 should no longer have this problem as they will automatically try using a different key.
Related Questions
- When apcupsd starts, I get the following error: ``attach_shmarea: cannot get shm area: Identifier removed.\ What is the problem?
- When I install Comtun, I got an error complaining ws2_32.dll is missing. How to fix this problem?
- We have error messages appearing when we try to install the CD. What is the problem?