why aren't the ports open? about logplex

[cbarraford]

i think i did find an error the in the logs. It just didn't show up quickly.

gen_server <0.140.0> terminated with reason: rdb_load_timeout
CRASH REPORT Process <0.140.0> with 0 neighbours exited with reason: rdb_load_timeout in gen_server:terminate/6 line 744

[voidlock]

What version of redis is being used? That looks like a problem with the nsync module while attempting to sync channel/drain data. Unfortunately, this module does not work with newer versions of redis. I know that it will work with redis 2.2.x

[cbarraford]

I'm running on version 2.8.9 I believe. —
Sent from Mailbox

On Tue, Jul 29, 2014 at 5:22 PM, Alex Arnell [email protected]
wrote:

What version of redis is being used? That looks like a problem with the nsync module while attempting to sync channel/drain data. Unfortunately, this module does not work with newer versions of redis. I know that it will work with redis 2.2.x

Reply to this email directly or view it on GitHub:
#97 (comment)

[cbarraford]

i switched to a new redis box running 2.6.14 and it seemed to work just fine. Thanks for the help.

[cbarraford]

i installed version 2.8.9 locally and that worked ok, to my surprise. I then installed 2.8.9 on a remote box (to confirm that is not something funky between running redis locally or remote), and that worked fine as well.

I then pointed back to rediscloud (running version 2.8.9) and again, all the beam ports weren't open except for port 9100. Seems to be something weird between logplex and rediscloud not getting along. When i look at the keys in rediscloud instance, i see the user was created and a key(s) for redgrid ok.

[cbarraford]

Looks like rediscloud blocks usage of the SYNC command.

SYNC with master failed: -ERR command 'SYNC' is not allowed

[voidlock]

Logplex piggy backs on the redis replication features to sync configuration data. On startup it will attempt to set itself up as a read-only slave to the defined LOGPLEX_CONFIG_REDIS_URL. That will be the source of your SYNC.

My recommendation would be to run your own redis, allowing that SYNC command to work may not be something rediscloud will be willing to do.

[cbarraford]

@voidlock thanks. I'm talking with other providers and see if those will work. I may end up just self-hosting it. (rather avoid spending the time to build/maintain an HA redis cluster if i can)

I'll post here if i find a provider that will work.

[voidlock]

I would be very interested in know if there are any providers that will support the SYNC command, as I am sure that this issue will get raised again.

[cbarraford]

I heard back from openredis.com. They don't block the sync command, see available commands

Waiting to hear back from redisgreen. These were the only other providers i could find that had high availability with automatic failover.

[cbarraford]

redisgreen also states they don't block the SYNC command