S
SteveSaltDanwood
Guest
All, We migrated our systems onto a Linux server running OE 11.4 back in July . In Late November we had an outage on our Live server, and the DB log file reported a semaphore error. Server was rebooted, and everything went back to normal. Saturday just gone, we had another outage, followed by two on Monday and 2 yesterday. we are seeing entries like: [2015/12/14@15:27:47.359+0000] P-65624 T-140275601626944 I SRV 21: (1075) Semaphore id 30 was removed [2015/12/14@15:27:47.359+0000] P-143185 T-139735250765632 I SRV 23: (723) ** The server has disconnected. [2015/12/14@15:27:47.359+0000] P-65624 T-140275601626944 I SRV 21: (723) ** The server has disconnected. [2015/12/14@15:27:47.359+0000] P-143185 T-139735250765632 F SRV : (6517) SYSTEM ERROR: Unexpected error return from semAdd -1 [2015/12/14@15:27:51.722+0000] P-9582 T-140607981442880 I ABL 104: (1075) Semaphore id -32739 was removed [2015/12/14@15:27:51.722+0000] P-9549 T-140463995369280 I ABL 103: (1075) Semaphore id -32739 was removed [2015/12/14@15:27:51.723+0000] P-9549 T-140463995369280 F ABL : (6517) SYSTEM ERROR: Unexpected error return from semAdd -1 [2015/12/14@15:27:54.167+0000] P-11878 T-139624773539648 I SRV 18: (1132) Invalid semaphore id [2015/12/14@15:27:54.167+0000] P-11878 T-139624773539648 I SRV 18: (10839) SYSTEM ERROR: Unable to get value of semaphore set : semid = 28, errno = 22. [2015/12/14@15:27:54.167+0000] P-11878 T-139624773539648 I SRV 18: (-----) semLockLog_2: semValue val = -1 [2015/12/14@15:27:54.167+0000] P-11878 T-139624773539648 I SRV 18: (1132) Invalid semaphore id [2015/12/14@15:27:54.167+0000] P-11878 T-139624773539648 I SRV 18: (10839) SYSTEM ERROR: Unable to set semaphore set : semid = -32739, errno = 22. [2015/12/14@15:27:54.169+0000] P-11878 T-139624773539648 I SRV 18: (2520) Stopped. Our sys Admin has increased both SEMMSL, SEMMNS and SEMOPM slightly, but based on the limited reading about the values these need to be (article P61278) , we should have been fine. Is there anything we can do to monitor our situation, and what should we be looking at. The Production server has 128Gb on memory, and we've only allocated a small percentage of that to the database at the moment, so we should not be running out of memory, as one article I read suggested Regards, Steve Salt Application Developer (accidental DBA)
Continue reading...
Continue reading...