UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1890 views

ovell-afptcpd information in /var/log/messages

I am trying to remove the afptcpd and dhcpd log entries in the /var/log/messages file. I followed TID 7004133 but they still keep showing up in messages file. I am running SP3 and do not know if it still works. Does anyone know how to do this or has more information on how to make this work?

Here is what I added to the syslog-ng.conf.in file: filter f_messages { not facility(news, mail) and not filter(f_iptables) and not filter(f_afptcp) and not filter(f_dhcpd); };
I then ran the SuSEconfig --verbose --module syslog-ng which gave me now errors. I then restarted the rcsyslog. I tested this on two different servers and it will not work on either.

Thank's for the help
Labels (2)
0 Likes
12 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

In article <gprater.52c9ko@no-mx.forums.novell.com>, Gprater wrote:
> I am trying to remove the afptcpd and dhcpd log entries in the
> /var/log/messages file
>

Now you have me trying the same thing for dhcp at one client, and that
exercise also showed that the dhcpd.log was getting rather large as
there wasn't a logrotate set for (used ntp as a base to get rotation
happening)
It appears to be working for me from the one log entry so far that is
in the dhcpd.log that is not in messages anymore (it is a Sunday
evening after all). I'll know better in the morning if it is properly
working.

I would check on your side that there are appropriate sections for,
filter f_dhcpd
filter f_afptcpd
and that they look healthy

from the one server of my client's that I just got it working
filter f_dhcpd { facility(daemon) and match('^dhcpd:'); };
destination dhcpmessages { file(var/log/dhcpd.log); };
log { source(src); filter(f_dhcpd); destination(dhcpmessages);};

It would also be worth posting the results of
cat /etc/*release
so that we can be better sure in any comparisons



Andy Konecny
KonecnyConsulting.ca in Toronto
-----------------------------------------------------------------------
-
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Fleet Admiral
Fleet Admiral

On 28/10/2011 23:16, gprater wrote:

> I am trying to remove the afptcpd and dhcpd log entries in the
> /var/log/messages file. I followed TID 7004133 but they still keep
> showing up in messages file. I am running SP3 and do not know if it
> still works. Does anyone know how to do this or has more information on
> how to make this work?


By SP3 do you mean OES2 SP3?

> Here is what I added to the syslog-ng.conf.in file: filter f_messages
> { not facility(news, mail) and not filter(f_iptables) and not
> filter(f_afptcp) and not filter(f_dhcpd); };
> I then ran the SuSEconfig --verbose --module syslog-ng which gave me
> now errors. I then restarted the rcsyslog. I tested this on two
> different servers and it will not work on either.


Reading the above you would appear to suggest that you added the line
"filter f_messages ..." line to syslog-ng.conf.in?

Since there is already a "filter f_messages ..." line in the file you
need to edit the existing line and not add another declaration for
f_messages. That would explain why you are still getting AFP and DHCP
messages in /var/log/messages since these are allowed by the existing
f_messages declaration.

HTH.
--
Simon
Novell Knowledge Partner (NKP)

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
Fleet Admiral
Fleet Admiral

On 31/10/2011 02:49, Andy Konecny wrote:

> I would check on your side that there are appropriate sections for,
> filter f_dhcpd
> filter f_afptcpd
> and that they look healthy


If these declarations are missing do not try adding them by hand.

Instead run /opt/novell/afptcpd/bin/upgrade_afp.sh as per the Additional
Information section of TID 7004133 to add the f_afptcpd declaration.

To add the f_dhcpd declaration you need to use
/opt/novell/dhcp/bin/dhcp_config.sh.

HTH.
--
Simon
Novell Knowledge Partner (NKP)

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
Absent Member.
Absent Member.

Here are the results of the release file.

SUSE Linux Enterprise Server 10 (i586)
VERSION = 10
PATCHLEVEL = 3
LSB_VERSION="core-2.0-noarch:core-3.0-noarch:core-2.0-ia32:core-3.0-ia32"
Novell Open Enterprise Server 2.0.3 (i586)
VERSION = 2.0.3
PATCHLEVEL = 3
BUILD
0 Likes
Absent Member.
Absent Member.

I did edit and add the information to the file. I just tried running the dhcp_config.sh and it is asking for an option. What should I use to add it file?
0 Likes
Fleet Admiral
Fleet Admiral

On 31/10/2011 15:36, gprater wrote:

> Here are the results of the release file.
>
> SUSE Linux Enterprise Server 10 (i586)
> VERSION = 10
> PATCHLEVEL = 3
> LSB_VERSION="core-2.0-noarch:core-3.0-noarch:core-2.0-ia32:core-3.0-ia32"
> Novell Open Enterprise Server 2.0.3 (i586)
> VERSION = 2.0.3
> PATCHLEVEL = 3
> BUILD


So that confirms 32-bit OES2 SP3 (on SLES10 SP3).

Please be aware that OES2 SP3 is now supported on SLES10 SP4 though I
don't expect that will help things in this case.

HTH.
--
Simon
Novell Knowledge Partner (NKP)

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
Fleet Admiral
Fleet Admiral

On 31/10/2011 15:46, gprater wrote:

> I did edit and add the information to the file. I just tried running the
> dhcp_config.sh and it is asking for an option. What should I use to add
> it file?


I think it might be useful if you posted the contents of your modified
syslog-ng.conf.in file, either as a reply here or via susepaste.org.
--
Simon
Novell Knowledge Partner (NKP)

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
Absent Member.
Absent Member.

Here are the contents of the file.

#@SuSEconfig@
#@SuSEconfig@ This is a template file used by SuSEconfig
#@SuSEconfig@ to generate the final syslog-ng.conf.
#@SuSEconfig@
#@SuSEconfig@ SuSEconfig adds additional log sockets from
#@SuSEconfig@ /etc/sysconfig/syslog to the source bellow.
#@SuSEconfig@
#
# File format description can be found in syslog-ng.conf(5)
# and /usr/share/doc/packages/syslog-ng/syslog-ng.txt.
#

#
# Global options.
#
options { long_hostnames(off); sync(0); perm(0640); stats(3600); };

#
# 'src' is our main source definition. you can add
# more sources driver definitions to it, or define
# your own sources, i.e.:
#
#source my_src { .... };
#
source src {
#
# include internal syslog-ng messages
# note: the internal() soure is required!
#
internal();

#
# the following line will be replaced by the
# socket list generated by SuSEconfig using
# variables from /etc/sysconfig/syslog:
#
@SuSEconfig_SOCKETS@

#
# uncomment to process log messages from network:
#
#udp(ip("0.0.0.0") port(514));
};


#
# Filter definitions
#
filter f_iptables { facility(kern) and match("IN=") and match("OUT="); };

filter f_console { level(warn) and facility(kern) and not filter(f_iptables)
or level(err) and not facility(authpriv); };

filter f_newsnotice { level(notice) and facility(news); };
filter f_newscrit { level(crit) and facility(news); };
filter f_newserr { level(err) and facility(news); };
filter f_news { facility(news); };

filter f_mailinfo { level(info) and facility(mail); };
filter f_mailwarn { level(warn) and facility(mail); };
filter f_mailerr { level(err, crit) and facility(mail); };
filter f_mail { facility(mail); };

filter f_cron { facility(cron); };

filter f_local { facility(local0, local1, local2, local3,
local4, local5, local6, local7); };

filter f_acpid { match('^\[acpid\]:'); };
filter f_netmgm { match('^NetworkManager:'); };

filter f_messages { not facility(news, mail) and not filter(f_iptables) and not filter(f_afptcp) and not filter(f_dhcpd); };
filter f_warn { level(warn, err, crit) and not filter(f_iptables); };
filter f_alert { level(alert); };


#
# Most warning and errors on tty10 and on the xconsole pipe:
#
destination console { pipe("/dev/tty10" group(tty) perm(0620)); };
log { source(src); filter(f_console); destination(console); };

destination xconsole { pipe("/dev/xconsole" group(tty) perm(0400)); };
log { source(src); filter(f_console); destination(xconsole); };

# Enable this, if you want that root is informed immediately,
# e.g. of logins:
#
#destination root { usertty("root"); };
#log { source(src); filter(f_alert); destination(root); };


#
# News-messages in separate files:
#
destination newscrit { file("/var/log/news/news.crit"
owner(news) group(news)); };
log { source(src); filter(f_newscrit); destination(newscrit); };

destination newserr { file("/var/log/news/news.err"
owner(news) group(news)); };
log { source(src); filter(f_newserr); destination(newserr); };

destination newsnotice { file("/var/log/news/news.notice"
owner(news) group(news)); };
log { source(src); filter(f_newsnotice); destination(newsnotice); };

#
# and optionally also all in one file:
# (don't forget to provide logrotation config)
#
#destination news { file("/var/log/news.all"); };
#log { source(src); filter(f_news); destination(news); };


#
# Mail-messages in separate files:
#
destination mailinfo { file("/var/log/mail.info"); };
log { source(src); filter(f_mailinfo); destination(mailinfo); };

destination mailwarn { file("/var/log/mail.warn"); };
log { source(src); filter(f_mailwarn); destination(mailwarn); };

destination mailerr { file("/var/log/mail.err" fsync(yes)); };
log { source(src); filter(f_mailerr); destination(mailerr); };

#
# and also all in one file:
#
destination mail { file("/var/log/mail"); };
log { source(src); filter(f_mail); destination(mail); };


#
# acpid messages in one file:
#
destination acpid { file("/var/log/acpid"); };
log { source(src); filter(f_acpid); destination(acpid); flags(final); };

#
# NetworkManager messages in one file:
#
destination netmgm { file("/var/log/NetworkManager"); };
log { source(src); filter(f_netmgm); destination(netmgm); flags(final); };


#
# Cron-messages in one file:
# (don't forget to provide logrotation config)
#
#destination cron { file("/var/log/cron"); };
#log { source(src); filter(f_cron); destination(cron); };


#
# Some boot scripts use/require local[1-7]:
#
destination localmessages { file("/var/log/localmessages"); };
log { source(src); filter(f_local); destination(localmessages); };


#
# All messages except iptables and the facilities news and mail:
#
destination messages { file("/var/log/messages"); };
log { source(src); filter(f_messages); destination(messages); };


#
# Firewall (iptables) messages in one file:
#
destination firewall { file("/var/log/firewall"); };
log { source(src); filter(f_iptables); destination(firewall); };


#
# Warnings (except iptables) in one file:
#
destination warn { file("/var/log/warn" fsync(yes)); };
log { source(src); filter(f_warn); destination(warn); };

#
# Enable this, if you want to keep all messages in one file:
# (don't forget to provide logrotation config)
#
#destination allmessages { file("/var/log/allmessages"); };
#log { source(src); destination(allmessages); };


filter f_dhcpd { facility(daemon) and match('^dhcpd:'); };
destination dhcpmessages { file(var/log/dhcpd.log); };
log { source(src); filter(f_dhcpd); destination(dhcpmessages);};
filter f_cifs {match('^CIFS');};
destination d_cifs {file("/var/log/cifs/cifs.log");};
log {source(src); filter (f_cifs); destination (d_cifs);};
filter f_afptcp {match('^afptcp');};
destination d_afptcpd {file("/var/log/afptcpd/afptcp.log");};
log {source(src); filter (f_afptcp); destination (d_afptcpd);};
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

In article <gprater.52hbin@no-mx.forums.novell.com>, Gprater wrote:
> I did edit and add the information to the file. I just tried running the
> dhcp_config.sh and it is asking for an option. What should I use to add
> it file?
>

Option? Perhaps more detail might be of use.

Pulling the dhcpd entries is working just fine for me now for the two
systems I fixed up last night. 64-bit OES2sp3 that were installed as sp2


Andy Konecny
KonecnyConsulting.ca in Toronto
------------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Fleet Admiral
Fleet Admiral

On 31/10/2011 19:06, gprater wrote:

> filter f_messages { not facility(news, mail) and not
> filter(f_iptables) and not filter(f_afptcp) and not filter(f_dhcpd); };


Is the above two lines or one continuous line that's wrapped? It's hard
to tell.

> filter f_dhcpd { facility(daemon) and match('^dhcpd:'); };
> destination dhcpmessages { file(var/log/dhcpd.log); };
> log { source(src); filter(f_dhcpd); destination(dhcpmessages);};
> filter f_cifs {match('^CIFS');};
> destination d_cifs {file("/var/log/cifs/cifs.log");};
> log {source(src); filter (f_cifs); destination (d_cifs);};
> filter f_afptcp {match('^afptcp');};
> destination d_afptcpd {file("/var/log/afptcpd/afptcp.log");};
> log {source(src); filter (f_afptcp); destination (d_afptcpd);};


Both f_dhcpd and f_afptcp (plus f_cifs) are defined so no need to run
either the upgrade_afp.sh or dhcp_config.sh scripts.

When you ran (run) "SuSEconfig --verbose --module syslog-ng" does it
warn that you have modified syslog-ng.conf as per the following snippet
from output?

"ATTENTION: You have modified //etc/syslog-ng/syslog-ng.conf. Leaving
it untouched...
You can find my version in //etc/syslog-ng/syslog-ng.conf.SuSEconfig..."

If so, that would explain why this isn't behaving because syslog-ng.conf
wasn't updated with syslog-ng.conf.SuSEconfig being created instead.

HTH.
--
Simon
Novell Knowledge Partner (NKP)

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
Absent Member.
Absent Member.

smflood;2150121 wrote:
On 28/10/2011 23:16, gprater wrote:

> I am trying to remove the afptcpd and dhcpd log entries in the
> /var/log/messages file. I followed TID 7004133 but they still keep
> showing up in messages file. I am running SP3 and do not know if it
> still works. Does anyone know how to do this or has more information on
> how to make this work?


By SP3 do you mean OES2 SP3?

> Here is what I added to the syslog-ng.conf.in file: filter f_messages
> { not facility(news, mail) and not filter(f_iptables) and not
> filter(f_afptcp) and not filter(f_dhcpd); };
> I then ran the SuSEconfig --verbose --module syslog-ng which gave me
> now errors. I then restarted the rcsyslog. I tested this on two
> different servers and it will not work on either.


Reading the above you would appear to suggest that you added the line
"filter f_messages ..." line to syslog-ng.conf.in?

Since there is already a "filter f_messages ..." line in the file you
need to edit the existing line and not add another declaration for
f_messages. That would explain why you are still getting AFP and DHCP
messages in /var/log/messages since these are allowed by the existing
f_messages declaration.

HTH.
--
Simon
Novell Knowledge Partner (NKP)

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------



Ok I checked and think I have it listed. Is this not correct?

# Filter definitions
#
filter f_iptables { facility(kern) and match("IN=") and match("OUT="); };

filter f_console { level(warn) and facility(kern) and not filter(f_iptables)
or level(err) and not facility(authpriv); };

filter f_newsnotice { level(notice) and facility(news); };
filter f_newscrit { level(crit) and facility(news); };
filter f_newserr { level(err) and facility(news); };
filter f_news { facility(news); };

filter f_mailinfo { level(info) and facility(mail); };
filter f_mailwarn { level(warn) and facility(mail); };
filter f_mailerr { level(err, crit) and facility(mail); };
filter f_mail { facility(mail); };

filter f_cron { facility(cron); };

filter f_local { facility(local0, local1, local2, local3,
local4, local5, local6, local7); };

filter f_acpid { match('^\[acpid\]:'); };
filter f_netmgm { match('^NetworkManager:'); };

filter f_messages { not facility(news, mail) and not filter(f_iptables) and not filter(f_afptcp) and not filter(f_dhcpd); };
filter f_warn { level(warn, err, crit) and not filter(f_iptables); };
filter f_alert { level(alert); };
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.