Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
It could be checking the wrong location (like /var/log/ instead) or the logging / monitoring application hasn't got appropriate access rights, or the file was deleted, or an attempt was made to rotate the log but logrotate couldn't create the file anew because the file system was full already (as in your http://www.linuxquestions.org/questi...ce-4175452117/).
Originally Posted by prathamesh7478
why i am getting this messages.
Your first thread was about copying huge files (let me guess: to /var), your second one was about /var being full so now the reason "why" isn't interesting but why you haven't gone over there yet to fix things good. If you're an admin you should know what to do (else ask an admin) or else spill some serious information like what services the machine runs, what files are open in /var, where there's enough free space to move files to, current space usage in /var, stuff like that.
This will show owners/perms and existing messages files.
Your messages.z can be read with zcat, unless its actually messages.Z, in which case use the uncompress cmd.
I'm guessing this is Solaris.
The error msg implies the old messages files has been rotated and the new one one not created or its been deleted or it cannot be created due to a full partition.
Can you run both du and df on that partition and post the results.
It may be a deleted file that is still being held open by a process.
Also run df -i to show the inodes usage.
PS if this has indeed already been solved, please post the soln, otherwise ask the Mods to undo the 'SOLVED' flag.
Moderator note: thread marked as unsolved, until the OP posts a solution (as requested). @prathamesh7478: as mentioned this thread is strictly related to the other one you started. Please, drive the discussion in only one place (here) to avoid confusion and to add information that can be useful to solve your issue(s). Thank you in advance.
The issue is resolved when we found out the messages file was compress
by some one so its extension had change messages.z.So the process using it could not find it.I just created a normal file messages and the issue was solved the alerts stopped automatically.