[issue30434] multiprocessing AuthenticationError "digest sent was rejected"

Change by Xiang Zhang : -- resolution: -> out of date stage: test needed -> resolved status: open -> closed ___ Python tracker ___

[issue30434] multiprocessing AuthenticationError "digest sent was rejected"

Zackery Spytz added the comment: Python 2.7 is no longer supported, so I think this issue should be closed. -- nosy: +ZackerySpytz ___ Python tracker ___ _

[issue30434] multiprocessing AuthenticationError "digest sent was rejected"

Xiang Zhang added the comment: I can't reproduce the failure with 2.7.13 but I do encounter the same failure just now, much same as yours, 2.7.5 and 2.7.13. I'd like to describe my situation. I have one client process started by 2.7.13(I build it from source) and one server process started

[issue30434] multiprocessing AuthenticationError "digest sent was rejected"

Alex Perry added the comment: The docstring for the class points out that the `multiprocessing.Manager()` function creates started instances of the SyncManager class. You should probably follow that advice, it calls start() for you. -- nosy: +arp11

[issue30434] multiprocessing AuthenticationError "digest sent was rejected"

New submission from Soon Jeffrey: This is codes I run: class TopicManager(SyncManager): pass Server side: m = TopicManager(address=('', 5), authkey='12345') s = m.get_server() s.serve_forever() client side: m = TopicManager(address=('eng-g9-018', 5), authkey='12345') m.connect() W