METRICS doesn't work

[ghost]

As I installed the new instance, acesttoi.fr, metrics doesn't work. I did no changes to the main branch.

Browser shows "nginx 404"….

[missytake]

Hm, what does your /etc/cron.d/chatmail-metrics file say? It's supposed to create /var/www/html/metrics, which apparently doesn't exist.

[ghost]

The command outof crontab works fine by hand, then the site works. Some bug with cron? 🤔 missytake ***@***.***> schrieb am Mo., 6. Mai 2024, 13:17:

Hm, what does your /etc/cron.d/chatmail-metrics file say? It's supposed to create /var/www/html/metrics, which apparently doesn't exist. — Reply to this email directly, view it on GitHub <#282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK35VRZT2SD22MO5CUM6FNLZA5RDPAVCNFSM6AAAAABHFS4FP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVG43TMNBWHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

cron was not installed. ??? Ok, maybe it is a good idea to controll it by cmdeploy. On some OS installations it seams to be missing.

[link2xt]

Or we should switch to using systemd timer as we depend on systemd anyway.

[ghost]

Yes, I agree. Good idea! link2xt ***@***.***> schrieb am Di., 7. Mai 2024, 17:54:

…

Or we should switch to using systemd timer as we depend on systemd anyway. — Reply to this email directly, view it on GitHub <#282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK35VR7HFIGRJFH7CQYLMSDZBD2LXAVCNFSM6AAAAABHFS4FP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYG44DSMBZHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ghost]

Correct. Christian Hagenest ***@***.***> schrieb am Sa., 18. Mai 2024, 18:34:

…

pyinfra doesn't support the creation of systemd timers, so we just copy one over with file.put, right? — Reply to this email directly, view it on GitHub <#282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK35VRYQDMAVHWWNQTTSEETZC57J3AVCNFSM6AAAAABHFS4FP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYHA3TINJXGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[missytake]

Or we should switch to using systemd timer as we depend on systemd anyway.

I don't have a problem with it, but it makes it slightly harder for the openBSD folks.

[missytake]

There are more cronjobs, which also would need a systemd timer (when they fail it's less obvious, but even more problematic).

Or we just install cron, which would be less work.

I'm fine with both :)

[hagenest]

currently deliberating if my love for systemd outweighs my love for easy solutions

[hpk42]

On Sun, May 19, 2024 at 04:42 -0700, missytake wrote: > Or we should switch to using systemd timer as we depend on systemd anyway. I don't have a problem with it, but it makes it slightly harder for the openBSD folks.

Good point. We rely on systemd already but is there real need to use it as replacement for Cron?

[hagenest]

only reason afaik is that cron is deprecated on Debian 12 and it may not be installed on all systems by default. Using systemd would mean we need one fewer dependency.

But on most of our users systems, cron was installed anyways. It may only happen on Raspbian?

[ghost]

Not on Raspian, there cron is usualy installed by default. Especially Dietpi, which is the better OS for Raspis and Co uses cron itself. Some VPS setups don't install cron - and other things. Christian Hagenest ***@***.***> schrieb am So., 26. Mai 2024, 19:42:

…

only reason afaik is that cron is deprecated on Debian 12 and it may not be installed on all systems by default. Using systemd would mean we need one fewer dependency. But on most of our users systems, cron was installed anyways. It may only happen on Raspbian. — Reply to this email directly, view it on GitHub <#282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK35VRYIVX5A26A46GL5EOLZEINJ5AVCNFSM6AAAAABHFS4FP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGI4TMNRVGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>