Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #195045 > unrolled thread

Jessie: No logrotate since October 2016?

Started byJohn Cunningham <djohngo@gmail.com>
First post2018-04-24 18:50 +0200
Last post2018-05-10 13:10 +0200
Articles 9 — 6 participants

Back to article view | Back to linux.debian.user

Contents

  Jessie: No logrotate since October 2016? John Cunningham <djohngo@gmail.com> - 2018-04-24 18:50 +0200
    Re: Jessie: No logrotate since October 2016? Sven Joachim <svenjoac@gmx.de> - 2018-04-24 20:10 +0200
      Re: Jessie: No logrotate since October 2016? Boyan Penkov <boyan.penkov@gmail.com> - 2018-04-24 20:10 +0200
        Re: Jessie: No logrotate since October 2016? Brad Rogers <brad@fineby.me.uk> - 2018-04-24 20:30 +0200
          Re: Jessie: No logrotate since October 2016? Boyan Penkov <boyan.penkov@gmail.com> - 2018-05-04 01:40 +0200
    Re: Jessie: No logrotate since October 2016? Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2018-05-06 11:30 +0200
      Re: Jessie: No logrotate since October 2016? Boyan Penkov <boyan.penkov@gmail.com> - 2018-05-06 19:20 +0200
      Re: Jessie: No logrotate since October 2016? John Cunningham <djohngo@gmail.com> - 2018-05-08 18:20 +0200
    Re: Jessie: No logrotate since October 2016? Dominique Dumont <dod38fr@googlemail.com> - 2018-05-10 13:10 +0200

#195045 — Jessie: No logrotate since October 2016?

FromJohn Cunningham <djohngo@gmail.com>
Date2018-04-24 18:50 +0200
SubjectJessie: No logrotate since October 2016?
Message-ID<vI9iF-1Ye-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Howdy,

I just noticed that logrotate hasn't been running since October 2016 on one
of my Jessie boxes.  Manually running logrotate works without issue. This
is approximately the time I upgraded it from Wheezy. I hate to wade into
the pool of systemd hate, but is this systemd's fault? I noticed
anacron doesn't exist on this system. Is it supposed to anymore? Or is that
one of the things that have been deprecated? If so, how are the
/etc/cron.daily jobs getting run these days?

I cheated and added logrotate to root's crontab as an ugly hack to get them
rotating. What is the *right* way to get it going again?

Thanks,

--John

[toc] | [next] | [standalone]

#195046

FromSven Joachim <svenjoac@gmx.de>
Date2018-04-24 20:10 +0200
Message-ID<vIay6-2Vi-11@gated-at.bofh.it>
In reply to#195045
On 2018-04-24 16:40 +0000, John Cunningham wrote:

> I just noticed that logrotate hasn't been running since October 2016 on one
> of my Jessie boxes.  Manually running logrotate works without issue. This
> is approximately the time I upgraded it from Wheezy. I hate to wade into
> the pool of systemd hate, but is this systemd's fault?

No.

> I noticed
> anacron doesn't exist on this system. Is it supposed to anymore? Or is that
> one of the things that have been deprecated? If so, how are the
> /etc/cron.daily jobs getting run these days?

If your system is not running 24/7, then anacron is very much
recommended.

Cheers,
       Sven

[toc] | [prev] | [next] | [standalone]

#195047

FromBoyan Penkov <boyan.penkov@gmail.com>
Date2018-04-24 20:10 +0200
Message-ID<vIay6-2Vi-13@gated-at.bofh.it>
In reply to#195046
In this vein, is there a way to intelligently indicate to the system 
that this is the case, and automatically read the crontab, then write an 
intelligent anacrontab with sane defaults?

Cheers!

On 04/24/2018 02:04 PM, Sven Joachim wrote:
> If your system is not running 24/7, then anacron is very much
> recommended.
>
> Cheers,
>         Sven
>

[toc] | [prev] | [next] | [standalone]

#195048

FromBrad Rogers <brad@fineby.me.uk>
Date2018-04-24 20:30 +0200
Message-ID<vIaRr-33m-3@gated-at.bofh.it>
In reply to#195047

[Multipart message — attachments visible in raw view] — view raw

On Tue, 24 Apr 2018 14:09:06 -0400
Boyan Penkov <boyan.penkov@gmail.com> wrote:

Hello Boyan,

>that this is the case, and automatically read the crontab, then write
>an intelligent anacrontab with sane defaults?

From the anacron page on packages.debian.org;

This package is pre-configured to execute the daily jobs of the Debian
system. You should install this program if your system isn't powered on
24 hours a day to make sure the maintenance jobs of other Debian
packages are executed each day.

Not a full answer, but gets you part way to where you want to be, I hope.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
You're only laughing 'cause you haven't heard the news
Sleeep - Wah!

[toc] | [prev] | [next] | [standalone]

#195271

FromBoyan Penkov <boyan.penkov@gmail.com>
Date2018-05-04 01:40 +0200
Message-ID<vLvZo-7Si-15@gated-at.bofh.it>
In reply to#195048

[Multipart message — attachments visible in raw view] — view raw

Really late response here, but thanks — some reading of /etc/anacrontab and run-parts does make clear that edits of the crontab will then be run by anacron

Thanks kindly!
--
Boyan Penkov
www.boyanpenkov.com

> On Apr 24, 2018, at 14:27, Brad Rogers <brad@fineby.me.uk> wrote:
> 
> On Tue, 24 Apr 2018 14:09:06 -0400
> Boyan Penkov <boyan.penkov@gmail.com> wrote:
> 
> Hello Boyan,
> 
>> that this is the case, and automatically read the crontab, then write
>> an intelligent anacrontab with sane defaults?
> 
> From the anacron page on packages.debian.org;
> 
> This package is pre-configured to execute the daily jobs of the Debian
> system. You should install this program if your system isn't powered on
> 24 hours a day to make sure the maintenance jobs of other Debian
> packages are executed each day.
> 
> Not a full answer, but gets you part way to where you want to be, I hope.
> 
> -- 
> Regards  _
>         / )           "The blindingly obvious is
>        / _)rad        never immediately apparent"
> You're only laughing 'cause you haven't heard the news
> Sleeep - Wah!

[toc] | [prev] | [next] | [standalone]

#195322

FromJonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
Date2018-05-06 11:30 +0200
Message-ID<vMo9s-1wp-1@gated-at.bofh.it>
In reply to#195045
John Cunningham:

> I hate to wade into the pool of systemd hate, but is this systemd's 
> fault? I noticed anacron doesn't exist on this system. Is it supposed 
> to anymore? Or is that one of the things that have been deprecated? If 
> so, how are the /etc/cron.daily jobs getting run these days?
>
You'll have to check the timeframe of when these changes happened with 
respect to Debian 8, but a Debian 9 system does not use cron to run 
anacron and various other things like phpsessionclean, nor use anacron 
itself to run various further things.  You'll find [ ! -d 
/run/systemd/system ] in various places in Debian Linux nowadays that 
turns stuff off when systemd is running, as well as reliance on the fact 
that systemd ignores non-native stuff if it has native stuff of the same 
name (such as anacron.timer).

* https://unix.stackexchange.com/a/438379/5132

* https://sources.debian.org/src/anacron/2.3-24/debian/anacron.timer/

* https://sources.debian.org/src/apt/1.6.1/debian/apt.apt-compat.cron.daily/

* https://sources.debian.org/src/man-db/2.8.3-2/debian/cron.daily/

Moreover, you will find the similar [ -x /usr/sbin/anacron ] in various 
places to control what happens when anacron is not installed.

* https://sources.debian.org/src/cron/3.0pl1-130/debian/crontab.main/

So bear in mind that your learned ideas about what runs what are no 
longer true.

[toc] | [prev] | [next] | [standalone]

#195355

FromBoyan Penkov <boyan.penkov@gmail.com>
Date2018-05-06 19:20 +0200
Message-ID<vMvuh-6cB-5@gated-at.bofh.it>
In reply to#195322

[Multipart message — attachments visible in raw view] — view raw

--
Boyan Penkov
www.boyanpenkov.com

> On May 6, 2018, at 05:10, Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> wrote:
> 
> John Cunningham:
> 
>> I hate to wade into the pool of systemd hate, but is this systemd's fault? I noticed anacron doesn't exist on this system. Is it supposed to anymore? Or is that one of the things that have been deprecated? If so, how are the /etc/cron.daily jobs getting run these days?
>> 
> You'll have to check the timeframe of when these changes happened with respect to Debian 8, but a Debian 9 system does not use cron to run anacron and various other things like phpsessionclean, nor use anacron itself to run various further things.  You'll find [ ! -d /run/systemd/system ] in various places in Debian Linux nowadays that turns stuff off when systemd is running, as well as reliance on the fact that systemd ignores non-native stuff if it has native stuff of the same name (such as anacron.timer).
> 
> * https://unix.stackexchange.com/a/438379/5132

Thanks for the pointer, particularly here...

> 
> * https://sources.debian.org/src/anacron/2.3-24/debian/anacron.timer/
> 
> * https://sources.debian.org/src/apt/1.6.1/debian/apt.apt-compat.cron.daily/
> 
> * https://sources.debian.org/src/man-db/2.8.3-2/debian/cron.daily/
> 
> Moreover, you will find the similar [ -x /usr/sbin/anacron ] in various places to control what happens when anacron is not installed.
> 
> * https://sources.debian.org/src/cron/3.0pl1-130/debian/crontab.main/
> 
> So bear in mind that your learned ideas about what runs what are no longer true.
>

[toc] | [prev] | [next] | [standalone]

#195501

FromJohn Cunningham <djohngo@gmail.com>
Date2018-05-08 18:20 +0200
Message-ID<vNdvj-Kr-1@gated-at.bofh.it>
In reply to#195322

[Multipart message — attachments visible in raw view] — view raw

On Sun, May 6, 2018 at 5:10 AM Jonathan de Boyne Pollard <
J.deBoynePollard-newsgroups@ntlworld.com> wrote:

>
> So bear in mind that your learned ideas about what runs what are no
> longer true.
>
>
If I still did sigfiles, this would now be in mine. Thank you very much for
your helpful reply.

--John

[toc] | [prev] | [next] | [standalone]

#195568

FromDominique Dumont <dod38fr@googlemail.com>
Date2018-05-10 13:10 +0200
Message-ID<vNRCq-7Xx-15@gated-at.bofh.it>
In reply to#195045
On mardi 24 avril 2018 18:40:55 CEST John Cunningham wrote:
> I cheated and added logrotate to root's crontab as an ugly hack to get them
> rotating. What is the *right* way to get it going again?

I just noticed a similar problem on my system. I've installed systemd-cron and purged cron.

Now systemd handles daily jobs:
$ systemctl status cron-daily.timer
● cron-daily.timer - systemd-cron daily timer
   Loaded: loaded (/lib/systemd/system/cron-daily.timer; static; vendor preset: enabled)
   Active: active (waiting) since Thu 2018-05-10 12:46:37 CEST; 3min 37s ago
  Trigger: Fri 2018-05-11 06:25:00 CEST; 17h left
     Docs: man:systemd.cron(7)

mai 10 12:46:37 gandalf systemd[1]: Started systemd-cron daily timer.

Now log files should be rotated again.

HTH

-- 
https://github.com/dod38fr/config-model/ -o- http://search.cpan.org/~ddumont/
    http://ddumont.wordpress.com/        -o-   irc: dod at irc.debian.org

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web