Unable to log #2023
Replies: 3 comments 1 reply
-
I believe the Debian package would be Also to note, |
Beta Was this translation helpful? Give feedback.
-
@genius3000 is correct about AppArmor and the default path although Also, 100 is an incredibly high flush value for logging. You should probably lower it to something sensible like 10 or omit it to use the default. You may also want to consider using our .deb packages as they're more frequently updated than the Debian ones. |
Beta Was this translation helpful? Give feedback.
-
Thank you both for the suggestions. Things are working as expected now using the .deb package and this configuration:
Would it be possible to update the documentation to specify the path is absolute? https://docs.inspircd.org/3/configuration/#path |
Beta Was this translation helpful? Give feedback.
-
Description
Unable to enable logging
Steps to reproduce the issue:
mkdir /etc/inspircd/logs && chown irc:irc /etc/inspircd/logs
systemctl restart inspircd
I would expect to see something similar to the output of
journalctl -u inspircd.service
logged to /etc/inspircd/logs/ircd.log or even under /var/logs/inspircd.log.I see no ircd.log file created under /etc/inspircd/logs.
I see there was a similar issue here: inspircd/docker#106
But I am using the standard file name and still experience this issue.
./bin/inspircd --version
: InspIRCd-3.12.0-debianBeta Was this translation helpful? Give feedback.
All reactions