Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-822 Topic 10 Question 66 Discussion

Actual exam question for Oracle's 1Z0-822 exam
Question #: 66
Topic #: 10
[All 1Z0-822 Questions]

You are mentoring a colleague who recently added a local7.notice entry to the /etc/syslog.conf file. After restarting the logging service, your colleague notices that no new records are being logged and asks for your help. Included in the file are these entries:

...

(19)*.alert root

(20)*.emerg *

(21)local7.notice /var/log/Appx.log

...

While running the syslogd process in debug mode, you notice the following:

You examine the /var/adm/messages file:

Jan 6 00:23:10 so111-server syslogd: line 21: unknown priority name ''notice ''

What do you identify as the cause of the problem?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Zoila
1 months ago
I bet the application logging to /var/log/Appx.log just doesn't use the notice priority. It's always something with those finicky apps, isn't it?
upvoted 0 times
...
Mari
1 months ago
You know, I once had a syslog issue where there was a hidden character at the end of the line. Gotta watch out for those sneaky gremlins!
upvoted 0 times
Louis
10 days ago
C) There is an extra space in line 21 in the /etc/syslog.comf file.
upvoted 0 times
...
Bethanie
14 days ago
B) The application that logs to /var/log/Appx.log does not support the notice priority.
upvoted 0 times
...
Stephen
19 days ago
A) There is a control or nonprintable character at the end of line 21 in the /etc/syslog.conf file.
upvoted 0 times
...
...
Abel
2 months ago
Hmm, I'd check the facility first. Local7 not supporting the notice priority seems like the most likely culprit here.
upvoted 0 times
Ernestine
14 days ago
User 3: Let's verify if local7 indeed does not support the notice priority.
upvoted 0 times
...
Huey
15 days ago
User 2: That could be it. Maybe we should double-check that.
upvoted 0 times
...
Lilli
1 months ago
User 1: I think the issue might be with the facility local7 not supporting the notice priority.
upvoted 0 times
...
...
Gregoria
2 months ago
The extra space in line 21 of the /etc/syslog.conf file must be the issue. That's a silly mistake, but easy to overlook.
upvoted 0 times
Justa
4 days ago
Should I remove the space and restart the logging service?
upvoted 0 times
...
Hassie
8 days ago
That makes sense. It's easy to miss small details like that.
upvoted 0 times
...
Shantay
13 days ago
Yes, you are correct. The extra space in line 21 is causing the issue.
upvoted 0 times
...
Gene
14 days ago
Thank you for your help. I'll make that change right away.
upvoted 0 times
...
Melodie
15 days ago
Yes, that should fix the problem. Just remove the space and restart the logging service.
upvoted 0 times
...
Alesia
1 months ago
So, should I just remove the extra space from line 21?
upvoted 0 times
...
Laura
1 months ago
Yes, you are correct. The extra space in line 21 is causing the issue.
upvoted 0 times
...
...
Zita
2 months ago
I believe option C is the cause, there seems to be an extra space in line 21.
upvoted 0 times
...
Elmer
2 months ago
I agree with Nobuko, there might be a control character at the end of line 21.
upvoted 0 times
...
Nobuko
2 months ago
I think the cause of the problem is option A.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77