I noticed this error during a deployment of numerous servers that were configured with litespeed, postgreSQL, and ruby. The installation process was to install ruby, install ruby gems, install postgreSQL, install litespeed, and then sync up the web directory using SVN. After doing so connect via a browser to the server to test things out. On one server I was getting a “503 Service Unavailable” error. The lshttpd(litespeed) logs looked like the below example.
You might see this error when attempting to install various packages or gems on CentOS Linux. I noticed it when attempting to install the ruby gem named eventmachine. After installing one RPM package via yum I no longer received the error when attempting to install the eventmachine gem.
PostgreSQL authentication can be controlled using the pg_hba.conf file to specify what IP addresses have access to the postgres database. After making changes to this file you should never reboot the server but instead signal it to reload this configuration file. Follow the below steps to reload.
This article will assist in removing any annoying User Agent displaying for Windows Internet Explorer.
You are probably curious what this is after you saw it in some web logs of some sort. It is likely from a legitimate application you have installed as some form of add-on to Internet Explorer. I did a bunch of reading trying to find out exactly how it got there but ended up concluding that it could have been any number of third party add-ons I have added to IE. So anyhow then I decided I did not want it showing up as my User Agent so I attempted to remove it following the steps below.
Cacti is an open source tool that polls network devices and provides a web based interface to view historical data about these devices. It is a really great tool to monitor disk usage, network traffic, and pretty much anything else you can think of. When installing cacti it is easy to forget about the log that cacti generates and over time the log can grow in size especially if your configuration includes a logging level of DEBUG. Below I describe how to rotate the cacti log as well as turn down the logging level to LOW on a CentOS 5 server.
First lets set up logrotate to rotate the cacti log.
1. Install logrotate: yum install logrotate
2. Create Cacti config: vi /etc/logrotate.d/cacti
Add the below contents to the new file
# keep two weeks of versions online
# rotate the log each day
# compress the logs
# create new file with the correct user/group attributes
create 644 cactiuser cactiuser
# add a YYYYMMDD extension instead of a number
Make sure the path is the correct location for your cacti.log file.
3. Run logrotate: logrotate -f /etc/logrotate.conf