up vote 0 down vote favorite
1
share [g+] share [fb]

I have a windowservice which named Trunk which stopped one day I just want to know the reason behind it? This is an entry in the logs,

Nov 25 15:54:52.157 :Trunk-1516:Trunk:Stopping Trunk. 
Nov 25 15:54:52.314 :Trunk-1516:Trunk:Shutting down, signaled C:\Program F

I had seen service is registered with specific account, so I thought that user logged off from the machine that may be the reason behind it or any LAN disconnection problem . But Having taken another look at the above entry we seem to have a constant failure being generated in vmd which causes Trunk to detect vmd requires a restart.

link|improve this question
I would say it depends on how regularly it's hitting the restart limit... If it's fairly regular and always with the same error then it's probably worth looking into. If it's not very regular and you cannot replicate it for troubleshooting then just increase the tolerance slightly. – HaydnWVN Nov 28 '11 at 8:36
I don't know enough about services in 2003 and nor do i have a 2003 server here to play with... Where did you find the limit of 4 from - it's likely that plug-in/program will give you information about changing the restart limit. 'probably worth looking into' = find out what's causing it to fail, and then fix it! :) – HaydnWVN Nov 29 '11 at 10:20
Goodluck, any option for testing - ie not a live system? I've run memtest overnight before now to try and find/diagnose memory problems... :) – HaydnWVN Nov 29 '11 at 17:02
@HaydnWVN Due to this memory leak, the vmd component has been set to restart once every 24 hours. – Steve Nov 29 '11 at 17:12
Has that cleared the TRUNK error? Or is it still being produced and just not hitting the restart limit? – HaydnWVN Nov 30 '11 at 8:57
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.