Live indexing error

[slayer49]

After enabling replication-cron and live indexing, I started getting this error from mq:

mq_1           | =ERROR REPORT==== 25-May-2020::15:19:22 ===
mq_1           | closing AMQP connection <0.6209.0> (172.18.0.4:47864 -> 172.18.0.5:5672):
mq_1           | {handshake_error,tuning,0,
mq_1           |     {exit,
mq_1           |         {amqp_error,not_allowed,
mq_1           |             "negotiated channel_max = 0 is higher than the maximum allowed value (2047)",
mq_1           |             'connection.tune'},
mq_1           |         'connection.tune_ok',
mq_1           |         [{rabbit_misc,protocol_error,1,
mq_1           |              [{file,"src/rabbit_misc.erl"},{line,312}]},
mq_1           |          {rabbit_reader,handle_method0,2,
mq_1           |              [{file,"src/rabbit_reader.erl"},{line,1207}]},
mq_1           |          {rabbit_reader,handle_method0,3,
mq_1           |              [{file,"src/rabbit_reader.erl"},{line,1160}]},
mq_1           |          {rabbit_reader,handle_input,3,
mq_1           |              [{file,"src/rabbit_reader.erl"},{line,1075}]},
mq_1           |          {rabbit_reader,recvloop,4,
mq_1           |              [{file,"src/rabbit_reader.erl"},{line,472}]},
mq_1           |          {rabbit_reader,run,1,[{file,"src/rabbit_reader.erl"},{line,454}]},
mq_1           |          {rabbit_reader,start_connection,4,
mq_1           |              [{file,"src/rabbit_reader.erl"},{line,390}]},
mq_1           |          {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}}
mq_1           |
mq_1           | =INFO REPORT==== 25-May-2020::15:19:22 ===
mq_1           | accepting AMQP connection <0.6212.0> (172.18.0.4:47868 -> 172.18.0.5:5672)
db_1           | 2020-05-25 15:19:24.721 UTC [621] WARNING:  amqp[mq:5672] login failed on broker 1
db_1           | 2020-05-25 15:19:24.721 UTC [621] CONTEXT:  SQL statement "SELECT amqp.publish(1, 'search', 'update', (
db_1           | 	            WITH keys(id) AS (SELECT NEW.id)
db_1           | 	            SELECT jsonb_set(jsonb_set(to_jsonb(keys), '{_table}', '"artist_credit"'),
db_1           | 	                             '{_operation}', '"update"')::text FROM keys
db_1           | 	        ))"
db_1           | 	PL/pgSQL function search_artist_credit_update() line 3 at PERFORM```

```WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
     1039      8206  93%         0         0WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
     1040      8208  93%         0         0WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
     1041      8212  94%         0         0WARNING:  amqp[mq:5672] login failed on broker 1
WARNING:  amqp[mq:5672] login failed on broker 1
     1042      8214  94%         0         0WARNING:  amqp[mq:5672] login failed on broker 1
     1043      8215  94%         0         0WARNING:  amqp[mq:5672] login failed on broker 1
     1044      8216  94%         0         0WARNING:  amqp[mq:5672] login failed on broker 1
     1045      8217  94%         0         0WARNING:  amqp[mq:5672] login failed on broker 1
     1046      8218  94%         0         0WARNING:  amqp[mq:5672] login failed on broker 1

[yvanzo]

This was a regression of v-2020-05-18-postgres12 which has just been fixed in v-2020-06-02.