Your message dated Sat, 18 Dec 2010 10:32:56 +0100
with message-id <[email protected]>
and subject line Re: Bug#607261: Bug fixed?
has caused the Debian Bug report #607261,
regarding Conflict between AF_INET and AF_INET6 sockets with 
net.ipv6.bindv6only=0
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.)


-- 
607261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607261
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: prayer: fails to start if no IPv6 Routers present
Package: prayer
Version: 1.3.3-dfsg1-2
Severity: normal

*** Please type your report below this line ***

after installing a new debian squeeze system, prayer fails to start with this error message:
> > #/etc/init.d/prayer start
  Error was: [os_bind_inet_socket()] bind() failed: Address already in use
Aborted
 failed!

but according to netstat, the http and https ports are free.

Config in /etc/prayer/prayer.cf
> use_http_port       80
> use_https_port      443

a deep inspection shows that the problem is that no IPv6 Routers are (in my environment) present.

So the prayer was not able to bring the IPv6 Ports up.

As a lot of people have an "only IPv4 LAN", this error is hard to find.

Solution:
In the prayer.cf add after:
# Define a single HTTP port to bind to:
#
# You can define an arbitary list of ports of both kinds by using a series
# of separate "use_http_port" and "use_https_port" directives, with one
# port on each line. Format: "interface:port" or "ipaddr:port" to bind to a
# single interface, "port" to bind to all interfaces.

The lines:
# If you bind to all interfaces, prayer will bind to IPv6 and IPv4
# parallel and fails if one of this is not present. If you have
# only IPv4 (or only IPv6), you should use # the "ipaddr:port"
# format.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages prayer depends on:
ii  adduser                 3.112+nmu2       add and remove users and groups
ii  libc-client2007e        8:2007e~dfsg-3.1 c-client library for mail protocol
ii  libc6                   2.11.2-7         Embedded GNU C Library: Shared lib
ii  libdb4.8                4.8.30-2         Berkeley v4.8 Database Libraries [
ii  libldap-2.4-2           2.4.23-7         OpenLDAP libraries
ii  libssl0.9.8             0.9.8o-3         SSL shared libraries
ii  libtidy-0.99-0          20091223cvs-1    HTML syntax checker and reformatte
ii  logrotate               3.7.8-6          Log rotation utility
ii  nullmailer [mail-transp 1:1.04-1.2       simple relay-only mail transport a
ii  ssl-cert                1.0.26           simple debconf wrapper for OpenSSL
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime
prayer recommends no packages.

Versions of packages prayer suggests:
ii  aspell                        0.60.6-4   GNU Aspell spell-checker
pn  imap-server                   <none>     (no description available)
ii  ispell                        3.1.20.0-7 International Ispell (an interacti
pn  prayer-accountd               <none>     (no description available)
pn  prayer-templates-src          <none>     (no description available)

-- Configuration Files:
/etc/default/prayer changed [not included]
/etc/prayer/prayer.cf changed [not included]




--- End Message ---
--- Begin Message ---
Version: 1.3.3-dfsg1-3

On fredagen den 17 december 2010, you stated the following:
> Hi!
> 
> This bug was marked pending with the 1.3.3-dfsg1-3 upload, which has
> been uploaded in the meantime.  But without the corepsonding closes
> entry in it's changelog.
> 
> However, the changelog reads, like the needed patch was applied.
> 
> Could you please check, wether this bug is closed and mark this bug
> fixed (please don't forget the version header) or remove the pending
> tag (and comment)?

Oops. Evidently I forgot to rebuild the package after I added the closes entry 
and checked in the change in SVN, but the patch is there.

-- 
Magnus Holmgren        [email protected]
Debian Developer 

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to