2023-05-02T05:35:10  <bmwiedemann[m]> Will check that in 1h when back on a computer.
2023-05-02T06:59:56  *** DimStar_ is now known as DimStar
2023-05-02T07:54:33  *** teepee_ is now known as teepee
2023-05-02T11:59:21  *** cucumis[m] is now known as cucumis6626[m]
2023-05-02T12:24:31  <malcolmlewis> heli[m], ping
2023-05-02T12:25:01  <malcolmlewis> hellcp, ping (apologies heli[m])
2023-05-02T12:26:05  <hellcp> poor heli
2023-05-02T12:27:36  <bmwiedemann[m]> hah! the downloadcontent2 cert expired, because the cron daemon was not enabled.
2023-05-02T12:29:51  <pjessen> hah ..... why would the cron daemon not be enabled .....
2023-05-02T12:30:05  <malcolmlewis> hellcp, can you look at the Forum topic list, it doesn't seem to update?
2023-05-02T12:30:13  <bmwiedemann[m]> vendor preset: disabled
2023-05-02T12:30:35  <bmwiedemann[m]> it is Leap 15.4
2023-05-02T12:31:27  <hellcp> seems like sidekiq was down
2023-05-02T12:31:28  <hellcp> I started it
2023-05-02T12:32:51  <malcolmlewis> hellcp, yes i saw that mentioned
2023-05-02T12:33:53  <malcolmlewis> hellcp, will that fix rss feeds too?
2023-05-02T12:34:07  <hellcp> probably
2023-05-02T12:34:24  <hellcp> sidekiq does most of the threaded tasks like that
2023-05-02T12:34:37  <malcolmlewis> hellcp, so that's on the server, can it be restarted in the admin panel?
2023-05-02T12:34:50  <hellcp> I don't think so
2023-05-02T12:35:12  <hellcp> but anyone that can access the server can just do systemctl start discourse-sidekiq
2023-05-02T12:35:18  <malcolmlewis> hellcp, so can we add some sort of alert?
2023-05-02T12:35:47  <hellcp> admin dashboard mentions it right now
2023-05-02T12:35:55  <hellcp> there could be an alert added to monitoring
2023-05-02T12:36:09  <hellcp> but I don't know how to set up monitoring
2023-05-02T12:36:18  <hellcp> feel free to create a ticket on progress for that
2023-05-02T12:39:18  <malcolmlewis> hellcp, the theming has disappeared..
2023-05-02T12:40:03  <hellcp> I updated one of the theme components, you may need to refresh the page
2023-05-02T12:40:17  <hellcp> if that doesn't work I guess we need to restart discourse-puma
2023-05-02T12:40:17  <bmwiedemann[m]> interesting. I installed cronie on another VM and there I got vendor preset: enabled
2023-05-02T12:40:24  <malcolmlewis> hellcp, yup
2023-05-02T12:41:51  <pjessen> hmm, I don't recall ever having to enable cron myself
2023-05-02T12:49:13  <malcolmlewis> systemd timers all the way...
2023-05-02T12:50:09  <bmwiedemann[m]> but then I need 3 files instead of 1: .timer .service and script
2023-05-02T13:03:04  <malcolmlewis> bmwiedemann[m], but depends on when you need it running, can use a default timer... plus if need a real fast one can run in less than a minute, can't do that with cron.
2023-05-02T13:04:10  <malcolmlewis> also depends on the command your running, can do it all in the service?
2023-05-02T13:04:18  <acidsys> afaik on new installations we no longer ship cronie by default in favor of systemd services
2023-05-02T13:05:01  <acidsys> but I thought it was only tumbleweed
2023-05-02T13:05:24  <malcolmlewis> bmwiedemann[m], this is an example of a long one in a service https://github.com/malcolmlewis/systemd-minio-service/blob/main/minio.service
2023-05-02T13:51:21  *** teepee_ is now known as teepee
2023-05-02T14:13:29  <pjessen> do user timers work with systemd?  I've never tried.
2023-05-02T14:13:53  <acidsys> probably requires lingering for the user to be enabled
2023-05-02T14:15:09  <pjessen> acidsys: fyi, with leap 15.5 - cronie installed and enabled by default.
2023-05-02T14:15:26  <malcolmlewis> acidsys, as a login user, could also be a system user (daemon checking for an update?)
2023-05-02T14:17:31  <pjessen> for the plain user, what is the systemd equivlalent of "crontab -e" ?  (just being curious)
2023-05-02T14:18:22  <acidsys> pjessen: interesting, wonder if there was a reason .. maybe some base packages still shipping with only a crontab dropin
2023-05-02T14:18:58  <pjessen> acidsys: I did check, but my leap155 dfoesn't have anything in /etc/cron.d
2023-05-02T14:19:54  <acidsys> to edit `systemctl --user edit my-cool-timer.timer`, but to create a new one I think the best way is to create a file in ~/.config/systemd/user/my-cool-timer.timer manually
2023-05-02T14:20:20  <acidsys> because systemctl edit will do override files even with --full .. not sure if there's some other flag
2023-05-02T14:21:01  <pjessen> acidsys: tnx!
2023-05-02T14:21:10  <acidsys> malcolmlewis: if it's a system user then the service should just run in the system context and use the "User" option
2023-05-02T14:22:25  <pjessen> oops, systemctl --user edit....  didnt' work. on leap155
2023-05-02T14:23:22  <acidsys> it should work, if an existing unit is there in .config/systemd/user/
2023-05-02T14:23:41  <acidsys> if there's no existing unit then it won't work
2023-05-02T14:25:03  <acidsys> after you add the file to the directory you need to either `systemctl --user start` it, or if you want it to be picked up without starting then `systemctl --user daemon-reload`
2023-05-02T14:25:43  <acidsys> well basically the same things you would do for system units just every command with `--user`
2023-05-02T14:26:44  <pjessen> sounds like fun :-)  creating a timer sort of works on leap 15.3, now I need to figure out how to change the editoor vim :_)
2023-05-02T14:27:02  <acidsys> you mean the systemctl edit editor?
2023-05-02T14:27:14  <pjessen> yeah, I know there is a variable I can set
2023-05-02T14:27:18  <acidsys> you can use EDITOR=vim
2023-05-02T14:28:09  <malcolmlewis> pjessen, in ~/.profile add export EDITOR=/usr/bin/vim
2023-05-02T14:28:26  <malcolmlewis> or nano or whichever one your using
2023-05-02T14:28:31  <pjessen> yeah :-)
2023-05-02T14:29:26  <malcolmlewis> acidsys, google still uses cron, I delete them anyway ;)
2023-05-02T14:30:03  <acidsys> I too think cron is more convenient sometimes but it's yet another superfluous daemon running on a machine
2023-05-02T14:31:06  <acidsys> and I like the service concept, for debugging scheduled tasks being able to just start and watch the stdout in the system journal is handy
2023-05-02T14:42:13  <pjessen> funny, on leap155, the edit user timer complains that $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined
2023-05-02T14:43:00  <pjessen> on leap153. with a desktop, the value is /run/user/1000 and /run/user/1000/bus
2023-05-02T14:44:03  <pjessen> if I set them manually, it works
2023-05-02T14:48:04  <acidsys> pjessen: are you in a login shell?
2023-05-02T14:48:14  <acidsys> for example ssh directly to the account?
2023-05-02T14:49:15  <pjessen> I thought I was, but it was in fact su to user
2023-05-02T14:49:41  <pjessen> yeah, that was it.
2023-05-02T14:50:18  <pjessen> well, cool stuff, I've not had reason to try that before.  A bit cumbersome compared to crontab -e
2023-05-02T14:50:27  <acidsys> I remember `sudo -i` or `su -l` to not fully do the trick .. for some reason
2023-05-02T14:50:38  <pjessen> I like that the config is in the homedir though
2023-05-02T14:50:42  <acidsys> I have this handy snippet saved to mitigate the problem, let me find it
2023-05-02T14:52:08  <acidsys> `env XDG_RUNTIME_DIR=/run/user/(id -u pod) sudo -Eu pod systemctl --user <something>`
2023-05-02T14:52:19  <acidsys> "pod" being the user
2023-05-02T14:52:44  <acidsys> and $() for bash
2023-05-02T15:33:21  <pjessen> 185.244.165.231 ? does anyone know that server?
2023-05-02T15:35:05  <pjessen> it is filling up the logs on provo-mirror
2023-05-02T15:37:31  <pjessen> well, that is only one culprit
2023-05-02T15:38:38  <pjessen> ignore
2023-05-02T16:34:34  <pjessen> 185.244.165.231  keeps querying nginx_status on provo-mirror.
2023-05-02T16:34:51  <pjessen> several times per second. I'm going to ban it
2023-05-02T16:55:59  <pjessen> poo#128531
2023-05-02T18:42:56  *** teepee_ is now known as teepee
2023-05-02T23:26:32  *** teepee_ is now known as teepee