GreenArrow Email Software Documentation

Troubleshooting

Overview

Most problems connecting through the GreenArrow Proxy are visible in the in the rspawn-limiter log.

For example, to see the last 5 minutes of this log, run the following command:

logdir_select_time --last '5 minutes' --dir /var/hvmail/log/rspawn-limiter | tai64nlocal

Incorrect Shared Secret

reconnect: error connecting to greenarrow proxy gaproxy1: The HMAC you sent was incorrect (this most likely means you do not have the correct greenarrow_proxy_shared_secret configured).

This message indicates that the value this GreenArrow instance has configured for greenarrow_proxy_shared_secret most likely does not match the value of shared_secret configured on the proxy server.

GreenArrow Instance IP Not Authorized

reconnect: error connecting to greenarrow proxy gaproxy1: EOF

This message indicates the proxy server is hanging up on the GreenArrow instance. This is likely because of the allow_from directive in the proxy server configuration. That directive must be configured to allow any IP address from which a GreenArrow instance might connect.

To confirm this, observe the greenarrow_proxy logs (if running in Systemd, this can be viewed by running journalctl -u greenarrow_proxy.service --follow).

2024-09-10 17:36:31.008867500 new incoming connection: clientip=<127.0.0.1>
2024-09-10 17:36:31.008869500 received connection from client 127.0.0.1, which is not matched by the allow_from configuration, disconnecting

This message confirms that we’re hanging up on the GreenArrow instance due to its IP address not being included in an allow_from directive.

GreenArrow Instance Version Greater Than Proxy Server

reconnect: error connecting to greenarrow proxy gaproxy1: You are running a version (4.330.0-0) greater than the proxy server (4.329.0-5). You must upgrade the proxy server BEFORE GreenArrow instances.

This message indicates that you’ve likely upgraded a GreenArrow instance prior to upgrading the proxy server.

To resolve this, you must either downgrade the GreenArrow instance, or upgrade the greenarrow_proxy exeuctable.

Duplicated GreenArrow Instance Unique Identifier

disconnected from remote throttle: Your unique identifier has been used by a new session, you are being disconnected.

This message is received when two GreenArrow instances with the same backend datastore connects to the same GreenArrow Proxy. If you’ve cloned an instance (or perhaps have cloned a backing volume), run the following command to regenerate this identifier:

greenarrow update regenerate_server_unique_random_seed


Copyright © 2012–2024 GreenArrow Email