SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0003550: Notification problem in HA - MantisBT
MantisBT - Endian Firewall
View Issue Details
0003550Endian FirewallOther Servicespublic2011-03-21 12:032011-10-07 16:27
0003550: Notification problem in HA
In HA the SYNC between Master and Slave is detected as failed SSH login and *allot* of emails are sent.

A workaround would be ignoring the internal (Master/Slave) IP and ignore the mail notification.

Other problem (suggestion); In HA the mail notifications should be distinguished.
Issue History
2011-03-21 12:03ardit-endianNew Issue
2011-03-21 12:03ardit-endianTag Attached: purple
2011-03-21 12:16luca-endianNote Added: 0006000
2011-03-21 12:24lorenzo-endianAssigned To => peter-endian
2011-03-21 12:24lorenzo-endianStatusnew => confirmed
2011-03-24 15:41luca-endianNote Added: 0006009
2011-04-15 09:31luca-endianRelationship addedchild of 0001928
2011-06-07 11:05ardit-endianNote Added: 0006631
2011-07-05 16:06luca-endianNote Added: 0006887

2011-03-21 12:16   
in order to keep different configuration for endian notification we could exclude from the sync the folder: /var/efw/eventlog/config
2011-03-24 15:41   
by default this event notification is enabled..
2011-06-07 11:05   
A simple workaround (temporary until this is fixed) would be editing:

/etc/logsurfer/rules.d/ssh.tmpl and remove the first 2 lines.
Than: -df

This will stop the mail flood without further operations.
2011-07-05 16:06   
Fixed in this way:

root@efw-master:/etc/ha # cat exclude.conf

root@efw-slave:/var/efw/eventlog # cat config
        "event": "20200018",
        "mail_enabled": "off"
] -df

If slave has its own event notification configuration page would be possible to set up different event notification for master and slave.
By default of course the ssh connection successful event must not be available on slave