search

gbiagomba / eventlog-to-syslog

Automatically exported from code.google.com/p/eventlog-to-syslog
0 stars 0 forks source link

Service stop after standby #49

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Standby the computer
2. Turn on the computer
3. Show service.msc, "Eventlog to syslog" service is not running

What version of the product are you using? On what operating system?

I tested the last version 4.4.2 on Windows Seven Pro 64 bits.

Original issue reported on code.google.com by duylong...@gmail.com on 15 Oct 2011 at 10:56

GoogleCodeExporter commented 9 years ago 
I will look into what I can do to change this, but I can't give you a time 
period right now. It is a very rare use case.

Original comment by sherwin....@gmail.com on 20 Oct 2011 at 3:02

GoogleCodeExporter commented 9 years ago 
i noticed that the service was not starting after a power on off computer - 
found the following entry in application eventlog

Connecting socket for LogHost1 (192.168.1.245:514) failed with error 10065: A 
socket operation was attempted to an unreachable host

I've now set the service to attempt a restart after 1 minute if it fails

Original comment by mr.mmor...@gmail.com on 18 Jul 2012 at 10:16

GoogleCodeExporter commented 9 years ago 
found that you need to change the service type to Automatic(Delayed Start) and 
it will work without problems, this is because it will load after windows has 
finished loading normal stuff including the firewall

Original comment by mr.mmor...@gmail.com on 18 Jul 2012 at 10:32

GoogleCodeExporter commented 9 years ago 
I believe this is linked to Issue 66. Will see if resolving that also resolves 
this.

Original comment by sherwin....@gmail.com on 16 Oct 2012 at 4:38