You can have them both running at the same time.
Is you syslog running?
Check
systemctl status rsyslogd.
The logging system has changed from the old syslog-ng to systemd's
rsyslogd.
As per man page (5) of rsyslog.conf I set the strings to
have inn2 logging separated by file, but even restarting inn2 and
systemd nothing is logged in those files, only in /var/log/news/news
and I can't understand why.
On 01/12/2023 12:28, Marco Moock wrote:
You can have them both running at the same time.
IHMO it's not a good idea having 2 system for logging
Is you syslog running?
Check
systemctl status rsyslogd.
Yep, all system logging correctly, only news and inn nothing.
*********************
# Configurazione per i messaggi di livello critico di news
news.=crit -/var/log/news/news.crit
# Configurazione per i messaggi di errore di news
news.=err -/var/log/news/news.err
# Configurazione per i messaggi di livello notice di news
news.=notice -/var/log/news/news.notice
# Configurazione per i messaggi di debug di news
news.=debug -/var/log/news/news.debug
*********************
*********************
# Configurazione per i messaggi di livello critico di news
news.=crit -/var/log/news/news.crit
# Configurazione per i messaggi di errore di news
news.=err -/var/log/news/news.err
# Configurazione per i messaggi di livello notice di news
news.=notice -/var/log/news/news.notice
# Configurazione per i messaggi di debug di news
news.=debug -/var/log/news/news.debug
*********************
Hi,
Ivo Gandolfo a tapoté le 01/12/2023 10:46:
*********************
# Configurazione per i messaggi di livello critico di news
news.=crit -/var/log/news/news.crit
# Configurazione per i messaggi di errore di news
news.=err -/var/log/news/news.err
# Configurazione per i messaggi di livello notice di news
news.=notice -/var/log/news/news.notice
# Configurazione per i messaggi di debug di news
news.=debug -/var/log/news/news.debug
*********************
On debian stable, in /etc/rsyslog.d/news.conf I have :
#############AJouté ######################################
#
# Logging for INN news system.
#
news.crit /var/log/news/news.crit
news.err /var/log/news/news.err
news.notice -/var/log/news/news.notice ##########################################################
Can you find the lines in the /var/log/syslog or /var/log/messages
files?
Do they show up in journald?
journalctl |grep inn
should show them.
On debian stable, in /etc/rsyslog.d/news.conf I have :
#############AJouté ######################################
#
# Logging for INN news system.
#
news.crit /var/log/news/news.crit >> news.err /var/log/news/news.err >> news.notice -/var/log/news/news.notice >> ##########################################################
I can confirm this works fine on Debian Bookworm (stable). It is the
same config as mine, and it works here. Not sure what might be
different in Ubuntu.
If you see it on syslog, it is most likely a problem with the syslog
config.
Does the identifier of the log file lines is the same as in the config?
Hi Marco, on syslog I see the duplicate of /var/log/news/news file
(start inn, stop, restart, reload, message coming from peer etc) but
nothing else (ad example my post from rnews or nrppd).
It was almost certain that it was a problem with rsyslogd and its configuration, but since yamò and RetroGuy have a similar OS (debian)
and I was trying to use the same configuration and it wasn't working,
this situation created a lot of frustration.
Did you now figured out what the problem was?
On 01/12/2023 17:20, Marco Moock wrote:
If you see it on syslog, it is most likely a problem with the syslog
config.
Does the identifier of the log file lines is the same as in the config?
It was almost certain that it was a problem with rsyslogd and its configuration, but since yamò and RetroGuy have a similar OS (debian)
and I was trying to use the same configuration and it wasn't working,
this situation created a lot of frustration.
On 01/12/2023 19:36, Marco Moock wrote:
Did you now figured out what the problem was?
Nope. I'm trying some test, but at this moment no :/
Ivo Gandolfo <usenet@bofh.team> writes:
On 01/12/2023 19:36, Marco Moock wrote:
Did you now figured out what the problem was?
Nope. I'm trying some test, but at this moment no :/
I have had similiar problem.
I found that in newest debian developers add/changed systemd unit file.
I found when I use systemd with
CapabilityBoundingSet=...
commented rsyslog start to log in.
But I had not time to check problem deeper.
KJ
On Dec 2, 2023 at 7:16:38 AM CST, "Kamil Jońca" <kjonca@poczta.onet.pl> wrote:
Ivo Gandolfo <usenet@bofh.team> writes:
On 01/12/2023 19:36, Marco Moock wrote:
Did you now figured out what the problem was?
Nope. I'm trying some test, but at this moment no :/
I have had similiar problem.
I found that in newest debian developers add/changed systemd unit file.
I found when I use systemd with
CapabilityBoundingSet=...
commented rsyslog start to log in.
But I had not time to check problem deeper.
KJ
What is the entire contents of the CapabilityBoundingSet value in the Debian rsyslog systemd unit file?
On 02/12/2023 14:57, Kamil Jońca wrote:
But without success.
I am not sure if problem is with directory owner(s) or something else.
KJ
In my case the file /etc/systemd/system.conf entire file is commented #.
I will try with your setup.
Sincerely
But without success.
I am not sure if problem is with directory owner(s) or something else.
KJ
On 02/12/2023 15:59, Ivo Gandolfo wrote:
On 02/12/2023 14:57, Kamil Jońca wrote:
But without success.
I am not sure if problem is with directory owner(s) or something else.
KJ
In my case the file /etc/systemd/system.conf entire file is commented #.
I will try with your setup.
Sincerely
Just tested and nothing appens... Seem's rsyslogd don't have pleasure to
work with news inn2...
Sincerely
Just tested and nothing appens... Seem's rsyslogd don't have pleasure
to work with news inn2...
On 02/12/2023 15:59, Ivo Gandolfo wrote:
On 02/12/2023 14:57, Kamil Jońca wrote:
But without success.
I am not sure if problem is with directory owner(s) or something else.
KJ
In my case the file /etc/systemd/system.conf entire file is commented #.
I will try with your setup.
Sincerely
Just tested and nothing appens... Seem's rsyslogd don't have pleasure to
work with news inn2...
Sincerely
Check
/etc/systemd/journald.conf
for:
ForwardToSyslog=yes
HTH
Today I updated my distro and ran into a problem.
The logging system has changed from the old syslog-ng to systemd's
rsyslogd.
As per man page (5) of rsyslog.conf I set the strings to have inn2
logging separated by file, but even restarting inn2 and systemd nothing
is logged in those files, only in /var/log/news/news and I can't
understand why.
I don't know whether your issue is now solved. Just in case, maybe it
comes from the fact that your rsyslog package does not provide /etc/rsyslog.d/news.conf; Marco added one last week in the
2.7.2~20231223-1 Debian package.
[/etc/rsyslog.d/news.conf]
#
# Logging for the INN news system.
#
news.crit action(type="omfile" file="/var/log/news/news.crit" fileOwner="news" fileGroup="news" createDirs="off")
news.err action(type="omfile" file="/var/log/news/news.err" fileOwner="news" fileGroup="news" createDirs="off")
news.notice action(type="omfile" file="/var/log/news/news.notice" fileOwner="news" fileGroup="news" createDirs="off")
Today I updated my distro and ran into a problem.
The logging system has changed from the old syslog-ng to systemd's
rsyslogd.
As per man page (5) of rsyslog.conf I set the strings to have inn2
logging separated by file, but even restarting inn2 and systemd nothing
is logged in those files, only in /var/log/news/news and I can't
understand why.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 63:57:36 |
Calls: | 6,712 |
Files: | 12,244 |
Messages: | 5,356,076 |