Tag Info

New answers tagged

3

Doh! It was due to user error. We figured out that someone, unbeknownst to my team and presumably someone on the team that made the virtual machines and installed the OS, deliberately configured the Services snapin on all three machines to connect to the same single host! So the software was working as designed. Erasing the service entries on each of the ...


5

This isn't the normal Windows behavior. It must be something application-specific that is unique to this specific application/service.


0

I too had this issue, however, I found a TechNet thread that really helped me clue in on a fix for this. Basically, the problem was that somehow the servers identity certificate had gotten deleted from the certificate store and it needed to be regenerated. When the certificate is missing it causes the "Windows Server Service Provider Registry" service to ...


0

I'm really not a fan of init based process management (and runit is basically an init substitute). As yo uare discovering, simple-minded restarting of failed processes as soon as they die is not a particularly good strategy. I've used init to restart monit, but that's as far as it goes. (potentially OOM killer could kill monit). So, I'd encourage you to ...


1

I'm not familiar with this facility, however, if it was my task to solve this problem, and a very short man page reading did not offer a simple knob to tune this behaviour, I'd do the following: Either extend the existing service start script, or if that is cumbersome, insert a new start script into the chain (which in turn starts the original start ...


1

If your issue is the service starting in a different order you should change the number in the other set of scripts, I mean, not the KXXscript, but the SXXscript since the scripts starting with S affect the start of said services. The K are related with the stop (Kill) of services, so basically you changed the order in which bind9 and openvpn are stopped, ...


1

The reason why this was failing was because of DCOM in Windows. I set mine to run as Administrator (in Identity) section. http://stackoverflow.com/a/11359745/234307


0

The problem was the windows firewall (Server 08). For some reason he was locking door 3128 by internal NIC. I created an inbound rule and resolved.



Top 50 recent answers are included