Quote:
Originally Posted by AsgAnquietas
I'm sorry, TB0ne, but I don't understand half of what you are saying...
|
Obviously.
Quote:
|
"The automated report runs fine." - what automated report ? If you are reffering to the daily Logwatch, it also missed reporting vsftpd logs on Aug 8th and Aug 9th.
|
...and is picking things up going forward, *EXACTLY AS IT SHOULD*. Again, as you have logwatch configured, it pulls things from YESTERDAY....automatically...and it is WORKING.
Quote:
|
"You get the correct results when you run it for a limited range." - I don't know what you mean. When running with "--range '-X days'" it doesn't work OK for some specific days.
|
Right...meaning it's working *GOING FORWARD*...exactly as you have it configured. Can't get what's not there, and you're just not understanding this.
Quote:
|
"Yet (somehow) there's a problem with logwatch??" - OF COURSE there is a problem with Logwatch. VSFTPD logs fine. Logwatch misses the logs for specific days...
|
...which you have it configured to do. Again, you can go back one more day now than you could before....indicating that logwatch is working. Again, you have logrotate in the mix, yet have logwatch configured to NOT look at things going backwards (the "archive" flag).
Quote:
|
"We *STILL* understand what you're saying, so restating the problem adds nothing new...you need to think about what you're posting, though" --- what ??? I don't know what you mean. I replied to another forum member, that's why I reposted. What's wrong with that ?
|
Stating the exact same things over and over do NOT add any new information to the issue, and only clutters up the thread.
Quote:
"EVERYTHING you're posting indicates that logwatch is running the way it should" --- it's obvious that you still don't understand the problem ! IT DOESN'T WORK OK !!!
"Not processing files that logrotate is handlding, since # Archives = No" --- ok, so what ? I need to process from vsftpd.log, which is not an archive.
"Detail is NOT set to high: Detail = Low" --- i've set it to High, still no results. There are CLEARLY LOGS of VSFTPD in Aug 8th and Aug 9th, which Logwatch misses them.
|
You just don't understand the answers...we can only explain it to you, but we can't understand it for you.
Quote:
"Have you checked /usr/share/logwatch/scripts/services/* for the appropriate vsftpd file?" --- yes, I checked the file.
"Because you have, Service = All, instead of specifying the service which you said you did." --- yes, I also have other services reported by Logwatch.
Here it's the vsftpd service file from Logwatch:
Code:
scpej-hga [~] # cat /usr/share/logwatch/default.conf/services/vsftpd.conf
# You can put comments anywhere you want to. They are effective for the
# rest of the line.
# this is in the format of <name> = <value>. Whitespace at the beginning
# and end of the lines is removed. Whitespace before and after the = sign
# is removed. Everything is case *insensitive*.
# Yes = True = On = 1
# No = False = Off = 0
Title = vsftpd-messages
# Which logfile group...
LogFile = vsftpd
# *OnlyService = vsftpd
*RemoveHeaders =
# Set this to 1 if you want to ignore unmatched FTP messages...
$vsftpd_ignore_unmatched = 0
# Set this to 1 if you want to ignore requests for robots.txt
$vsftpd_ignore_robots = 0
# NOTE: Be sure to add these to your FTP server's vsftpd.conf file:
# (NOT this logwatch configuration file)
# xferlog_enable=YES
# xferlog_std_format=YES
# dual_log_enable=YES
# vi: shiftwidth=3 tabstop=3 et
|
...and did you add those lines to vsftpd.conf, and restart the service???
AGAIN: logwatch is picking things up going forward. You have it configured to do that...unsure of what results you're expecting, or how many times it needs to be explained to you, on the three different forums you've posted this same thing.
Good luck.
