D
dvoyat
Guest
Hi Coming back to this issue with some more findings. It's been a bit painfull to capture evidence but I've been able to replicate the case and to eliminate but need to understand what has changed between 11.7 and 11.7.2 to make it happen on same RedHat 7.2 server. As short summary I've been tracking what could remove the semaphore which eventually get db crashed a bit later. We start DB from adminserver (autostart) and adminserver is started from 'sudo' using some restricted user account. The semaphore are owned by same restricted account. We also use this restricted account for some other maintenance activity either via manual "sudo" or via scheduled process (cron). Whenever I raise a "sudo" command against this restricted account I've been able running "ipcs -s" to check that there was no longer any semaphore set available. I did test several times and each time semaphore get removed. I did a bit of search and I manage to eliminate the case by disabling "RemoveIPC=yes" in RH logind.conf (default feature since RH 7 as per my understanding) and restarting systemd-logind. And this indeed prevent the removal of - at least - semaphores. After that DB works fine for more than 24hrs with its regular db activity via appserver, batch processes.... There lot of forum suggesting that proper way of fixing this kind of issue is not to disable "RemoveIPC" but to ensure that all processes & daemon requiring communication & synchronization mecanism are fired by system users which are excluded from the removal. I'll probably consider that later on with more inhouse expert but the fact is that it was working fine with 11.7. I'll contact Progress Tech Support anyway but if anyone has some experience there I'm more than happy to get feedback. As a background all our current application & DB server are so far running HPUX, we're just doing test with RH Linux for now. Denis
Continue reading...
Continue reading...