Hi Marc
Yes but I have a check to check if "$RANDOM" is an empty string...
This should work... At least it has done that in the past.
// Ola
On Tue, 11 Jun 2024 at 21:35, Marc Haber wrote:
>
> On Tue, Jun 11, 2024 at 08:12:27PM +0200, Ola Lundqvist wrote:
> > Certainly. If you know those I'm ha
On Tue, Jun 11, 2024 at 08:12:27PM +0200, Ola Lundqvist wrote:
> Certainly. If you know those I'm happy to fix them.
>
> I thought I had fixed them all already.
The one that jumped to my mind is $RANDOM which doesnt work in dash.
I would recommend just using /bin/bash in the shebang line. At lea
Hi Marc
Certainly. If you know those I'm happy to fix them.
I thought I had fixed them all already.
Cheers
// Ola
On Tue, 11 Jun 2024 at 15:52, Marc Haber wrote:
>
> On Mon, Jun 10, 2024 at 11:02:30PM +0200, Ola Lundqvist wrote:
> > Sorry, I meant to run with dash -x. Or do dash not have that
On Mon, Jun 10, 2024 at 11:02:30PM +0200, Ola Lundqvist wrote:
> Sorry, I meant to run with dash -x. Or do dash not have that option?
It has this option.
But I see a problem in cron-apt using bashisms while using the /bin/sh
shebang line. I don't know whether this have to do with this, bug, but
i
Hi Marc
Sorry, I meant to run with dash -x. Or do dash not have that option?
Cheers
// Ola
On Wed, 15 May 2024 at 10:36, Marc Haber wrote:
>
> > Can you run it with bash -x from cron? Hopefully it tells where it breaks
>
> Using bash will not help here, that's the problem. cron-apt is a /bin/s
> Can you run it with bash -x from cron? Hopefully it tells where it breaks
Using bash will not help here, that's the problem. cron-apt is a /bin/sh
script, and on many systems /bin/sh is dash. And, $RANDOM doesn't exist
in dash.
Change cron-apt's shebang line to use /bin/bash and it should be fi
Thank you. According to the log everything works fine. Did it work fine now?
If possible attach the file as an attachment and the syslog where you have
the kernel error log.
// Ola
On Mon, 30 Jan 2023 at 15:02, Richard Rosner
wrote:
> I now found the problem. The mails from cron had been sorte
I now found the problem. The mails from cron had been sorted into spam because
they had "root (Cron Daemon)" as sender and rspamd didn't like the sender
domain to be forged to r...@domain.de. Anyway, the error message says
"/usr/bin/test: /usr/bin/test: can't execute file". I guess it didn't li
Really strange!
Not sure what could be wrong here.
// Ola
On Fri, 27 Jan 2023 at 13:17, Richard Rosner
wrote:
> Oddly enough, that doesn't work. I already did set the MAILTO directive so
> I should get the mail. But even after changing it to
>
> */5 * * * * root bash -x test -x /usr/sbin/cron-
Oddly enough, that doesn't work. I already did set the MAILTO directive so I
should get the mail. But even after changing it to
*/5 * * * * root bash -x test -x /usr/sbin/cron-apt && bash -x
/usr/sbin/cron-apt > /root/cron-apt.log 2>&1nothing is being written to the
mentioned file. File permiss
Hi Richard
It is a different email I'm referring to. When a script, run by
cron, prints something on standard output that will be sent to the root
user as an email. At least in standard configuration.
You should therefore have received two emails. One from cron-apt itself. We
know that will not ar
They are supposed to be sent to the mail address defined in the cron-apt
config. It didn't arrive there. Or did the change of executing cron-apt change
anything about that?
Richard
On January 27, 2023 12:18:13 AM GMT+01:00, Ola Lundqvist
wrote:
>Hi Richard
>
>I thought you would get the cron
Hi Richard
I thought you would get the cron output from bash -x in an email so I could
see more what happens. It should be sent to the root user. Or have
you redirected those emails so you do not get them?
Sorry for not being clear on that.
Best regards
// Ola
On Thu, 26 Jan 2023 at 15:15, Ric
With RUNSLEEP disabled, I get
2023-01-26T04:00:01.178308+01:00 ts CRON[60845]: (root) CMD (bash -x test -x
/usr/sbin/cron-apt && bash -x /usr/sbin/cron-apt)
2023-01-26T04:00:02.235676+01:00 ts sSMTP[60847]: Sent mail for
r...@ts.domain.de (221 mailserver.de) uid=0 username=root outbytes=672
No
Argh!
Can you run it with bash -x from cron? Hopefully it tells where it breaks
Den tis 24 jan. 2023 17:06Richard Rosner
skrev:
> No, and it did send a mail.
>
> --
> Richard Rosner
>
> Studierendenschaft der RWTH Aachen University
> Fachschaft Materialwissenschaft und Werkstofftechnik
> Intzes
No, and it did send a mail.
--
Richard Rosner
Studierendenschaft der RWTH Aachen University
Fachschaft Materialwissenschaft und Werkstofftechnik
Intzestraße 1
52072 Aachen
Tel.: +49 241 80-95781
rros...@fsmuw.rwth-aachen.de
www.fsmuw.rwth-aachen.de
Am Dienstag, 24. Januar 2023 16:44 CET, schri
Did you get that kernel error?
Den tis 24 jan. 2023 14:12Richard Rosner
skrev:
> This is the output (not sure if attachments are possible here, so I put it
> into the body):
>
> + export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
> + PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr
This is the output (not sure if attachments are possible here, so I put it into
the body):
+ export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
+ UMASK_TIGHT=077
+ UMASK_APT=022
+ umask 077
+ STDOUT=
+ ALLCO
Hi Richard
Strange!
Can you try to copy cron-apt and comment this:
if [ -t 0 ]; then
RUNIMMEDIATELY="yes"
fi
And then run manually.
bash -x your-cron-apt-copy
It would help to understand what happens.
// Ola
On Mon, 23 Jan 2023 at 23:30, Richard Rosner
wrote:
> Hi,
> sleep 456 and sle
Hi,
sleep 456 and sleep 1200 work without any problems. Also, I don't have any
special kernel. Currently, Output of uname -a is "Linux ts 6.1.0-1-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 GNU/Linux". I don't even
have any other repository active other than the typical Debi
Hi
When you run cron-apt from a terminal RUNSLEEP is not used. This is why it
works when running manually.
Please try running the following in a command
sleep 456
or any large number for sleep.
Do you have some special kernel? The kernel should not give that problem.
cron-apt do not do anythi
Package: cron-apt
Version: 0.13.0.1
Severity: important
X-Debbugs-Cc: sub...@bugs.debian.org
Dear Maintainer,
when running cron-apt as shipped it works normal, running at 4 am and sending
an email when anything can be updated. But when adding the recommended RUNSLEEP
variable to the config, the
22 matches
Mail list logo
