Re: My First apt-get upgrade casualty - phpmyadmin 'broke'
- From: Joe <joe@xxxxxxxxxxxxxx>
- Date: Thu, 30 Nov 2006 10:34:01 +0000
John Hasler wrote:
Geoffrey R Thompson writes:After updating phpmyadmin, I got a dialog box saying there is a conflict
between my config file and the new one being offered. I selected the
?keep my config file? option ? hoping this would get me through. In
hindsight, I probably should have looked at the differences.
After the upgrade, I started getting ?Internal Server Error? 500 538 when going
to the phpmyadmin page.
dpkg-reconfigure phpmyadmin
I'd be willing to bet that this won't fix it. I don't know what will,
as I didn't have time to try anything beyond the obvious, but there was
an .htaccess issue after an upgrade to phpmyadmin on Sarge. I have
another Sarge installation with phpmyadmin on WMWare, but this didn't
seem to have the problem. The defaults are all still in place on that
version, while the document root is elsewhere on my real server. I have
a feeling that is the cause of the trouble, that someone somewhere
assumed /var/www.
I eventually reinstalled apache after recreating the offending .htaccess
files and reinstalling phpmyadmin didn't help. A nuisance, but still
probably much quicker than trying to find the root cause.
It worked yesterday...
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- References:
- My First apt-get upgrade casualty - phpmyadmin 'broke'
- From: Geoffrey R Thompson
- Re: My First apt-get upgrade casualty - phpmyadmin 'broke'
- From: John Hasler
- My First apt-get upgrade casualty - phpmyadmin 'broke'
- Prev by Date: Re: very short leases from D-Link DI524
- Next by Date: what's the killer app for GNU/Linux systems?
- Previous by thread: Re: My First apt-get upgrade casualty - phpmyadmin 'broke'
- Next by thread: Why is Caudium running?
- Index(es):
Relevant Pages
|
|
