Browse Source

[nats] Release v2.2.3

Details can be found [here](https://github.com/nats-io/nats-server/releases/tag/v2.2.3)

Signed-off-by: Ivan Kozlovic <[email protected]>
Ivan Kozlovic 4 years ago
parent
commit
991dd8e570
1 changed files with 12 additions and 12 deletions
  1. 12 12
      nats/content.md

+ 12 - 12
nats/content.md

@@ -35,15 +35,15 @@ The routing protocol has been dramatically improved and adds support for account
 
 $ docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%%
 [INF] Starting nats-server
-[INF]   Version:  2.2.2
-[INF]   Git:      [a5f3aab]
-[INF]   Name:     NDFKN2UHCGYJGFPP34WAMUJFQT64B7JFOKLBYDDRIDNONPJO3NAGOQZR
-[INF]   ID:       NDFKN2UHCGYJGFPP34WAMUJFQT64B7JFOKLBYDDRIDNONPJO3NAGOQZR
+[INF]   Version:  2.2.3
+[INF]   Git:      [b828e01]
+[INF]   Name:     NBP2RRYZQAGQMSDWSSERM57WWTAHEVF6WVUL44GET7WIF2PPBBRDGCWF
+[INF]   ID:       NBP2RRYZQAGQMSDWSSERM57WWTAHEVF6WVUL44GET7WIF2PPBBRDGCWF
 [INF] Using configuration file: nats-server.conf
 [INF] Starting http monitor on 0.0.0.0:8222
 [INF] Listening for client connections on 0.0.0.0:4222
 [INF] Server is ready
-[INF] Cluster name is IDBsbLzNE1vnhNsqZhLuvU
+[INF] Cluster name is Hjzup4jnxz0ik1NgzCmDlB
 [WRN] Cluster name was dynamically generated, consider setting one
 [INF] Listening for route connections on 0.0.0.0:6222
 ...
@@ -57,11 +57,11 @@ $ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222
 # If you want to verify the routes are connected, try this instead:
 $ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%% -c nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV
 [INF] Starting nats-server
-[INF]   Version:  2.2.2
-[INF]   Git:      [a5f3aab]
-[DBG]   Go build: go1.16.3
-[INF]   Name:     NDV5S72CIA5ZALWXUBGL3LIVG3A3PK36B32RQF25DUQYPG5KLV52EBSF
-[INF]   ID:       NDV5S72CIA5ZALWXUBGL3LIVG3A3PK36B32RQF25DUQYPG5KLV52EBSF
+[INF]   Version:  2.2.3
+[INF]   Git:      [b828e01]
+[DBG]   Go build: go1.16.4
+[INF]   Name:     NAWDIG223JIIHFFYCKAP7A5XRRWBR2Y6NP5PRB4EWTQSEC3CVH57ZNQB
+[INF]   ID:       NAWDIG223JIIHFFYCKAP7A5XRRWBR2Y6NP5PRB4EWTQSEC3CVH57ZNQB
 [INF] Using configuration file: nats-server.conf
 [DBG] Created system account: "$SYS"
 [INF] Starting http monitor on 0.0.0.0:8222
@@ -69,7 +69,7 @@ $ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222
 [DBG] Get non local IPs for "0.0.0.0"
 [DBG]   ip=172.17.0.3
 [INF] Server is ready
-[INF] Cluster name is 70r4HcDuxqObLOrd6s1by9
+[INF] Cluster name is oGH4Co27ZR04s3K1G1VGIm
 [WRN] Cluster name was dynamically generated, consider setting one
 [INF] Listening for route connections on 0.0.0.0:6222
 [DBG] Trying to connect to route on nats-main:6222 (172.17.0.2:6222)
@@ -80,7 +80,7 @@ $ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222
 [DBG] Trying to connect to route on nats-main:6222 (172.17.0.2:6222)
 [DBG] 172.17.0.2:6222 - rid:4 - Route connect msg sent
 [INF] 172.17.0.2:6222 - rid:4 - Route connection created
-[DBG] 172.17.0.2:6222 - rid:4 - Registering remote route "NDUA32CQBEAM25FKPHFEGKBF5JIQQFDBGFSFXJ7R275CYFSGZ4DDCOSG"
+[DBG] 172.17.0.2:6222 - rid:4 - Registering remote route "NCWRNTWRXEVHR5DKGKL5WDKJK5C3FDFB3S2I57TUET43SG7CKUIOW7FD"
 [DBG] 172.17.0.2:6222 - rid:4 - Sent local subscriptions to route
 ```