Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 'ERR ntpd' to loganalyzer ignore files #816

Merged
merged 1 commit into from
Mar 6, 2019

Conversation

romankachur-mlnx
Copy link
Contributor

Signed-off-by: Roman Kachur romankac@mellanox.com

Description of PR

Summary:
The fact that ntpd daemon produces sporadical ERR messages into syslog
https://github.com/ntp-project/ntp/issues/23
becames false positive condition for Loganalyzer,
which analyzes syslog and fails test with:
ERR ntpd[7534]: routing socket reports: No buffer space available

Type of change

  • [] Bug fix
  • [] Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Approach

How did you do it?

I added ntpd ERR to Loganalyzer excluded lists
roles/test/files/tools/loganalyzer/loganalyzer_common_ignore.txt roles/test/tasks/acl/acltb_ignore_messages.txt roles/test/tasks/fib/fib_ignore_messages.txt roles/test/tasks/lag/lag_ignore_messages.txt roles/test/tasks/pfc_wd/config_test/config_test_ignore_messages roles/test/tasks/pfc_wd/functional_test/ignore_pfc_wd_messages

How did you verify/test it?

Taking a piece of syslog with

start-LogAnalyzer-mgtest.2019-02-06.20:56:15
............................................
Feb  6 20:56:55.719124 mts-sonic-dut ERR ntpd[7859]: routing socket reports: No buffer space available
Feb  6 20:56:55.727391 mts-sonic-dut ERR ntpd[7859]: routing socket reports: No buffer space available
Feb  6 20:56:55.799915 mts-sonic-dut ERR ntpd[7859]: routing socket reports: No buffer space available
Feb  6 20:56:55.831232 mts-sonic-dut ERR ntpd[7859]: routing socket reports: No buffer space available
............................................

I initiated Loganalyzer
python loganalyzer.py --action analyze --logs /tmp/syslog --run_id mgtest.2019-02-06.20:56:15 --out_dir /tmp/mgtest.2019-02-05.20:20:35 -m loganalyzer_common_match.txt -i loganalyzer_common_ignore.txt -e loganalyzer_common_expect.txt -v
which finished clear

Expected and found matches: 0
Total matches: 0
Total expected and found matches: 0
Total expected but not found matches: 0

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

Signed-off-by: Roman Kachur <romankac@mellanox.com>
@andriymoroz-mlnx andriymoroz-mlnx requested a review from yxieca March 6, 2019 15:46
@yxieca yxieca merged commit 358b3d7 into sonic-net:master Mar 6, 2019
yxieca pushed a commit that referenced this pull request Mar 7, 2019
Signed-off-by: Roman Kachur <romankac@mellanox.com>
@yxieca
Copy link
Collaborator

yxieca commented Mar 7, 2019

Made to 201811 branch on 3/6/2019

liat-grozovik pushed a commit that referenced this pull request Apr 24, 2019
…les (#865)

The ntpd may generate 'ERR ntpd' in syslog and caused unnecessary test
case failure. Previous PR #816
added a matching pattern of 'ERR ntpd' in loganalyzer igonre files to
ignore the ntpd error messages. However, ntpd may generate two formats
of error messages. The previously added matching pattern can only match
one of the formats. This change is to update the pattern to match both
of the formats.

Signed-off-by: Xin Wang <xinw@mellanox.com>
yxieca pushed a commit that referenced this pull request Apr 26, 2019
…les (#865)

The ntpd may generate 'ERR ntpd' in syslog and caused unnecessary test
case failure. Previous PR #816
added a matching pattern of 'ERR ntpd' in loganalyzer igonre files to
ignore the ntpd error messages. However, ntpd may generate two formats
of error messages. The previously added matching pattern can only match
one of the formats. This change is to update the pattern to match both
of the formats.

Signed-off-by: Xin Wang <xinw@mellanox.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants