In my Raspberry Pi I have processes ongoing i background. However they seems, for some reason..., to become disabled at midnight
(at 00:00).

For the time being I have to restart them, with crontab, at 00:01 every night.

/var/log/syslog does not give any clarification.


Greatful for hints on how to solve the problem.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 12/11/2023 15:55, Bengt Törnqvist wrote:

In my Raspberry Pi I have processes ongoing i background. However they seems, for some reason..., to become disabled at midnight
(at 00:00).

For the time being I have to restart them, with crontab, at 00:01 every night.

/var/log/syslog does not give any clarification.

Greatful for hints on how to solve the problem.

What sort of thing are these misbehaving processes?

Could some external process like the loss of internet connection or
maybe timeout of a TCP connection be crashing them?

--
Brian Gregory (in England).

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 12/11/2023 15:55, Bengt Törnqvist wrote:

In my Raspberry Pi I have processes ongoing i background. However they seems, for some reason..., to become disabled at midnight
(at 00:00).

In my Raspberry Pi I have processes ongoing in background. However they
seems, for some reason to stay enabled at midnight.
So its a process specifiic problem, and since you give no detail. on the processes, its pretty hard to say why.

For the time being I have to restart them, with crontab, at 00:01 every night.

/var/log/syslog does not give any clarification.

Greatful for hints on how to solve the problem.

If they are managed by systemd look in ITS logs.
Also consider if they have any code that cares about the time in them,
and if it doesn't like going from e.g. 23:59 to 00:01.

Make them spew our debug info,

--
There is nothing a fleet of dispatchable nuclear power plants cannot do
that cannot be done worse and more expensively and with higher carbon
emissions and more adverse environmental impact by adding intermittent renewable energy.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

My assumption was that there might be some clean up procedure i Linux, started at midnight, which I was not aware of, that disabled my background procedures.
I have now learnt that this could not be the case. I have to dig further in my programs myself in order to try to find the reason(s).

Thank you all for responding.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Hello Bengt!

Monday November 13 2023 10:24, you wrote to All:

My assumption was that there might be some clean up procedure i Linux, started at midnight, which I was not aware of, that disabled my
background procedures. I have now learnt that this could not be the
case. I have to dig further in my programs myself in order to try to
find the reason(s).

Thank you all for responding.

Using root and your login take a look at if there are any processes in crontab by doing crontab -l

It is possible that there is a midnight process that is scheduled but saying that there should not be any that do so with running processes but does depend on your installed distro.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.4/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

T24gMTIvMTEvMjAyMyAxNTo1NSwgQmVuZ3QgVMO2cm5xdmlzdCB3cm90ZToNCj4gSW4gbXkg UmFzcGJlcnJ5IFBpIEkgaGF2ZSBwcm9jZXNzZXMgb25nb2luZyBpIGJhY2tncm91bmQuIEhv d2V2ZXIgdGhleSBzZWVtcywgZm9yIHNvbWUgcmVhc29uLi4uLCB0byBiZWNvbWUgZGlzYWJs ZWQgYXQgbWlkbmlnaHQNCj4gKGF0IDAwOjAwKS4NCg0KQXJlIHlvdSB1c2luZyBzeXN0ZW1k IHdpdGggU3RhbmRhcmRPdXRwdXQgdG8gaW52b2tlIHlvdXIgcHJvY2VzcywgYW5kIA0KaGF2 ZSBsb2cgcm90YXRpb24gc2V0IHVwPyBJZiBzbyB5b3UgcHJvYmFibHkgYXJlbid0IGhhbmRs aW5nIHRoZSBIVVAgDQpzaWduYWwgd2hlbiB0aGUgbG9nIGZpbGUgaXMgcm90YXRlZC4gVXNp bmcgQ29weVR1bmNhdGUgaW4gdGhlIGxvZ3JvdGF0ZSANCmNvbmYgbWlnaHQgc29sdmUgdGhl IGlzc3VlLg0KDQotLS1kcnVjaw0KDQo=

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Mon, 13 Nov 2023 10:24:17 -0800 (PST), Bengt Törnqvist wrote:

My assumption was that there might be some clean up procedure i Linux, started at midnight, which I was not aware of, that disabled my
background procedures.

Have you had a look to see exactly what is run at set times and/or
intervals?

Jobs defined in /etc/cron.* are run hourly, daily, weekly and monthly and
are never automatically removed, i.e. thay are run at the specified
intervals forever.

Scripts dropped into /etc/crontab are run pnce and then deleted.

I have now learnt that this could not be the case. I have to dig
further in my programs myself in order to try to find the reason(s).

Thank you all for responding.

--

Martin | martin at
Gregorie | gregorie dot org

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

I have come to the conclusion that the problem is related to that I have a program using a "gpio out port".

If I, for testing, disables the program using the "out port", the problem disappears.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 17/11/2023 08:38, Bengt Törnqvist wrote:

I have come to the conclusion that the problem is related to that I have a program using a "gpio out port".

If I, for testing, disables the program using the "out port", the problem disappears.

Well it cant be a *general* issue, because I have a background daemon
that controls 4 gpio ports as outputs and have been running now....

heating-controller:~ $ uptime
09:51:18 up 22 days, 21:44, 1 user, load average: 0.15, 0.07, 0.01

...clicking it's little relays.

So there is something specific to that program or how it is interacting
with the hardware.
--
"And if the blind lead the blind, both shall fall into the ditch".

Gospel of St. Mathew 15:14

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)