Remote logging problem

Hi,

I try to setup remote logging from MT (2.9.27) to unix machine but without any success, MT not send anything… I try MT_syslog too on win machine but the same result (when I send message from MT_syslog to unix it works), MT send nothing and I not see in MT any connections to port 514.
Whats wrong ? I try it on 2.9.27 and on one old version 2.9.7 too but still nothnig :frowning:

Anyone have ideas ?

/Tomi

nobody ? everybody have it working without problems ?? :frowning:

/Tomi


Hai tom...and jerry

nice to tell you about my experince, my MT_Syslog is working fine until now, we make remote all my MT RouterOSs like centalize. my MT_sylog run under Microsoft Windows. you can customize logging system and login in on your router goto:

/sy lo
put any topics with "action=remote" as you will make remote topic

/sy lo ac
assign any ip with "remote=your_destination_ip_machine:514"

make sure you has MT_sylog.exe at destination machine and must match with 'remote-action'
i thing that correct config will success to make downloading any incident on your router.

so sorry friend, an english is not well

good luck!

regards
BalimoreDOTcom

thanks for answer, but you describe only setup. I have setup already but problem is in , why MT not send any data out when is set to remote logging, I sniff traffic but nothing goes from MT → remote_host:514, nothing… I try various config in MT but nothing help, still silence…

/Tomi

set in logging to log in MT device and same thing go to remote, and check if something happens to be logged :unamused: baybe that helps you out

normal logging works, only remote not, here is the config what I use (but I try many other various combination)
/ system logging
add topics=info prefix=“” action=disk disabled=no
add topics=error prefix=“” action=disk disabled=no
add topics=warning prefix=“” action=disk disabled=no
add topics=critical prefix=“” action=disk disabled=no
add topics=pptp prefix=“” action=disk disabled=no
add topics=warning,error,critical,system,web-proxy,event,state,notification,deb
ug,packet,firewall,info prefix=“mk01” action=remote disabled=no
/ system logging action
set memory name=“memory” target=memory memory-lines=100 memory-stop-on-full=no
set disk name=“disk” target=disk disk-lines=10000 disk-stop-on-full=no
set echo name=“echo” target=echo remember=yes
set remote name=“remote” target=remote remote=192.168.0.12:514

/Tomi


Hai, Tom....
The script, i thing read from top to bottom, i thing too when is the action already done the second one is not valid, so. sorry if i am wrong...

/system logging
add topics=info prefix="" action=remote disabled=no 
add topics=error prefix="" action=remote disabled=no 
add topics=warning prefix="" action=remote disabled=no 
add topics=critical prefix="" action=remote disabled=no 
add topics=pptp prefix="" action=remote disabled=no 
add topics=warning,error,critical,system,web-proxy,event,state,notification,deb\
    ug,packet,firewall,info prefix="mk01" action=remote disabled=no

until now my MT_syslog Downloader is work fine with remote to MS Windows XP

regrads
BalimoreDOTcom

thanks to all, now I find problem, remote logging dont want work until anything is logged localy. After disabling all local logs , remote start working, its little strange but ok :slight_smile:

/Tomi


Hai Tom...and Jerry

Yes, little strange but good handling, i think. that's will make router nice to process not too much log entry, your action solution is increase space your RAM or DISK, prioritise that action for RB is better. that's my logica, sorry when is not true :wink:

regards
Hasbullah.com