| 5 Oct 2023 |
 dch | Iām hoping it can work in write-only mode | 19:57:33 |
 czp | To use the S3 destination on FreeBSD you have to compile syslog-ng yourself from ports. Enable the PYTHON and PYTHO_MOD options. And do not forget to run the syslog-ng-update-virtualenv command to initialize the virtual env with dependencies. | 20:34:44 |
| czp | Unfortunately this means now downloading deps for Kubernetes support too, so 50+ MB wasted. | 20:35:55 |
| 6 Oct 2023 |
|  nasgartam joined the room. | 08:49:42 |
|  chris_44001 joined the room. | 14:07:09 |
|  24367dfa joined the room. | 14:59:14 |
| 10 Oct 2023 |
|  bishow_41696 joined the room. | 08:57:00 |
|  .mousam joined the room. | 08:59:59 |
| 14 Oct 2023 |
 bazsi77 | You could easily patch the requirements.txt file that the syslog-ng-update-virtualenv uses and remove the Kubernetes libs. As long as they are not used from a syslog-ng config it will work | 06:00:36 |
| bazsi77 | hofione mranno alltilla1337 I have cleaned up my ivykis PR that we were using to build syslog-ng against, so it can be merged to ivykis master. This however means that I had to drop an unrelated patch that Hofi submitted. | 06:03:01 |
| bazsi77 | I have now created tip/syslog-ng for the same purpose that is set to the same commit that we built against previously. However we would need to change our .gitmodules to point there. I submitted a PR to do just that: https://github.com/syslog-ng/syslog-ng/pull/4670 | 06:05:15 |
| bazsi77 | Existing git clones would continue to work even without #4670 but new ones might not, until we merge the above. | 06:06:13 |
| bazsi77 | I also submitted Hofi's patch against ivykis master. | 08:24:02 |
| 16 Oct 2023 |
 hofione | thanks for the update! | 08:24:04 |
| 17 Oct 2023 |
|  remigiusz_74277 joined the room. | 08:18:06 |
|  .remno joined the room. | 08:20:40 |
| 18 Oct 2023 |
|  sartigan joined the room. | 18:11:15 |
| 23 Oct 2023 |
|  mengzyou joined the room. | 03:36:55 |
| 24 Oct 2023 |
|  philip.peter_10466 joined the room. | 09:48:20 |
| philip.peter_10466 | Hi,
I'm looking to configure syslog-ng with remote logging via mTLS. In my use case the certificates to authenticate on the remote server might not be available during the initial start of syslog-ng. I have some thoughts on how to approach this, but I'm not sure if this is the right place for this.
Is this discord also a place to ask support question, or more for development chat? | 10:25:25 |
| bazsi77 | Sure, this is the best place | 10:26:16 |
| bazsi77 | We didn't separate dev/user questions to avoid splitting the focus | 10:26:42 |
| philip.peter_10466 | Awesome, thank you š | 10:26:48 |
| bazsi77 | You mean the key is not present at startup? | 10:27:21 |
| philip.peter_10466 | So I want to log to a remote server via a syslog destination. However the cert-file and key-file files will only be created after the device is started. There is an identity-daemon that takes care of initial provisioning and rotating the keys. | 10:28:54 |
| philip.peter_10466 | However I would want syslog-ng to buffer all messages and send them once it's available | 10:29:31 |
| bazsi77 | Ok, I see. | 10:29:41 |
| bazsi77 | Are you able to modify the config once the keys are there? | 10:30:13 |
| philip.peter_10466 | If I start syslog-ng with the cert-file and key-file missing it won't start, since the config is broken. If I create empty placeholder files it will start, but error on sending the messages | 10:30:39 |
| philip.peter_10466 | That's one option I'm considering, it gets a bit tricky, because this is an embedded device with a read-only root and seperate user writable partition. So I would probably need to point it to a different config after the keys are fetched. | 10:32:35 |
