Closed jhkrischel closed 6 years ago
how many txes per second you've been sending, we haven't seen zmq errors so far
ignore that, those are exactly values we use, somehow container must be missing them
This was running our demo that did subscriptions - until I added those parameters, everything immediately timed-out. Under normal circumstances, I'd do less than 10 pub/sub transactions, and it would be done - without the parameters, it kept retrying every few seconds and never succeeded.
{"level":"verbose","message":"websocket VDQWMEVBXHZT7PHQGI6NQYAKRXWGGK6L: created /ws websocket connection","timestamp":"2018-06-18T06:13:54.938Z"}
{"level":"info","message":"subscribing to status/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM","timestamp":"2018-06-18T06:13:55.040Z"}
{"level":"error","message":"zmq status/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM: connection attempt timed out","timestamp":"2018-06-18T06:13:55.041Z"}
{"level":"info","message":"subscribing to cosignature/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM","timestamp":"2018-06-18T06:13:55.140Z"}
{"level":"info","message":"subscribing to confirmedAdded/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM","timestamp":"2018-06-18T06:13:55.140Z"}
{"level":"info","message":"subscribing to unconfirmedAdded/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM","timestamp":"2018-06-18T06:13:55.140Z"}
{"level":"info","message":"subscribing to unconfirmedRemoved/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM","timestamp":"2018-06-18T06:13:55.141Z"}
{"level":"info","message":"subscribing to partialAdded/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM","timestamp":"2018-06-18T06:13:55.141Z"}
{"level":"info","message":"subscribing to partialRemoved/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM","timestamp":"2018-06-18T06:13:55.141Z"}
{"level":"error","message":"zmq cosignature/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM: connection attempt timed out","timestamp":"2018-06-18T06:13:55.141Z"}
{"level":"error","message":"zmq confirmedAdded/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM: connection attempt timed out","timestamp":"2018-06-18T06:13:55.142Z"}
{"level":"error","message":"zmq unconfirmedAdded/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM: connection attempt timed out","timestamp":"2018-06-18T06:13:55.142Z"}
{"level":"error","message":"zmq unconfirmedRemoved/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM: connection attempt timed out","timestamp":"2018-06-18T06:13:55.142Z"}
{"level":"error","message":"zmq partialAdded/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM: connection attempt timed out","timestamp":"2018-06-18T06:13:55.142Z"}
{"level":"error","message":"zmq partialRemoved/SCQ4HFC7D75OFNXICJT4UM6GAYATW5C4EKRI6FRM: connection attempt timed out","timestamp":"2018-06-18T06:13:55.142Z"}
{"level":"verbose","message":"websocket VDQWMEVBXHZT7PHQGI6NQYAKRXWGGK6L: disconnected /ws websocket connection","timestamp":"2018-06-18T06:13:57.116Z"}
Need to patch ruby/catapult-templates/rest_gateway/rest.json.mt to include the three parameters in the mq section.
Added missing template params, commit: https://github.com/tech-bureau/catapult-service-bootstrap/commit/3becb80c07ef7bf146d307b846eec7c82d046712#diff-eeda22f594118b18166f0cbd8d150068
Sweet, thanks @kaiyzen !
When running a rest gateway with the rest.json built during docker-compose up, massive zmq errors until the following parameters were added to the mq section :