Your message dated Mon, 17 Jul 2017 03:04:39 +0000
with message-id <e1dwwkt-00023p...@fasolo.debian.org>
and subject line Bug#868150: fixed in up-imapproxy 1.2.8~svn20161210-3
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-3
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: Thu, 13 Jul 2017 21:02:35 -0500
Source: up-imapproxy
Binary: imapproxy
Architecture: source amd64
Version: 1.2.8~svn20161210-3
Distribution: unstable
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-3) unstable; urgency=medium
.
* Correct the service file.
Thanks to Marc Dequènes (Duck) (Closes: 868150)
* Move the pidfile to /run
Checksums-Sha1:
278979e14ba22b641f88ec3b141d2779b1e9c270 2140
up-imapproxy_1.2.8~svn20161210-3.dsc
98232872d06c5173d9474895a658cb35fb52905b 28448
up-imapproxy_1.2.8~svn20161210-3.debian.tar.xz
71f697ed7194f7bb1686b18e5e6daeeb51a80aa7 96266
imapproxy-dbgsym_1.2.8~svn20161210-3_amd64.deb
728b4cc3c72d37eb5e7cf2e9bd5383c6f5c9327b 59916
imapproxy_1.2.8~svn20161210-3_amd64.deb
6726778ac581d59298410129ef88764799272fe2 5856
up-imapproxy_1.2.8~svn20161210-3_amd64.buildinfo
Checksums-Sha256:
5dca0f8867a81beb53eb2332481b00c30f5d0077bbf542315240bb18a8d06053 2140
up-imapproxy_1.2.8~svn20161210-3.dsc
92e3e42e1124cd3b8cf87fd57addb84ba4136585b365f65cd6c1b18fcd80f0ba 28448
up-imapproxy_1.2.8~svn20161210-3.debian.tar.xz
a0777307cbda6fbca5c3cc6840e760e5d552082bd1eb74c89fe571e73f4509a8 96266
imapproxy-dbgsym_1.2.8~svn20161210-3_amd64.deb
039d14786c3377b1d472ac1f5f45af33d4b1b11b385c2ff76a0930d934b3293b 59916
imapproxy_1.2.8~svn20161210-3_amd64.deb
c69614df5b6cd402fa01421f1e7a22b770c407555a96edf0e0bb02ba33072b83 5856
up-imapproxy_1.2.8~svn20161210-3_amd64.buildinfo
Files:
03e798827d111e3c19a8e9507fa169ca 2140 mail optional
up-imapproxy_1.2.8~svn20161210-3.dsc
2e1ae29b6b0821d5ca5c505398c9dc07 28448 mail optional
up-imapproxy_1.2.8~svn20161210-3.debian.tar.xz
7fa9ff9734886d1c01ace79dc32b6495 96266 debug extra
imapproxy-dbgsym_1.2.8~svn20161210-3_amd64.deb
2a2fd7481c3f450d2fc63eaef0febd22 59916 mail optional
imapproxy_1.2.8~svn20161210-3_amd64.deb
84c61db0df49bc77ebc10f2180ff8d28 5856 mail optional
up-imapproxy_1.2.8~svn20161210-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAllsJOMUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbW9Q/8C/AnmCNiz6ASQX1Ggfrv1RIu3/SC
F7jjkNXaD/GjK6krHRpbABa8CMlNs4dnMmKaflTB2yXuX9CG94hqViVjpoM83fm4
5k7JqbJLZLpQYMUfI56qrQMDdImNVRvF46auntnycsysjJzMkHfXebshpybZkCkp
lnPFm+/F6AYoNezS3b+agvKrTyUu4EHtAymJ2tQofYy1N73su47jmMZFG8huvinU
7FTnlyTJSawKihMyMjMAUglOIsLN7s9lYJAwX+U/Yz4hpaPP8n/C56XJWbUaGSGj
JK1UN3PelyOttHwpoA/OV9i3LVkUA90P+fS7Muf2sHzzYNspgeGe/f+/9ZYMBVJa
TzZVOoCcs8pXD+ODpCjRuHYnzhtxc3G3JufhPQ4t+hELeC4K9wqkCOAzIS1NTa0S
FPiKFQxtXUwk7uoWxs7r6L7pWQuelLs18l3fYFy/Ctpm3uSjNWRjLPQu+mI+XYU4
ZisZzfzkqREzNPRB0pWfm4kgFd8fYY00uEtEB9D+aKdUixMI+WGewFooSskRvOSG
P7Ke8//kNfDptNGvtL+k6ct7Wg1dPBmeMaJ1eyAIjnKb65fedCV0GHOw/zw4rNxL
elRfid+RCk2HT0kouRbrj/fIo0hzldLxMg8bowCUzVToYuoX9AjPewClz/8haGQ8
vpp+CflMNXR5yhI=
=pBjJ
-----END PGP SIGNATURE-----
--- End Message ---
