search

dokku / dokku-nats

a nats plugin for dokku
MIT License
26 stars 8 forks source link

NATS is not destroying (you have to manual send CTRL-C) #16

Closed rabbagliettiandrea closed 5 years ago

rabbagliettiandrea commented 6 years ago

Last dokku version, last naft plugin version.

Example: 

root@atlas:~# dokku nats:create test && dokku --force nats:destroy test
       Waiting for container to be ready
=====> Nats container created: test
=====> Container Information
       Config dir:          /var/lib/dokku/services/nats/test/config
       Data dir:            /var/lib/dokku/services/nats/test/data
       Dsn:                 nats://test:feec0825eaa41508b3c7ddb81a489fef@dokku-nats-test:4222
       Exposed ports:       -                        
       Id:                  7cc628062f2220de7450d5868e2fc23d691133ea7fe29513de421cff1794e4db
       Internal ip:         172.17.0.22              
       Links:               -                        
       Service root:        /var/lib/dokku/services/nats/test
       Status:              running                  
       Version:             nats:0.9.4               
-----> Deleting test
       Deleting container data
-----> Stopping container
=====> Container stopped
       Removing container
       Removing data
[1] 2017/12/21 12:42:49.072358 [INF] Starting nats-server version 0.9.4
[1] 2017/12/21 12:42:49.072488 [INF] Starting http monitor on 0.0.0.0:8222
[1] 2017/12/21 12:42:49.072730 [INF] Listening for client connections on 0.0.0.0:4222
[1] 2017/12/21 12:42:49.072815 [INF] Server is ready
[1] 2017/12/21 12:42:49.073362 [INF] Listening for route connections on 0.0.0.0:6222
             ^^^ HERE YOU HAVE TO SEND CTRL-C
josegonzalez commented 6 years ago

Interesting. I wonder if upgrading to nats 1.0.4 fixes this issue. Can you try it and see?

josegonzalez commented 5 years ago

This works now and is tested in our TravisCI tests.