Unfortunately, that's not the solution to my problem, but thanks for the answer.

is the php header on the page correct ?

I'm not sure what you mean by "php header".

Maybe this one from the phpmyadmin index.php:

But it also doesn't work if I change this to:

You could install this

Oddly I had a similar problem upgrading. I am currently using php4, when upgrading sarg to etch, apt decided to install the apache2 module for php5. I simply apt'ed the right one and it behaved nicely after that. This was on a Alpha box if that makes a difference.

Could it be a problem on ubuntu?
Could it be that you should open a new thread in ubuntu ?

What do you mean by "right one"? php4 again?

In the meantime I did so. But I haven't gotten a helpful answer yet, so I still appreciate your help. :-)

Another removal/installation of the phpmyadmin-package did the job. Furthermore I remove the directory /usr/share/phpmyadmin/ by hand in between. Maybe that was the point. Anyway: Thank's for your help.

I guess I'm late, but some people may have such problem like I had before.

in order to run apache2 you should use the following command:

In Debian you can't run it just like on ubuntu by issuing /etc/init.d/apache2 start.

For some reason it s different in apach2 for Debian.

They also have changed httpd.conf name to apache2.conf

If you have apache2.conf, you should comment the entry for httpd.conf if it exists.

I don't think so. I've always started it this way. I'm having that problem now that I've bootstraped a new system. I must be missing a package of some sort that debootstrap didn't install

Farslayer: I know I'm way late on the thread, but thank you for post #13! I have been browsing the web for 30 minutes looking for exactly this:

That's the one thing that was not mentioned on the dozen or so sites I went to. After recently getting Apache working (again) on my machine, I didn't realize my modules got fouled in the reconfig until my wife tried getting to her webmail account.

Thanks again!

CJ

Go back to Post #6 and reread that...

You have to edit a variable in the file /etc/default/apache2.
This file's comment is misleading -- it says "on boot" when it means "when invoked by /etc/init.d/apache2 script" (which usually is on bootup/shutdown). When NO_START=1, Apache will not start unless manually invoked via apache2ctl. No amount of /etc/init/apache2 start | restart will touch it until "NO_START=0", like mine.

Also, I disagree: You should not comment the entry for httpd.conf. I'm no expert, but I gather that the reason for its being there is to make it easier to enact user (err, administrator -- as opposed to Apache developer) modifications to the way Apache runs. The apache2.conf file is big and heavily commented, and there's nothing wrong with editing it when necessary, but when all you need to do is one quick little thing like add PHP support (perhaps temporarily, to test, see if it will work), it's a lot easier to do it in a smaller file (e.g. httpd.conf) where it's much easier to find your modifications and distinguish them from the configurations provided by the package maintainers.

I can see your viewpoint, however, and I also agree with it -- sometimes it's easier just to edit one great big huge file, so that you can keep everything together and you know where it all is (e.g., did I make the PHP enablement in apache2.conf, httpd.conf, or in one of my (God knows how many) sites-available/* files?)... However, for me, that's like keeping all of my clothes in one great big drawer in my dresser; No matter how well I fold them (commenting, dividing a file) I still wind up with a bunch of stuff in one location that's hard to go through to get what I want out of it. I see apache2.conf as being intended for overall webserver config, httpd.conf as being for this-system's-administrator's-changes, and the various files in sites-available as being for website-specific alterations. If you want per-directory stuff, keep it in .htaccess.




Anywhoo, hope this helps. Cheers!

I just upgraded debian using dist-upgrade. Then Apache is not working. Any idea?

I tried $/etc/init.d/apache start or $apache2ctl start
It just say starting.

Then, I tried $ps -aux | grep httpd

shows nothing. So apache is not running