We thought that we had the same issue and what we determined was that the audit_protocol.log on the auditing node (node 1 in our case) was the only place that the audit_protocol.log(s) were updated. The Master node did have them in there as long as we had an entry in the //etc/mcp/override/syslog.conf file for logging to the file (we had two entries one for a logging host and one for the file locally). We then got rid of the local files as we didn't need them on the box and they turned over pretty quickly.
The other command I issued was :
isi audit settings modify --syslog-forwarding-enabled=yes --syslog-audit-events=close,create,delete,rename,set_security --zone={zone name] and this "kicked off" the logging.
Vieira1
25 Posts
0
April 12th, 2018 17:00
Hi!
Try to restart the syslogd!
isi_for_array 'pkill -SIGUSR1 syslogd'
Regards,
Vieira1
25 Posts
0
April 12th, 2018 17:00
Or you can use "isi_for_array -s "killall -HUP syslogd"
Regards,
P_frullani
7 Posts
0
April 13th, 2018 08:00
I have already tried, but nothing changed.
No one had this behavior ?
Pierluigi
akashS1
2 Posts
0
April 16th, 2018 02:00
The /var/log/audit_protocol.log file should be getting updated once you enable syslog forwarding.
Syslog forwarding should be enabled per access zone also. Hope you did that. If not, command to do that is,
isi audit settings modify --syslog-forwarding-enabled=yes --syslog-audit-events=close,create,delete --zone=zone3
Once enabled, protocol syslog will start getting written to /var/log/audit_protocol.log
Also, you can check for audit logs using
isi_for_array -s 'isi_audit_viewer -t protocol'
The syslog forwarding settings look fine. Hope it works after this.
P_frullani
7 Posts
0
April 16th, 2018 05:00
Thanks akashS for your answer.
I think there should be something strange in 8.1.0.0 as my settings seems to be fine:
IsilonTest-1# isi audit settings view
Audit Failure: create, delete, rename, set_security, close
Audit Success: create, delete, rename, set_security, close
Syslog Audit Events: create, delete, rename, set_security
Syslog Forwarding Enabled: Yes
IsilonTest-1# isi audit settings view --zone TestAccessZone
Audit Failure: create, delete, rename, set_security, close
Audit Success: create, delete, rename, set_security, close
Syslog Audit Events: create, delete, rename, set_security
Syslog Forwarding Enabled: Yes
and the isi_audit_viewer reports everything I do on my shares but either the /var/log/audit_protocol.log than the syslog don't get any lines.
I will try to get an 8.0.0.x virtual machine to see if is some sort of regression or similar.
Thanks.
Pierluigi
dkeith55
6 Posts
0
September 26th, 2018 11:00
We thought that we had the same issue and what we determined was that the audit_protocol.log on the auditing node (node 1 in our case) was the only place that the audit_protocol.log(s) were updated. The Master node did have them in there as long as we had an entry in the //etc/mcp/override/syslog.conf file for logging to the file (we had two entries one for a logging host and one for the file locally). We then got rid of the local files as we didn't need them on the box and they turned over pretty quickly.
The other command I issued was :
isi audit settings modify --syslog-forwarding-enabled=yes --syslog-audit-events=close,create,delete,rename,set_security --zone={zone name] and this "kicked off" the logging.