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
|Anonymous | Login||2019-04-23 17:55 UTC|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001489||Endian Firewall||Other Services||public||2008-11-28 00:14||2009-10-27 12:01|
|Target Version||Fixed in Version||2.3|
|Summary||0001489: Remote syslog not working|
|Description||I have a windows box configured as a syslogger on 10.0.0.10 port 514 which I know to be working correctly.|
I have a endian fw box (virtulaized on vmware workstation with 2 network interfaces - green [10.0.0.1] and red [192.168.0.1]). On Endian I have set the syslog settings to Remote with the ip address of the syslogger 10.0.0.10.
I am not recieving any syslog message from the Endian box.... I can ping the syslogger from the Endian box no problem....I have only one firewall rule which is allow any to any.
|Tags||No tags attached.|
It's working for us with linux boxes.
It's UDP, are you aware of that?
Can you capture traffic on your windows box in order to check if syslog packets arrive? They should..
Did not try to receive packets on a windows event logger. However that should also work.
I have the same problem as suk1. Have a centos 4.7 box that I log too. Use to work with Endian 2.1.2 but no with 2.2 rc3. I have restored from a 2.1.2 backup don't know if that might be the problem
same problem too on a fresh installation of 2.2RC3 (no update, no restore)
Syslog works fine on previous versions
One green, same lan 192.168.1.0/24 than my syslog windows station
After working deeper into the problem I could solve the issue by the following:
- mkdir /var/efw/ha (wasn't there before)
- echo "HA_ENABLED=off" >> /var/efw/ha/settings
- chown -R nobody:nobody /var/efw/ha
Maybe it helps someone else...
Yeap this solution fix the problem for me.
Remote logging is not working :-)
wow. nice one!
Seems that in last time we have more bugs which happen only on versions with some enterprise parts missing
However this is a really nice one. The problem is within the RecursiveNull class of Cheetah.
Your workaround certainly works also.
|2008-11-28 00:14||suk1||New Issue|
|2008-12-09 20:49||peter-endian||Note Added: 0001855|
|2008-12-11 05:53||fugazi||Note Added: 0001864|
|2008-12-17 09:56||StephCo||Note Added: 0001882|
|2009-02-14 16:38||marcus||Note Added: 0001963|
|2009-02-14 18:07||marcus||Note Added: 0001964|
|2009-02-14 18:09||marcus||Note Deleted: 0001963|
|2009-02-15 06:11||fugazi||Note Added: 0001965|
|2009-02-16 14:41||peter-endian||Note Added: 0001969|
|2009-02-16 14:41||peter-endian||Assigned To||=> peter-endian|
|2009-02-16 14:41||peter-endian||Status||new => confirmed|
|2009-02-16 14:46||peter-endian||Issue cloned: 0001565|
|2009-02-16 14:46||peter-endian||Relationship added||parent of 0001565|
|2009-02-19 17:05||peter-endian||Status||confirmed => resolved|
|2009-02-19 17:05||peter-endian||Fixed in Version||=> 2.3|
|2009-02-19 17:05||peter-endian||Resolution||open => fixed|
|2009-10-27 12:01||peter-endian||Status||resolved => closed|
|Copyright © 2000 - 2012 MantisBT Group|