Hello Lance,
On Sun, Oct 16, 2022 at 06:35:37PM +0200, Helge Kreutzmann wrote:
> On Fri, Oct 07, 2022 at 12:34:33PM +, Lance Lin wrote:
> > Since you already have cron files, perhaps you could back them up,
> > uninstall anacron, remove the files, and then
> > re-install anacron (-35), and
Hello Lance,
On Fri, Oct 07, 2022 at 12:34:33PM +, Lance Lin wrote:
> I believe I've found the issue! Sorry it has taken so long to get back to you
> but I believe I have an answer.
>
> It seems to be related to an inadequate cleanup. I don't have a great
> explanation but I found something
Hello Lin,
thanks for your analysis and answer.
On Fri, Oct 07, 2022 at 12:34:33PM +, Lance Lin wrote:
> I believe I've found the issue! Sorry it has taken so long to get back to you
> but I believe I have an answer.
Great! Thanks for your research.
> It seems to be related to an
Hello Helge,
> Do you have any idea what both anacron.service and anacron.timer are
> disabled?
>
> So somehow anacron -34 disabled both the service and the timer.
>
> Anything you want me to look at?
>
> Next step would be how to properly enable them again…
>
> Thanks!
>
> Greetings
>
> Helge
I
Hello Lance,
On Fri, Sep 30, 2022 at 05:10:01PM +0200, Helge Kreutzmann wrote:
> On Fri, Sep 30, 2022 at 12:53:09PM +, Lance Lin wrote:
> > Thank you for your help in tracking this down. I apologize that the -35
> > revision didn't fix it.
> >
> > > So the check in the cron file is wrong! It
Hello Lance,
thanks for your analysis.
On Fri, Sep 30, 2022 at 12:53:09PM +, Lance Lin wrote:
> Thank you for your help in tracking this down. I apologize that the -35
> revision didn't fix it.
>
> > So the check in the cron file is wrong! It should be
> > if [ -d /run/systemd/system ];
Hello Helge,
Thank you for your help in tracking this down. I apologize that the -35
revision didn't fix it.
> So the check in the cron file is wrong! It should be
> if [ -d /run/systemd/system ]; then …
>
> Is this the solution? Or is there a downside in changing this? And I
> definitely did
Hello Lance,
On Thu, Sep 29, 2022 at 09:15:13PM +0200, Helge Kreutzmann wrote:
> Sep 29 20:30:01 twentytwo CRON[11425]: (root) CMD ([ -x /etc/init.d/anacron ]
> && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start
> >/dev/null; fi)
>
> /etc/init.d/anacron exists,
reopen 1019554
found 1019554 2.3-35
thanks
Hello Lance,
On Wed, Sep 21, 2022 at 01:40:18PM +, Lance Lin wrote:
> > As you can see, cron.daily is still on Sunday.
> >
>
> > So something prevents anacron from starting.
> >
>
> > Please tell me what helps tracing this down.
>
> I think Roy
Hello Helge,
> As you can see, cron.daily is still on Sunday.
>
> So something prevents anacron from starting.
>
> Please tell me what helps tracing this down.
I think Roy Clark's email on this list found the problem.
Someone had reported that there were dangling symlinks for the timer and
Hello Lance,
On Tue, Sep 13, 2022 at 12:22:07PM +, Lance Lin wrote:
> Thank you for your report. I'm happy to work on this.
>
> > So cron.weekly is now overdue and cron.daily did not get touched since
> > the 5th, consistent with the update of the package.
> >
>
> > Cron itself works,
On Mon, 19 Sep 2022 12:59:59 + Lance Lin wrote:
>
> Thank you for tracking this down. I did make the change in -33.
>
> Yes, I made the change to remove dangling symlinks on uninstall. I
>
> didn't realize this was called on upgrades, so I've moved the logic
>
> inside the "purge" case.
>
> I
Mike,
> I'm seeing the same issue, and I believe I've tracked it down to these
> lines in the debian/anacron.postrm:
>
> # Close bug #993348, remove dangling symlinks if they exist
> if [ -f /etc/systemd/system/multi-user.target.wants/anacron.service ]; then
> rm
Hello Lance,
On Tue, Sep 13, 2022 at 12:22:07PM +, Lance Lin wrote:
> Thank you for your report. I'm happy to work on this.
I'll try to start anacron manually on Sunday. So if you want to
investigate anything before I do so, please let me know.
Greetings
Helge
--
Dr. Helge
Hello Lance,
On Tue, Sep 13, 2022 at 12:22:07PM +, Lance Lin wrote:
> Thank you for your report. I'm happy to work on this.
Thank you very much, this is highly appreciated.
> > So cron.weekly is now overdue and cron.daily did not get touched since
> > the 5th, consistent with the update of
Hello,
$ ls -tlr /var/spool/anacron/
insgesamt 12
-rw--- 1 root root 9 16. Aug 17:03 cron.monthly
-rw--- 1 root root 9 3. Sep 09:31 cron.weekly
-rw--- 1 root root 9 5. Sep 13:02 cron.daily
So cron.weekly is now overdue and cron.daily did not get touched since
the 5th, consistent
16 matches
Mail list logo
