it also seems that your /var/log/snort directory is owned by root too. Please go to the upper directory and issue this command:
cd .. (assuming that your current directory thet you show in your initial posting is /something like
/var/log/snort and you are currently changing to this directory)
chown -R snort.snort snort
So instead of my previous chmod command use this one with -R in the uppr directory whre it holds snort logs directory.
Main Topics
Browse All Topics





by: KeremEPosted on 2009-05-04 at 16:14:06ID: 24300245
Hi,
It seems that your file permissions and ownership is wrong. The alert file should look like this:
-rw-r--r-- 1 snort snort 23959 2009-05-05 00:52 alert
so what you can do is changing the ownership of the file first with a command similar to this:
# chown snort.snort alert
# chmod 644 alert
In any case no log file should ever have executable attribute set.
A command like that generally shows you user and group setting of your snort:
# ps -aef | grep snort
such as:
snort 381 1 0 Mar31 ? 00:13:57 /usr/sbin/snort -c /etc/snort/snort.conf -D -u snort -g snort -d -e -o -p -b -A fast -m 022 -i eth2
at least you can try to locate your snort.conf and verify user and group info there (in my example it is located in /etc/snort
I hope this helps.
Cheers,
K.