TODO.org: Update TODOs
This commit is contained in:
parent
1d9e913cca
commit
e690123872
30
TODO.org
30
TODO.org
@ -1233,3 +1233,33 @@ DEADLINE: <2023-03-31 Fri>
|
||||
- [X] [[file:./.guix/rekahsoft/guix-config/vms/searx0-home-rekahsoft-ca.scm]]
|
||||
- [X] [[file:./.guix/rekahsoft/guix-config/vms/vault0-home-rekahsoft-ca.scm]]
|
||||
|
||||
** TODO Look into issues with syslog forwarding not working until service is manually restarted
|
||||
DEADLINE: <2023-04-04 Tue>
|
||||
|
||||
I noticed this after upgrading all guix vms to enable syslog forwarding. It seems that I need
|
||||
to manually restart the syslogd service after reboots. More investigations required.
|
||||
|
||||
Confirmed on:
|
||||
- git0
|
||||
- vault0
|
||||
- grocy0
|
||||
- dash0
|
||||
- ci0
|
||||
|
||||
Rebooting vault0 to see if the change was just a one-off after rebooting following my most
|
||||
recent upgrades, or is an issue upon every boot. It appears to happen every boot 😢.
|
||||
|
||||
My first guess is that the syslogd service needs to depend on network (but imho that doesn't
|
||||
make that much sense, as it should still eventually work once the network is online).
|
||||
|
||||
** TODO Setup docker syslog driver on vm's that use docker
|
||||
DEADLINE: <2023-04-06 Thu>
|
||||
|
||||
See [[https://docs.docker.com/config/containers/logging/syslog/][docker syslog driver documentation]] for more details on how to configure it. Note however
|
||||
that in guix, the guix docker-configuration (documentation in [[info:guix#Miscellaneous Services][Miscellaneous Services]] section)
|
||||
does not allow this to be configured. However, as documented in [[info:guix#Service Reference][Service Reference]] section,
|
||||
the ~etc-service-type~ can be extended to place the appropriate ~/etc/docker/daemon.json~
|
||||
configuration file in place.
|
||||
|
||||
Alternatively, the docker-configuration could be updated to support setting logging
|
||||
configuration and other options.
|
||||
|
Loading…
Reference in New Issue
Block a user