NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
whats wrong with this picture.. (chirpa pokes at readynasos)
Running ReadyNASOS 6 with uptime of three hours, receiving a 20kb/s rsync stream (over slow DSL line). Besides that it is completely idle, no web admin open either.
Okay, if you missed it,... look at the CPU time for readynasd :o And in the time of writing this post (~3 minutes), the CPU time usage has gone up 12 minutes. System load is at a nice steady 2.01.
Another fun note, no 'cloud' services are enabled, but LeafP2P and ReadyCloud are running, and have a connection 'phoning home' to netgear anyways. Can't wait to see any secure offices try to use this OS as is. Blocking readycloud.netgear.com causes a memleak in rcbrokerd, sending that into a spiral also.
# w
00:47:34 up 3:06, 1 user, load average: 2.23, 2.12, 2.07
# ps -ef --forest
UID PID PPID C STIME TTY TIME CMD
root 2 0 0 Mar24 ? 00:00:00 [kthreadd]
root 3 2 0 Mar24 ? 00:00:00 \_ [ksoftirqd/0]
root 5 2 0 Mar24 ? 00:00:00 \_ [kworker/u:0]
root 6 2 0 Mar24 ? 00:00:00 \_ [migration/0]
root 7 2 0 Mar24 ? 00:00:00 \_ [migration/1]
root 9 2 0 Mar24 ? 00:00:00 \_ [ksoftirqd/1]
root 11 2 0 Mar24 ? 00:00:00 \_ [migration/2]
root 12 2 0 Mar24 ? 00:00:42 \_ [kworker/2:0]
root 13 2 0 Mar24 ? 00:00:00 \_ [ksoftirqd/2]
root 14 2 0 Mar24 ? 00:00:00 \_ [migration/3]
root 16 2 0 Mar24 ? 00:00:00 \_ [ksoftirqd/3]
root 17 2 0 Mar24 ? 00:00:00 \_ [khelper]
root 217 2 0 Mar24 ? 00:00:00 \_ [sync_supers]
root 219 2 0 Mar24 ? 00:00:00 \_ [bdi-default]
root 221 2 0 Mar24 ? 00:00:00 \_ [kblockd]
root 326 2 0 Mar24 ? 00:00:00 \_ [khubd]
root 333 2 0 Mar24 ? 00:00:00 \_ [md]
root 433 2 0 Mar24 ? 00:00:00 \_ [rpciod]
root 471 2 0 Mar24 ? 00:00:00 \_ [kswapd0]
root 536 2 0 Mar24 ? 00:00:00 \_ [fsnotify_mark]
root 554 2 0 Mar24 ? 00:00:00 \_ [nfsiod]
root 574 2 0 Mar24 ? 00:00:00 \_ [xfs_mru_cache]
root 576 2 0 Mar24 ? 00:00:00 \_ [xfslogd]
root 577 2 0 Mar24 ? 00:00:00 \_ [xfsdatad]
root 578 2 0 Mar24 ? 00:00:00 \_ [xfsconvertd]
root 587 2 0 Mar24 ? 00:00:00 \_ [crypto]
root 602 2 0 Mar24 ? 00:00:00 \_ [kthrotld]
root 680 2 0 Mar24 ? 00:00:00 \_ [scsi_eh_0]
root 683 2 0 Mar24 ? 00:00:00 \_ [scsi_eh_1]
root 686 2 0 Mar24 ? 00:00:00 \_ [scsi_eh_2]
root 689 2 0 Mar24 ? 00:00:00 \_ [scsi_eh_3]
root 692 2 0 Mar24 ? 00:00:00 \_ [scsi_eh_4]
root 695 2 0 Mar24 ? 00:00:00 \_ [scsi_eh_5]
root 701 2 0 Mar24 ? 00:00:00 \_ [kworker/u:5]
root 707 2 0 Mar24 ? 00:00:00 \_ [target_completi]
root 708 2 0 Mar24 ? 00:00:00 \_ [LIO_rd_mcp]
root 709 2 0 Mar24 ? 00:00:00 \_ [iscsi_ttx]
root 710 2 0 Mar24 ? 00:00:00 \_ [iscsi_trx]
root 711 2 0 Mar24 ? 00:00:00 \_ [iscsi_ttx]
root 712 2 0 Mar24 ? 00:00:00 \_ [iscsi_trx]
root 713 2 0 Mar24 ? 00:00:00 \_ [iscsi_ttx]
root 714 2 0 Mar24 ? 00:00:00 \_ [iscsi_trx]
root 715 2 0 Mar24 ? 00:00:00 \_ [iscsi_ttx]
root 716 2 0 Mar24 ? 00:00:00 \_ [iscsi_trx]
root 802 2 0 Mar24 ? 00:01:44 \_ [kworker/0:2]
root 994 2 0 Mar24 ? 00:01:14 \_ [kworker/1:2]
root 1156 2 0 Mar24 ? 00:00:06 \_ [md0_raid1]
root 1165 2 0 Mar24 ? 00:00:01 \_ [md1_raid1]
root 1167 2 0 Mar24 ? 00:00:00 \_ [md1_resync]
root 1178 2 38 Mar24 ? 01:09:03 \_ [md127_raid5]
root 1180 2 21 Mar24 ? 00:37:56 \_ [md127_resync]
root 1264 2 0 Mar24 ? 00:00:00 \_ [btrfs-genwork-1]
root 1265 2 0 Mar24 ? 00:00:00 \_ [btrfs-submit-1]
root 1266 2 0 Mar24 ? 00:00:00 \_ [btrfs-delalloc-]
root 1267 2 0 Mar24 ? 00:00:00 \_ [btrfs-fixup-1]
root 1270 2 0 Mar24 ? 00:00:00 \_ [btrfs-endio-met]
root 1272 2 0 Mar24 ? 00:00:00 \_ [btrfs-freespace]
root 1274 2 0 Mar24 ? 00:00:00 \_ [btrfs-cache-1]
root 1275 2 0 Mar24 ? 00:00:00 \_ [btrfs-readahead]
root 1276 2 0 Mar24 ? 00:00:00 \_ [btrfs-cleaner]
root 1277 2 0 Mar24 ? 00:00:01 \_ [btrfs-transacti]
root 1392 2 0 Mar24 ? 00:00:00 \_ [btrfs-delayed-m]
root 1455 2 0 Mar24 ? 00:00:28 \_ [kworker/3:2]
root 1457 2 0 Mar24 ? 00:00:00 \_ [btrfs-endio-3]
root 2083 2 0 Mar24 ? 00:00:00 \_ [btrfs-genwork-1]
root 2084 2 0 Mar24 ? 00:00:02 \_ [btrfs-submit-1]
root 2085 2 0 Mar24 ? 00:00:00 \_ [btrfs-delalloc-]
root 2086 2 0 Mar24 ? 00:00:00 \_ [btrfs-fixup-1]
root 2087 2 0 Mar24 ? 00:00:00 \_ [btrfs-endio-1]
root 2088 2 0 Mar24 ? 00:00:00 \_ [btrfs-endio-met]
root 2089 2 0 Mar24 ? 00:00:00 \_ [btrfs-endio-met]
root 2091 2 0 Mar24 ? 00:00:00 \_ [btrfs-freespace]
root 2092 2 0 Mar24 ? 00:00:00 \_ [btrfs-delayed-m]
root 2093 2 0 Mar24 ? 00:00:00 \_ [btrfs-cache-1]
root 2094 2 0 Mar24 ? 00:00:00 \_ [btrfs-readahead]
root 2098 2 0 Mar24 ? 00:00:00 \_ [btrfs-cleaner]
root 2099 2 0 Mar24 ? 00:00:02 \_ [btrfs-transacti]
root 2141 2 0 Mar24 ? 00:00:00 \_ [flush-btrfs-4]
root 4769 2 0 Mar24 ? 00:00:41 \_ [kworker/2:2]
root 4777 2 0 Mar24 ? 00:00:29 \_ [kworker/3:0]
root 9580 2 0 Mar24 ? 00:00:00 \_ [btrfs-worker-5]
root 9629 2 0 Mar24 ? 00:00:01 \_ [btrfs-worker-3]
root 9723 2 0 Mar24 ? 00:00:00 \_ [btrfs-endio-met]
root 12376 2 0 Mar24 ? 00:00:59 \_ [kworker/1:0]
root 22138 2 0 Mar24 ? 00:00:00 \_ [flush-btrfs-5]
root 22269 2 0 Mar24 ? 00:00:00 \_ [btrfs-worker-2]
root 22270 2 0 Mar24 ? 00:00:00 \_ [btrfs-worker-3]
root 1601 2 0 Mar24 ? 00:00:29 \_ [kworker/0:0]
root 5200 2 0 Mar24 ? 00:00:00 \_ [btrfs-endio-met]
root 8872 2 0 00:12 ? 00:00:00 \_ [btrfs-endio-wri]
root 12738 2 0 00:29 ? 00:00:00 \_ [btrfs-endio-wri]
root 13304 2 0 00:32 ? 00:00:00 \_ [btrfs-endio-wri]
root 14442 2 0 00:37 ? 00:00:00 \_ [btrfs-worker-2]
root 14756 2 0 00:38 ? 00:00:00 \_ [btrfs-endio-2]
root 15165 2 0 00:40 ? 00:00:00 \_ [btrfs-endio-wri]
root 15166 2 0 00:40 ? 00:00:00 \_ [btrfs-endio-wri]
root 15262 2 0 00:40 ? 00:00:00 \_ [btrfs-endio-wri]
root 15263 2 0 00:40 ? 00:00:00 \_ [btrfs-endio-wri]
root 15264 2 0 00:40 ? 00:00:00 \_ [btrfs-endio-wri]
root 15301 2 0 00:40 ? 00:00:00 \_ [btrfs-endio-met]
root 1 0 0 Mar24 ? 00:00:04 /sbin/init
root 1537 1 0 Mar24 ? 00:00:01 /lib/systemd/systemd-journald
root 1539 1 0 Mar24 ? 00:00:00 /sbin/udevd
root 2815 1539 0 Mar24 ? 00:00:00 \_ /sbin/udevd
root 3206 1539 0 Mar24 ? 00:00:00 \_ /sbin/udevd
root 2116 1 0 Mar24 ? 00:00:00 /sbin/mdadm -F -s -y -p /frontview/bin/md_event
root 2121 1 0 Mar24 ? 00:00:00 /usr/sbin/acpid
root 2127 1 0 Mar24 ? 00:00:00 /usr/sbin/cron
root 2128 1 0 Mar24 ? 00:00:00 /usr/sbin/raidard -S
root 2133 1 0 Mar24 ? 00:00:00 /lib/systemd/systemd-logind
83 2136 1 0 Mar24 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root 2142 1 0 Mar24 tty1 00:00:00 /sbin/agetty --noclear tty1 38400
root 2149 1 0 Mar24 ttyS0 00:00:00 /sbin/agetty -s ttyS0 115200 38400 9600
root 2219 1 4 Mar24 ? 00:07:38 /usr/sbin/readynasd -v 3 -t
root 2237 1 0 Mar24 ? 00:00:00 /frontview/bin/fvbackup-q
root 2247 1 0 Mar24 ? 00:00:57 /usr/sbin/readystatsd
root 2711 1 0 Mar24 ? 00:00:00 /opt/p2p/bin/leafp2p -n
root 2718 2711 0 Mar24 ? 00:00:10 \_ /opt/p2p/bin/leafp2p -n
root 2717 1 0 Mar24 ? 00:00:00 /opt/readycloud/bin/rcbrokerd -v 3
root 4881 2717 0 Mar24 ? 00:00:00 \_ /opt/readycloud/bin/rcbrokerd -v 3
root 4084 1 0 Mar24 ? 00:00:00 /usr/sbin/sshd -D
root 5125 4084 0 Mar24 ? 00:00:00 \_ sshd: root@pts/0
root 5127 5125 0 Mar24 pts/0 00:00:00 | \_ -bash
root 15454 5127 0 00:41 pts/0 00:00:00 | \_ ps -ef --forest
root 22108 4084 1 Mar24 ? 00:01:14 \_ sshd: root@notty
root 22110 22108 0 Mar24 ? 00:00:00 \_ rsync --server -vlogDtArze.iLsf --modify-window=1 . //data/Backup/
root 22111 22110 0 Mar24 ? 00:00:08 \_ rsync --server -vlogDtArze.iLsf --modify-window=1 . //data/Backup/
root 4776 1 0 Mar24 ? 00:00:01 /usr/sbin/connmand -n
root 4787 1 0 Mar24 ? 00:00:00 /usr/sbin/minissdpd
root 4792 1 0 Mar24 ? 00:00:00 /usr/sbin/upnphttpd
avahi 6038 1 0 Mar24 ? 00:00:00 avahi-daemon: running
avahi 6039 6038 0 Mar24 ? 00:00:00 \_ avahi-daemon: chroot helper
root 9792 1 0 Mar24 ? 00:00:01 /usr/sbin/apache2 -k start
admin 9793 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
admin 9794 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
admin 9795 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
admin 9796 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
admin 9797 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
admin 9821 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
admin 10598 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
admin 11145 9792 0 Mar24 ? 00:00:00 \_ /usr/sbin/apache2 -k start
Okay, if you missed it,... look at the CPU time for readynasd :o And in the time of writing this post (~3 minutes), the CPU time usage has gone up 12 minutes. System load is at a nice steady 2.01.
Another fun note, no 'cloud' services are enabled, but LeafP2P and ReadyCloud are running, and have a connection 'phoning home' to netgear anyways. Can't wait to see any secure offices try to use this OS as is. Blocking readycloud.netgear.com causes a memleak in rcbrokerd, sending that into a spiral also.
6 Replies
Replies have been turned off for this discussion
- To remove the default bundled apps, and the unused phoning home apps (unless you want the cloud services)...
# apt-get remove plexmediaserver-ros6 leafp2p vault readydrop rdbroker remote replicate rnp2-installer
The following packages will be REMOVED:
leafp2p plexmediaserver-ros6 rdbroker readydrop remote replicate rnp2-installer vault
0 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
After this operation, 6,538 kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 11928 files and directories currently installed.)
Removing remote ...
Removing leafp2p ...
Removing plexmediaserver-ros6 ...
Removing rdbroker ...
Removing readydrop ...
Removing replicate ...
Removing rnp2-installer ...
Removing vault ... - Removing the only 'app' installed, dpkg will try to remove the /apps/ directory, watch out!
# apt-get remove htop
The following packages will be REMOVED:
htop
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 160 kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 11796 files and directories currently installed.)
Removing htop ...
dpkg: warning: while removing htop, unable to remove directory '/apps': Device or resource busy - directory may be a mount point?
To keep from seeing an 'app' for htop, I used Debian's repo instead, for a stock console version (# apt-get install -t wheezy htop) - The memleak you mentioned, would I see this in an environment where internet access is essentially unavailable, say behind a proxy requiring authentication?
- Possibly ya, the daemon keeps retrying to connect. Apparently in their more recent betas they had addressed a bunch of memleaks. So I guess we wait for 6.0.5 or 6.1 to come out at some point.
- Chirpa, do you know if this memleak issue was fixed as of 6.0.6?
I am keen to stop all the unnecessary communication apps in my new 314 and don't want to cause more problems by doing so. - Haven't tested it much, I don't use ReadyNAS systems myself anymore.
I stopped posting in this thread, updates are now over here: viewtopic.php?p=393467#p393467
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
