I've configured Mass Config Push to run a security review of our Mikrotik devices.
commands are:
/ip service export
/user export
This gives normal output in windows terminal window as expected.
However, when running Mass Config Push, it shows that the config push was run but no output shows up at all.
Mass Config Push is showing no output after running.
Hi,
Can you please enable both "Debug logging" and "Device output logging" under "Zones > your_zone > Debug mode" and re-run the push (on just one device is sufficient)? After, please upload the relevant parts from both logs, as well as a screenshot of the Output Group in Config Push please.
Thanks!
Can you please enable both "Debug logging" and "Device output logging" under "Zones > your_zone > Debug mode" and re-run the push (on just one device is sufficient)? After, please upload the relevant parts from both logs, as well as a screenshot of the Output Group in Config Push please.
Thanks!
No output from the device_output log. We are using the remote cores also if that helps.
The Last Run: time is wrong as well. It doesn't show the time I clicked on run now. I had to configure it to run on a schedule for the first run to work partially right.
Unimus.log
-----
2021-04-09 15:31:55.936 DEBUG 2340 --- [io-reader-9] net.unimus.core.api.RequestReceiverImpl : Processing 'GetLogFileRequest(opId=95921cd9-7739-4ef5-88b3-fa45213b809c, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b)'
2021-04-09 15:31:55.937 DEBUG 2340 --- [io-reader-9] n.u.c.a.h.GetLogFileRequestHandler : Getting log file
2021-04-09 15:31:55.937 DEBUG 2340 --- [io-reader-9] n.u.c.a.h.GetLogFileRequestHandler : Reading content of 'C:\ProgramData\Unimus-Core\log\unimus-core.log'
device_output.log
-----
empty
The Last Run: time is wrong as well. It doesn't show the time I clicked on run now. I had to configure it to run on a schedule for the first run to work partially right.
Unimus.log
-----
2021-04-09 15:31:55.936 DEBUG 2340 --- [io-reader-9] net.unimus.core.api.RequestReceiverImpl : Processing 'GetLogFileRequest(opId=95921cd9-7739-4ef5-88b3-fa45213b809c, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b)'
2021-04-09 15:31:55.937 DEBUG 2340 --- [io-reader-9] n.u.c.a.h.GetLogFileRequestHandler : Getting log file
2021-04-09 15:31:55.937 DEBUG 2340 --- [io-reader-9] n.u.c.a.h.GetLogFileRequestHandler : Reading content of 'C:\ProgramData\Unimus-Core\log\unimus-core.log'
device_output.log
-----
empty
I scheduled the test and ran it on the schedule. Debug output appears that it ran, logged in and provided the correct output, but the output is not show up in the Unimus GUI.
Unimus.log
-----
device output log
-----
Unimus.log
-----
Code: Select all
2021-04-09 16:16:04.950 DEBUG 2340 --- [io-reader-4] net.unimus.core.api.RequestReceiverImpl : Processing 'PushBatchRequest{, pushPresetId=6, commands='/ip service export
/user export
', requireEnableMode=false, requireConfigureMode=false, devices=1}'
2021-04-09 16:16:04.951 DEBUG 2340 --- [io-reader-4] u.c.a.h.OperationPushStartRequestHandler : Processing discovery operation request with '1' job(s)
2021-04-09 16:16:04.952 DEBUG 2340 --- [io-reader-4] u.c.a.h.OperationPushStartRequestHandler : Creating and registering job(s)
2021-04-09 16:16:04.952 DEBUG 2340 --- [io-reader-4] n.u.core.api.registry.JobRegistryImpl : Registering 'net.unimus.core.api.job.PushJob@bee9a92a'
2021-04-09 16:16:04.952 DEBUG 2340 --- [io-reader-4] u.c.a.h.OperationPushStartRequestHandler : Registered '1' job(s)
2021-04-09 16:16:04.952 DEBUG 2340 --- [io-reader-4] u.c.a.h.OperationPushStartRequestHandler : Sending operation start response
2021-04-09 16:16:04.952 TRACE 2340 --- [io-reader-4] n.u.core.api.ForwardingResponseSender : Sending 'OperationStartResponse(opId=CPO-6, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b, acceptedJobs=[D-0c073e52-2c97-44ce-a964-e69ef174f0f8], rejectedJobs=[])'
2021-04-09 16:16:04.952 DEBUG 2340 --- [io-reader-4] n.u.core.standalone.TcpResponseSender : Sending response 'OperationStartResponse(opId=CPO-6, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b, acceptedJobs=[D-0c073e52-2c97-44ce-a964-e69ef174f0f8], rejectedJobs=[])'
2021-04-09 16:16:04.953 DEBUG 2340 --- [io-reader-4] u.c.a.h.OperationPushStartRequestHandler : Submitting job(s) for execution
2021-04-09 16:16:04.953 DEBUG 2340 --- [io-reader-4] net.unimus.core.api.JobExecutors : Submitting job 'net.unimus.core.api.job.PushJob@bee9a92a'
2021-04-09 16:16:04.954 DEBUG 2340 --- [interact-8] net.unimus.core.api.job.PushJob : Executing job 'JobKey(operationId=CPO-6, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b, jobId=D-0c073e52-2c97-44ce-a964-e69ef174f0f8)'
2021-04-09 16:16:04.954 DEBUG 2340 --- [interact-8] net.unimus.core.api.job.PushJob : Sending job execution started message
2021-04-09 16:16:04.954 TRACE 2340 --- [interact-8] n.u.core.api.ForwardingResponseSender : Sending 'JobStartedMessage(opId=CPO-6, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b, jobId=D-0c073e52-2c97-44ce-a964-e69ef174f0f8)'
2021-04-09 16:16:04.954 DEBUG 2340 --- [interact-8] n.u.core.standalone.TcpResponseSender : Sending response 'JobStartedMessage(opId=CPO-6, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b, jobId=D-0c073e52-2c97-44ce-a964-e69ef174f0f8)'
2021-04-09 16:16:04.954 DEBUG 2340 --- [interact-8] n.u.c.service.push.CliConfigPushService : Starting configuration push to 'x.x.x.x'
2021-04-09 16:16:04.954 TRACE 2340 --- [interact-8] n.u.c.service.push.CliConfigPushService : Building connector to 'x.x.x.x'
2021-04-09 16:16:04.955 DEBUG 2340 --- [interact-8] n.u.c.service.push.CliConfigPushService : Checking 'SSH' availability on 'x.x.x.x'
2021-04-09 16:16:04.955 TRACE 2340 --- [interact-8] n.u.c.s.connection.ssh.SshConnection : Checking ssh availability on 'x.x.x.x':'22' within timeout '10000'ms
2021-04-09 16:16:04.959 TRACE 2340 --- [interact-8] n.u.c.service.connection.CliConnection : Closing device CLI session
2021-04-09 16:16:04.959 TRACE 2340 --- [interact-8] n.u.c.s.connection.ssh.SshConnection : Closing SSH raw socket
2021-04-09 16:16:04.960 TRACE 2340 --- [interact-8] n.u.c.s.connection.ssh.SshConnection : Ssh available on 'x.x.x.x':'22'
2021-04-09 16:16:04.961 DEBUG 2340 --- [interact-8] n.u.c.service.push.CliConfigPushService : Opening 'SSH' session to 'x.x.x.x'
2021-04-09 16:16:04.961 TRACE 2340 --- [interact-8] n.u.c.s.connection.ssh.SshConnection : Creating SSH session to x.x.x.x:22 with 'Credential{id=4, username='summit+ct', password = 10 character(s)}', connectTimeout '10000'ms
2021-04-09 16:16:05.824 DEBUG 2340 --- [interact-8] n.u.core.cli.login.CliLoginStateMachine : CLI login process for 'x.x.x.x:22' starting in CONNECTED state
2021-04-09 16:16:06.831 DEBUG 2340 --- [interact-8] n.u.core.cli.login.CliLoginStateMachine : CLI login process for 'x.x.x.x:22' moving to BANNER_DETECTED state
2021-04-09 16:16:07.841 DEBUG 2340 --- [interact-8] n.u.core.cli.login.CliLoginStateMachine : CLI login process for 'x.x.x.x:22' moving to PROMPT_DETECTED state
2021-04-09 16:16:07.842 DEBUG 2340 --- [interact-8] n.u.core.cli.login.CliLoginStateMachine : CLI login process for 'x.x.x.x:22' moving to AUTHENTICATED state
2021-04-09 16:16:07.902 DEBUG 2340 --- [interact-8] n.u.c.c.i.CliOutputCollectionHandler : CLI output retrieval complete, retrieved '1' pages of data
2021-04-09 16:16:07.902 TRACE 2340 --- [interact-8] n.u.c.cli.formatting.CliOutputFormatter : Stripping empty lines from beginning of backup
2021-04-09 16:16:07.902 TRACE 2340 --- [interact-8] n.u.c.cli.formatting.CliOutputFormatter : Stripping empty lines from ending of backup
2021-04-09 16:16:07.957 DEBUG 2340 --- [interact-8] n.u.c.c.i.CliOutputCollectionHandler : CLI output retrieval complete, retrieved '1' pages of data
2021-04-09 16:16:07.958 TRACE 2340 --- [interact-8] n.u.c.cli.formatting.CliOutputFormatter : Stripping empty lines from beginning of backup
2021-04-09 16:16:07.958 TRACE 2340 --- [interact-8] n.u.c.cli.formatting.CliOutputFormatter : Stripping empty lines from ending of backup
2021-04-09 16:16:07.958 TRACE 2340 --- [interact-8] n.u.c.service.connection.CliConnection : Closing device CLI session
2021-04-09 16:16:07.959 TRACE 2340 --- [interact-8] n.u.c.s.connection.ssh.SshConnection : Closing SSH shell channel
2021-04-09 16:16:07.959 TRACE 2340 --- [interact-8] n.u.c.s.connection.ssh.SshConnection : Closing SSH session
2021-04-09 16:16:07.959 DEBUG 2340 --- [interact-8] net.unimus.core.api.job.PushJob : Sending job response
2021-04-09 16:16:07.959 TRACE 2340 --- [interact-8] n.u.core.api.ForwardingResponseSender : Sending 'PushJobFinishedMessage(opId=CPO-6, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b, jobId=D-0c073e52-2c97-44ce-a964-e69ef174f0f8, metadata=JobMetadata(startTime=1618006564954, duration=3005), result=PushJobResult(deviceUuid=D-0c073e52-2c97-44ce-a964-e69ef174f0f8, pushPresetId=6, error=null, promptRegex=[\[<].+?\] .*?> $, runtimeError=null))'
2021-04-09 16:16:07.960 DEBUG 2340 --- [interact-8] n.u.core.standalone.TcpResponseSender : Sending response 'PushJobFinishedMessage(opId=CPO-6, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b, jobId=D-0c073e52-2c97-44ce-a964-e69ef174f0f8, metadata=JobMetadata(startTime=1618006564954, duration=3005), result=PushJobResult(deviceUuid=D-0c073e52-2c97-44ce-a964-e69ef174f0f8, pushPresetId=6, error=null, promptRegex=[\[<].+?\] .*?> $, runtimeError=null))'
-----
Code: Select all
HEADER:
Address: x.x.x.x
Zone number: UT008
Job type: PUSH
Job started: 2021-04-09 16:16:04.954
Job finished: 2021-04-09 16:16:07.959
DEVICE OUTPUT START:
<<SSH connect - socket>>SSH-2.0-ROSSSH
<<SSH disconnect - socket>><<SSH connect - session>><<SSH connect - shell channel>>
MMM MMM KKK TTTTTTTTTTT KKK
MMMM MMMM KKK TTTTTTTTTTT KKK
MMM MMMM MMM III KKK KKK RRRRRR OOOOOO TTT III KKK KKK
MMM MM MMM III KKKKK RRR RRR OOO OOO TTT III KKKKK
MMM MMM III KKK KKK RRRRRR OOO OOO TTT III KKK KKK
MMM MMM III KKK KKK RRR RRR OOOOOO TTT III KKK KKK
MikroTik RouterOS 6.48.1 (c) 1999-2020 http://www.mikrotik.com/
[?] Gives the list of available commands
command [?] Gives help on the command and list of arguments
[Tab] Completes the command/word. If the input is ambiguous,
a second [Tab] gives possible options
/ Move up to base level
.. Move up one level
/command Use command at the base level
[9999B
[9999B(158 messages not shown)
apr/09/2021 16:15:52 system,error,critical login failure for user admin from x.x.x.x via winbox
[9999B[xxxxx@UTxxxxx2826] >
TIMESTAMP: 2021-04-09 16:16:07.845
[9999B[xxxxx@UTxxxxx2826] > /ip service export
# apr/09/2021 16:16:02 by RouterOS 6.48.1
# software id = xxxxx-VQBS
#
# model = CCR1036-8G-2S+
# serial number = xxxxx2826
/ip service
set telnet address=\
x.x.x.0/24 disabled=\
yes
set ftp address=\
x.x.x.0/24 disabled=\
yes
set www address=\
x.x.x.0/24 disabled=\
80
set ssh address=\
x.x.x.0/24 disabled=\
set www-ssl address=\
x.x.x.0/24 disabled=\
set api address=\
x.x.x.0/24 disabled=\
set winbox address=\
x.x.x.0/24 disabled=\
set api-ssl address=\
x.x.x.0/24 disabled=\
[9999B[xxxxx@UTxxxxx2826] > /user export
# apr/09/2021 16:16:03 by RouterOS 6.48.1
# software id = xxxxx-VQBS
#
# model = CCR1036-8G-2S+
# serial number = xxxxx2826
/user group
set full policy=local,telnet,ssh,ftp,reboot,read,write,policy,test,winbox,password,web,sniff,sensitive,api,romon,dude,tikapp
add name=property-management policy=read,write,web,!local,!telnet,!ssh,!ftp,!reboot,!policy,!test,!winbox,!password,!sniff,!sensitive,!api,!romon,!dude,!tikapp skin=speed-control-1
/user
add group=full name=xxxxx
/user aaa
set use-radius=yes
[9999B[xxxxx@UTxxxxx2826] > <<SSH disconnect - channel & session>>
DEVICE OUTPUT END:
judddare wrote: ↑Fri Apr 09, 2021 9:38 pmNo output from the device_output log. We are using the remote cores also if that helps.
The Last Run: time is wrong as well. It doesn't show the time I clicked on run now. I had to configure it to run on a schedule for the first run to work partially right.
Unimus.log
-----
2021-04-09 15:31:55.936 DEBUG 2340 --- [io-reader-9] net.unimus.core.api.RequestReceiverImpl : Processing 'GetLogFileRequest(opId=95921cd9-7739-4ef5-88b3-fa45213b809c, zoneId=Z-c88d91da-13d2-4e89-9326-c0ed56d7bd9b)'
2021-04-09 15:31:55.937 DEBUG 2340 --- [io-reader-9] n.u.c.a.h.GetLogFileRequestHandler : Getting log file
2021-04-09 15:31:55.937 DEBUG 2340 --- [io-reader-9] n.u.c.a.h.GetLogFileRequestHandler : Reading content of 'C:\ProgramData\Unimus-Core\log\unimus-core.log'
device_output.log
-----
empty
Unimus-debug-config-push.png
The fact that the Push doesn't run on-demand and only on schedule, and that it's not creating Output Groups is really strange... like I mentioned in the last post, if you could please create a Support Ticket on our Portal, and we can schedule a Zoom session to debug directly.