NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
augur
May 29, 2020Apprentice
Resilio Sync seems crashing my Readynas 4 Pro recurrently
Hi,
I am using Resilio Sync Ready NAS App to sync my Notebook and another Ready NAS. From time to time my Ready NAS freeze totally. No access via SMB or HTTP anymore. Also the LCD display if frozen. Bit if I sniff the network packages I can see Resilio Sync is still talking to other nodes (it looks like this).
Does anybody know such behavior? Even the logs are stopped to be written. Could I perhaps activate a watchdog somehow that it will restart my NAS automatically?
Using newest OS 6.10.3.
May 26 00:59:03 netgear2 dbus[2933]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
May 26 00:59:03 netgear2 dbus[2933]: [system] Successfully activated service 'org.opensuse.Snapper'
May 26 01:09:00 netgear2 connmand[2956]: ntp: adjust (slew): +0.003976 sec
May 26 01:17:01 netgear2 CRON[21468]: pam_unix(cron:session): session opened for user root by (uid=0)
May 26 01:17:01 netgear2 CRON[21469]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 26 01:17:01 netgear2 CRON[21468]: pam_unix(cron:session): session closed for user root
May 26 01:26:04 netgear2 connmand[2956]: ntp: adjust (slew): +0.002419 sec
May 26 01:43:08 netgear2 connmand[2956]: ntp: adjust (slew): +0.001086 sec
May 26 01:59:40 netgear2 dbus[2933]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
May 26 01:59:41 netgear2 dbus[2933]: [system] Successfully activated service 'org.opensuse.Snapper'
May 26 02:00:12 netgear2 connmand[2956]: ntp: adjust (slew): +0.000565 sec
May 26 02:17:01 netgear2 CRON[24128]: pam_unix(cron:session): session opened for user root by (uid=0)
May 26 02:17:01 netgear2 CRON[24129]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 26 02:17:01 netgear2 CRON[24128]: pam_unix(cron:session): session closed for user root
May 26 02:17:16 netgear2 connmand[2956]: ntp: adjust (slew): +0.000223 sec
-- Reboot --
May 29 22:50:18 netgear2 cron[2814]: (CRON) INFO (pidfile fd = 3)
May 29 22:50:18 netgear2 cron[2814]: (CRON) INFO (Running reboot jobs)
May 29 22:50:19 netgear2 wsdd2[2820]: starting.
May 29 22:50:19 netgear2 avahi-daemon[2815]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
May 29 22:50:19 netgear2 avahi-daemon[2815]: Successfully dropped root privileges.
May 29 22:50:19 netgear2 avahi-daemon[2815]: avahi-daemon 0.6.32 starting up.
May 29 22:50:19 netgear2 mdadm[2913]: NewArray event detected on md device /dev/md0
May 29 22:50:19 netgear2 mdadm[2913]: NewArray event detected on md device /dev/md1
May 29 22:50:19 netgear2 avahi-daemon[2815]: Successfully called chroot().
May 29 22:50:19 netgear2 avahi-daemon[2815]: Successfully dropped remaining capabilities.
May 29 22:50:19 netgear2 avahi-daemon[2815]: Loading service file /services/front
Cheers,
Nils
augur wrote:
Could less ram cause a totally freezed System?Yes, if it results in a critical process not having enough memory to run.
4 Replies
Replies have been turned off for this discussion
- SandsharkSensei - Experienced User
Have you upgraded the RAM in your Pro4 to at least 2GB? Other users have reported that OS 6.10.x can have issues if you have only the default 1GB in a legacy device. Adding Resilio Sync can't make that any better. All native Intel based ReadyNAS have at least 2GB, so Netgear has not made any concessions (as it has on the ARM systems) to acccomodate less memory. Since the 100 series ARM systems only came with 1GB and cannot be upgraded, the ARM version of the OS has some things left out.
- StephenBGuru - Experienced User
augur wrote:
Bit if I sniff the network packages I can see Resilio Sync is still talking to other nodes (it looks like this).
Nothing in your log snipped relates to Resilio Sync, so I am a bit confused on what you are meaning.
I agree with Sandshark on upgrading the RAM.
Sandshark wrote:
Since the 100 series ARM systems only came with 1GB
Actually the RN100 series has only 512 MB.
- augurApprenticeHi.
It’s a Pro 4 with 1Gb Ram. Wireshark told me that some communication was still going on in that time no logs where written for about 3 days until I restarted it manually.
Could less ram cause a totally freezed System?
Cheers
Nils
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!