Our Community Forums will be closing on June 27, 2024. Please visit att.com/support for all your support needs.
RhodesMan's profile
ACE - Guru

ACE - Guru

 • 

992 Messages

Tuesday, February 3rd, 2015 12:25 AM

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 Achiever*
*I am not an AT&T employee, and 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.

Mentor

 • 

70 Messages

9 years ago

Joel,
 
Unfortunately, once the RG re-boots, the previous log entries are gone. 
 
 
I have not had a re-boot since I removed the surge protector.  From that point on, the only two items plugged into the same outlet were the NVG589 and the U-Verse TV WAP.  Since then, I moved the WAP across the room with a longer CAT-5 cable, which, I swear, has improved the TV quality.  One of the issues put forward by one of the AT&T techs was the number of wireless devices in close proximity.   Since I was not going to move my printer or stop using a wireless mouse, this seemed to be a good move.
 
 
The next item on the agenda is to phsically transfer my service to another port.
 
 
Barry

Tutor

 • 

6 Messages

9 years ago

How do you get AT&T to change your port?  Is there any special instructions?   Also, what level of tech support  has to do this?

Mentor

 • 

70 Messages

9 years ago

The tech reset the port connection, which resolved the problem for about eight hours. When problembs began again, I contacted him and he said he would escalate and schedule a line tech to physically change the port.  I'm still waiting, somewhat patiently.

ACE - Guru

 • 

992 Messages

9 years ago

Barry,

Sorry to hear you are still having problems.

Has the tech, tested the signal to noise ratio of the incoming signal?

If this is good then changing ports will probably not make a difference and will indicate that the problem is probably somewhere else.

 

Joel

 

 

 

Mentor

 • 

70 Messages

9 years ago

I don’t know. I would “assume” that either he tested that or that test will be ordered and/or conducted before the port is changed. I try to post progress in the couple of discussions on the topic. The tech indicated this would take a few days and I would be notified when the change would take effect as there would obviously be a loss of service during the change.
Stay tuned!

Tutor

 • 

6 Messages

9 years ago

Thank you for the suggestion... I'm going to try this.     So far so good...  definitely not as much buffering going on on my mobile devices with the IPv6 turned off.    I truly hope that this is the fix to this problem.

Mentor

 • 

35 Messages

9 years ago

@DarkFury - hey, no problem. Glad to help. Please let us know how things look tomorrow and maybe a few others can chime in as well and test this out on their end and report back their results. That way we can start getting the word out on several other threads where folks are having similar issues. Maybe after a week or two it will propagate out to a lot of the users that are having this IPv6 issue and not realize it's the culprit. Because right now, we aren't in a desperate need for IPv6 functionality at this point. And hopefully when we do get to that point AT&T can fix this, what I believe to be a IPv6 DNS issue. Good luck!

ACE - Guru

 • 

992 Messages

9 years ago

Again I am pleased that turning off IPv6 is making a difference for some of you.

This has not been my experience though. All the namserver errors my logfile is reporting is with 99.99.99.53 which is the IPv4 namerserver.

I am however not having the same amount of trouble as many of you although often there is a many second gap between 99.99.99.53 not responding and responding causing website problems.

 

I noticed some new errors in the logfile this evening as follows:-

 

2015-03-10T19:40:23-07:00 L5 cwmp[1518]: next Periodic Inform after 86400 s
2015-03-10T19:40:23-07:00 L4 cwmp[1518]: Resolving ACS URL - Retry 0
2015-03-10T19:40:23-07:00 L5 cwmp[1518]: Connect to https://cwmp.c01.sbcglobal.net/cwmp/services/CWMP [144.160.14.34] Retry 0
2015-03-10T19:40:24-07:00 L5 cwmp[1518]: (SSL) Connect Success: cwmp.c01.sbcglobal.net
2015-03-10T19:40:24-07:00 L5 cwmp[1518]: (SSL) Certificate Verify Success: cwmp.c01.sbcglobal.net
2015-03-10T19:40:27-07:00 L4 sdb[331]: IGMP: /var/tmp/mcp.stats.1 not found! - Item not found
2015-03-10T19:40:27-07:00 L5 cwmp[1518]: Post Inform - reason 2 PERIODIC 
2015-03-10T19:40:28-07:00 L5 cwmp[1518]: Receive InformResponse
2015-03-10T19:40:28-07:00 L5 cwmp[1518]: Post 0
2015-03-10T19:40:28-07:00 L5 cwmp[1518]: Receive GetParameterValues
2015-03-10T19:40:28-07:00 L5 cwmp[1518]: Post GetParameterValuesResponse (chunk-length - 2376)
2015-03-10T19:40:28-07:00 L4 cwmp[1518]: Continue GetParameterValuesResponse (chunk-length - 0)
2015-03-10T19:40:28-07:00 L5 cwmp[1518]: Receive SetParameterValues
2015-03-10T19:40:28-07:00 L3 sdb[331]: lan_redirect_status_get: error
2015-03-10T19:40:28-07:00 L3 sdb[331]: dns_lan_redirect_notify. DOWN. restart proxy
2015-03-10T19:40:28-07:00 L5 cwmp[1518]: Post SetParameterValuesResponse
2015-03-10T19:40:29-07:00 L5 cwmp[1518]: Receive GetParameterValues

Mentor

 • 

35 Messages

9 years ago

@RhodesMan - Quick question, why are you using 99.99.99.53 and or 99.99.99.153 as your AT&T DNS servers? Those DNS servers have longed been plagued with issues. I have even posted a link to an article from www.networkworld.com reporting that these DNS servers have been causing issues all the way back to 2012. I checked the default AT&T DNS servers on my NVG589 modem and they are the following: 68.94.156.9 68.94.157.9
I recommend changing your primary and secondary IPv4 DNS servers to these servers as soon as you are able. Also, if you have added 8.8.8.8 and 8.8.4.4 anywhere on your laptops, PC's, iPhones/iPads, then please also remove and let the devices utilize the routers DNS servers after you have changed to the IP's I have listed above. There is no need in using Google's public DNS servers (8.8.8.8 & 8.8.4.4) and causing even further issues.

Also, just to mention, after making the DNS changes to your AT&T NVG589 above, go ahead and power cycle your router after you have applied/saved your changes. Good luck!

Networkworld article-

http://www.networkworld.com/article/2452987/network-management/pingplotter-and-atandts-flaky-dns-servers.html

ACE - Guru

 • 

992 Messages

9 years ago

Thanks for the interesting reply.

It's not possible to change the DNS server addresses on the 589 and mine are set to

68.94.156.8 and 68.94.157.8.

I really don't know where the 99.99.xx.xx DNS errors are coming from although I see I am still getting these

 

2015-03-11T00:29:08-07:00 L3 dnsmasq[1787]: no responses from nameserver '68.94.157.8'
2015-03-11T00:29:08-07:00 L3 dnsmasq[1787]: nameserver '68.94.157.8' is now responding
2015-03-11T00:30:46-07:00 L3 dnsmasq[1787]: no responses from nameserver '68.94.156.8'
2015-03-11T00:30:46-07:00 L3 dnsmasq[1787]: nameserver '68.94.156.8' is now responding

 

After experimenting with other DNS on individual PC's I have since set them back to auto and flushed DNS to make sure they take effect.

 

Although I have tried before with no +ve result, I have again disabled IPv6 on the 589.

 

The fact still remains that we had none of these issue before the GPON upgrade regardless of which RG was used.

 

 

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.