Solved

Router reboots itself

  • 5 April 2019
  • 7 replies
  • 1627 views
S
My router reboots itself every few minutes and when I check the System Log, there is this, "daemonerrsyslog: stund:error on sendto (128), reopening socket" Any help? This is getting repetitive and annoying.
icon

Best answer by Drew C. 8 April 2019, 15:57

Router is a SmartRG SR360n on software version 2.5.0.15 and here is the log:



This isn't an Extreme Networks product and we're not able to provide you with support. I would suggest you contact SmartRG or your ISP for further assistance.



Their site indicates the following:

If you are a subscriber, please contact your Internet service provider directly with questions or concerns about equipment functionality and network reliability as we are a manufacturer who supplies products to service providers.
View original

7 replies

Drew C.
Userlevel 7
Please provide more information. Hardware model and software version will be helpful.
Are there any other logs before or after the reboot that may give a better indication of what happened?
S
Router is a SmartRG SR360n on software version
2.5.0.1. I'll post the system log when it reboots again, as I have turned it off and therefore lost the logs from when the problem happened. Recently, It's been rebooting every few seconds sometimes.
S
Apr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:32daemonerrsyslog: stund:error on sendto (128), reopening socketApr 7 20:46:36daemonerrsyslog: tr69c:996.940:clearModemConnectionURL:1351:could not get lock, lckRet=9809Apr 7 20:46:38daemonerrsyslog: PhpAnalytics:Could not find instHead for InternetGatewayDevice.WANDevice.{i}.WANDSLInterfaceConfig. {1,1,1}Apr 7 20:46:38daemonerrsyslog: PhpAnalytics:cmsObj_get for MDMOID_WAN_DSL_INTF_CFG error. cmsRet=9005Apr 7 20:46:38daemonerrsyslog: tr69c:998.581:readMessageFromSmd:1072:unrecognized msg 0x10002801Apr 7 20:46:49daemonalertkernel: Intrusion -> IN=ppp0.1 OUT= MAC= SRC=222.186.43.80 DST=190.59.8.239 LEN=40 TOS=0x00 PREC=0x00 TTL=236 ID=61279 PROTO=TCP SPT=56893 DPT=3389 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000Apr 7 20:47:02daemonalertkernel: Intrusion -> IN=ppp0.1 OUT= MAC= SRC=195.154.161.74 DST=190.59.8.239 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=47985 PROTO=TCP SPT=57336 DPT=4923 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000Apr 7 20:47:15daemonalertkernel: Intrusion -> IN=ppp0.1 OUT= MAC= SRC=62.173.149.167 DST=190.59.8.239 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=56086 PROTO=TCP SPT=57317 DPT=7801 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000Apr 7 20:47:26daemonalertkernel: Intrusion -> IN=ppp0.1 OUT= MAC= SRC=185.254.122.11 DST=190.59.8.239 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=13129 PROTO=TCP SPT=49268 DPT=5005 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000Apr 7 20:47:31daemonalertkernel: Intrusion -> IN=ppp0.1 OUT= MAC= SRC=112.112.142.20 DST=190.59.8.239 LEN=40 TOS=0x00 PREC=0x00 TTL=48 ID=32181 PROTO=TCP SPT=4808 DPT=37215 WINDOW=11760 RES=0x00 SYN URGP=0 MARK=0x8000000
S
Please provide more information. Hardware model and software version will be helpful.
Are there any other logs before or after the reboot that may give a better indication of what happened?

Router is a SmartRG SR360n on software version 2.5.0.15 and here is the log:

3 Attachments
Drew C.
Userlevel 7
Router is a SmartRG SR360n on software version 2.5.0.15 and here is the log:

This isn't an Extreme Networks product and we're not able to provide you with support. I would suggest you contact SmartRG or your ISP for further assistance.

Their site indicates the following:
If you are a subscriber, please contact your Internet service provider directly with questions or concerns about equipment functionality and network reliability as we are a manufacturer who supplies products to service providers.
S

Router is a SmartRG SR360n on software version 2.5.0.15 and here is the log:This isn't an Extreme Networks product and we're not able to provide you with support. I would suggest you contact SmartRG or your ISP for further assistance.

Their site indicates the following:

If you are a subscriber, please contact your Internet service provider directly with questions or concerns about equipment functionality and network reliability as we are a manufacturer who supplies products to service providers.


Very well. Thank You for your help.
S
Thank you so much... I had the same problem
famous IP address login panel

Reply