Replication fails after reboot - connecting manually works, however

Status
Not open for further replies.

mpfusion

Contributor
Joined
Jan 6, 2014
Messages
198
Hi,

after a server reboot the replication stopped working.

Storage → Replication Tasks → Status: Failed: ssh: connect to host example.com port 12345: Operation timed out

It worked fine before the reboot. Connecting manually works, however:

ssh -i /data/ssh/replication -p 12345 example.com


So it's not a networking/firewall issue. Otherwise connecting from the box via
SSH wouldn't succeed . Why does it fail using the replication mechanism?

There's no logging about this in /var/log/messages and /var/log/debug.log
contains no useful info about why it might fail. How to debug this? What exact
command does the replication use (so I can run in in the shell)?

FreeNAS-11.1-U4
Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz
163693MB
 
D

dlavigne

Guest
Anything in /var/log/messages around the time of the failure?
 

mpfusion

Contributor
Joined
Jan 6, 2014
Messages
198
No, not a single new line in /var/log/messages. Replication stuff seems to be logged to /var/log/debug.log which shows:

Nov 1 16:38:04 freenas /autorepl.py: [tools.autorepl:221] Autosnap replication started
Nov 1 16:38:04 freenas /autorepl.py: [tools.autorepl:222] temp log file: /tmp/repl-46995
 

mpfusion

Contributor
Joined
Jan 6, 2014
Messages
198
Update: After a week the problem fixed itself. The error vanished and replication started working again.
 
Status
Not open for further replies.
Top