Hi again, There was a related fix in 2.5.1089 for a very similar issue. You are either using an older version or there is still something lurking in there.
Regards, Botond On Mon, 3 Feb 2014 11:02:30 -0700 Scott H <scott.harps...@gmail.com> wrote: > Just to update, been testing different things. If i run nxlog.exe -c > 'config\nxlog.conf' > > failed to determine FQDN hostname: The requested name is valid, but no data > of the requested type was found. > > if i run nxlog.exe alone, same error. Is it freaking out on my fqdn. This > is a AD controller. > > > On Mon, Feb 3, 2014 at 9:14 AM, Scott H <scott.harps...@gmail.com> wrote: > > > Hi just joined, I just got into nxlogs and have been building a front end > > syslogger for some time. I have tried about all the syslog clients for > > windows and nxlogs is the best. I have it working on a windows 2008 server > > just fine. I put it on my 2012 and the service wont start. > > > > Here is my Error: > > > > Windows: Could not start the nxlog service on Local Computer. > > > > Error 1053: The service did not respond tot he start or control request in > > a timely fashion. > > > > This is my Config: I commented out some extensions hoping to just at least > > start nxlogs, but no luck. > > > > define ROOT C:\Program Files (x86)\nxlog > > > > Moduledir %ROOT%\modules > > CacheDir %ROOT%\data > > Pidfile %ROOT%\data\nxlog.pid > > SpoolDir %ROOT%\data > > LogFile %ROOT%\data\nxlog.log > > > > # > > #<Extension syslog># > > # Module xm_syslog > > #</Extension> > > > > #<##Input internal> > > # Module im_internal > > #</Input> > > > > <Input in> > > Module im_msvistalog > > </Input> > > > > <Output out> > > Module om_tcp > > Host x.x.x.x #This is my servers ip, just hidden. > > Port 514 > > </Output> > > > > <Route 1> > > Path in => out > > </Route> > > > > > > > > In the event log > > > > Faulting application name: nxlog.exe, version: 0.0.0.0, time stamp: > > 0x525fa959 > > Faulting module name: msvcrt.dll, version: 7.0.9200.16384, time stamp: > > 0x5010ae12 > > Exception code: 0xc0000005 > > Fault offset: 0x0000ef28 > > Faulting process id: 0x8c4 > > Faulting application start time: 0x01cf20f836baf8eb > > Faulting application path: C:\Program Files (x86)\nxlog\nxlog.exe > > Faulting module path: C:\Windows\SYSTEM32\msvcrt.dll > > Report Id: 81479d8a-8ceb-11e3-93fe-d89d676ecadf > > Faulting package full name: > > Faulting package-relative application ID: > > > > Any ideas? I tried upgrading my ms c++redist runtime but didnt help, > > rebooted, nothing. > > > > There is no log in nxlogs to see because it doesnt ever get that far. > > > > Thanks, > > Scott > > ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
