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

[ansible] ERROR! [pid ...] mitogen: Router(Broker(...)): no route for Message(..., 102, ...) #305

Closed
dw opened this Issue Jul 15, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@dw
Owner

dw commented Jul 15, 2018

There is a race condition when starting new contexts relating to the logging package. It manifests as:

ERROR! [pid 57194] 15:20:13.693557 E mitogen.ctx.fork.6961: mitogen: 
Router(Broker(0x7f085df59310)): no route for Message(0, 1005, 1005, 102, None, 
"mitogen\x0010\x00register(Context(4, 'parent'), mitogen."..72), my ID is 1005

It is harmless and will be fixed soon! I'm creating a bug for it so people looking at the tracker will find an entry and an explanation

@dw dw added bug ansible labels Jul 15, 2018

@dw dw changed the title from [ansible] ERROR! [pid ...] mitogen: Router(Broker(...)): no route for Message(...) to [ansible] ERROR! [pid ...] mitogen: Router(Broker(...)): no route for Message(..., 102, ...) Jul 15, 2018

@dw

This comment has been minimized.

Owner

dw commented Jul 17, 2018

It is due to logging being activated before the parent stream is added, resulting in racyness depending on whether or not the Broker thread is scheduled (and processes deferred LogHandler calls) before the call to register(). There is a reason for deferring activation, but I can't immediately spot it. Maybe a thinko regarding not having the importer configured before receiving messages?

@dw dw added the target:v0.2 label Aug 11, 2018

dw added a commit that referenced this issue Sep 7, 2018

@dw dw closed this Sep 7, 2018

dw added a commit that referenced this issue Sep 8, 2018

dw added a commit that referenced this issue Oct 30, 2018

Merge remote-tracking branch 'origin/dmw'
- issue #411: fix check_host_keys="accept"
- issue #305: dead message if max message size exceeded
- issue #369: implement Connection.reset()
- issue #76: disconnect propagation
- log format string fixes
- various 2/3 test fixes
- large message benchmark
- centralize stub client utils in data/stubs/
- activate faulthandler in tests
- better OpenSSH 7.5+ permission denied handling
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment