# ssh user@192.168.0.9 queue simple print
Works for me on 5.2:We are having issues with ssh too with 5.x.
We've got 100 Mikrotiks aprox in our network. We have some scritps running in linux servers that perform regular backups and maintenance tasks to Mikrotiks through ssh. Everything worked flawlessly till we upgraded some devices to 5.x(5.0 and 5.2).
It's a weird issue, if I execute from a linux terminal something like:
ssh -i id_dsa admin@10.1.2.3 "/export" > backup1.bak
ssh -i id_dsa admin@10.1.2.3 "/tools user-mana sess print where active" > act_sess.txt
it works, but when commands like this are in a script launched from cron, it doesn't works. No error displayed anywhere. Mikrotik's device log shows the connection/disconnection. If you perform any action, Eg: "/inter ether1 disable", it is executed.
Problem only appears to me when you issue some comand to Mikrotik device through a ssh scheduled in cron. The command is executed but it's stdout isn't recieved. I know, it's weird
It only occurs with 5.x. We've got those scripts runing for more than one year without any issue.
sh-3.2# ssh -i ~/.ssh/scripts_ro_id_dsa scripts_ro@66.78.251.41 "/ip fire man exp"
# may/13/2011 08:59:01 by RouterOS 5.2
# software id = WTPH-Z5E2
#
sh-3.2# ssh -i ~/.ssh/scripts_ro_id_dsa scripts_ro@66.78.251.41 "/ip fire man exp" > output.txt
sh-3.2# more output.txt
# may/13/2011 08:59:07 by RouterOS 5.2
# software id = WTPH-Z5E2
#
sh-3.2#
sh-3.2# crontab -e
crontab: installing new crontab
sh-3.2# crontab -l | grep ssh
5 9 * * * ssh -i ~/.ssh/scripts_ro_id_dsa scripts_ro@66.78.251.41 "/ip fire man exp" > /tmp/output_cron.txt
sh-3.2# date
Fri May 13 09:00:14 PDT 2011
sh-3.2#
sh-3.2# date
Fri May 13 09:05:14 PDT 2011
sh-3.2# more output_cron.txt
# may/13/2011 09:05:11 by RouterOS 5.2
# software id = WTPH-Z5E2
#
sh-3.2#
ssh user@mik.ro.tik.ip '/export' |wc -cWrite failed: Broken pipehello fewi.Works for me on 5.2:We are having issues with ssh too with 5.x.
We've got 100 Mikrotiks aprox in our network. We have some scritps running in linux servers that perform regular backups and maintenance tasks to Mikrotiks through ssh. Everything worked flawlessly till we upgraded some devices to 5.x(5.0 and 5.2).
It's a weird issue, if I execute from a linux terminal something like:
ssh -i id_dsa admin@10.1.2.3 "/export" > backup1.bak
ssh -i id_dsa admin@10.1.2.3 "/tools user-mana sess print where active" > act_sess.txt
it works, but when commands like this are in a script launched from cron, it doesn't works. No error displayed anywhere. Mikrotik's device log shows the connection/disconnection. If you perform any action, Eg: "/inter ether1 disable", it is executed.
Problem only appears to me when you issue some comand to Mikrotik device through a ssh scheduled in cron. The command is executed but it's stdout isn't recieved. I know, it's weird
It only occurs with 5.x. We've got those scripts runing for more than one year without any issue.
Code: Select allsh-3.2# ssh -i ~/.ssh/scripts_ro_id_dsa scripts_ro@66.78.251.41 "/ip fire man exp" # may/13/2011 08:59:01 by RouterOS 5.2 # software id = WTPH-Z5E2 # sh-3.2# ssh -i ~/.ssh/scripts_ro_id_dsa scripts_ro@66.78.251.41 "/ip fire man exp" > output.txt sh-3.2# more output.txt # may/13/2011 08:59:07 by RouterOS 5.2 # software id = WTPH-Z5E2 # sh-3.2# sh-3.2# crontab -e crontab: installing new crontab sh-3.2# crontab -l | grep ssh 5 9 * * * ssh -i ~/.ssh/scripts_ro_id_dsa scripts_ro@66.78.251.41 "/ip fire man exp" > /tmp/output_cron.txt sh-3.2# date Fri May 13 09:00:14 PDT 2011 sh-3.2# sh-3.2# date Fri May 13 09:05:14 PDT 2011 sh-3.2# more output_cron.txt # may/13/2011 09:05:11 by RouterOS 5.2 # software id = WTPH-Z5E2 # sh-3.2#
