Customer had upgraded from Language Weaver Edge 8.5.4 to 8.6, and the application was not coming up.  The customer was receiving this error:

ERROR startWatchdog - AMQP connection failed (translation-engine-metrics): 
Failed to open an AMQP connection to {Hostname:localhost SecurePort:2222 
Username:xxx Password:* ExchangeID:ets.default AutoStart:true}: 
Could not connect to message broker: dial tcp [::1]:2222: connect: 
connection refused

host-agent.log contained the following:

[2023-05-08 13:05:49.124] [112362] ERROR func2 - translation engine (1111) 
process exited: exit status 73
[2023-05-08 13:05:58.667] [112368] ERROR RespondWithError - 
Responding with error: &{Error:{Code:400 Message:no translation engine 
exists with id 1111 Details:}}

 

Ran the RabbitMQ service independently to see error messages that indicated there were permission issues with the .erlang.cookie file.  Stopped the mtedge service, deleted the file, restarted the mtedge service and everything came up fine.

To run the RabbitMQ service independently in order to see error messages on Linux machine (would need slight modifications to run on Windows), create a new file as a shell script (i.e., newfilejustcreated.sh), making sure that read/write/modify permissions are on the file:
 

#!/bin/bash

export ERLANG_HOME=/opt/sdl/ets/extra/erlang
export HOME=/opt/sdl/ets/data
export PATH=/opt/sdl/ets/extra/erlang/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export LD_LIBRARY_PATH=:/opt/sdl/ets/extra/erlang/lib/crypto-4.9.0.2/priv/lib:/opt/sdl/ets/extra/erlang/lib/ncurses-5.0/priv/lib
export RABBITMQ_CONF_ENV_FILE=/opt/sdl/ets/conf/rabbitmq-env.conf

/opt/sdl/ets/extra/rabbitmq-server/sbin/rabbitmq-server

execute as a shell script,
#./newfilejustcreated.sh

Error that was seen in this case:

[error] Cookie file /opt/sdl/ets/data/.erlang.cookie must be accessible by owner only Distribution failed:
 {{:shutdown, {:failed_to_start_child, "auth, {'Cookie file /opt/sdl/ets/data/.erlang.cookie must be accessible by owner only',........

 

RabbitMQ service keeps going down and mtedge application relies on this service to communicate throughout the whole application.