NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
deleting user automatically
Model: ReadyNAS 104
OS: windows 7
Date: Nov 03 17:36
My user account automatically deleted.
I didn't login ReadyNAS admin page at the time. one day I login use "dkeigo" account as usual.
But this time cannot login and deleted my user account.
I attached some log file. Some one attacked my ReadyNAS or I misoperation and deleted my user account?
Please help me
Thanks.
Keigo
system.log
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {RX} 74 packets 9648 bytes
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {TX} 110360 packets 22002713 bytes
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {update} flags 4098 <DOWN>
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {newlink} index 5 address 9A:3E:89:6A:77:FC mtu 1400
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {newlink} index 5 operstate 2 <DOWN>
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {del} route fe80:: gw :: scope 0 <UNIVERSE>
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {del} route ff00:: gw :: scope 0 <UNIVERSE>
Nov 03 17:36:53 ReadyNAS connmand[1584]: (null) {del} address 5.212.26.174/8 label LeafNets
Nov 03 17:36:53 ReadyNAS connmand[1584]: LeafNets {dellink} index 5 operstate 2 <DOWN>
Nov 03 17:36:53 ReadyNAS connmand[1584]: (null) {RX} 74 packets 9648 bytes
Nov 03 17:36:53 ReadyNAS connmand[1584]: (null) {TX} 110360 packets 22002713 bytes
Nov 03 17:36:53 ReadyNAS connmand[1584]: (null) {remove} index 5
systemd-journal.log
Nov 03 17:24:25 ReadyNAS connmand[1584]: ntp: time slew +0.059440 s
Nov 03 17:35:33 ReadyNAS xagent[21868]: net_helper.c:59 ERROR: Cannot read data from socket. errno = 104 - Connection reset by peer.
Nov 03 17:35:33 ReadyNAS xagent[21868]: msg_processor.c:694 ERROR: Failed to connect to xbroker. Sleeping for 60 secs.
Nov 03 17:36:46 ReadyNAS rcbrokerd[21872]: ../common/unregister.h:62 DEBUG:../common/unregister.h:62 Unregister
Nov 03 17:36:47 ReadyNAS remote[28948]: Adding network to list for _SUB_dkeigo_E3C53E2A-C156-4C17-96CC-6B8258B6C42A
Nov 03 17:36:47 ReadyNAS remote[28948]: Adding network to list for dkeigo
Nov 03 17:36:47 ReadyNAS remote[28948]: Folder shares 1
Nov 03 17:36:47 ReadyNAS remote[28948]: Number shares 1
Nov 03 17:36:47 ReadyNAS remote[28948]: Share
Nov 03 17:36:47 ReadyNAS remote[28948]: Getting network for dkeigo
Nov 03 17:36:47 ReadyNAS remote[28948]: Adding network share list nas-E4-C4-94_E8FCAFE4C494's dkeigo network 0x8e680 0x84320
Nov 03 17:36:47 ReadyNAS xagent_prestart.sh[28947]: HW = 3EPD4AE800158
Nov 03 17:36:47 ReadyNAS xagent_prestart.sh[28947]: MODEL_ID = ReadyNAS 104
Nov 03 17:36:47 ReadyNAS remote[28948]: Connection shares 1
Nov 03 17:36:47 ReadyNAS remote[28948]: Number shares 1
Nov 03 17:36:47 ReadyNAS remote[28948]: Share Connection
Nov 03 17:36:47 ReadyNAS xagent_prestart.sh[28947]: NEW_HW = 3EPD4AE800158
Nov 03 17:36:47 ReadyNAS xagent[28971]: sh: 1: kill: No such process
Nov 03 17:36:47 ReadyNAS systemd[1]: PID 21872 read from file /var/run/rcbrokerd.pid does not exist.
Nov 03 17:36:47 ReadyNAS xagent[28971]: msg_processor.c:206 ERROR: Failed to send msg to xhandler on port '127.0.0.1':10101.
Nov 03 17:36:48 ReadyNAS readynasd[1795]: sending signal 15 to procs
Nov 03 17:36:50 ReadyNAS readydropd[2032]: DEBUG:readydropd.c:884 /home has been changed
Nov 03 17:36:50 ReadyNAS readydropd[2032]: DEBUG:readydropd.c:663 Reload Share configs
Nov 03 17:36:51 ReadyNAS readynasd[1795]: User 'dkeigo' was deleted.
hi Keigo,
your NAS was registered on ReadyCLOUD with owner account dkeigo. On November 3, 2016 the NAS tried to connect to ReadyCLOUD server, but the server was not able to identify this device and returned response to the NAS requesting clenup local registration records. This is rare case and it can happen if the NAS configuration files get messed at some point. Unfortunally the logs provided do not allow to trace the root cause of the issue, I don't see anything suspicious there so far.
I recommend you to register your NAS back to ReadyCLOUD and see if the issue is resolved or still persists. Before you do this please go to NAS Admin page and open Cloud tab. If you still see ReadyCLOUD service toggled ON - please click 'Leave' button to make sure it is switched off.
There is one additional step you need to do before you can register your NAS to ReadyCLOUD again: your account dkeigo has to be upgraded to MyNETGEAR account. You can do it visiting ReadyCLOUD Portal https://readycloud.netgear.com and following the steps from this KB article How do I upgrade my ReadyCLOUD account if I do not have a MyNETGEAR.com account?
After you complete migration please return to the NAS Admin page and select Cloud tab. Click ReadyCLOUD toggle again to swith it ON and enter your MyNETGEAR account email and password, then click 'Join'.
When registration is complete - you should be able to access your NAS on ReadyCLOUD portal and use provided MyNETGEAR owner account to login to the NAS Admin configuration. The user should not be deleted from the NAS. If the problem persists - then a deeper research has to be done through the NAS secure diagnostics interface
10 Replies
Replies have been turned off for this discussion
Hi Keigo,
When was your ReadyNAS purchased? Might be best if you register the unit to check warranty support.
Regards,
I bought it 1 year ago.
But already support expired. I have only hardware warranty.
So I ask hear.
If you know same some issue, please let me know.
Hi Keigo,
Based on the description of the issue that you have provided, I may need to check this with others who can probably assist you and get back to you as soon as possible.
Thanks for your cooperation!
Regards,
hi Keigo,
your NAS was registered on ReadyCLOUD with owner account dkeigo. On November 3, 2016 the NAS tried to connect to ReadyCLOUD server, but the server was not able to identify this device and returned response to the NAS requesting clenup local registration records. This is rare case and it can happen if the NAS configuration files get messed at some point. Unfortunally the logs provided do not allow to trace the root cause of the issue, I don't see anything suspicious there so far.
I recommend you to register your NAS back to ReadyCLOUD and see if the issue is resolved or still persists. Before you do this please go to NAS Admin page and open Cloud tab. If you still see ReadyCLOUD service toggled ON - please click 'Leave' button to make sure it is switched off.
There is one additional step you need to do before you can register your NAS to ReadyCLOUD again: your account dkeigo has to be upgraded to MyNETGEAR account. You can do it visiting ReadyCLOUD Portal https://readycloud.netgear.com and following the steps from this KB article How do I upgrade my ReadyCLOUD account if I do not have a MyNETGEAR.com account?
After you complete migration please return to the NAS Admin page and select Cloud tab. Click ReadyCLOUD toggle again to swith it ON and enter your MyNETGEAR account email and password, then click 'Join'.
When registration is complete - you should be able to access your NAS on ReadyCLOUD portal and use provided MyNETGEAR owner account to login to the NAS Admin configuration. The user should not be deleted from the NAS. If the problem persists - then a deeper research has to be done through the NAS secure diagnostics interface
Thanks for advicing to me.
It make sence and all clear of my problem.
Thanks again.
Keigo.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
