In a master-slave replication environment, what is required to automatically promote the slave as the master if the master goes down. What are common practice used to change the database reference from an application if the heartbeat of the master database is not detected?
Do I need a cluster to achieve this or is simple 2 machine environment sufficient?
Selinux is currently installed on the machine but there's no simple way to enable and modify RBAC for users. Seedit is available for Fedora and CentOS but it is not working on Ubuntu distros.
Are there any other RBAC solutions that are supported on Ubuntu/Debian with tools like Seedit to modify the policies. SEAdmin does not work in Ubuntu 10.04
Due to compliance issues, there is a need to store all tomcat logs for at least 6 months on a central server.
Is there a way to send the logs to rsyslog server or any other mechanism that will accomplish the task. I tried changing CATALINA_OUT to /var/log/syslog, and it does record it in the file however rsyslog-mysql does not pick it up.
Short of sending the logs to a remote host, what are some ways to move the logs automatically besides using rsync, cron, scp