Your message dated Tue, 30 May 2006 00:39:27 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [Fwd: Re: Bug#369020: imapproxy: grepping the
/proc/PID/cmdline causes startup to fail]
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: imapproxy
Version: 1.2.4-4
Severity: important
installing this for the first time, this message came up
Selecting previously deselected package imapproxy.
(Reading database ... 72772 files and directories currently installed.)
Unpacking imapproxy (from .../imapproxy_1.2.4-4_i386.deb) ...
Setting up imapproxy (1.2.4-4) ...
Starting IMAP proxy: grep: /proc/6370/cmdline: No such file or directory
Failed to start imapproxy. Check logs for details.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages imapproxy depends on:
ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy
ii libc6 2.3.6-9 GNU C Library: Shared libraries
ii libncurses5 5.5-2 Shared libraries for terminal hand
ii libssl0.9.8 0.9.8b-2 SSL shared libraries
ii libwrap0 7.6.dbs-9 Wietse Venema's TCP wrappers libra
imapproxy recommends no packages.
-- debconf information:
* imapproxy/imap-server: mail
--- End Message ---
--- Begin Message ---
Portsentry was making imapproxyd unable to start and thus the startup
sequence could not be completed.
-------- Original Message --------
Subject: Re: Bug#369020: imapproxy: grepping the /proc/PID/cmdline
causes startup to fail
Date: Mon, 29 May 2006 14:11:05 -0500
From: Good Times <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
hi
i think i found the problem
i have portsentry installed, and since i had no imap server running before, it
was listening there
i stopped portsentry, then started imapproxy without issue, then restarted
portsentry
aaron
--
was the narrow way there
in our midst
all along
-Mercury Rev
On Fri, May 26, 2006 at 07:01:00PM -0500, [EMAIL PROTECTED] wrote:
> what other info could I send?
>
> aaron
>
> -----Original Message-----
> From: =?ISO-8859-1?Q?Jos=E9_Luis_Tall=F3n?= <[EMAIL PROTECTED]>
> Date: Friday, May 26, 2006 5:48 pm
> Subject: Re: Bug#369020: imapproxy: grepping the /proc/PID/cmdline causes
> startup to fail
>
> tags 369020 unreproducible moreinfo
> severity 369020 normal
> quit
>
> Good Times wrote:
> Package: imapproxy
> Version: 1.2.4-4
> Severity: important
>
> Hi!
>
> > installing this for the first time, this message came up
>
> > Selecting previously deselected package imapproxy.
> (Reading database ... 72772 files and directories currently installed.)
> Unpacking imapproxy (from .../imapproxy_1.2.4-4_i386.deb) ...
> Setting up imapproxy (1.2.4-4) ...
> Starting IMAP proxy: grep: /proc/6370/cmdline: No such file or directory
> Failed to start imapproxy. Check logs for details.
>
> The grep is only intended to check whether imapproxy actually started or not.
> That means that something made start-stop-daemon or imapproxy itself
> fail to start.
>
> My guess: the supplied imap server address (`mail') as per the debconf
> information below does NOT resolve. This would make imapproxy fail to start
> and hence cause the behaviour you describe.
>
> Is DNS resolution working properly? What does "ping mail" say in your
> installation?
> Is there a running (and accesible) IMAP server at `mail'?
> Is there something preventing IMAPproxy to start (say some other process
> listening at the same port) ?
> -- System Information:
> Debian Release: testing/unstable
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'stable')
> Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.7
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
>
> > Versions of packages imapproxy depends on:
> ii debconf [debconf-2.0] 1.5.1 Debian configuration management
> sy
> ii libc6 2.3.6-9 GNU C Library: Shared libraries
> ii libncurses5 5.5-2 Shared libraries for terminal
> hand
> ii libssl0.9.8 0.9.8b-2 SSL shared libraries
> ii libwrap0 7.6.dbs-9 Wietse Venema's TCP wrappers
> libra
>
> > imapproxy recommends no packages.
>
> Seems ok.
> -- debconf information:
> * imapproxy/imap-server: mail
>
> ^^^^^^^^^^^^^^^^^^
>
>
>
> J.L.
>
>
>
--- End Message ---
