Can't access mediawiki pages after apt-get upgrade

I did an apt-get upgrade on Ubuntu server 10.10 and now the bitnami welcome page displays just fine at http://x.×.×.x/. Anything in http://x.×.×.x/mediawiki gets an HTTP 500 error. So I basically cannot see any pages from the site now except the welcome page. I have a feeling something got upgraded that wasnt supposed to. Is there a way around this issue or do I need to reinstall wordpress?

Hi,

That is strange. Could you try to restart the servers?

$ sudo /opt/bitnami/ctlscript.sh restart

Thanks for your quick response Beltran. Unfortunately that did not work. Here is the output:

bitnami@linux:~$ sudo /opt/bitnami/ctlscript.sh restart
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd stopped
/opt/bitnami/mysql/scripts/ctl.sh : mysql stopped
110322 17:29:17 mysqld_safe Logging to ‘/opt/bitnami/mysql/data/mysqld.log’.
110322 17:29:17 mysqld_safe Starting mysqld.bin daemon with databases from /opt/bitnami/mysql/data
/opt/bitnami/mysql/scripts/ctl.sh : mysql started at port 3306
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80

could you check the /opt/bitnami/apache2/logs/error files?

Thanks for pointing that out. I found the problem.

[Tue Mar 22 15:21:34 2011] [error] [client 172.16.10.18] PHP Warning: require_once(/opt/bitnami/apps/mediawiki/htdocs/extensions/uncPath/uncPath.php) [function.require-once]: failed to open stream: No such file or directory in /opt/bitnami/apps/mediawiki/htdocs/LocalSettings.php on line 139
[Tue Mar 22 15:21:34 2011] [error] [client 172.16.10.18] PHP Fatal error: require_once() [function.require]: Failed opening required ‘/opt/bitnami/apps/mediawiki/htdocs/extensions/uncPath/uncPath.php’ (include_path=‘/opt/bitnami/apps/mediawiki/htdocs:/opt/bitnami/apps/mediawiki/htdocs/includes:/opt/bitnami/apps/mediawiki/htdocs/languages:.:/opt/bitnami/php/lib/php’) in /opt/bitnami/apps/mediawiki/htdocs/LocalSettings.php on line 139

I had added an extension to LocalSettings.php and I didnt have the file it was looking for the the correct location. Once I commented out the extension and restarted the servers everything started working. Thanks again for your help!

I’m glad to hear that :)