> On Thu, Jan 29, 2009 at 12:30:07PM +1100, James Harper wrote: > > > 2) I can make the bacula-fd crash (or stop - I don't know if it > > crashed, > > > or exited gracefully), by doing the following. I've tried this on two > > > separate > > > Windows 2003 Servers, running Exchange 2003. > > > > > > a) Dismount and tick the magic 'overwrite' tickboxes on First Storage > > > Group -> > > > Mailbox Store, and Public Folder Store. > > > b) Attempt to restore '/@EXCHANGE/Microsoft Information Store/First > > > Storage Group/Mailbox Store (Computer name)'. > > > > > > Here are the resulting error messages that are logged: > > > > > > Jan 28 11:27:58 bacula-dir: devel-wk3-32-fd JobId 15: Error: > > > HrESERestoreComplete failed with error 0xc7ff1004 - Unknown error. > > > Jan 28 11:28:01 bacula-dir: tserv.example.com-dir JobId 15: Fatal > > error: > > > Network error with FD during Restore: ERR=Connection reset by peer > > > Jan 28 11:28:01 bacula-dir: tserv.example.com-dir JobId 15: Fatal > > error: > > > No Job status returned from FD. > > > > > > If I instead attempt to restore '/@EXCHANGE/Microsoft Information > > > Store/First Storage Group', it works successfully. > > > > Obviously bacula-fd shouldn't just crash, but when restore a store, you > > also need to restore the logfiles. Are you doing that? > > > Actually, I don't think it was crashing, because Windows didn't give me > the 'report this to Microsoft' window. It is most likely just exiting. > > I wasn't expecting what I was doing above to work, I had just noticed that > sometimes the bacula-fd would stop running unexpectedly. What I outlined > above was a way in which I could reliably make that happen. >
Don't be so sure about the crashing. Windows tends to 'save up' those reports. While I was developing the plugin I went through heaps of crashes while getting the bugs out. It was only when I logged back in or rebooted that Windows suddenly told me about every single one of those crashes, individually. And it didn't do them all at once either, it would sometimes wait up to 10 seconds between me clicking "don't send" and telling me about the next one. Very frustrating. I see the same behaviour on a clients terminal server. Every single time an application crashes windows remembers it, and then when I log in as Administrator a few weeks later I get to hear about all of them. James ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
