Your message dated Wed, 23 Aug 2017 20:47:32 +0000
with message-id <e1dkcym-0000qg...@fasolo.debian.org>
and subject line Bug#868150: fixed in up-imapproxy 1.2.8~svn20161210-2+deb9u1
has caused the Debian Bug report #868150,
regarding imapproxy: fails to start
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 ow...@bugs.debian.org
immediately.)
--
868150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imapproxy
Version: 1.2.8~svn20161210-2
Severity: grave
Quack,
The server does not start. Trying to restart it does not change
anything. Here is the systemd status:
----------------------------------------------------------------------------
# systemctl status imapproxy
● imapproxy.service - IMAP proxy
Loaded: loaded (/lib/systemd/system/imapproxy.service; static; vendor
preset: enabled)
Active: inactive (dead)
Docs: man:imapproxyd(8)
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: main(): Internal admin
commands are disabled
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: main(): Allocating 3072 IMAP
connection structures.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: main(): Enabling openssl
library.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: Initialising 1
pthread_mutexes
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ServerInit(): Using
'/var/log/imapproxy_protocol.log' for global protocol logging file.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ServerInit(): proxying to
IMAP server 'localhost'.
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ServerInit(): Proxying to
IMAP port 143
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: ParseBannerAndCapability:
Attempting to parse capability string: * OK [CAPABILITY IMAP4rev1
LITERAL+ SA
Jul 12 14:32:49 Orfeo in.imapproxyd[18803]: [238B blob data]
Jul 12 14:32:49 Orfeo systemd[1]: Started IMAP proxy.
----------------------------------------------------------------------------
The service is marked as "static", which is wrong in this case IIUC.
Interestingly:
----------------------------------------------------------------------------
# systemctl enable imapproxy
Synchronizing state of imapproxy.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable imapproxy
The unit files have no installation config (WantedBy, RequiredBy, Also,
Alias
settings in the [Install] section, and DefaultInstance for template
units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another
unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which
has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path,
timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
----------------------------------------------------------------------------
There is indeed not [Install] section. If I add one with
"WantedBy=multi-user.target" I can enable the service but still it does
not start properly.
But if I use the init script directly it starts fine (and the service
works fine too, so the config is all right):
----------------------------------------------------------------------------
# /etc/init.d/imapproxy start
Starting imapproxy (via systemctl): imapproxy.service.
# /etc/init.d/imapproxy status
● imapproxy.service - IMAP proxy
Loaded: loaded (/lib/systemd/system/imapproxy.service; enabled;
vendor preset: enabled)
Active: active (running) since Wed 2017-07-12 14:40:25 CEST; 2min 37s
ago
Docs: man:imapproxyd(8)
Process: 19772 ExecStart=/usr/sbin/imapproxyd -f /etc/imapproxy.conf
(code=exited, status=0/SUCCESS)
Process: 19766 ExecStartPre=/usr/share/imapproxy/prepare-chroot
(code=exited, status=0/SUCCESS)
Main PID: 19776 (imapproxyd)
Tasks: 2 (limit: 4915)
Memory: 1.6M
CPU: 19ms
CGroup: /system.slice/imapproxy.service
└─19776 /usr/sbin/imapproxyd -f /etc/imapproxy.conf
Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: ServerInit(): proxying to
IMAP server 'localhost'.
Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: ServerInit(): Proxying to
IMAP port 143
Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: ParseBannerAndCapability:
Attempting to parse capability string: * OK [CAPABILITY IMAP4rev1 …cot
ready.
Jul 12 14:40:25 Orfeo in.imapproxyd[19772]: [238B blob data]
Jul 12 14:40:25 Orfeo systemd[1]: Started IMAP proxy.
Jul 12 14:40:25 Orfeo in.imapproxyd[19776]: BecomeNonRoot(): Process
will run as uid 65534 (nobody) and gid 65534 (nogroup).
Jul 12 14:40:25 Orfeo in.imapproxyd[19776]: BecomeNonRoot(): Process
chrooted in /var/lib/imapproxy/chroot
Jul 12 14:40:25 Orfeo in.imapproxyd[19776]: BecomeNonRoot(): enabled
no_new_privs
Jul 12 14:40:25 Orfeo in.imapproxyd[19776]: main(): Launched ICC recycle
thread with id 140509281154816
Jul 12 14:40:25 Orfeo in.imapproxyd[19776]: main(): imapproxy version
1.2.8 [SVN] normal server startup.
Hint: Some lines were ellipsized, use -l to show in full.
----------------------------------------------------------------------------
In the end, with the following patch it works fine:
----------------------------------------------------------------------------
--- imapproxy.service.orig 2017-07-12 14:57:35.000000000 +0200
+++ /lib/systemd/system/imapproxy.service 2017-07-12
14:50:15.000000000 +0200
@@ -8,3 +8,8 @@
Type=forking
ExecStartPre=/usr/share/imapproxy/prepare-chroot
ExecStart=/usr/sbin/imapproxyd -f /etc/imapproxy.conf
+PIDFile=/run/imapproxy.pid
+
+[Install]
+WantedBy=multi-user.target
+
----------------------------------------------------------------------------
Regards.
--
Marc Dequènes
--- End Message ---
--- Begin Message ---
Source: up-imapproxy
Source-Version: 1.2.8~svn20161210-2+deb9u1
We believe that the bug you reported is fixed in the latest version of
up-imapproxy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Richard Laager <rlaa...@wiktel.com> (supplier of updated up-imapproxy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 07 Aug 2017 23:58:28 -0500
Source: up-imapproxy
Binary: imapproxy
Architecture: source amd64
Version: 1.2.8~svn20161210-2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Richard Laager <rlaa...@wiktel.com>
Changed-By: Richard Laager <rlaa...@wiktel.com>
Description:
imapproxy - IMAP protocol proxy
Closes: 868150
Changes:
up-imapproxy (1.2.8~svn20161210-2+deb9u1) stretch; urgency=medium
.
* Correct the service file.
Thanks to Marc Dequènes (Duck) (Closes: 868150)
* Move the pidfile to /run
Checksums-Sha1:
e7506f75b8c227831add426a8858c4b1513388b3 2168
up-imapproxy_1.2.8~svn20161210-2+deb9u1.dsc
b289f26c9b2544d10708af826d78e1d7bb306fa6 28500
up-imapproxy_1.2.8~svn20161210-2+deb9u1.debian.tar.xz
22663157fa7569b0325e1018523ae75683a8b1b7 96314
imapproxy-dbgsym_1.2.8~svn20161210-2+deb9u1_amd64.deb
c6af866ac7b77e56244603757be3934faac3b8e6 59930
imapproxy_1.2.8~svn20161210-2+deb9u1_amd64.deb
e0af1f400f0fbf4a9e52d6890c2068a45e222b92 6154
up-imapproxy_1.2.8~svn20161210-2+deb9u1_amd64.buildinfo
Checksums-Sha256:
3f0ae44a9ac0e8edf48cc805885028e372abb84091826287eb2844460f7d2229 2168
up-imapproxy_1.2.8~svn20161210-2+deb9u1.dsc
a80aa4dda03aa9a0c6f63099d0a6e9f2a82db74c89d714657839568678e3a9ff 28500
up-imapproxy_1.2.8~svn20161210-2+deb9u1.debian.tar.xz
5e1a22fa41939088a60ec92965bd3ecb5480c750707cce82b4389eae0e760395 96314
imapproxy-dbgsym_1.2.8~svn20161210-2+deb9u1_amd64.deb
511eaf30069c463635b736f90783c474abce6eeaedbcb98708acf974783afaf0 59930
imapproxy_1.2.8~svn20161210-2+deb9u1_amd64.deb
8aa3c3075d5888279790f6db05a3a7a629dc4a0e9f03c3a51c1ea28da7cfb18a 6154
up-imapproxy_1.2.8~svn20161210-2+deb9u1_amd64.buildinfo
Files:
5eec7fbdfcd2b468357813a23971e49e 2168 mail optional
up-imapproxy_1.2.8~svn20161210-2+deb9u1.dsc
ed81ac16812f65ad1ea0fa25ee4bf209 28500 mail optional
up-imapproxy_1.2.8~svn20161210-2+deb9u1.debian.tar.xz
ad677e51509a7becc5c5b8c45b43bb7c 96314 debug extra
imapproxy-dbgsym_1.2.8~svn20161210-2+deb9u1_amd64.deb
67a1e10dc39312a199acb777d820e423 59930 mail optional
imapproxy_1.2.8~svn20161210-2+deb9u1_amd64.deb
8e3fe1dd99275201610eeb59d657840a 6154 mail optional
up-imapproxy_1.2.8~svn20161210-2+deb9u1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlmSf3MUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpYoGRAAryrB+5otTiAlz9uzO9PJ85K4KLNR
B/tk/hT3mVQ/CwxEKEtSOxkvlK0WK9FrRQqSGH4SDoh9qA3wutxn7j2pYhNXXARh
FhON6VCrwo5QnFS5NE3cslpouz9yWwlAg4YFlo56+qX4rtGe2uwY7oyp6KPjqkqs
z58//k8K1meTyyZYbLLcaimP6QihhBe6LCDlEYAobD6uuF4zN5OLU3ezEGn5iYgt
E1FbB6qVROMizzfroWDUQKwNES+sZdv2Apqr2nm2Kw70PqgdigHJlcSY12P8pU/p
kCliBfcqUaa6WsATuzsrn1qhUJel3WoiANHe6/XD55j8azGnZHgu8uSL75Vmc1JB
0WDgucEzywvOJif0HqkVPe6wqV7CLe/r4eMFdnZPiWqevltf8Qb245cOws14QEu3
dVfQuUozX+UmfU2LS74HwrkA8k3GzQqlZ1V52y7TYsZU+rYSkzEazM+cIyBkWLxi
mGtOQUYN5goXN09CO+9AAXa0xfdQfkk1/pe2hUR/3enipVwgl+wYuPyEIelEvUAX
PknnFWSEVZyZl8pAdiBg5vmvi2936zdYCVSQd6o5XWuKOS6t41J3iQ487H6Mr7fO
TdGwqWiZbQRmzQtS5RI4pBV3dCv1/AFNUg9EN+A0HL8yNYK58/SFyHS2d4AQJQGt
Chb96l6OxEbnqXE=
=cifZ
-----END PGP SIGNATURE-----
--- End Message ---
