Apache

After upgrading a Debian install to use PHP 5.4, I ran into the following error:

PHP Warning: Unknown: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in Unknown on line 0

I ran into the following error (or something like it) while setting up Drupal's xmlsitemap module:

public://xmlsitemap/lOtsOfgoBBlDegOOk not found or not writable

This is as expected some kind of permissions issue. Why the module can't sort this on its own, I do not know. As with everything Drupal, clear the cache first to see if that fixes things. It sometimes does. If not, you will need to get your hands dirty on the commandline (if linux):

I've been trying to .. empower .. the Nagios 3 web interface in Ubuntu/Debian to allow me to turn off service checking at will. I do this when I am checking logs etc. to debug some issue and all the spam from Nagios' polling is getting in the way. Nagios comes with an option to "disable active checks of this service" which when click should, well, disable active checks of the service. Clicking it, however, resulted in the following message:

Nagios is currently not checking for external commands.

If you've ever visited a webserver's error page, it will usually state the error followed by information about the server. This will customarily tend to include the webserver software, its version, possibly information about some of the modules compiled in as well as the server's address and port. While this might look generous and helpful, it also allows bad guys as well as other parties to probe the server to find out what it is running as well as other details such as version information. This information can be used for nefarious purposes.

After an upgrade from Lucid to Precise, my PHP install started complaining about a library:

PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/gd.so'

While I've got a hunch that the actual problem is related to issues I had during the upgrade, turning this error (and other similar ones) off is as simple as going into /etc/php5/conf.d and renaming the file, in this case gd.ini to something like gd.ini.bak.

On a server I am working on right now, I installed a PHP application and attempted to run it. However, I ran into a "500 Internal Server Error". Upon further investigation by checking the logs, I found the following errors in the Apache error log:

SoftException in Application.cpp:357: UID of script "/home/foo/public_html/index.php" is smaller than min_uid
Premature end of script headers: index.php

PHP provides a number of different versions for install in Windows. There are versions which are tagged with VC6 and other with VC9. There are also thread-safe and non-thread-safe versions of the installer available for download. After some digging and trial & error fiddlery, my conclusion is that VC9 and non-thread-safe are for the Microsoft IIS webserver while the VC6 and thread-safe installers are for Apache and other non-IIS webservers.

Hope this helps :)

When (re)installing httpd today, I ran into the following error message:
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.
: make_sock: could not bind to address 0.0.0.0:80

While trying to check the vhost configuration on my Kubuntu dev box, I had to run httpd -S. Of course, since ubuntu renamed httpd to apache (a bit like calling a Veyron a Bugatti), I had to run apache2 -S. This however led to the following error message:
apache2: bad user name ${APACHE_RUN_USER}

Server: Apache 2.0.52 + SVN 1.4.3 + mod_dav_svn enabled. Most repositories also use a bunch of post commit hooks to automate tasks.
Client: Eclipse 3.2.2 + stock subclipse callisto install.

Error message:

commit -m "commit message." files
RA layer request failed
svn: Commit failed (details follow):
svn: PROPFIND request failed on '/repo/path/!svn/vcc/default'
svn: PROPFIND of '/repo/path/!svn/vcc/default': Could not read status line: connection was closed by server. (http://example.com)