Difference between revisions of "Dev Troubleshooting"

Revision as of 17:22, 2 February 2009

Is your system updated?

Make sure that your system is updated. Dreamwidth code is best supported by Ubuntu Intrepid. To update all your packages, you should be logged in as root and then run:

apt-get update
apt-get upgrade

If you need to upgrade Ubuntu from Hardy to Intrepid, first you will want to edit this file:

vi /etc/apt/sources.list

And replace all instances of "hardy" with "intrepid". The easy vi command for that is:

%s/hardy/intrepid/g

Then, run the two apt-get commands above and do a system restart.

Is your code updated?

There are instructions to update your DW code at Dev Maintenance.

Restarting Apache

Sometimes stopping and restarting Apache can help:

sudo /etc/init.d/apache2 stop
sudo /etc/init.d/apache2 start

Restarting Apache is also needed when you've changed Perl code.

Apache access and error logs

The access and error logs for Apache (the web server) are located at /var/log/apache2/access.log and /var/log/apache2/error.log for a default Ubuntu installation. Loading blank pages are probably the result of mod_perl crashing (often called a "segfault").

You can see the latest access and error messages by using the tail command:

sudo tail /var/log/apache2/error.log

Are there new ljconfig.pl options you are missing?

Check and see if there have been changes, such as additions or removals, to variables in ljconfig.pl. If nothing else, start fresh from the example and re-enter the information from your current config:

mv etc/ljconfig.pl etc/ljconfig.backup
cp doc/ljconfig.pl.txt etc/ljconfig.pl

Apache fails to start

If you've been coding and Apache fails to restart, make sure to check the error logs for the problem:

sudo tail /var/log/apache2/error.log