Logfile not accessible
list James Wade
I'm monitoring about 8 log files on a system, and on some of them, I'm getting a "Logfile not accessible" . I can login to the box as the hobbit user and cat the files out just fine. The privileges all match up with the other logfiles that are working just fine. Manually, I can see the files just fine. How does Hobbit try to read the log files? I would appreciate any suggestions. Thanks.James
list Buchan Milne
▸
On Tuesday 28 November 2006 01:02, James Wade wrote:
I'm monitoring about 8 log files on a system, and on some of them, I'm getting a "Logfile not accessible" . I can login to the box as the hobbit user and cat the files out just fine. The privileges all match up with the other logfiles that are working just fine. Manually, I can see the files just fine.
But, if you changed the hobbit user's group memberships since you last restarted the hobbit client, you would receive the new group when logging in, but the client would still be running without that group. So, try restarting the client. Regards, Buchan -- Buchan Milne ISP Systems Specialist - Monitoring/Authentication Team Leader B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
list James Wade
The group membership has always been the same. I've never changed it, and the group membership and ownership of the logfiles, both working and non-working are the same. How does Hobbit look at log files? A standard Cat, Grep, Tail? Can anyone give me a way to debug this? Thanks.....James
▸
-----Original Message-----
From: Buchan Milne [mailto:user-9b139aff4dec@xymon.invalid]
Sent: Tuesday, November 28, 2006 3:01 AM
To: user-ae9b8668bcde@xymon.invalid
Cc: James Wade
Subject: Re: [hobbit] Logfile not accessible
On Tuesday 28 November 2006 01:02, James Wade wrote:I'm monitoring about 8 log files on a system, and on some of them, I'm getting a "Logfile not accessible" . I can login to the box as the hobbit user and cat the files out just fine. The privileges all match up with the other logfiles that are working just fine. Manually, I can see the files just fine.
But, if you changed the hobbit user's group memberships since you last restarted the hobbit client, you would receive the new group when logging in, but the client would still be running without that group. So, try restarting the client. Regards, Buchan -- Buchan Milne ISP Systems Specialist - Monitoring/Authentication Team Leader B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
list Jerry Yu
what OS r u on ? could it be some ACL or SELinux policy or alike to forbid the process/daemon to access while interactive shell is ok?
▸
On 11/28/06, James Wade <user-659655b2ea05@xymon.invalid> wrote:The group membership has always been the same. I've never changed it, and the group membership and ownership of the logfiles, both working and non-working are the same. How does Hobbit look at log files? A standard Cat, Grep, Tail? Can anyone give me a way to debug this? Thanks.....James -----Original Message----- From: Buchan Milne [mailto:user-9b139aff4dec@xymon.invalid] Sent: Tuesday, November 28, 2006 3:01 AM To: user-ae9b8668bcde@xymon.invalid Cc: James Wade Subject: Re: [hobbit] Logfile not accessible On Tuesday 28 November 2006 01:02, James Wade wrote:I'm monitoring about 8 log files on a system, and on some of them, I'm getting a "Logfile not accessible" . I can login to the box as the hobbit user and cat the files out just fine. The privileges all match up with the other logfiles that are working just fine. Manually, I can see the files just fine.But, if you changed the hobbit user's group memberships since you last restarted the hobbit client, you would receive the new group when logging in, but the client would still be running without that group. So, try restarting the client. Regards, Buchan -- Buchan Milne ISP Systems Specialist - Monitoring/Authentication Team Leader B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
list Henrik Størner
▸
On Tue, Nov 28, 2006 at 08:52:41AM -0600, James Wade wrote:
The group membership has always been the same. I've never changed it, and the group membership and ownership of the logfiles, both working and non-working are the same. How does Hobbit look at log files? A standard Cat, Grep, Tail?
It uses Hobbit's "logfetch" utility, which basically opens the file for reading.
Can anyone give me a way to debug this?
Have you checked for errors in the client logs ? ~hobbit/client/logs/ on the client system. Regards, Henrik
list James Wade
Yes, I did. I've suspended monitoring the log files with problems for now. I'll try again later in the week. I had to work out another monitoring problem late last night. I'll send a email on the problem because I need assistance. Thanks....James
▸
-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Wednesday, November 29, 2006 6:36 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Logfile not accessible
On Tue, Nov 28, 2006 at 08:52:41AM -0600, James Wade wrote:The group membership has always been the same. I've never changed it, and the group membership and ownership of the logfiles, both working and non-working are the same. How does Hobbit look at log files? A standard Cat, Grep, Tail?
It uses Hobbit's "logfetch" utility, which basically opens the file for reading.
Can anyone give me a way to debug this?
Have you checked for errors in the client logs ? ~hobbit/client/logs/ on the client system. Regards, Henrik
list Usa Ims
Greetings everybody, I have this one log file that is going from yellow to green back to yellow every 3 minutes. The xymon-client is installed on a MySQL server. When the BB Display goes to yellow it indicates: Warnings in /opt/mysql/log-error/zzzzzz-error.log yellow Logfile not accessible But I see activity in the log. However, the log file does exists there with the proper permissions for everyone to read. -rw-r--r-- 1 mysql mysql 44143540 Oct 29 10:02 zzzzzz-error.log When it turns green, it indicates: No entries in /opt/mysql/log-error/zzzzzz-error.log Full log /opt/mysql/log-error/zzzzzz-error.log But I see activity in the log. What could be causing this flopping from green to yellow and back to green? Thanks in advance. usaims
list Jeremy Laidman
Every 3 minutes is a bit peculiar because the client message with the log entries gets sent every 5 minutes. Could it be that there are two client processes running at the same time? Permissions on the file look OK, but it could be that permissions on directory tree are not sufficient. J On 30/10/2014 1:15 AM, "usa ims via Xymon" <xymon at xymon.com> wrote:
---------- Forwarded message ---------- From: usa ims <user-42bb6445007b@xymon.invalid> To: xymon at xymon.com Cc: Date: Wed, 29 Oct 2014 07:08:55 -0700 Subject: Logfile not accessible
▸
Greetings everybody,
I have this one log file that is going from yellow to green back to yellow
every 3 minutes.
The xymon-client is installed on a MySQL server.
When the BB Display goes to yellow it indicates:
Warnings in /opt/mysql/log-error/zzzzzz-error.log
yellow Logfile not accessible
But I see activity in the log.
However, the log file does exists there with the proper permissions for
everyone to read.
-rw-r--r-- 1 mysql mysql 44143540 Oct 29 10:02 zzzzzz-error.log
When it turns green, it indicates:
No entries in /opt/mysql/log-error/zzzzzz-error.log
Full log /opt/mysql/log-error/zzzzzz-error.log
But I see activity in the log.
What could be causing this flopping from green to yellow and back to green?
Thanks in advance.
usaims
list Usa Ims
Hi, Lately I've been having a problem with one log file, it goes from green to yellow almost every 3 to 5 minutes. I'll get 'Logfile not accessible'. The logfile is in '/opt/mysql/log-error/xxxxxx-error.log' It exists, it has 777 permissions, it is constantly being written too, it is only 52 mgs. I have restarted xymon-client on the server. Here is the rest of the error: Full log /opt/mysql/log-error/xxxxxx-error.log Cannot open logfile /opt/mysql/log-error/xxxxxx-error.log : No such file or directory Here is the 'ls' command on it. -rwxrwxrwx 1 mysql mysql 54394406 Jan 7 16:23 /opt/mysql/log-error/xxxxxx-error.log Thanks in advance.
list Paul Root
My guess is that the xymon user doesn't have permissions in one of the directories in the tree. Do an "ls -l /opt /opt/mysql /opt/mysql/log-error"
▸
-----Original Message-----
From: usa ims [mailto:user-42bb6445007b@xymon.invalid]
Sent: Wednesday, January 07, 2015 3:27 PM
To: xymon at xymon.com
Subject: Logfile not accessible
Hi,
Lately I've been having a problem with one log file, it goes from green to yellow almost every 3 to 5 minutes.
I'll get 'Logfile not accessible'. The logfile is in '/opt/mysql/log-error/xxxxxx-error.log'
It exists, it has 777 permissions, it is constantly being written too, it is only 52 mgs.
I have restarted xymon-client on the server.
Here is the rest of the error:
Full log /opt/mysql/log-error/xxxxxx-error.log
Cannot open logfile /opt/mysql/log-error/xxxxxx-error.log : No such file or directory
Here is the 'ls' command on it.
-rwxrwxrwx 1 mysql mysql 54394406 Jan 7 16:23 /opt/mysql/log-error/xxxxxx-error.log
Thanks in advance.
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.