| 26 Aug 2023 |
|  giakinh2000 changed their display name from giakinh2000 to giakinh2000#0. | 10:43:45 |
| giakinh2000 changed their display name from giakinh2000#0 to giakinh2000. | 10:43:49 |
| 29 Aug 2023 |
|  korro_93890 joined the room. | 07:54:39 |
| 30 Aug 2023 |
|  florianstoeber_64616 joined the room. | 06:05:42 |
| 31 Aug 2023 |
 mranno | grg_2145 hofione It seems the nightly is broken, the auth token used for uploading packages to Azure has probably expired:
https://github.com/syslog-ng/syslog-ng/actions/runs/6031020756/job/16364163198
Could you take a look, please? We had internal documentations about how these auth tokens were generated.
(This is about the APT repository ose-repo.syslog-ng.com) | 06:28:43 |
| mranno | * grg_2145 hofione It seems the nightly is broken, the auth token used for uploading packages to Azure has probably expired:
https://github.com/syslog-ng/syslog-ng/actions/runs/6031020756/job/16364163198
Could you take a look, please? We had internal documentation about how these auth tokens were generated.
(This is about the APT repository ose-repo.syslog-ng.com) | 06:29:08 |
| mranno | * grg_2145 hofione It seems the nightly is broken, the auth token used for uploading packages to Azure has probably expired:
https://github.com/syslog-ng/syslog-ng/actions/runs/6031020756/job/16364163198
AZURE_SAS_TOKEN - uploaded on on Aug 28, 2022
Could you take a look, please? We had internal documentation about how these auth tokens were generated.
(This is about the APT repository ose-repo.syslog-ng.com) | 06:32:58 |
| mranno | * grg_2145 hofione It seems the nightly is broken, the auth token used for uploading packages to Azure has probably expired:
https://github.com/syslog-ng/syslog-ng/actions/runs/6031020756/job/16364163198
AZURE_SAS_TOKEN - uploaded on Aug 28, 2022
Could you take a look, please? We had internal documentation about how these auth tokens were generated.
(This is about the APT repository ose-repo.syslog-ng.com) | 06:33:06 |
 grg_2145 | Sorry I dod not check discord immediately in the meantime fyi I asked folti about it, hopefully it will be fixed soon. | 08:05:49 |
| mranno | Thank you | 08:06:54 |
|  @genofire:matrix.sum7.eu left the room. | 16:10:06 |
|  cyrusmc_22944 joined the room. | 21:50:58 |
| 1 Sep 2023 |
| grg_2145 | It lookes like that is is fine now 🙂 (for 2 years at least) | 08:51:18 |
| mranno | Sounds like a reasonable amount of time 😄 thank you, grg_2145 and Folti! | 08:58:41 |
| 4 Sep 2023 |
|  orionhungary joined the room. | 12:10:59 |
 hofione | Hi,
FYI
It seems the GitHub CI builds are failing continuously with some strange error, I can see the result, but not the reason. (My bet is some space issue again?!)
I asked Folti to check this out in the morning | 22:03:20 |
| 6 Sep 2023 |
|  f.stoeber joined the room. | 14:53:18 |
| f.stoeber changed their display name from f.stoeber to f.stoeber#0. | 15:12:44 |
| f.stoeber changed their display name from f.stoeber#0 to f.stoeber. | 15:12:45 |
| 7 Sep 2023 |
| hofione | Hi,
It's been a while i tried to build and run syslog-ng, but now I get an error when starting it (built from latest master)
iv_tls_user_register: called after iv_init
were there any changes in the last few weeks that could cause an issue like this? | 14:52:43 |
 bazsi77 | This is usually caused by a module that sits in your install directory which was compiled against an older syslog-ng version | 14:53:47 |
| bazsi77 | The old module pulls in an old libsyslog-ng.so version both initializing ivykis | 14:54:18 |
| hofione | thanks, cleaning up my install dest!
just curious, should not
cmake --build ./build -j 16 --target clean
clean up the install destination too? | 14:55:50 |
 czp | My experience on FreeBSD, where the compile is not in a chroot, like all the build system compile syslog-ng on SUSE or Fedora: if syslog-ng is installed, then syslog-ng compiled against the old libsyslog-ng.so and fails to start in many cases, as during installation the old lib is replaced by the new one... | 15:09:04 |
| bazsi77 | no, it just cleans your build dir. in automake there's an uninstall target along with install | 16:05:34 |
| 8 Sep 2023 |
| bazsi77 | hofione alexb271 I was reviewing the proxied-tcp changes (PR #4613) where I suggested to get rid off the old implementation. I delved into a bit more and stumbled into the niceties of the "multitransport" feature, which I don't like too much. At the moment, I can see a single user of it in the tree (the "proxied-tls-passthrough" logproto) and I was wondering if you had any out-of-tree user of it. | 04:41:12 |
| bazsi77 | Nevertheless, I think the proxies-tcp LogProto and constructor can be removed easily while leaving in the passthrough version, which we should also be able to remove, but maybe a bit more involved. I'd be willing to remove the partial "removal" for now. We will get to the rest eventually. | 04:42:35 |
| grg_2145 | HI bazsi77 I quickly cheked it, we indeed have a out of tree user of the multitransport user for it our ALTP implementation
If ytoure curious on what it is a good description for it is here https://support.oneidentity.com/technical-documents/syslog-ng-premium-edition/7.0.33/administration-guide/77#TOPIC-2036703 | 06:18:13 |
| grg_2145 | this is probably the reason why the multitransport thing exists in syslog-ng | 06:18:41 |
| mranno | Multitransport is used to implement STARTTLS functionality or to enable compression on-the-fly. | 07:04:29 |
