Your message dated Tue, 02 Feb 2010 02:43:33 +0100
with message-id <[email protected]>
and subject line Re: portsentry: possible incorrect dependency on init script
has caused the Debian Bug report #567450,
regarding portsentry: possible incorrect dependency on init script
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
567450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567450
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: portsentry
Version: 1.2-12
Severity: important
User: [email protected]
Usertags: incorrect-dependency
Hi,
portsentry has a dependency on $all which in 99% of the cases is incorrect.
By depending on $all, no other init script can depend on portsentry, possibly
preventing the other script from working properly.
Please fix the dependencies.
P.S. this is a release goal and should be fixed ASAP.
Regards,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--- End Message ---
--- Begin Message ---
Hi Raphael,
I'm closing this bug because I consider 'portsentry' software should start as
latest as possible.
All services should be already started before 'portsentry' starts, if not,
their will not be able to
bind on their respective ports.
As an example:
(DESIDERED BEHAVIOUR)
By configuring 'portsentry' to monitor 80/tcp and starting the latest as
possible, you'll get an
error message in the logfile and the process continues binding on other
configured ports ports.
[snip]
Feb 2 02:19:49 host portsentry[10315]: adminalert: Going into listen mode on
TCP port: 79
Feb 2 02:19:49 host portsentry[10315]: adminalert: Going into listen mode on
TCP port: 80
Feb 2 02:19:49 host portsentry[10315]: adminalert: ERROR: could not bind TCP
socket: 80. Attempting
to continue
Feb 2 02:19:49 host portsentry[10315]: adminalert: Going into listen mode on
TCP port: 119
Feb 2 02:19:49 host portsentry[10315]: adminalert: Going into listen mode on
TCP port: 143
Feb 2 02:19:49 host portsentry[10315]: adminalert: ERROR: could not bind TCP
socket: 143.
Attempting to continue
Feb 2 02:19:49 host portsentry[10315]: adminalert: Going into listen mode on
TCP port: 540
Feb 2 02:19:49 host portsentry[10315]: adminalert: Going into listen mode on
TCP port: 635
[snip]
(UNDESIDERED BEHAVIOUR)
by configuring 'portsentry' to monitor 80/tcp and starting before apache, will
not let apache to
bind on port 80/tcp producing this message:
[snip]
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
[snip]
Please, feel free to reopen it if you have another perspective.
Cheers.
--
Dario Minnucci <[email protected]>
Phone: +34 902021030 | Fax: +34 902024417 | Support: +34 807450000
Key fingerprint = 62FF F60F CE79 9CE4 EBA8 523F FC84 1B2D 82C8 B711
signature.asc
Description: OpenPGP digital signature
--- End Message ---
