NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
"No logs exist" and things get worse
I have been running a ReadyNAS Ultra 6 Plus (6x2 TByte in X-Raid 2 mode) for some years with few problems and much success. The device was always upgraded to the latest RAIDiator and has been running 4.2.25 since whenever that was released. A few non-standard services have been running for at least a few months with problems: SSH, Plex Media Server, and the CrashPlan backup program. There have been no configuration changes for at least a few months.
Today, for the first time, I have encountered a serious problem. First, when logging myself into ReadyNAS FrontView, I got a notice of new log items, but when I went to the logs, the page indicated that "No logs exist." According to the advice on this forum, I attempted to reboot the server from the admin page, but that did not have any effect. So I tried to remember where the server was physically located, found it, and did a reboot by pressing the power button twice (i.e., a soft reboot).
When the server was rebooted things were worse, rather than better. Now I could no longer open any of the SMB shares from any of my home workstations. Logging myself into FrontView showed still no logs, but neither was there any error. All the shares were still listed under Shares/Share Listing. Status/Health showed all green lights. The only item which was even close to being out of the safe range was Temp Sys at 57 degrees Celsius, but that might always have been around that level.
When I ssh-ed into the server, things appeared fine. The underlying data files in the filesystem appear still to be there. I did a 'ps -edalf' (I'll be damned if I can remember what all those switches mean, but they just came from muscle memory from my days as UN*X sysadmin). Nothing suspicious there at first glance, but I've appended the results below.
Does anybody have any help or advice? I'd hate to nuke the settings, reconfigure everything, and reinstall and reconfigure my addons (if I even remember how exactly to do so).
Today, for the first time, I have encountered a serious problem. First, when logging myself into ReadyNAS FrontView, I got a notice of new log items, but when I went to the logs, the page indicated that "No logs exist." According to the advice on this forum, I attempted to reboot the server from the admin page, but that did not have any effect. So I tried to remember where the server was physically located, found it, and did a reboot by pressing the power button twice (i.e., a soft reboot).
When the server was rebooted things were worse, rather than better. Now I could no longer open any of the SMB shares from any of my home workstations. Logging myself into FrontView showed still no logs, but neither was there any error. All the shares were still listed under Shares/Share Listing. Status/Health showed all green lights. The only item which was even close to being out of the safe range was Temp Sys at 57 degrees Celsius, but that might always have been around that level.
When I ssh-ed into the server, things appeared fine. The underlying data files in the filesystem appear still to be there. I did a 'ps -edalf' (I'll be damned if I can remember what all those switches mean, but they just came from muscle memory from my days as UN*X sysadmin). Nothing suspicious there at first glance, but I've appended the results below.
Does anybody have any help or advice? I'd hate to nuke the settings, reconfigure everything, and reinstall and reconfigure my addons (if I even remember how exactly to do so).
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
4 S root 1 0 0 80 0 - 517 poll_s 08:45 ? 00:00:00 init [2]
1 S root 2 0 0 80 0 - 0 kthrea 08:45 ? 00:00:00 [kthreadd]
1 S root 3 2 0 80 0 - 0 run_ks 08:45 ? 00:00:00 [ksoftirqd/0]
1 S root 6 2 0 -40 - - 0 cpu_st 08:45 ? 00:00:00 [migration/0]
1 S root 7 2 0 -40 - - 0 cpu_st 08:45 ? 00:00:00 [migration/1]
1 S root 8 2 0 80 0 - 0 worker 08:45 ? 00:00:00 [kworker/1:0]
1 S root 9 2 0 80 0 - 0 run_ks 08:45 ? 00:00:00 [ksoftirqd/1]
1 S root 10 2 0 80 0 - 0 worker 08:45 ? 00:00:02 [kworker/0:1]
1 S root 11 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [khelper]
1 S root 158 2 0 80 0 - 0 bdi_sy 08:45 ? 00:00:00 [sync_supers]
1 S root 160 2 0 80 0 - 0 bdi_fo 08:45 ? 00:00:00 [bdi-default]
1 S root 162 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kblockd]
1 S root 163 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kacpid]
1 S root 164 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kacpi_notify]
1 S root 165 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kacpi_hotplug]
1 S root 272 2 0 80 0 - 0 hub_th 08:45 ? 00:00:00 [khubd]
1 S root 279 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [md]
1 S root 380 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [rpciod]
1 S root 406 2 0 80 0 - 0 kswapd 08:45 ? 00:00:04 [kswapd0]
1 S root 471 2 0 80 0 - 0 fsnoti 08:45 ? 00:00:00 [fsnotify_mark]
1 S root 473 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [aio]
1 S root 489 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [nfsiod]
1 S root 505 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [crypto]
1 S root 522 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kthrotld]
1 S root 567 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [scsi_tgtd]
1 S root 599 2 0 80 0 - 0 scsi_e 08:45 ? 00:00:00 [scsi_eh_0]
1 S root 602 2 0 80 0 - 0 scsi_e 08:45 ? 00:00:00 [scsi_eh_1]
1 S root 605 2 0 80 0 - 0 scsi_e 08:45 ? 00:00:00 [scsi_eh_2]
1 S root 608 2 0 80 0 - 0 scsi_e 08:45 ? 00:00:00 [scsi_eh_3]
1 S root 611 2 0 80 0 - 0 scsi_e 08:45 ? 00:00:00 [scsi_eh_4]
1 S root 614 2 0 80 0 - 0 scsi_e 08:45 ? 00:00:00 [scsi_eh_5]
1 S root 620 2 0 80 0 - 0 worker 08:45 ? 00:00:00 [kworker/u:5]
1 S root 627 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [bond0]
1 S root 648 2 0 80 0 - 0 worker 08:45 ? 00:00:00 [kworker/1:1]
1 S root 692 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kstriped]
1 S root 695 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [ksnapd]
1 S root 696 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kondemand]
1 S root 697 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [kconservative]
1 S root 700 2 0 60 -20 - 0 rescue 08:45 ? 00:00:00 [usbhid_resumer]
5 S root 830 1 0 80 0 - 450 poll_s 08:45 ? 00:00:00 ifplugd -i eth1
1 S root 839 2 0 80 0 - 0 md_thr 08:45 ? 00:00:02 [md0_raid1]
1 S root 846 2 0 80 0 - 0 md_thr 08:45 ? 00:00:00 [md1_raid6]
1 S root 852 2 0 80 0 - 0 md_thr 08:45 ? 00:00:01 [md2_raid5]
1 S root 882 2 0 80 0 - 0 kjourn 08:45 ? 00:00:00 [kjournald]
5 S root 921 2 0 80 0 - 0 bdi_wr 08:46 ? 00:00:00 [flush-9:0]
5 S root 941 1 0 76 -4 - 586 poll_s 08:46 ? 00:00:00 udevd --daemon
1 S root 1994 1 0 80 0 - 424 poll_s 08:46 ? 00:00:00 /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.soc
5 S root 2000 1 0 80 0 - 422 poll_s 08:46 ? 00:00:00 /usr/sbin/raidard
5 S root 2048 1 0 80 0 - 1365 poll_s 08:46 ? 00:00:00 /usr/sbin/sshd
1 S root 2055 2 0 60 -20 - 0 rescue 08:46 ? 00:00:00 [kdmflush]
1 S root 2089 2 0 80 0 - 0 kjourn 08:46 ? 00:00:00 [jbd2/dm-0-8]
1 S root 2090 2 0 60 -20 - 0 rescue 08:46 ? 00:00:00 [ext4-dio-unwrit]
1 S root 2170 1 0 80 0 - 667 skb_re 08:46 ? 00:00:00 /usr/sbin/quota_nld
5 S daemon 2175 1 0 80 0 - 453 poll_s 08:46 ? 00:00:00 /sbin/portmap
5 S root 2222 1 0 80 0 - 437 poll_s 08:46 ? 00:00:00 /sbin/syslogd -m 0
5 S daemon 2231 1 0 80 0 - 489 hrtime 08:46 ? 00:00:00 /usr/sbin/atd
5 S root 2236 1 0 80 0 - 425 syslog 08:46 ? 00:00:00 /sbin/klogd -x -c 3
5 S root 2248 1 0 80 0 - 940 poll_s 08:46 ? 00:00:00 /usr/sbin/cupsd
5 S 21 2253 1 0 80 0 - 688 poll_s 08:46 ? 00:00:00 /usr/bin/dbus-daemon --system
1 S root 2255 1 0 80 0 - 494 hrtime 08:46 ? 00:00:00 /usr/sbin/cron
5 S root 2433 1 0 80 0 - 3725 poll_s 08:46 ? 00:00:00 /usr/sbin/smbd -D
5 S root 2517 2433 0 80 0 - 3725 poll_s 08:46 ? 00:00:00 /usr/sbin/smbd -D
5 S nobody 2658 1 0 80 0 - 2864 poll_s 08:46 ? 00:00:00 proftpd: (accepting connections)
5 S root 2665 1 0 80 0 - 431 poll_s 08:46 ? 00:00:00 ifplugd -i bond0 -q -f -d0 -w -I
5 S root 2695 1 0 80 0 - 431 poll_s 08:46 ? 00:00:00 ifplugd -i eth0 -q -f -u0 -d0 -w -I
5 S root 2712 1 0 80 0 - 431 poll_s 08:46 ? 00:00:00 ifplugd -i eth1 -q -f -u0 -d0 -w -I
5 S root 2806 1 0 80 0 - 453 poll_s 08:46 ? 00:00:00 /sbin/udhcpc -i eth0 -H Storion -t 3 -p /var/run/udhcpc.e
5 S root 2894 1 0 80 0 - 784 hrtime 08:46 ? 00:00:00 /frontview/bin/monitor_enclosure
5 S root 2943 1 0 85 5 - 9136 poll_s 08:46 ? 00:00:00 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf
5 S root 2951 1 0 80 0 - 2704 poll_s 08:46 ? 00:00:00 nmbd -D
1 S root 2953 2951 0 80 0 - 2615 pipe_w 08:46 ? 00:00:00 nmbd -D
5 S root 2972 1 0 80 0 - 4835 poll_s 08:46 ? 00:00:00 /usr/sbin/minidlna
5 S root 2984 1 0 80 0 - 531 poll_s 08:46 ? 00:00:00 /usr/sbin/ntpd
5 S root 2999 1 0 80 0 - 424 poll_s 08:46 ? 00:00:00 /usr/sbin/upnpd eth0
5 S root 3017 1 0 80 0 - 444 poll_s 08:46 ? 00:00:00 /usr/sbin/lld2d eth0
4 S root 3031 1 0 80 0 - 50556 futex_ 08:46 ? 00:00:18 /c/.plex/plexserver
5 S root 3299 1 0 80 0 - 3906 hrtime 08:46 ? 00:00:00 /usr/sbin/mt-daapd
4 S root 3462 3031 0 95 15 - 26828 pipe_w 08:47 ? 00:00:13 Plex Plug-in [com.plexapp.system] /c/.plex/Library/Applic
1 S admin 3509 1 0 78 -2 - 481 poll_s 08:47 ? 00:00:00 /lib/nut/hidups -x lowbatt_pct=0 /dev/usb/hiddev0
1 S admin 3553 1 0 78 -2 - 483 poll_s 08:47 ? 00:00:00 /sbin/upsd
5 S root 3581 1 0 78 -2 - 440 hrtime 08:47 ? 00:00:00 /sbin/upsmon -p
0 S root 3665 1 0 80 0 - 425 n_tty_ 08:47 ttyS0 00:00:00 /sbin/getty -L ttyS0 9600 tty1
4 S root 3797 3031 0 80 0 - 16207 pipe_w 08:48 ? 00:00:03 Plex Plug-in [com.plexapp.agents.wikipedia] /c/.plex/Libr
4 S root 3799 3031 0 80 0 - 16429 pipe_w 08:48 ? 00:00:04 Plex Plug-in [com.plexapp.agents.themoviedb] /c/.plex/Lib
1 S root 3919 2 0 80 0 - 0 worker 08:54 ? 00:00:00 [kworker/u:0]
0 S root 5071 1 0 99 19 - 173227 futex_ 09:24 ? 00:00:05 /usr/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanServic
1 S root 5135 2 0 80 0 - 0 worker 09:27 ? 00:00:00 [kworker/0:2]
1 S root 5148 2 0 80 0 - 0 bdi_wr 09:27 ? 00:00:00 [flush-253:0]
5 S admin 5477 2943 0 85 5 - 9381 poll_s 09:30 ? 00:00:00 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf
5 S admin 6035 2943 0 85 5 - 9513 poll_s 09:34 ? 00:00:02 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf
4 S root 7262 3031 0 80 0 - 16609 pipe_w 09:47 ? 00:00:03 Plex Plug-in [com.plexapp.agents.localmedia] /c/.plex/Lib
4 S root 7307 3031 0 80 0 - 16760 pipe_w 09:47 ? 00:00:01 Plex Plug-in [com.plexapp.agents.movieposterdb] /c/.plex/
4 S root 7347 3031 0 80 0 - 15762 pipe_w 09:47 ? 00:00:01 Plex Plug-in [com.plexapp.agents.opensubtitles] /c/.plex/
4 S root 7504 3031 0 80 0 - 15836 pipe_w 09:48 ? 00:00:02 Plex Plug-in [com.plexapp.agents.lastfm] /c/.plex/Library
5 S root 7967 2433 0 80 0 - 3780 poll_s 09:52 ? 00:00:00 /usr/sbin/smbd -D
4 R root 8174 2048 0 80 0 - 2063 - 09:54 ? 00:00:00 sshd: root@pts/0
4 S root 8180 8174 0 80 0 - 1245 wait 09:54 pts/0 00:00:00 -bash
4 R root 8282 8180 0 80 0 - 1105 - 09:55 pts/0 00:00:00 ps -edalf
24 Replies
Replies have been turned off for this discussion
- Yeah, I was wondering if jna*.tmp files were Java related. If they are, it is quite possibly CrashPlan.
Still, I wish the ReadyNAS would not allow itself to become essentially bricked by something as simple as a overfull tmp directory. A simple solution would be to at least purge the tmp directory on every boot. That would reduce the problem to one solvable by reboot and seems the right thing to do in any case. - I think an OS Re-install might clear /tmp
- Afraid not. That is the first thing that tech support suggested. I tried it (and it took, resetting e.g. the admin password), but the problem was not fixed until they logged themselves in remotely and removed the tmp junk.
- Do we know the exact path name(s) to tmp files on our RN devices?
Mine runs and runs and while I do occasionally download all logs and then clear them (the Backup logs do get really big if left alone) there is no other regular maintenance that I do software-wise. - The jna files are all in /tmp. And something--probably the Java CrashPlan app--keeps spamming new ones into there.
- I see them also - the times are pretty irregular, I think they are related to either when the service starts, or perhaps when java itself starts.
Mine went back about 2 years, and only totaled about 2 MB. - One more bit of information: The problem was tracked down to the java app, CrashPlan. Reviewing the logs it turns out that, about a month ago, it started crashing every couple of minutes. Each of those crashes left a /tmp/jna*.tmp file behind. The reason for the crashes in turn was that CrashPlan kept running out of memory. Altering the JVM's memory ceiling from 512 MBytes to 2 GBytes, https://support.code42.com/CrashPlan/Latest/Troubleshooting/CrashPlan_Runs_Out_Of_Memory_And_Crashes#Linux_.2F_Solaris seems to have fixed the problem for now. However, given that the ReadyNAS only has one GByte of physical RAM, I hope CrashPlan doesn't mind virtual.
- I reset mine to 1 GB some time ago (I also ran into the crashing problem). Then I upgraded the physical memory to 2 GB, which seemed to improve Crashplan's performance.
- Interesting. I recall upgrading the memory on my ReadyNAS to 1 gByte, but that may have been my old NV. How much memory can you put into a ultra 6+ and what types does it take?
- You can put 8GB (2x 4GB). See suggestions for e.g. the Pro 6
If you download the logs what is the BIOS date in bios_ver.log ?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
