Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixed answers between channels #77

Open
XtoZee opened this issue Jun 19, 2018 · 3 comments
Open

Mixed answers between channels #77

XtoZee opened this issue Jun 19, 2018 · 3 comments

Comments

@XtoZee
Copy link

XtoZee commented Jun 19, 2018

Good day.
I'm using mikronode mainly for mikrotik router port manipulation.
During initial state I disable needed ports in loop with promises using one persistent connection to Mikrotik and one-per-command channel. I tested "bad port" port situation and noticed that sometimes i get "no such item" error on working, configured ports that usually work OK. And that happened right after real "bad" port.
Normal situation:

[19.06 08:46:08] ER: 0:ether28 port down failed!!! Reason: no such item
[19.06 08:46:08] OK: 0:ether14 port down
[19.06 08:46:08] OK: 0:ether13 port down
[19.06 08:46:08] OK: 0:ether12 port down
[19.06 08:46:08] OK: 0:ether11 port down
[19.06 08:46:08] OK: 0:ether10 port down
[19.06 08:46:08] OK: 0:ether9 port down
[19.06 08:46:08] OK: 0:ether8 port down
[19.06 08:46:08] OK: 0:ether7 port down
[19.06 08:46:08] OK: 0:ether6 port down
[19.06 08:46:08] OK: 0:ether5 port down

Bad answers:

[19.06 08:46:17] ER: 0:ether28 port down failed!!! Reason: no such item
[19.06 08:46:17] ER: 0:ether14 port down failed!!! Reason: no such item
[19.06 08:46:17] ER: 0:ether13 port down failed!!! Reason: no such item
[19.06 08:46:17] ER: 0:ether12 port down failed!!! Reason: no such item
[19.06 08:46:17] OK: 0:ether11 port down
[19.06 08:46:17] OK: 0:ether10 port down
[19.06 08:46:17] OK: 0:ether9 port down
[19.06 08:46:17] OK: 0:ether8 port down
[19.06 08:46:17] OK: 0:ether7 port down
[19.06 08:46:17] OK: 0:ether6 port down
[19.06 08:46:17] OK: 0:ether5 port down

After turning on debugging I saw (if I understand it right) real problem - the answer is received in the same channel and what is more strange - seems that channels are not created right.

Creating channel  1529398091373
Channel 1529398091373 Created
Writing on channel 1529398091373 /interface/ethernet/disable { numbers: 'ether28' }
Creating channel  1529398091373
Channel 1529398091373 Created
Writing on channel 1529398091373 /interface/ethernet/disable { numbers: 'ether14' }
Creating channel  1529398091389
Channel 1529398091389 Created
Writing on channel 1529398091389 /interface/ethernet/disable { numbers: 'ether13' }
Creating channel  1529398091389
Channel 1529398091389 Created
Writing on channel 1529398091389 /interface/ethernet/disable { numbers: 'ether12' }
Creating channel  1529398091389
Channel 1529398091389 Created
Writing on channel 1529398091389 /interface/ethernet/disable { numbers: 'ether11' }
Creating channel  1529398091389
Channel 1529398091389 Created
Writing on channel 1529398091389 /interface/ethernet/disable { numbers: 'ether10' }
Creating channel  1529398091389
Channel 1529398091389 Created
Writing on channel 1529398091389 /interface/ethernet/disable { numbers: 'ether9' }
Creating channel  1529398091404
Channel 1529398091404 Created
Writing on channel 1529398091404 /interface/ethernet/disable { numbers: 'ether8' }
Creating channel  1529398091404
Channel 1529398091404 Created
Writing on channel 1529398091404 /interface/ethernet/disable { numbers: 'ether7' }
Creating channel  1529398091404
Channel 1529398091404 Created
Writing on channel 1529398091404 /interface/ethernet/disable { numbers: 'ether6' }
Creating channel  1529398091404
Channel 1529398091404 Created
Writing on channel 1529398091404 /interface/ethernet/disable { numbers: 'ether5' }
Creating channel  1529398091404
Channel 1529398091404 Created
Writing on channel 1529398091404 /interface/ethernet/disable { numbers: 'ether5' }
Login stream complete
Channel (1529398091373)::TRAP
*** Register Command: trap 1 { type: 'trap',
  tag: '1529398091373',
  data: [ { field: 'message', value: 'no such item' } ],
  cmd:
   { id: 1,
     command: '/interface/ethernet/disable',
     args: { numbers: 'ether28' } } }
[19.06 08:48:11] ------------------------------------------ER: 0:ether28 port down failed!!! Reason: no such item
Channel (1529398091373)::CLOSED
Closing channel  1529398091373
Channel (1529398091373)::TRAP
*** Register Command: trap 1 { type: 'trap',
  tag: '1529398091373',
  data: [ { field: 'message', value: 'no such item' } ],
  cmd:
   { id: 1,
     command: '/interface/ethernet/disable',
     args: { numbers: 'ether14' } } }
[19.06 08:48:11] ------------------------------------------ER: 0:ether14 port down failed!!! Reason: no such item
Channel (1529398091373)::CLOSED
Closing channel  1529398091373
Channel (1529398091389)::data flatMap
Channel (1529398091389)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether13 port down
Channel (1529398091389)::CLOSED
Closing channel  1529398091389
Channel (1529398091389)::data flatMap
Channel (1529398091389)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether12 port down
Channel (1529398091389)::CLOSED
Closing channel  1529398091389
Channel (1529398091389)::data flatMap
Channel (1529398091389)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether11 port down
Channel (1529398091389)::CLOSED
Closing channel  1529398091389
Channel (1529398091389)::data flatMap
Channel (1529398091389)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether10 port down
Channel (1529398091389)::CLOSED
Closing channel  1529398091389
Channel (1529398091389)::data flatMap
Channel (1529398091389)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether9 port down
Channel (1529398091389)::CLOSED
Closing channel  1529398091389
Channel (1529398091404)::data flatMap
Channel (1529398091404)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether8 port down
Channel (1529398091404)::CLOSED
Closing channel  1529398091404
Channel (1529398091404)::data flatMap
Channel (1529398091404)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether7 port down
Channel (1529398091404)::CLOSED
Closing channel  1529398091404
Channel (1529398091404)::data flatMap
Channel (1529398091404)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether6 port down
Channel (1529398091404)::CLOSED
Closing channel  1529398091404
Channel (1529398091404)::data flatMap
Channel (1529398091404)::done_ret flatMap
[19.06 08:48:11] OK: 0:ether5 port down
Channel (1529398091404)::CLOSED
Closing channel  1529398091404
Login stream complete
Channel (1529398091404)::data flatMap
Channel (1529398091404)::done_ret flatMap
[19.06 08:48:11] OK: 1:ether5 port down
Channel (1529398091404)::CLOSED
Closing channel  1529398091404
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1
Clearing command cache for # 1

There's one incorrect answer right after the real "bad" port operation.
There can be upto 6 answers in the same channel.

Another bad thing is that in last log 2 ports "ether5" are downed on different connections to different routers but work on the same channel.

I may be wrong in my conclusions but please explain me what i'm doing wrong if I do.

Node: v.8.9.1
Mikronode: v.2.3.11
RouterOS: v.6.40.3

@Trakkasure
Copy link
Owner

Is this still occurring?

@XtoZee
Copy link
Author

XtoZee commented Dec 13, 2018

Haven't seen this for now. But this surely needed some special conditions (that I don't know) to repeat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@Trakkasure @XtoZee and others