Re: Bug#245963: apache-common: Apache doesn't restart after an update
No. The problem is that php4 requires libapache-mod-ssl as a workaround
for a very well known bug. If you disable both php4 and -ssl you will see
that apache works fine.
Fabio
On Mon, 26 Apr 2004, Frederic Massot wrote:
> Package: apache-common
> Version: 1.3.29.0.2-4
> Severity: normal
>
> Hi,
>
> After having updated Apache of version 1.3.29.0.1-3
> towards version 1.3.29.0.2-4, Apache does not restart.
>
> The command "apachectl configtest" does not return any errors.
> The command "/etc/init.d/apache start" return : Starting web server: apache.
> But there is no process of apache ?!
>
> The solution is to install the libapache-mod-ssl (2.8.16-7) packet.
>
> Is necessary it can be to mark libapache-mod_ssl packet of the "Depends" status ?
>
>
> Regards.
>
>
> -- System Information:
> Debian Release: testing/unstable
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.24
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages apache-common depends on:
> ii apache-utils 1.3.29.0.2-4 Utility programs for webservers
> ii debconf 1.4.22 Debian configuration management sy
> ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
> ii libdb4.2 4.2.52-16 Berkeley v4.2 Database Libraries [
> ii libexpat1 1.95.6-8 XML parsing C library - runtime li
> ii mime-support 3.26-1 MIME files 'mime.types' & 'mailcap
> ii perl 5.8.3-3 Larry Wall's Practical Extraction
> ii sed 4.0.9-2 The GNU sed stream editor
> ii ucf 1.02 Update Configuration File: preserv
>
> -- debconf information:
> * apache-common/confignotes:
> apache-common/old-logrotate-exists:
> apache-common/logs:
> apache-shared/debconf-modules: mod_unique_id, mod_status, mod_setenvif, mod_rewrite, mod_negotiation, mod_mime, mod_log_config, mod_info, mod_gzip, mod_expires, mod_encoding, mod_dir, mod_cgi, mod_auth_pgsql, mod_auth_dbm, mod_auth_db, mod_auth, mod_alias, mod_access, libproxy, mod_php4, mod_dav, mod_ssl
> apache-shared/restart: false
>
>
>
--
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.
Reply to: