[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Apache2/PHP7 fails in Buster



On Thu, Jan 16, 2020 at 05:29:44PM +0000, Tony van der Hoff wrote:
> On 16/01/2020 16:39, Roberto C. Sánchez wrote:
> > On Thu, Jan 16, 2020 at 03:55:46PM +0000, Tony van der Hoff wrote:
> > > 
> > > 
> > > On 16/01/2020 15:11, Roberto C. Sánchez wrote:
> > > > > 
> > > > Can you send me (directly) the files from that system named
> > > > '/var/lib/dpkg/info/libapache2-mod-php7.3*'?
> > > 
> > > Apparently not:
> > > 
> > > 
> > > <roberto@debian.org>: host mailly.debian.org[82.195.75.114] said: 550 HELO
> > >      mismatch Forged HELO for (shell.localdomain) (in reply to RCPT TO
> > > command)
> > > 
> > That's bizzare.  I've been receiving other mail at this address, so I
> > wonder if it might be an issue on your side.
> > 
> It may well be. However this Postfix server has been running for many years,
> and I've not had any such occurrence. But that's not important right now.
> 
> > > archive attached
> > 
> > Hmm.  I thought the list might reject that, but it seems I was mistaken.
> > 
> > Either way, your postinst script seems fine.
> > 
> > My recommendation is to edit libapache2-mod-php7.3.postinst to add on a
> > new line after 'set -e': set -x
> > 
> > That will make bash trace the execution to the console.
> > 
> > After you have added that 'set -x' then: sudo dpkg --pending --configure
> > 
> > That should leave your terminal output right near the point in the
> > script where it is erroring out.  If you still have questions at that
> > point then post the output of the dpkg command.
> > 
> 
> OK, fine, thanks. I'm afraid my bash-fu is a little rusty, so I'd appreciate
> you taking a look.

+ a2enmod -m -q php7.3
+ return 1
+ exit 1

Well, it seems it's failing because it tries to enable the php7.3
module -- which it can't do, because the module's not THERE.

If it were me, I would attempt to purge this package (not just remove),
and then reinstall it.

If purging fails because of a2enmod being unable to find the module
and manipulate it in various ways, then it might be necessary to
short-circuit the prerm/postinst/etc. scripts so that they do nothing,
just so you can purge everything.

The normal way to do that with a prerm or postinst script is to stick
"exit 0" near the top of it.


Reply to: