Hello,
in order to reproduce the bug, I can compare two commands:
1st command
sudo /usr/bin/daemon --noconfig --name bcron-start /usr/sbin/bcron-start
this one lauches bcron-start as a daemon, and syslog reports that
bcron-start exited with 111 status. This one is actually launched,
OOPS,
I missed reading one line in /var/log/syslog:
2022-12-12T16:37:38.266481+01:00 georges daemon: bcron-start: client (pid
1425506) exited with 111 status, exiting
So, the problem is still unfixed.
signature.asc
Description: PGP signature
Hi Tomas,
Tomas Hodek a écrit :
> [...]
> issue with crond, [...] I was able to catch what it is doing with strace:
>
> rt_sigprocmask(SIG_BLOCK, [HUP USR1 USR2 PIPE ALRM CHLD TSTP URG VTALRM PROF
> [...]
> read(5, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 4096
> [...]
> But problem is
Hi Georges,
issue with crond, we are currently having is that main process some
times hangs with high single core cpu usage. When its happens, jobs are
often delayed or not executed at all. We are talking about about 1300
user crontabs. Some are empty one, some are using up to 10 jobs.
Dear Thomas,
Tomas Hodek a écrit :
> I have been using Debian on servers for many years, but this is first time I
> had to file bug report, so i am quite newbie in how to properly debug
> package.
Please can you remind me why you could not use cron for your crontabs?
As I understand cron's
Hello,
only workaround I was able to create is to restart crond after a while
:) But did not find any solution to make bcron to work.
Fact, that no one reported any problems must be if not much people uses
it - I had same issue even on clean install. It is possible, no one
noticed it...
Dear Hodek,
have you found a workaround to manage your cron jobs?
Let me summarize the current situation:
- you raised bug report 1020415 three months ago, based on your
experience with bcron version 0.11-9, which is part of debian/stable
aka bullseye; version 0.11-9 has been released in
Hi Georges
no, problem is with fresh install of stable.
Tomas
On 28. 09. 22 15:35, Georges Khaznadar wrote:
Hi Thomas,
The issue with bcron appears when you switch from oldstable to stable,
doesn't it?
Maybe it comes from a fuzzy integration of bcron with systemd.
Have you tried to switch
Hi Thomas,
The issue with bcron appears when you switch from oldstable to stable,
doesn't it?
Maybe it comes from a fuzzy integration of bcron with systemd.
Have you tried to switch back to SysVinit?
Here is an e-mail thread about switching Bullseye to SysVinit, which is
two years old:
Hello,
i have already tried to upgrade to debian/testing - result is the same.
As for stable - maybe something else has changed since release?
Does this helps - daemon from init script in debug mode?
Sep 21 13:27:12 hostname bcron-sched[2363937]: Starting bcron system
scheduler:
Dear Thomas,
I made a mistake, when I read your first bug report: as your APT policy
was based on 'stable', you were reporting about the current stable
version, 0.11-9.
So the misbehavior which motivates your report, was introduced before I
adopted the package. This is weird, since version
Hi
about acl, it is strange, since package acl was not installed (thought this
package is required to manipulate acl)
this was all tested on current stable version (0.11-9)
getfacl crontabs/
# file: crontabs/
# owner: cron
# group: cron
# flags: --t
user::rwx
group::---
other::---
Hi Thomas,
thank you for your investigation work.
The modifications which I made, since version 0.11-9 which was
maintained by Dmitri Bogdanov, are aiming to prepare a transition from
cron (whose upstream is no longer maintained) to cronie (not for
tomorrow, but at some time later). For such a
Hi Georges,
I have tried to enter log messages as requested (also included header
files for syslog library), recompiled etc... But i am not able to get
any relevant informations from syslog - nothing is written. Am I missing
something?
I have also made fresh install of debian 11 and even
Dear Thomas,
can you give me more information? The error code 111 can be throwed from
many parts of bcron's code, as you can see by launching
`grep 111 *.c` in the directory of bcron's source. Most errors come with
an informative string, like ...
bcron-update.c:die1sys(111, "Could not
Package: bcron
Version: 0.11-9
Severity: important
Dear Maintainer,
init script /etc/init.d/bcron-sched should start schedulers, but child fails
with 111 status code. When launching /usr/sbin/bcron-start manually from
terminal it runs successfully.
Only relevant thing in syslog is:
daemon:
16 matches
Mail list logo
