C
cverbiest
Guest
Found the trigger for the issue and a solution. The database is started using a script that basically does sudo -u proadmin proserve LISA sudo -u proadmin probiw LISA sudo -u proadmin proapw LISA sudo -u proadmin proapw LISA if someone logs on to the system with user proadmin using ssh, and executes proshut LISA -C list the semaphore errors occur when that user logs off. As long as the proadmin user does not log off the db stays up & running. On our test server the issue went away with a yum update
Continue reading...
Continue reading...