MIME-Version: 1.0
References: <CAFeSbqjnRXNZ72NdD+G6ScKKBTQXAxpMk=XyH1sPGs+L2atF_A@mail.gmail.com>
 <f6fb8364619a84f9b535edaaceb568dc2377da0d.camel@cybertec.at>
 <CAFeSbqjqi1DZjQDatiZehk3GpkX_dFv=qgfsgWxKbsACSWJv_g@mail.gmail.com>
 <20250202082618.trv7vpxw3stkqqw4@hjp.at> <be48b84f-ffcb-4be7-9489-3686ad74b5bd@gmail.com>
 <20250202195713.do65y2ewc6vjk3r5@hjp.at> <147245a5-5105-4cf1-85cf-bb92176b9702@gmail.com>
 <5ad33e59-a786-407c-ac03-98d248f0edac@aklaver.com>
In-Reply-To: <5ad33e59-a786-407c-ac03-98d248f0edac@aklaver.com>
From: Paul Brindusa <paulbrindusa88@gmail.com>
Date: Wed, 12 Feb 2025 13:15:57 +0000
Message-ID: <CAFeSbqh_+CSC0Ot98ML_O=ybd3AJRUbfREAUAC2KOsG6bhNdgg@mail.gmail.com>
Subject: Re: Log retention query
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000c6b1b2062df1bedb"
Archived-At: <https://www.postgresql.org/message-id/CAFeSbqh_%2BCSC0Ot98ML_O%3Dybd3AJRUbfREAUAC2KOsG6bhNdgg%40mail.gmail.com>
Precedence: bulk

--000000000000c6b1b2062df1bedb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFPM Adrian Klaver <adrian.klaver@aklaver=
.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.klaver@aklaver.com
>
>

--=20
Kind Regards,
Paul Brindusa
paulbrindusa88@gmail.com

--000000000000c6b1b2062df1bedb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Good afternoon,<div><br></div><div>Apologies for coming=C2=
=A0back=C2=A0to you so late.</div><div><br></div><div>Again I want to thank=
 everyone for all the help provided regarding this. The main culprit was th=
e cron job and trying to run it as root.</div><div>Main thing is i&#39;ve l=
earned a lot from your answers about the logs.</div><div>Thank you again.</=
div><div><br></div></div><br><div class=3D"gmail_quote gmail_quote_containe=
r"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb 2, 2025 at 9:33=E2=80=
=AFPM Adrian Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian=
.klaver@aklaver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">On 2/2/25 12:04, Paul Brindusa wrote:<br>
&gt; I am defo sure that my syntax was fine.<br>
&gt; <br>
&gt; I have tried the same syntax to remove the logs manually from the <br>
&gt; folder=C2=A0 and it worked perfectly.<br>
&gt; <br>
&gt; The cronjob was set from root, so I am assuming it has the right <br>
&gt; privileges over the folder in cause.<br>
&gt; <br>
<br>
Did you use the correct directory in the cron command?<br>
<br>
&gt; <br>
&gt; @ Adrian the cluster runs on Rocky9<br>
<br>
What repo are you using to install Postgres from?<br>
<br>
&gt; <br>
&gt; There is no error from cron that is the weird bit as well.<br>
&gt; <br>
&gt; I do not have MAILTO set up on cron.<br>
<br>
I would do that, then you should get the errors.<br>
<br>
You could also look in the system log at the time the cron job was <br>
executed to see if it recorded the error.<br>
<br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; Paul<br>
&gt; <br>
<br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
<br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr"><div>Kind Regards,</div><div>Paul Brindusa</div>=
<div><a href=3D"mailto:paulbrindusa88@gmail.com" target=3D"_blank">paulbrin=
dusa88@gmail.com</a></div><div><br></div></div></div>

--000000000000c6b1b2062df1bedb--