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.
DarkFury
Tutor
•
6 Messages
8 years ago
0
0
MadisonAL
Mentor
•
68 Messages
8 years ago
0
0
Bob Bednar
Mentor
•
42 Messages
8 years ago
Be aware that the NVG589 has a KNOWN problem with its internal battery back-up causing a freezing gateway. AT&T's only response to this problem is (a) to use the NVG589 WITHOUT installing its internal back-up battery, and (b) await a replacement gateway (somewhere in the works, but thus far for MANY months, with no one knowing any timeline). They also do NOT authorize using any external battery back-up with the NVG589, so if you have your phone bundled with U-Verse, you WILL lose phone connectivity during a power outage! (The last service tech's response to this loss of home phone: You do have a cell phone, don't you?) It amazes me that a large, powerful entity like AT&T can't pressure Motorola into SOLVING THE PROBLEM in a timely manner. And good luck trying to escalate this problem within AT&T. Their response is to 'send out another service tech', who also knows about the problem but has no solution. [I have had FOUR service techs out thus far!]
0
0
RhodesMan
ACE - Guru
•
953 Messages
8 years ago
Hi Bob.
Sorry to hear about your frustration.
It took me a while working with the folks from AT&T to eventually get a stable environment.
As a matter of interest, do you have a telephone that does not require being plugged into the mains to operate ie. not a cordless phone etc., attached to your AT&T telephone service?
0
0
wyliesdiesels
Tutor
•
4 Messages
7 years ago
i stumbled on this thread after noticing my log file had numerous name server errors.
I dont have an answer on how to fix it or whats causing it but i did notice that several others have commented about thier service having connection issues. I have had the exact same problem so i wanted to give some folks some insight into what i discovered and how i got my line fixed.
We moved into this house in february when we had our service put in. We have TV and internet, The service worked fine for months until one day it started dropping several times a day.
I had numerous premise techs out who blamed the modem and replaced it, blamed my battery backup, inside wiring(which is all CAT5) picking up electrical noise, surge strips, etc and ended up plugging everything into non protected power strips. The issues with the line dropping continued. Of course, it didnt drop while they were here....
I then asked for an outside wireman/splice tech to check for any issues on the line.(Im an electrician and telecom tech so I knew about splice techs). The Guy came out, removed some bridge taps, checked the line, switched my port at the VRAD and everything was good, no dropped connections.....for about a week....Problems started up again. They sent another premise tech out who couldnt figure it out.
I then requested another splice tech. Got a different guy, who was very thorough and genuinely wanted to figure out what the issue was. I also had reached out to att via facebook and the social media department started monitoring my line.
Both the network admins monitoring my line and the splice tech checked the logs at the VRAD and nothing was logged about my line disconnecting. I thought this was very odd until someone told me that it only took a snapshot every 5 mins. My line would only go down for 2 maybe 3 mins. This is why there was no log of my line going down.
This splice tech(Robert) changed my port again, checked everything out, checked the underground wire from VRAD to my house(which is newer twisted pair BTW)....and we were good for another week or so. Robert gave me his cell number and said to call him directly if i had any more issues because he didnt want to have numerous new hands trying to fix it by doing the same things that were already tried over and over.....then we dropped even worse than before....
I couldnt get ahold of Robert for a month despite calling over and over(this started just after 4th of July).... Finally in agust i got sick of the line issues so i again contacted att via facebook. Explained to them what was going on and they contacted Robert's supervisor. The supervisor called me, i again explained my story and then Robert called me. He came right over, checked things out again. Couldnt find anything different EXCEPT him and the monitoring center did see a few log entries of the line dropping. Which was good.
Because i had spoken to the social media department/monitoring(via facebook and the telephone) they had made a ticket for an outside splice tech to come out. So he(named Rob;different guy) came out the day after Robert, decided to try changing my port yet again and discovered that several of the ports on the card in the VRAD were bad. The 3 previous ports i had been on were bad as well as several other customers ports. Apparently, at least half the card was full but not one other customer in my neighborhood had called in and complained of an issue....go figure....
Robert and the previous splice techs had no way of discovering this because the ports and the card had given no indication of being bad. They would intermittently go bad and then work again. He said usually when the ports and thus the card, go bad its usually the whole card/every port, and not intermittently.
So the latest splice tech(Rob) switched the card i was on and I have not had one disconnect or line issue since. O and i went back and plugged everything back into my battery backup because as i suspected, surge strips and battery backups arent gonna cause line connection issues. It has been almost 2 months now and I havent had one disconnect.
I recently ran into Robert passing by him while waiting in traffic. we talked for a few minutes while waiting in traffic. He said that someone from the construction department has to go out to the VRAD and replace the cards as they are having issues....
Hope my experience helps someone else.....good luck....
0
0