×

Switch Account

G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Reply
Highlighted
Copper Contributor
Copper Contributor
Posts: 16
Registered: ‎11-18-2017

G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 1 of 10
(654 Views)

Over the past few days, many of my wifi clients have been having internet connectivity / DHCP issues. Debugging this myself, I noticed that this problem appears to be happening on my 2.4GHz network (5GHz and wired are fine). I changed my 2.4GHz channel selection from Auto to fixed and it appeared to be working better until my son complained his video froze again. UGH. I went over to my office and noticed the router rebooting. Fabulous. Yesterday Mohamed tried explaining to me that my clients were the issue and he suggested I upgraded my service. I logged into my router and looked at the SystemLog and this is proof my router was rebooted "by ACS". 

 

Apr 12 16:08:23 2020 local3.info<158> dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Apr 12 16:08:23 2020 local3.info<158> dhcpd: All rights reserved.
Apr 12 16:08:23 2020 local3.info<158> dhcpd: Copyright 2004-2017 Internet Systems Consortium.
Apr 12 16:08:23 2020 local3.info<158> dhcpd: Internet Systems Consortium DHCP Server 4.3.6
Apr 12 16:08:20 2020 local1.info<142> System: System is now initialized. Reason undefined. Reboot count 2. Running firmware 02.02.00.16 (02.02.00.16_20190528_022627_9fe6379f_jenkins)
Apr 12 16:08:10 2020 uucp.debug<71> System: BHR4 restart event (soft). Reason: undefined
Apr 12 16:08:10 2020 local3.debug<159> System: BHR4 restart event (soft). Reason: undefined
Apr 12 16:08:10 2020 local1.debug<143> System: BHR4 restart event (soft). Reason: undefined
Apr 12 16:08:10 2020 local0.debug<135> System: BHR4 restart event (soft). Reason: undefined
Apr 12 16:06:40 2020 local1.info<142> System: Performing software shutdown. Reason undefined. Running firmware 02.02.00.16 (02.02.00.16_20190528_022627_9fe6379f_jenkins)
Apr 12 16:06:38 2020 local1.info<142> cwmpclient[1923]: Reboot requested by ACS

9 REPLIES 9
Highlighted
Gold Contributor VI Gold Contributor VI
Gold Contributor VI
Posts: 1,560
Registered: ‎12-02-2012

Re: G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 2 of 10
(636 Views)

You're talking mostly to other users here.  If you want help from Verizon, try their Twitter support or the VZ Direct forum at DSLreports.com.  They are staffed by their social media support team which often does a better job then the phone support.

 

We users may be able to give you some pointers.  I'm not sure many of us know what "ACS" means in the router log, though.  It would help to know the router model and if the problem occurs on Ethernet connected devices too.

 

Any other details you can describe, such as status lights during reboots, might help the user base here give you useful suggestions.

 

Highlighted
Copper Contributor
Copper Contributor
Posts: 16
Registered: ‎11-18-2017

Re: G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 3 of 10
(580 Views)

The router model is G1100 and the problem only happens on 2.4GHz connection (5GHz and wired are fine).

 

During the reboot, I noticed all lights go off...followed by the globe turning solid red...followed by a white globe and a white wifi signal. 

Highlighted
Copper Contributor
Copper Contributor
Posts: 16
Registered: ‎11-18-2017

G1100 SystemLog: Continual named errors starting on April 10, 2020

Message 4 of 10
(564 Views)

Been having various problems with my internet connectivity. One thing I noticed is continual error message in my System Log. Prior to this, the log would show INFORMATION messages every hour. Now it is showing named DNS errors non-stop.

 

Apr 10 09:04:21 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:04:21 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:04:21 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:04:16 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:02:55 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:02:55 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:02:55 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:02:50 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:01:35 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:01:35 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:01:35 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:01:30 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 08:59:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 08:59:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 08:59:50 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 08:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 07:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 06:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 05:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 04:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 03:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 02:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 01:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 00:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 23:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 22:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 21:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 20:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 19:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 18:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 17:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 16:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 15:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 14:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 13:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 12:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 11:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds

Highlighted
Copper Contributor
Copper Contributor
Posts: 16
Registered: ‎11-18-2017

G1100 AdvancedLog: Continual SSL_shutdown errors starting on April 11, 2020

Message 5 of 10
(562 Views)

Starting on April 11, 2020, my G1100 router has been logging continual error messages about lighttpd. Does anyone know how to check if a recent update has been pushed to the router? I have been seeing various issues in the past couple of days. Below is a snippet from my AdvancedLog.

 

Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:10 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:37 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:26 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:44 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:41 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 12:43:35 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587213815, active: 1
Apr 11 10:56:14 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172, timestamp: 1587207374, active: 1
Apr 11 09:02:28 2020 local7.info<190> miniupnpd[1741]: Removing port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172
Apr 11 09:02:14 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172, timestamp: 1587200534, active: 1
Apr 11 04:16:17 2020 local7.info<190> miniupnpd[1741]: Removing port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157
Apr 11 04:15:50 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587183350, active: 1
Apr 11 03:53:52 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587182032, active: 1
Apr 11 02:31:44 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587177104, active: 1
Apr 11 01:31:44 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587173504, active: 1
Apr 11 00:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587169899, active: 1
Apr 10 23:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587166299, active: 1
Apr 10 22:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587162699, active: 1
Apr 10 21:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587159099, active: 1
Apr 10 20:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587155499, active: 1
Apr 10 19:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587151899, active: 1
Apr 10 18:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587148299, active: 1
Apr 10 17:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587144699, active: 1
Apr 10 16:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587141099, active: 1

Highlighted
Copper Contributor
Copper Contributor
Posts: 16
Registered: ‎11-18-2017

Re: G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 6 of 10
(577 Views)

I'm curious if anyone knows how to check when their router was last updated. These reboot messages started happening and are labeled with 02.02.00.16

 

Apr 11 13:08:49 2020 local1.info<142> System: System is now initialized. Reason undefined. Reboot count 9. Running firmware 02.02.00.16 (02.02.00.16_20190528_022627_9fe6379f_jenkins)
Apr 11 13:08:40 2020 uucp.debug<71> System: BHR4 restart event (soft). Reason: undefined
Apr 11 13:08:40 2020 local1.debug<143> System: BHR4 restart event (soft). Reason: undefined
Apr 11 13:08:40 2020 local0.debug<135> System: BHR4 restart event (soft). Reason: undefined
Apr 11 13:07:10 2020 local1.info<142> System: Performing software shutdown. Reason undefined. Running firmware 02.02.00.16 (02.02.00.16_20190528_022627_9fe6379f_jenkins)
Apr 11 13:07:09 2020 local1.info<142> cwmpclient[2026]: Reboot requested by ACS

Highlighted
Contributor
Contributor
Posts: 1
Registered: ‎04-24-2020

Re: G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 7 of 10
(352 Views)

Did anybody resolve this issue?  I am facing this exact same problem( including logs).  For last week I have vested lots of time with Verizon support.  They have changed my router and ont. But, I still have same problem.  They are telling me that there is some device in my house that is causing this.  I have fios for almost two years without any issue and love it.  I am facing this issue for last several weeks only.  Since all of us are facing same issue, It's seems to me that Verizon has applied some upgrade to router or, something on Verizon network is causing this.  Verizon, please you should resolve this instead of each of us calling you and wasting everybody's time.  

Highlighted
Contributor
Contributor
Posts: 1
Registered: ‎05-20-2020

Re: G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 8 of 10
(173 Views)

Not sure if this is the same issue, but we lost internet twice in the past hour due to the router rebooting (twice).  

 

After looking at the router logs and speaking with Verizon:

- ACS = Auto-Config (Service?  They weren't sure)

- They were able to see that my router's firmware was updated as of the second reboot, to version 02.02.00.16 (from .14, they said), and that this was to install security fixes.

 

They also said that they don't do the firmware update - that the company Gateway, that makes the router, does, and that they don't have control over it.  (And that they can contact Gateway if ever needed, but the number for that is not public.)

 

Hope that helps!

Highlighted
Platinum Contributor III Platinum Contributor III
Platinum Contributor III
Posts: 5,867
Registered: ‎09-24-2008

Re: G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 9 of 10
(117 Views)

About the ACS, see

 

https://en.wikipedia.org/wiki/TR-069

 

I am sure that the ISP controls that.

 

Either:

 

The techs that you were speaking to are not high techs to know that yet.

 

OR if they do know that, they are not allowed to talk about or acknowledge it.

If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.


 

Highlighted
Platinum Contributor III Platinum Contributor III
Platinum Contributor III
Posts: 7,477
Registered: ‎12-15-2010

Re: G1100 Randomly Rebooting (preceded by Wifi Internet Connectivity Issues)

Message 10 of 10
(83 Views)

Do all of you have UPnP enabled in your router? Go to the Advanced settings in the router's Admin Web Interface and disable it if so. See if that helps.

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Covid19


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.