Using the latest bacula-fd for win32 (1.36.2) I am seeing occasional messages such as this:
Apr 19 13:23:40 hostname bacula[error] 0 Bacula error: 1063 at ..\..\filed\win32\winservice.cpp:325 StartServiceCtrlDispatcher failed. The service process could not connect to the service controller. (this is a message as relayed to a syslogd by ntsyslog from ntsyslog.sf.net) The file daemon is working without a hitch, but these errors logged periodically are getting on my nerves :) The message is most frequently logged by our Citrix server, but the other two servers (PDC + file shares) and a database server also occasionally log this message. Is it a case of the machine being very busy and the service controller not responding in a timely fashion? Our Citrix server can get quite loaded at times (more so than any of the other machines which mostly idle along). 1.36.1 also logged the same messages. -- Russell Howe [EMAIL PROTECTED] Today's Nemi: http://www.metro.co.uk/img/pix/nemi_apr19.jpg
smime.p7s
Description: S/MIME Cryptographic Signature
