- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all:
I’ve got an issue that seems to have just started within the last week or so -
My FIOS router seems to suddenly lose its connection completely, at approximately 10AM EST every day.
(the ‘globe’ icon on the front goes red, router eventually re-gains connection and devices come back up)
In the system logs, I’m seeing a similar pattern when this happens:
Apr 11 13:57:18 2017 local1.err<139> named[1333]: isc_socket_accept() failed: shutting down
Apr 11 13:57:18 2017 local1.err<139> named[1333]: client.c:2771: unexpected error:
Apr 11 13:57:18 2017 local1.err<139> named[1333]: zone fios-router.home/IN/internal-clients: not loaded due to errors.
Apr 11 13:57:18 2017 local1.err<139> named[1333]: zone fios-router.home/IN/internal-clients: NS 'FIOS_Quantum_Gateway.fios-router.home' has no address records (A or AAAA)
The Advanced Logs seem to show the following pattern (edited due to size):
Apr 11 13:57:22 2017 user.err<11> bhr4: System: getaddrinfo for 'www98.verizon.com' returns: -11: 'System error'
Apr 11 13:57:19 2017 user.err<11> bhr4: Firewall.FirewallLog: Failed to execute script: iptables -t nat -F PC_PREROUTING iptables -t nat -F PC_GUEST_PREROUTING iptables -t nat -D GNW_OPEN_APPR_GUESTS_HOOK -j PC_GUEST_PREROUTING iptables -t nat -D PREROUTING_GNW -j PC_GUEST_PREROUTING
Apr 11 13:57:18 2017 user.err<11> lighttpd[1342]: (log.c.194) server started
Apr 11 13:57:18 2017 user.err<11> bhr4: ProcessMonitorBs: Process not running
Apr 11 13:57:17 2017 user.err<11> bhr4: Firewall.FirewallLog: Failed to execute script: iptables -t nat -F PC_PREROUTING iptables -t nat -F PC_GUEST_PREROUTING iptables -t nat -D GNW_OPEN_APPR_GUESTS_HOOK -j PC_GUEST_PREROUTING iptables -t nat -D PREROUTING_GNW -j PC_GUEST_PREROUTING
Apr 11 13:57:16 2017 user.debug<15> rsad: RsaDaemonLog: Enter: void GreenWave::RsaDaemon::serve()
Apr 11 13:57:16 2017 user.info<14> rsad: RsaDaemonLog: GreenWave Systems Inc. (c) RSA Daemon v. 1.0.0
Apr 11 13:57:12 2017 user.err<11> bhr4: Firewall.PortTriggeringLog: Service: TFTP Triggering - Trivial File Transfer Protocol is not of type NetworkServiceType::PortTriggeringService
Apr 11 13:57:12 2017 user.err<11> bhr4: Firewall.PortTriggeringLog: Service: L2TP Triggering - Layer Two Tunneling Protocol is not of type NetworkServiceType::PortTriggeringService
Apr 11 13:57:05 2017 user.debug<15> System: BHR4 restart event
Apr 11 13:49:51 2017 user.debug<15> System: BHR4 time change event
Just wondering if anyone else has encountered any similar behavior?
Seems to me that it’s dropping table/record info, but I’m not sure if that’s because of the time change event or not.
Thanks for any info, if it looks familiar…
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having a similar issue. Connection goes down around 8:50pm and back up 10-11am the next morning. The system log is slightly different.
May 8 19:25:24 2017 local1.err<139> named[1324]: client 127.0.0.1#51139 (FIOS_Quantum_Gateway): view internal-clients: query failed (SERVFAIL) for FIOS_Quantum_Gateway/IN/A at query.c:6545 May 8 19:25:24 2017 local1.err<139> named[1324]: client 127.0.0.1#43624 (FIOS_Quantum_Gateway): view internal-clients: query failed (SERVFAIL) for FIOS_Quantum_Gateway/IN/A at query.c:6545 May 8 19:25:24 2017 local1.err<139> named[1324]: client 127.0.0.1#38094 (FIOS_Quantum_Gateway.fios-router.home): view internal-clients: query failed (SERVFAIL) for FIOS_Quantum_Gateway.fios-router.home/IN/A at query.c:6545 May 8 19:25:24 2017 local1.err<139> named[1324]: client 127.0.0.1#48757 (FIOS_Quantum_Gateway.fios-router.home): view internal-clients: query failed (SERVFAIL) for FIOS_Quantum_Gateway.fios-router.home/IN/A at query.c:6545 May 8 19:25:22 2017 local0.info<134> dhcpcd[1468]: eth0: soliciting a DHCP lease May 8 19:25:22 2017 local0.info<134> dhcpcd[1468]: eth0: soliciting an IPv6 router May 8 19:25:22 2017 local0.warn<132> dhcpcd[1468]: eth0: configured as a router, not a host May 8 19:25:22 2017 local0.warn<132> dhcpcd[1468]: all: configured as a router, not a host May 8 19:25:22 2017 local0.info<134> dhcpcd[1468]: version 6.0.5 starting May 8 19:25:20 2017 local3.info<158> dhcpd: Sending on Socket/fallback/fallback-net May 8 19:25:20 2017 local3.info<158> dhcpd: Sending on LPF/br-lan/20:c0:47:21:90:3b/192.168.1.0/24 May 8 19:25:20 2017 local3.info<158> dhcpd: Listening on LPF/br-lan/20:c0:47:21:90:3b/192.168.1.0/24 May 8 19:25:20 2017 local3.err<155> dhcpd: May 8 19:25:20 2017 local3.err<155> dhcpd: to which interface br-guest is attached. ** May 8 19:25:20 2017 local3.err<155> dhcpd: in your dhcpd.conf file for the network segment May 8 19:25:20 2017 local3.err<155> dhcpd: you want, please write a subnet declaration May 8 19:25:20 2017 local3.err<155> dhcpd: ** Ignoring requests on br-guest. If this is not what May 8 19:25:20 2017 local3.err<155> dhcpd: No subnet declaration for br-guest (no IPv4 addresses). May 8 19:25:20 2017 local3.err<155> dhcpd: May 8 19:25:20 2017 local3.info<158> dhcpd: Wrote 2 leases to leases file. May 8 19:25:20 2017 local3.info<158> dhcpd: Wrote 0 class decls to leases file. May 8 19:25:20 2017 local3.info<158> dhcpd: For info, please visit https://www.isc.org/software/dhcp/ May 8 19:25:20 2017 local3.info<158> dhcpd: All rights reserved. May 8 19:25:20 2017 local3.info<158> dhcpd: Copyright 2004-2014 Internet Systems Consortium. May 8 19:25:20 2017 local3.info<158> dhcpd: Internet Systems Consortium DHCP Server 4.2.6 May 8 19:25:18 2017 local1.err<139> named[1324]: zone FIOS_Quantum_Gateway/IN/internal-clients: not loaded due to errors. May 8 19:25:18 2017 local1.err<139> named[1324]: zone FIOS_Quantum_Gateway/IN/internal-clients: NS 'FIOS_Quantum_Gateway' has no address records (A or AAAA) May 8 19:25:18 2017 local1.err<139> named[1324]: zone myfiosgateway.com/IN/internal-clients: not loaded due to errors. May 8 19:25:18 2017 local1.err<139> named[1324]: zone myfiosgateway.com/IN/internal-clients: NS 'myfiosgateway.com' has no address records (A or AAAA) May 8 19:25:18 2017 local1.err<139> named[1324]: zone fios-router.home/IN/internal-clients: not loaded due to errors. May 8 19:25:18 2017 local1.err<139> named[1324]: zone fios-router.home/IN/internal-clients: NS 'FIOS_Quantum_Gateway.fios-router.home' has no address records (A or AAAA)
Technicians came in three times but nothing ever worked so far. Please share if you resolved the issue.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi zchen,
Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you. Please go to your profile page for the forum and scroll down the page to an area titled "My Support Cases". You can reach your profile page by clicking on your name located above your post, or at the top right of this page.
Under "My Support Cases" you will find a link to the private board where you and the agent may exchange information. The title of your post is the link. This should be checked on a frequent basis, as the agent may be waiting for information from you before they can proceed with any actions. To ensure you know when they have responded to you, you may subscribe to the case. At the top right of your support case there is a gear icon which provides a drop down menu with support case options. Click that and choose "subscribe". Please keep all correspondence regarding your issue in the private support portal.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So you lose internet access for nearly 12 hours a day?
What indications do you see on the router when it fails?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there a resolution for this issue yet? I'm having the same problem with almost the exact same err codes the first person posted.