NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyDR Jobs fail
We got 2 ReadyNAS 3138 with Firmware 6.6.0. On each of them we got a ReadyDR Job to synch one Share to the other.
The jobs were set to start on immediate (after weekly snapshot on sunday).
Each time the jobs start, but will never end. They got the state 'running' and show that 2.5 GB are copied when moving with the mouse over the job. Select 'cancel' will never cancel the job and we got only a chance to reboot both nas devices.
We already tried to schedule the job from immediate to a specific time (4 hours later, then the snapshot was done), but we got the same behaviour
When we manually start the job (after rebooting the nas), both jobs run without no failure (it takes about 1hour to replicate aprox 120GB).
There is no error message in the log, only under the job history we see an error Unknown error 143.
Any ideas or suggestions?
4 Replies
Replies have been turned off for this discussion
Hi danielmeier69,
Welcome to the community.
Based on the description of the issue that you have provided, I may need to check this with others who can probably assist you and get back to you as soon as possible.
Thanks for your cooperation!
Regards,
Can't find an option to attach a file, so i send the part of readydr.log So we rebooted the system dec 12 and started the job manualy. everything ok. now one week later on the 19. we started the job also manualy and it fails and on UI it shows transfered 2.5GB (as always, when the job fails) and it does not further count. When we reboot the system and start the job again it runs without any error. It seems there is a reboot needed each time before the job is running.
-- Reboot --
Dec 12 08:45:08 svch1nas90 replisync[2610]: daemon: Spawned SSH server on port 5253 (pid 2830)
Dec 12 08:49:49 svch1nas90 replisync[4718]: BESR_HG_2_HM: receiver: Receiving from svch1nas91 (2fe6ef9a): /data/NAS91_BESR/.snapshots/2
Dec 12 08:50:14 svch1nas90 replisync[2610]: BESR_HM_2_HG: daemon: Starting job [BESR_HM_2_HG], PID 4970
Dec 12 08:50:21 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Negotiated latest common snapshot: 0
Dec 12 08:50:21 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Syncing snapshots starting with 0
Dec 12 08:50:21 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Sending: /data/BESR/.snapshots/5
Dec 12 08:50:21 svch1nas90 replisync[2610]: At subvol /data/BESR/.snapshots/5/snapshot
Dec 12 09:46:28 svch1nas90 replisync[4718]: BESR_HG_2_HM: receiver: Receiving from svch1nas91 (2fe6ef9a): /data/NAS91_BESR/.snapshots/1
Dec 12 11:40:59 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Sending: /data/BESR/.snapshots/4
Dec 12 11:40:59 svch1nas90 replisync[26535]: BESR_HM_2_HG: sender: Using parent: /data/BESR/.snapshots/5/snapshot
Dec 12 11:40:59 svch1nas90 replisync[2610]: At subvol /data/BESR/.snapshots/4/snapshot
Dec 12 11:41:01 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Sending: /data/BESR/.snapshots/3
Dec 12 11:41:01 svch1nas90 replisync[26545]: BESR_HM_2_HG: sender: Using parent: /data/BESR/.snapshots/4/snapshot
Dec 12 11:41:01 svch1nas90 replisync[2610]: At subvol /data/BESR/.snapshots/3/snapshot
Dec 12 11:41:01 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Sending: /data/BESR/.snapshots/2
Dec 12 11:41:01 svch1nas90 replisync[26547]: BESR_HM_2_HG: sender: Using parent: /data/BESR/.snapshots/3/snapshot
Dec 12 11:41:01 svch1nas90 replisync[2610]: At subvol /data/BESR/.snapshots/2/snapshot
Dec 12 11:41:02 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Sending: /data/BESR/.snapshots/1
Dec 12 11:41:02 svch1nas90 replisync[26549]: BESR_HM_2_HG: sender: Using parent: /data/BESR/.snapshots/2/snapshot
Dec 12 11:41:02 svch1nas90 replisync[2610]: At subvol /data/BESR/.snapshots/1/snapshot
Dec 12 11:41:04 svch1nas90 replisync[4970]: BESR_HM_2_HG: sender: Completed job (Success)
Dec 12 11:41:04 svch1nas90 replisync[2610]: BESR_HM_2_HG: daemon: Child job BESR_HM_2_HG finished with status: Success
Dec 19 07:53:50 svch1nas90 replisync[2610]: BESR_HM_2_HG: daemon: Starting job [BESR_HM_2_HG], PID 14353
Dec 19 07:53:50 svch1nas90 replisync[14353]: BESR_HM_2_HG: sender: Syncing snapshots starting with 5
Dec 19 07:53:50 svch1nas90 replisync[14353]: BESR_HM_2_HG: sender: Sending: /data/BESR/.snapshots/6
Dec 19 07:53:50 svch1nas90 replisync[14356]: BESR_HM_2_HG: sender: Using parent: /data/BESR/.snapshots/5/snapshot
Dec 19 07:53:50 svch1nas90 replisync[2610]: At subvol /data/BESR/.snapshots/6/snapshot
Dec 19 07:54:28 svch1nas90 replisync[14522]: BESR_HG_2_HM: receiver: Receiving from svch1nas91 (2fe6ef9a): /data/NAS91_BESR/.snapshots/3
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:28 svch1nas90 replisync[14522]: daemon: _write error: Communication error on sendNew Log File after reboot and the job is counting over 2.5GB and this indicates that the job will run (when the job hangs, it hangs always on 2.5GB)
Dec 19 07:54:59 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:59 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 07:54:59 svch1nas90 replisync[14522]: daemon: _write error: Communication error on send
Dec 19 08:13:38 svch1nas90 replisync[2610]: daemon: Received quit signal!
Dec 19 08:13:38 svch1nas90 replisync[14353]: daemon: _write error: Communication error on send
Dec 19 08:13:38 svch1nas90 replisync[14353]: daemon: _write error: Communication error on send
Dec 19 08:13:38 svch1nas90 replisync[14353]: daemon: _write error: Communication error on send
Dec 19 08:13:38 svch1nas90 replisync[14353]: BESR_HM_2_HG: sender: Completed job (Unknown error 143)
Dec 19 08:13:38 svch1nas90 replisync[2610]: BESR_HM_2_HG: daemon: Child job BESR_HM_2_HG finished with status: Unknown error 143
Dec 19 08:13:38 svch1nas90 replisync[14522]: daemon: Socket connect failed! (Connection refused)
-- Reboot --
Dec 19 08:14:20 svch1nas90 replisync[2905]: daemon: Spawned SSH server on port 5253 (pid 2972)
Dec 19 08:15:27 svch1nas90 replisync[2905]: BESR_HM_2_HG: daemon: Starting job [BESR_HM_2_HG], PID 4686
Dec 19 08:15:28 svch1nas90 replisync[4686]: BESR_HM_2_HG: sender: Negotiated latest common snapshot: 0
Dec 19 08:15:28 svch1nas90 replisync[4686]: BESR_HM_2_HG: sender: Syncing snapshots starting with 0
Dec 19 08:15:28 svch1nas90 replisync[4686]: BESR_HM_2_HG: sender: Sending: /data/BESR/.snapshots/6
Dec 19 08:15:28 svch1nas90 replisync[2905]: At subvol /data/BESR/.snapshots/6/snapshotDo you still have this problem?
please upgrade FW to 6.6.1
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
