Bug#979710: xfonts-bolkhov-75dpi: Missing Cyrillic letter 'u'
Hello. I confirm the existance of this bug in 1.1.20001007-8.1, in particular for xfonts-bolkhov-misc package. Rollback to 1.1.20001007-8 fixes the issue. -- Eugene Berdnikov
Bug#979965: milter-greylist exits after running for a few minutes
Package: milter-greylist
Version: 4.6.2-2
Severity: important
Dear Maintainer,
After update to 4.6.2-2, milter-greylist runs for a few minutes
processing greylist requests then exits. No error in the daemon.log.
Daemon restarts with systemd over and over.
Starting milter-greylist by hand using strace shows this just before
it dies:
poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 1 ([{fd=3,
revents=POLLIN}])
accept(3, {sa_family=AF_UNIX}, [2]) = 10
fcntl(10, F_GETFD) = 0
fcntl(10, F_SETFD, FD_CLOEXEC) = 0
setsockopt(10, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
futex(0x7f0f22c221a4, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000 ) = ?
+++ exited with 71 +++
Previous version of milter-greylist on debian/testing was working fine
without this issue.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (750, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.6-x86_64-linode139 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages milter-greylist depends on:
ii adduser 3.118
ii init-system-helpers 1.60
ii libc62.31-6
ii libcurl4 7.74.0-1
ii libgeoip11.6.12-7
ii libmilter1.0.1 8.15.2-20
ii libopendkim112.11.0~beta2-4
ii libspf2-21.2.10-7+b7
ii lsb-base 11.1.0
Versions of packages milter-greylist recommends:
ii sendmail 8.15.2-20
milter-greylist suggests no packages.
-- Configuration Files:
/etc/default/milter-greylist changed [not included]
/etc/milter-greylist/greylist.conf changed [not included]
-- no debconf information
Bug#979965: milter-greylist exits after running for a few minutes
On 2021-01-12, Michael Grant wrote:
> After update to 4.6.2-2, milter-greylist runs for a few minutes
> processing greylist requests then exits. No error in the daemon.log.
> Daemon restarts with systemd over and over.
>
> Starting milter-greylist by hand using strace shows this just before
> it dies:
>
> poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 1 ([{fd=3,
> revents=POLLIN}])
> accept(3, {sa_family=AF_UNIX}, [2]) = 10
> fcntl(10, F_GETFD) = 0
> fcntl(10, F_SETFD, FD_CLOEXEC) = 0
> setsockopt(10, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
> futex(0x7f0f22c221a4, FUTEX_WAKE_PRIVATE, 1) = 1
> poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000 ) = ?
> +++ exited with 71 +++
>
> Previous version of milter-greylist on debian/testing was working fine
> without this issue.
Could you try running without the systemd .service file so that it falls
back to the init script; there may be differences between how the
.service file and the init script set up the environment to run it.
If that doesn't help, could you try rebuilding the previous version with
a current sid build environment and seeing if that is still affected?
There aren't many changes to the actual code or packaging, and my fear
is it might be changes in the toolchain used to build it since the
previous version.
live well,
vagrant
signature.asc
Description: PGP signature
Bug#979965: milter-greylist exits after running for a few minutes
Hi Michael,
On Tue, Jan 12, 2021 at 5:54 PM Vagrant Cascadian wrote:
>
> On 2021-01-12, Michael Grant wrote:
> > After update to 4.6.2-2, milter-greylist runs for a few minutes
> > processing greylist requests then exits. No error in the daemon.log.
> > Daemon restarts with systemd over and over.
> >
> > Starting milter-greylist by hand using strace shows this just before
> > it dies:
> >
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 1 ([{fd=3,
> > revents=POLLIN}])
> > accept(3, {sa_family=AF_UNIX}, [2]) = 10
> > fcntl(10, F_GETFD) = 0
> > fcntl(10, F_SETFD, FD_CLOEXEC) = 0
> > setsockopt(10, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
> > futex(0x7f0f22c221a4, FUTEX_WAKE_PRIVATE, 1) = 1
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000 ) = ?
> > +++ exited with 71 +++
> >
> > Previous version of milter-greylist on debian/testing was working fine
> > without this issue.
>
> Could you try running without the systemd .service file so that it falls
> back to the init script; there may be differences between how the
> .service file and the init script set up the environment to run it.
Can you also modify /lib/systemd/system/milter-greylist.service and
change the [Service] section to the following and test please..
[Service]
Type=forking
ExecStart=/usr/sbin/milter-greylist
Restart=on-failure
PrivateTmp=true
--
Regards
Sudip
Bug#979965: milter-greylist exits after running for a few minutes
On Tue, Jan 12, 2021 at 9:36 PM Michael Grant wrote: > > I have made this change: > > > > [Service] > > Type=forking > > ExecStart=/usr/sbin/milter-greylist > > Restart=on-failure > > PrivateTmp=true > > > > And it’s still restarting every few minutes: > > > > Jan 12 16:09:43 strange milter-greylist[255358]: racl 277 greylist [delay > 300] [aw 3888000] [maxpeek -1] default > > Jan 12 16:09:43 strange systemd[1]: Started Greylist Mail Filter Daemon. > > Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Main process > exited, code=exited, status=71/OSERR > > Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Failed with > result 'exit-code'. > > Jan 12 16:30:44 strange systemd[1]: milter-greylist.service: Scheduled > restart job, restart counter is at 2. > > Jan 12 16:30:44 strange systemd[1]: Stopped Greylist Mail Filter Daemon. > > Jan 12 16:30:44 strange systemd[1]: Starting Greylist Mail Filter Daemon... > > > > I just noticed it says ‘Scheduled restart job’, is that because it exits? Or > is that because some timer is killing it? I think its restarting because the service file has "Restart=on-failure". and since the main process is exiting with error systemd thinks the service has failed and so it restarts. To reproduce the error, do I just run milter-greylist with a greylist.conf and Sendmail/Postfix or do I need to have real mails to see the issue? -- Regards Sudip
Bug#979965: milter-greylist exits after running for a few minutes
Ok this is done, now we wait a bit.
Thanks.
-Mike
From: Sudip Mukherjee
Sent: 12 January 2021 20:48
To: 979...@bugs.debian.org; Michael Grant
Cc: Vagrant Cascadian
Subject: Re: Bug#979965: milter-greylist exits after running for a few minutes
Hi Michael,
On Tue, Jan 12, 2021 at 5:54 PM Vagrant Cascadian wrote:
>
> On 2021-01-12, Michael Grant wrote:
> > After update to 4.6.2-2, milter-greylist runs for a few minutes
> > processing greylist requests then exits. No error in the daemon.log.
> > Daemon restarts with systemd over and over.
> >
> > Starting milter-greylist by hand using strace shows this just before
> > it dies:
> >
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 1 ([{fd=3,
> > revents=POLLIN}])
> > accept(3, {sa_family=AF_UNIX}, [2]) = 10
> > fcntl(10, F_GETFD) = 0
> > fcntl(10, F_SETFD, FD_CLOEXEC) = 0
> > setsockopt(10, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
> > futex(0x7f0f22c221a4, FUTEX_WAKE_PRIVATE, 1) = 1
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000) = 0 (Timeout)
> > poll([{fd=3, events=POLLIN|POLLPRI}], 1, 5000 ) = ?
> > +++ exited with 71 +++
> >
> > Previous version of milter-greylist on debian/testing was working fine
> > without this issue.
>
> Could you try running without the systemd .service file so that it falls
> back to the init script; there may be differences between how the
> .service file and the init script set up the environment to run it.
Can you also modify /lib/systemd/system/milter-greylist.service and
change the [Service] section to the following and test please..
[Service]
Type=forking
ExecStart=/usr/sbin/milter-greylist
Restart=on-failure
PrivateTmp=true
--
Regards
Sudip
Bug#979965: milter-greylist exits after running for a few minutes
I have made this change: [Service] Type=forking ExecStart=/usr/sbin/milter-greylist Restart=on-failure PrivateTmp=true And it’s still restarting every few minutes: Jan 12 16:09:43 strange milter-greylist[255358]: racl 277 greylist [delay 300] [aw 3888000] [maxpeek -1] default Jan 12 16:09:43 strange systemd[1]: Started Greylist Mail Filter Daemon. Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Main process exited, code=exited, status=71/OSERR Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Failed with result 'exit-code'. Jan 12 16:30:44 strange systemd[1]: milter-greylist.service: Scheduled restart job, restart counter is at 2. Jan 12 16:30:44 strange systemd[1]: Stopped Greylist Mail Filter Daemon. Jan 12 16:30:44 strange systemd[1]: Starting Greylist Mail Filter Daemon... I just noticed it says ‘Scheduled restart job’, is that because it exits? Or is that because some timer is killing it?
Bug#979965: milter-greylist exits after running for a few minutes
On Tue, Jan 12, 2021 at 10:02:19PM +, Sudip Mukherjee wrote: > On Tue, Jan 12, 2021 at 9:36 PM Michael Grant wrote: > > > > I have made this change: > > > > > > > > [Service] > > > > Type=forking > > > > ExecStart=/usr/sbin/milter-greylist > > > > Restart=on-failure > > > > PrivateTmp=true > > > > > > > > And it’s still restarting every few minutes: > > > > > > > > Jan 12 16:09:43 strange milter-greylist[255358]: racl 277 greylist [delay > > 300] [aw 3888000] [maxpeek -1] default > > > > Jan 12 16:09:43 strange systemd[1]: Started Greylist Mail Filter Daemon. > > > > Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Main process > > exited, code=exited, status=71/OSERR > > > > Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Failed with > > result 'exit-code'. > > > > Jan 12 16:30:44 strange systemd[1]: milter-greylist.service: Scheduled > > restart job, restart counter is at 2. > > > > Jan 12 16:30:44 strange systemd[1]: Stopped Greylist Mail Filter Daemon. > > > > Jan 12 16:30:44 strange systemd[1]: Starting Greylist Mail Filter Daemon... > > > > > > > > I just noticed it says ‘Scheduled restart job’, is that because it exits? > > Or is that because some timer is killing it? > > I think its restarting because the service file has > "Restart=on-failure". and since the main process is exiting with error > systemd thinks the service has failed and so it restarts. > To reproduce the error, do I just run milter-greylist with a > greylist.conf and Sendmail/Postfix or do I need to have real mails to > see the issue? I could probably send you my config files. I do have a fairly large database of grey listed hosts. I probably don't want to post that in the bug tracking database! For me, it runs for a while in side sendmail as a milter, I get a few messages, then it restarts. The journalctl is huge, I will forward it to you after. It doesn't seem to have any extra info. signature.asc Description: PGP signature
Bug#980024: pdmenu: FTBFS with GCC 10
Source: pdmenu Version: 1.3.4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, pdmenu currently FTBFS in unstable with GCC 10 as default. There is a patch in the linked VCS repo from September that has not been uploaded - can you please consider uploading it? We applied it successfully in Ubuntu but would prefer not to carry a delta. Thanks, Logan
apsfilter is marked for autoremoval from testing
apsfilter 7.2.6-2 is marked for autoremoval from testing on 2021-02-17 It (build-)depends on packages with these RC bugs: 979231: a2ps: the new mailcap entry breaks mutt https://bugs.debian.org/979231 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
tourney-manager is marked for autoremoval from testing
tourney-manager 20070820-4 is marked for autoremoval from testing on 2021-02-02 It is affected by these RC bugs: 979220: tourney-manager: invalid maintainer address https://bugs.debian.org/979220 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
a2ps is marked for autoremoval from testing
a2ps 1:4.14-6 is marked for autoremoval from testing on 2021-02-17 It is affected by these RC bugs: 979231: a2ps: the new mailcap entry breaks mutt https://bugs.debian.org/979231 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
ifhp is marked for autoremoval from testing
ifhp 3.5.20-17 is marked for autoremoval from testing on 2021-02-17 It (build-)depends on packages with these RC bugs: 979231: a2ps: the new mailcap entry breaks mutt https://bugs.debian.org/979231 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
