On Sat, 2014-11-01 at 06:41 -0400, Jason W. wrote: > On Fri, Oct 31, 2014 at 8:54 PM, Chris <cpoll...@embarqmail.com> > wrote: > I am still fighting this issue. This has been going on since > Wednesday > morning since there was an update to the kernel. I have no > idea what to > check or even where to begin. If someone could help I'd really > appreciate it. > > > My guess would be your /etc/resolv.conf only has one nameserver listed > - 127.0.0.1 - and whatever resolver service you have running on your > server did not restart when you rebooted to update the kernel. > Hi Jason, actually my /etc/resolv.conf file has nameserver 127.0.1.1 as the only nameserver. I noticed this morning that the error is no longer there. The only thing I did last night was to restart SA although I know it has been running since the kernel update. Doing some back checking in my hourly syslog snippets I see that the last kernel update was on Oct 20th at 8pm. The error started immediately after that. My next SA update run was at 7:30 the next morning and SA was automatically restarted. The next message that came through did not have the error. The next kernel update was this past Wednesday which was installed just after SA update was run which due to rule updates restarted SA. Since then Thu and Fri there were no rule updates so SA was not automatically restarted. I guess to make a long story short for some reason I have to restart SA after a kernel update however I have no idea why and I'll have to test this theory after the next kernel update.
Does any of the above make any sense? Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 08:09:57 up 2 days, 13:06, 1 user, load average: 0.26, 0.20, 0.40 Ubuntu 14.04.1 LTS, kernel 3.13.0-39-generic
