Explore & discover

Helpful Links

NVG589 Log file errors

ACE - Guru

NVG589 Log file errors

I see this has been discussed a number of times before.

Arris and AT&T have ideas what's causing the issue but nobody is coming up with a solution.

It's not only the log file filling up so quickly it's also the odd freezes when trying to browse or receive emails. When it works it works very well, getting consistent 29Mb/s speeds.

 

This problem started when I was upgraded from Bpon to Gpon in December. AT&T say it's a NVG589 firmware issue and ARRIS say it's AT&T's problem. So, AT&T, when can we expect a solution?

 

Here is an extract of the log file

 

2015-02-02T12:30:25-08:00 L4 cwmp[1524]: Continue GetParameterValuesResponse (chunk-length - 0)
2015-02-02T12:30:25-08:00 L5 cwmp[1524]: Closing connection on HTTP 204
2015-02-02T12:30:25-08:00 L5 cwmp[1524]: (SSL) Closing Connection: cwmp.c01.sbcglobal.net
2015-02-02T12:37:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T12:37:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T12:43:18-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T12:43:18-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T12:43:31-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T12:43:31-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T12:51:22-08:00 L3 sdb[333]: ELAN: Port lan-4 (eth3) is DOWN
2015-02-02T12:53:13-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T12:53:13-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17
2015-02-02T12:58:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T12:58:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T12:59:01-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T12:59:01-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T13:08:58-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:08:58-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17
2015-02-02T13:13:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:13:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T13:14:48-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T13:14:48-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T13:24:43-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:24:43-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T13:24:47-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:24:47-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17
2015-02-02T13:28:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:28:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T13:30:36-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T13:30:36-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T13:40:32-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:40:32-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T13:43:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:43:05-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T13:46:24-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T13:46:24-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T13:56:19-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:56:19-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T13:56:21-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:56:21-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17
2015-02-02T13:58:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T13:58:20-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T14:02:25-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T14:02:25-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T14:12:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:12:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T14:18:03-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:18:03-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T14:18:08-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T14:18:08-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T14:28:06-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:28:06-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17
2015-02-02T14:33:04-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:33:04-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T14:33:54-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T14:33:54-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T14:43:50-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:43:50-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T14:43:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:43:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17
2015-02-02T14:48:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:48:02-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T14:49:42-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-02T14:49:42-08:00 L4 mcp[1130]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A80147 00000000 0000BEEF

2015-02-02T14:51:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:51:15-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T14:59:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T14:59:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T15:03:25-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:03:25-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T15:15:24-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:15:24-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T15:18:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:18:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T15:29:52-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:29:52-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T15:29:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:29:56-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T15:31:08-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53'
2015-02-02T15:31:08-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.53' is now responding
2015-02-02T15:31:12-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:31:12-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T15:31:16-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:31:16-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 17
2015-02-02T15:33:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:33:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T15:46:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:46:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T15:48:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:48:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 15
2015-02-02T15:50:39-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.153'
2015-02-02T15:50:40-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding
2015-02-02T15:53:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:53:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 12
2015-02-02T15:55:56-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53'
2015-02-02T15:55:56-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.53' is now responding
2015-02-02T15:55:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T15:55:59-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T15:57:08-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.153'
2015-02-02T15:57:08-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding
2015-02-02T16:03:22-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53'
2015-02-02T16:03:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T16:03:26-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T16:03:27-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding
2015-02-02T16:03:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 5
2015-02-02T16:03:40-08:00 L3 dnsmasq[1231]: bad name at /var/etc/hosts.dyn line 16
2015-02-02T16:09:23-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.153'
2015-02-02T16:09:23-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.153' is now responding
2015-02-02T16:10:26-08:00 L3 dnsmasq[1231]: no responses from nameserver '99.99.99.53'
2015-02-02T16:10:28-08:00 L3 dnsmasq[1231]: nameserver '99.99.99.53' is now responding
Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
7,127 Views
Message 1 of 46
Expert

Re: NVG589 Log file errors

@RhodesMan Click the ATT Uverse Care link in my signature, send the PM, explain your situation.

 

Include your account #, email address and a good phone # (land or cell) and time to contact you on.

Check the blue PM envelope, upper right on every page, for their reply. Good luck Smiley Wink

 

Chris
__________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? PM ATT Uverse Care (all service problems)
ATT Customer Care(all other problems)
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

Message 2 of 46
ACE - Guru

Re: NVG589 Log file errors

Hi Chris,

I did that last week. I have been in touch with them.

They dont have an answer for the logfile errors.

 

Thanks

 

Joel

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 3 of 46
Mentor

Re: NVG589 Log file errors

Hi Joel,

 

I have been getting the same errors.  I was communicating with "David T" from AT&T in the Private Message area for awhile, but decided he didn't really know much.  However, he did have me remove the surge protector, which stopped the intermittent reboot problem.

 

I have also been working with a Senior AT&T Tech and he really is in the same boat that we are in.  The NVG589 is just not ready for production.  While AT&T and Motorola fight about whose problem it is, we all suffer.

 

Barry

Message 4 of 46
ACE - Guru

Re: NVG589 Log file errors

Hi Barry,

I have also been going back and forth with the tech. folks at AT&T.

They are very willing to help but it's a bit of a hit and miss approach.

 

The questions is are these log files errors of any significance and do they affect performance in any way? AT&T are convinced that any random reboots I am getting have nothing to do with the errors. I believe that if the RG sees too many errors then it may reboot.

 

They have told me that they are aware of the errors and are working on a firmware upgrade. The current firmware came out the middle of last year so I would not hold my breath waiting for the upgrade. The log file is a useful tool when it's not cluttered with all of these errors.

 

My reboot problem only started when they did the Bpon to Gpon upgrade. I did not take a look at the 3801HGV log file before they exchanged it for the NVG589 so I don't know if the upgrade was the cause of the errors or if it's something to do with the NVG589.

 

I will say though that I am enjoying the wireless N and gigabit port speeds. I now get solid speedtest results rather than varying ones.

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 5 of 46
Expert

Re: NVG589 Log file errors

@RhodesMan It looks like it was having trouble w/the IPv6 DNS service in your log file at the bottom, I know I could turn off IPv6 in my 3800, maybe you can on the 589.  It returned it to the IPv4 DNS servers here.

 

The other errors look like problem w/a Host file that is in use, dnsmasq. Smiley Wink

 

Chris
__________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? PM ATT Uverse Care (all service problems)
ATT Customer Care(all other problems)
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

Message 6 of 46
ACE - Guru

Re: NVG589 Log file errors

Good suggestion Chris but one I had already tried. I switched off IPv6 for the last hour and the results don't change as follows. The only thing that made a bit of a difference was having only one computer attached to the NVG589 and setting the DNS on that computer to 8.8.8.8  I then started adding back devices and the one that caused the most number of errors was when Uverse TV was reattached. I have all the log results from that exercise if you are interested.

 

2015-02-07T12:26:04-08:00 L3 sdb[330]: lan_redirect_status_get: error
2015-02-07T12:26:04-08:00 L3 sdb[330]: dns_lan_redirect_notify. DOWN. restart proxy
2015-02-07T12:26:05-08:00 L3 sdb[330]: lan_redirect_status_get: error
2015-02-07T12:26:05-08:00 L3 sdb[330]: dns_lan_redirect_notify. DOWN. restart proxy
2015-02-07T12:26:05-08:00 L5 cwmp[1521]: Post SetParameterValuesResponse
2015-02-07T12:26:05-08:00 L5 cwmp[1521]: Receive GetParameterValues
2015-02-07T12:26:05-08:00 L5 cwmp[1521]: Post GetParameterValuesResponse (chunk-length - 2376)
2015-02-07T12:26:05-08:00 L4 cwmp[1521]: Continue GetParameterValuesResponse (chunk-length - 0)
2015-02-07T12:26:05-08:00 L5 cwmp[1521]: Receive SetParameterValues
2015-02-07T12:26:06-08:00 L3 sdb[330]: lan_redirect_status_get: error
2015-02-07T12:26:06-08:00 L3 sdb[330]: dns_lan_redirect_notify. DOWN. restart proxy
2015-02-07T12:26:06-08:00 L5 cwmp[1521]: Post SetParameterValuesResponse
2015-02-07T12:26:06-08:00 L5 cwmp[1521]: Closing connection on HTTP 204
2015-02-07T12:26:06-08:00 L5 cwmp[1521]: (SSL) Closing Connection: cwmp.c01.sbcglobal.net
2015-02-07T12:26:08-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:26:08-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 10
2015-02-07T12:27:32-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:27:32-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 10
2015-02-07T12:27:45-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T12:27:45-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:32:31-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T12:32:31-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:35:13-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T12:35:13-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:37:41-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T12:37:41-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:46:08-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 10
2015-02-07T12:46:08-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 12
2015-02-07T12:46:19-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 10
2015-02-07T12:46:19-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 12
2015-02-07T12:47:16-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T12:47:25-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 10
2015-02-07T12:47:25-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 12
2015-02-07T12:47:25-08:00 L3 dnsmasq[3194]: nameserver '68.94.156.8' is now responding
2015-02-07T12:50:10-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T12:50:45-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T12:52:44-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T12:52:44-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:54:42-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T12:54:42-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:55:49-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T12:56:02-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T12:56:28-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T12:56:29-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T12:57:32-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T12:57:32-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T12:59:34-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:00:10-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:00:24-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:00:26-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:00:56-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:00:56-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:01:25-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:01:25-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:02:01-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:02:01-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:02:35-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:02:35-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:03:15-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:03:20-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:03:20-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:03:21-08:00 L3 dnsmasq[3194]: nameserver '68.94.156.8' is now responding
2015-02-07T13:03:32-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:03:32-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:05:30-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:05:30-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:07:05-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:07:05-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:07:50-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:07:50-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:08:39-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:08:39-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:11:01-08:00 L4 mcp[3754]: mcp[handle_timers]: group (0xE00000FD) timer expired - dropping membership

2015-02-07T13:11:01-08:00 L4 mcp[3754]: mcp[handle_timers]: group (0xE00000FD) has stale rep/src entries C0A8014F 00000000 0000BEEF

2015-02-07T13:14:02-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:14:02-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:16:13-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:16:13-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:17:10-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:17:22-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:17:22-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:17:22-08:00 L3 dnsmasq[3194]: nameserver '68.94.156.8' is now responding
2015-02-07T13:18:33-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:19:26-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:20:22-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:20:22-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:22:05-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:22:05-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:22:19-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:22:19-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:23:36-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.156.8'
2015-02-07T13:23:36-08:00 L3 dnsmasq[3194]: nameserver '68.94.156.8' is now responding
2015-02-07T13:24:36-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:24:36-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:26:57-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:26:57-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:27:06-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:27:06-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
2015-02-07T13:28:34-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.157.8'
2015-02-07T13:28:34-08:00 L3 dnsmasq[3194]: nameserver '68.94.157.8' is now responding
2015-02-07T13:28:55-08:00 L3 dnsmasq[3194]: no responses from nameserver '68.94.156.8'
2015-02-07T13:28:55-08:00 L3 dnsmasq[3194]: nameserver '68.94.156.8' is now responding
2015-02-07T13:32:08-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 6
2015-02-07T13:32:08-08:00 L3 dnsmasq[3194]: bad name at /var/etc/hosts.dyn line 8
Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 7 of 46
Mentor

Re: NVG589 Log file errors

Hi Joel,

 

One would think that AT&T would have the talent to fix problems rather than making suggestions.  I have had IPv6 turned off since 1/12/2015, 13:24:33 with no noticeable difference.  

 

I'm wondering if they'll get this problem resolved before IPv6 becomes necessary. I'm doing diagnostics and paying for the "service" as you are.

 

Barry

 

 

Message 8 of 46
ACE - Guru

Re: NVG589 Log file errors

You are quite right Barry.

A friend of mine had Uverse via bonded pair installed yesterday.

His NVG589 started showing the same errors minutes after it was installed.

 

No doubt every NVG589 out there is doing this. It seems that in most instances it does not affect performance so there does not seem to be a lot of incentive to get this fixed.

 

I do do often notice certain websites struggling to resolve their address coinciding with a whole slew of error messages.

 

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 9 of 46
Tutor

Re: NVG589 Log file errors

I am also having this issue....  it is causing all kinds of delays in streaming content (especially to portable devices connected to the wi-fi).

 

I've already had a technicial replace my modem and that only temporarily fixed the issue... as 3 weeks later it is doing it again.

 

So frustrating...   I wish that Uverse had some updated information on this issue for us.    Is the problem in our hardware?

Message 10 of 46
ACE - Guru

Re: NVG589 Log file errors

There could be other environmental factors causing your WiFi problems.

 

The main problem though is that as long as the NVG589 continues to spew out all of the errors shown in the log file and we as consumers continue to have glitches the only assumption we can draw is that the glitches are related to the errors.

 

I have not had a RG reboot in nearly 2 weeks.

My WiFi is nice and fast.

I still continue though to have the odd site that struggles to resolve and this coincides with errors like below. Other times these errors continue but sites work OK.

 

2015-02-16T07:52:29-08:00 L3 dnsmasq[2977]: no responses from nameserver '99.99.99.53'
2015-02-16T07:52:29-08:00 L3 dnsmasq[2977]: nameserver '99.99.99.53' is now responding
2015-02-16T07:53:35-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 9
2015-02-16T07:53:35-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 11
2015-02-16T07:53:38-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 9
2015-02-16T07:53:38-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 11
2015-02-16T07:54:05-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 9
2015-02-16T07:54:05-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 11
2015-02-16T07:58:41-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 9
2015-02-16T07:58:41-08:00 L3 dnsmasq[2977]: bad name at /var/etc/hosts.dyn line 11
2015-02-16T07:58:53-08:00 L4 mcp[3754]: mcp[handle_timers]: group (0xE00000FC) timer expired - dropping membership

2015-02-16T07:58:53-08:00 L4 mcp[3754]: mcp[handle_timers]: group (0xE00000FC) has stale rep/src entries C0A8014F 00000000 0000BEEF
Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 11 of 46
Tutor

Re: NVG589 Log file errors

I don't think my problems are environmental...

 

I have slow loading pages over both wired and wireless connections here...  but it is definitely felt the hardest with my wireless devices.   

 

On Facebook for example, it takes forever it seems to get any kind of video to start running... however on my phone when I switch to a 3G/4G signal, those items load right up.   It only happens when I'm using Uverse connection.   I've also been on other open wireless, and it doesn't happen there either...

 

Either way, whatever this problem is, I truly hope that a solution can be found for it....

Message 12 of 46
ACE - Guru

Re: NVG589 Log file errors

DF. Have you followed Chris's suggestion to PM the customer service folks here? They can run tests to check the quality of the signal up to your house.
Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 13 of 46
ACE - Guru

Re: NVG589 Log file errors

I got enter to quickly. Something else to try.
Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 14 of 46
ACE - Guru

Re: NVG589 Log file errors

Sorry about this. The mobile site posts the cooment every time I hit enter. Unplug all devices from the RG except a directly wired computer. Then do some tests and report back here. Good luck. I know how frustrating these issues can be.
Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 15 of 46
Share this topic
Share this topic
Announcements

Are you having trouble logging in? Is your email password not working? Let us show you how to Reset your Email Password using myAT&T!

Additional Support