ACE - Guru
•
953 Messages
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 2021 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.
*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.
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
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.
0
0
DarkFury
Tutor
•
6 Messages
8 years ago
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....
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
A quick update.
Sometimes there are many seconds between the nameserver not responding and when it starts again. During that time many website struggle to resolve.
Yesterday I set the DNS server address on my PC to 8.8.8.8 and 8.8.4.4 thus overriding the ones internal to the NVG589. I also changed the IPv6 ones but they were never really the problem.
Since then I no longer get the nameserver error messages below and previously slow websites now pop up really quickly.
The dnsmasq[2513]: bad name at /var/etc/hosts.dyn line 8 errors however do continue but don't seem to affect performance at all.
0
0
MadisonAL
Mentor
•
68 Messages
8 years ago
Hi Joel,
At 9:00 this morning, AT&T reset their port. Since then, the only errors I have received are the Bad Name messages. The tech says that if the problem recurs, he will check out the port. In the meantime, no nameserver response issues or other issues that affect both TV and internet.
Now, other than my wife now complaining about the loss of Music Choice and the inferior online DVR access, everything seems to be okay.
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
Hi Barry,
I am surprised that you are now getting fewer namerserver errors as a result of the reset but I am pleased that it has made a difference for you.
As mentioned above changing DNS entries on my computer has made the most difference in my environment.
Hopefully they will find a fix so that we can use the log files for what they were intended for.
Joel
0
0
Signaladviser
Guru
•
1.1K Messages
8 years ago
Good luck
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
My RG again rebooted on it's own yesterday. This was after quite a good run of a few weeks without a reboot.
Now the problem is because there are so many nonsense error messages in the log file yesterday's events have already been overwritten by today's so I cant go and see what may have been the cause.
When it works, the NVG589 works well. I really don't know what they did when they upgraded us to GPON but that's when the problems started. First with the 3801 and now with the 589.
0
0