NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Jaybone512
Jan 18, 2021Aspirant
RN314 Front Panel - Null ffffffff880fa4cf
Hi, all. I've got a RN314 that's started showing "(null)+ffffffff880fa4cf" on the front panel. Currently running 6.10.1. The logs aren't showing any errors or warning, status on everything looks g...
- Jan 19, 2021
Pull a fresh log-gather from the cluster ("System" > "Logs" > "Download Logs") and look for the files there.
Jaybone512
Jan 19, 2021Aspirant
IPv6 is already disabled, actually.
nsne
Jan 19, 2021Virtuoso
Huh. Well, now I don't know what to think. When I came across this before, I recall being told it was down to IPv6.
At any rate, did a reboot solve it?
- mdgmJan 19, 2021Virtuoso
From memory, I think "null" doesn't tell you a lot about the error. You'd need to check the logs or if not in there monitor the serial console to get more information.
The LCD only shows a snippet of the kernel error message. The full error message (several lines) should be in kernel.log and systemd-journal.log if it has not already been rotated out.
- StephenBJan 19, 2021Guru - Experienced User
mdgm wrote:
From memory, I think "null" doesn't tell you a lot about the error. You'd need to check the logs or if not in there monitor the serial console to get more information.
Agreed. I suspect it's just indicating that a null pointer was de-referenced somewhere. Definitely worth looking for the error in the logs.
- Jaybone512Jan 19, 2021Aspirant
mdgm wrote:From memory, I think "null" doesn't tell you a lot about the error. You'd need to check the logs or if not in there monitor the serial console to get more information.
The LCD only shows a snippet of the kernel error message. The full error message (several lines) should be in kernel.log and systemd-journal.log if it has not already been rotated out.
Hi, thanks.
Where should those logfiles be found? I'm not seeing them anywhere.
root@RNfakeName:/# find . -name "*systemd-journal.lo*" root@RNfakeName:/# find . -name "*kernel.lo*" root@RNfakeName:/#
root@RNfakeName:/var/log# ls -clahsR *.log 132K -rw-r--r-- 1 root root 130K Dec 17 10:07 dpkg.log 4.0K -rw-r--r-- 1 root root 7 Jun 7 2016 LeafP2P.log 4.0K -rw-r--r-- 1 root root 2.9K Mar 12 2014 netatalk.log 4.0K -rw-r----- 1 root root 3.2K Nov 29 10:56 proftpd.log root@RNfakeName:/var/log#
- rn_enthusiastJan 19, 2021Virtuoso
Pull a fresh log-gather from the cluster ("System" > "Logs" > "Download Logs") and look for the files there.
Related Content
NETGEAR Academy

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