User Tools

Site Tools


FAQ

CentOS: I can not access my site via browser (503 Service Temporarily Unavailable)

Q: My browser fires this error message when opening my sites url:

Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

And in the apache error log the following messages are shown:

[Wed Oct 06 22:10:37 2010] [error] (13)Permission denied: proxy: HTTP: attempt to connect to 127.0.0.1:5000 (127.0.0.1) failed
[Wed Oct 06 22:10:37 2010] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)

A: This behavior is often related with SELinux. You could try to allow network conntects for http:

/usr/sbin/setsebool httpd_can_network_connect 1

SLES: The omd rpm requires php5-sockets and php5-sqlite - I can not find it.

Q: When trying to install the omd rpm package on SLES (e.g. 10 or 11) it requires the packages _php5-sockets_ and _php5-sqlite_ to be installed. How can I solve this?

A: Both packages can be found in the official SDKs of SLES10 and SLES11.

Moving omd to another location than /opt/omd

Q: I can not put omd to /opt/omd - how to put it to another place?

A: The easiest way is to install omd as usual, stop all sites, move /opt/omd to whatever you like, e.g. /usr/local/omd, remove the symlink /omd and create a new symlink /omd pointing to /usr/local/omd. Now you should be able to start your omd installation again.

Ubuntu and Mysql

Q: I get errors on Ubuntu when activating Mysql

A: Mysql cannot be started directly on Ubuntu due to AppArmor restrictions. The cleanest solution is to append the following lines to the file @/etc/apparmor.d/local/usr.sbin.mysqld@:

# START OMD
# Allow mysqld access to config and database files in OMD sites.
/opt/omd/sites/*/.my.cnf       r,
/opt/omd/sites/*/var/mysql/    r,
/opt/omd/sites/*/var/mysql/**  rwk,
/opt/omd/sites/*/tmp/**        rwkl,
/opt/omd/sites/*/tmp/          rw,
# END OMD

Now reload AppArmor using

/etc/init.d/apparmor reload

After that you should be able to activate and start the site specific MySQL instance.