search

flux-framework / flux-core

core services for the Flux resource management framework
GNU Lesser General Public License v3.0
168 stars 50 forks source link

broker: dangling sockets: cannot terminate ZMQ safely #2438

Open chu11 opened 5 years ago

chu11 commented 5 years ago

I assume similar to #1036. Some path not handled correctly?

lt-flux-broker: module 'job-ingest' was not cleanly shutdown
lt-flux-broker: module 'job-info' was not cleanly shutdown
lt-flux-broker: module 'job-info' was not cleanly shutdown
lt-flux-broker: module 'kvs' was not cleanly shutdown
lt-flux-broker: module 'job-ingest' was not cleanly shutdown
lt-flux-broker: module 'kvs-watch' was not cleanly shutdown
lt-flux-broker: module 'kvs-watch' was not cleanly shutdown
lt-flux-broker: module 'kvs-watch' was not cleanly shutdown
lt-flux-broker: module 'kvs' was not cleanly shutdown
lt-flux-broker: module 'job-info' was not cleanly shutdown
lt-flux-broker: module 'kvs' was not cleanly shutdown
lt-flux-broker: module 'job-ingest' was not cleanly shutdown
lt-flux-broker: module 'content-sqlite' was not cleanly shutdown
lt-flux-broker: module 'job-manager' was not cleanly shutdown
lt-flux-broker: module 'sched-simple' was not cleanly shutdown
lt-flux-broker: module 'job-exec' was not cleanly shutdown
lt-flux-broker: module 'job-info' was not cleanly shutdown
lt-flux-broker: module 'kvs' was not cleanly shutdown
lt-flux-broker: module 'job-ingest' was not cleanly shutdown
lt-flux-broker: module 'barrier' was not cleanly shutdown
lt-flux-broker: module 'kvs-watch' was not cleanly shutdown
E: (flux-broker) 19-10-02 17:32:07 dangling 'PAIR' socket created at shmem.c:187
E: (flux-broker) 19-10-02 17:32:07 dangling sockets: cannot terminate ZMQ safely
garlick commented 5 years ago

Right, the czmq atexit handler again. Was this while running a particular test or...?

chu11 commented 5 years ago

Yeah, while developing stdin support in the shell. I accidentally had a watcher hanging, saw it while Ctrl+C-ing the test. Saw maybe once or twice, not everytime :-(

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had activity for 365 days. It will be closed if no further activity occurs within 14 days. Thank you for your contributions.