From: | Paul Brindusa <paulbrindusa88(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Log retention query |
Date: | 2025-02-12 13:15:57 |
Message-ID: | CAFeSbqh_+CSC0Ot98ML_O=ybd3AJRUbfREAUAC2KOsG6bhNdgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Good afternoon,
Apologies for coming back to you so late.
Again I want to thank everyone for all the help provided regarding this.
The main culprit was the cron job and trying to run it as root.
Main thing is i've learned a lot from your answers about the logs.
Thank you again.
On Sun, Feb 2, 2025 at 9:33 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 2/2/25 12:04, Paul Brindusa wrote:
> > I am defo sure that my syntax was fine.
> >
> > I have tried the same syntax to remove the logs manually from the
> > folder and it worked perfectly.
> >
> > The cronjob was set from root, so I am assuming it has the right
> > privileges over the folder in cause.
> >
>
> Did you use the correct directory in the cron command?
>
> >
> > @ Adrian the cluster runs on Rocky9
>
> What repo are you using to install Postgres from?
>
> >
> > There is no error from cron that is the weird bit as well.
> >
> > I do not have MAILTO set up on cron.
>
> I would do that, then you should get the errors.
>
> You could also look in the system log at the time the cron job was
> executed to see if it recorded the error.
>
> >
> > Regards,
> >
> > Paul
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
--
Kind Regards,
Paul Brindusa
paulbrindusa88(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2025-02-12 18:50:37 | psql command line editing |
Previous Message | Tom Lane | 2025-02-11 17:50:14 | Re: Using Expanded Objects other than Arrays from plpgsql |