NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN102 - Management service offline after 6.2.3 update
Hi,
I'm running a RN102, NV+ and a RN104 at work, and I updated the RN102 to 6.2.3 today, as soon as I saw that there was a new firmware available.
The installation was unsuccessful, and I got an error message teling me to reboot the device. I rebooted it, and the power-LED began flashing blue (which it still does, an hour later).
I am unable to logon to the admin-interface, the device responds to ping and I am able to browse the smb-shares. When using RAIDar, I am getting the error Management srevice is offline", this message appear after the device has been online for ~2-3 minutes - before that no errors.
I have not yet tried to do a factory reset or anything, I thouhgt I'd try my luck here first.
Screenshot of the error-message from the admin-page aswell as RAIDar:
http://i.imgur.com/ApEJgAx.png
Cheers,
Martin
I'm running a RN102, NV+ and a RN104 at work, and I updated the RN102 to 6.2.3 today, as soon as I saw that there was a new firmware available.
The installation was unsuccessful, and I got an error message teling me to reboot the device. I rebooted it, and the power-LED began flashing blue (which it still does, an hour later).
I am unable to logon to the admin-interface, the device responds to ping and I am able to browse the smb-shares. When using RAIDar, I am getting the error Management srevice is offline", this message appear after the device has been online for ~2-3 minutes - before that no errors.
I have not yet tried to do a factory reset or anything, I thouhgt I'd try my luck here first.
Screenshot of the error-message from the admin-page aswell as RAIDar:
http://i.imgur.com/ApEJgAx.png
Cheers,
Martin
40 Replies
Replies have been turned off for this discussion
- Sent you a PM
- Thanks, I just replied.
- Did you guys find a solution for this?
- This is something which would require remote access to the system to investigate.
- I had a similar issue, but my rn102 would not even show up on the network, and the blue led kept flashing. After a couple of hours my so pulled the plug by mistake and connected it again, and it booted without an issue.
Since yours still responds to pings, you can try a few things if you have ssh enabled. You can check the logs with journalctl, and you an force a reboot with "reboot", and if you know which systemd unit is the one for the management service, you can check it's status with "systemctl status unit-name". - Sadly, I dont have ssh (or much else) enabled on the device.
I'm gonna move the device from my datacenter to my office today, hopefully i'll be able to open it up for remote access.
---
When I got to my dc the power-LED had started flashing again (had it in tech-support mode yesterday and it wasn't flashing). I've since moved it to the office, tried a normal boot (same error) and put it in techsupport mode again. - irxc, you should be able to access the management service again now.
mdgm wrote: irxc, you should be able to access the management service again now.
That is correct, the device is up and running just like before the firmware-upgrade.
Thanks a million!- Hi, I have the same issue after the upgrade on RN312. Is there a documented solution?
This is what I can get to from RAIDar logs, also when I ssh, it looks like readynasd and snapperd are consuming abnormal CPU (50% and 20%). These segfaults appear to occur 4 times a minute
2015-04-26 13:06:55: readynasd[29042]: segfault at 0 ip 00007fda17f26cf6 sp 00007fff8b775de0 error 4 in libreadynas.so.0.1.1[7fda17f09000+31000]
2015-04-26 13:06:41: readynasd[28474]: segfault at 0 ip 00007f41cfaa3cf6 sp 00007fff6bcc5dd0 error 4 in libreadynas.so.0.1.1[7f41cfa86000+31000]
2015-04-26 13:06:28: readynasd[27268]: segfault at 0 ip 00007fd55c5c6cf6 sp 00007fffb31d2090 error 4 in libreadynas.so.0.1.1[7fd55c5a9000+31000]
2015-04-26 13:06:10: readynasd[26021]: segfault at 0 ip 00007f8c64ddccf6 sp 00007fff9edc9350 error 4 in libreadynas.so.0.1.1[7f8c64dbf000+31000]
2015-04-26 13:05:45: readynasd[25548]: segfault at 0 ip 00007fa279dd9cf6 sp 00007fff8fcb7450 error 4 in libreadynas.so.0.1.1[7fa279dbc000+31000]
2015-04-26 13:05:33: readynasd[24875]: segfault at 0 ip 00007f5476ffdcf6 sp 00007fffa5450d50 error 4 in libreadynas.so.0.1.1[7f5476fe0000+31000]
2015-04-26 13:05:15: readynasd[24198]: segfault at 0 ip 00007f12d907acf6 sp 00007fff8497df70 error 4 in libreadynas.so.0.1.1[7f12d905d000+31000]
2015-04-26 13:05:02: readynasd[22938]: segfault at 0 ip 00007fc0c66eccf6 sp 00007fffc7e41f50 error 4 in libreadynas.so.0.1.1[7fc0c66cf000+31000]
2015-04-26 13:04:38: readynasd[21716]: segfault at 0 ip 00007f0726a64cf6 sp 00007fff0c294550 error 4 in libreadynas.so.0.1.1[7f0726a47000+31000]
2015-04-26 13:04:14: readynasd[20454]: segfault at 0 ip 00007f330d9c8cf6 sp 00007fffa4043960 error 4 in libreadynas.so.0.1.1[7f330d9ab000+31000]
2015-04-26 13:03:50: readynasd[19990]: segfault at 0 ip 00007f5406376cf6 sp 00007fff547859b0 error 4 in libreadynas.so.0.1.1[7f5406359000+31000]
2015-04-26 13:03:39: readynasd[18783]: segfault at 0 ip 00007f8645e47cf6 sp 00007fff41a65e60 error 4 in libreadynas.so.0.1.1[7f8645e2a000+31000]
2015-04-26 13:03:15: readynasd[18320]: segfault at 0 ip 00007fd4dec57cf6 sp 00007fffb350cf80 error 4 in libreadynas.so.0.1.1[7fd4dec3a000+31000]
2015-04-26 13:03:04: readynasd[17721]: segfault at 0 ip 00007f3f3fe25cf6 sp 00007fff6c5e82b0 error 4 in libreadynas.so.0.1.1[7f3f3fe08000+31000] - Sent you a PM
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
