On Wed, Jun 24, 2015 at 3:07 AM Philipp Storz <[email protected]> wrote:
> Am 23.06.2015 um 17:01 schrieb Michael Mol: > > On Tue, Jun 23, 2015 at 10:43 AM Michael Mol <[email protected] <mailto: > [email protected]>> wrote: > > > > I've been struggling for weeks to get a particular Windows machine > (out of eight or so) to give > > me a full backup. All the other machines work fine, it's just this > one that won't give me a > > backup. This email started out with me trying to document the > precise set of backup failure > > symptoms I'm seeing, but I can't even get it to give me a failure > mode and timing that's > > consistent for two consecutive runs. > > > > That leaves trying to get a debug trace...but when I follow the > instructions > > at > http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-27600024.2 > for > > enabling the debug trace as part of the system service, I get a "The > service has terminated > > unexpectedly" error. > > > > The Bareos daemon is running as the "local system" account, so it > shouldn't be a permissions > > issue with wherever it's trying to drop the bareos.trace file. > The docs tell you that where the trace file will be; it is C:\ > > "After restarting the service, you will find a file called C:\bareos > -_fd.trace which will contain > the debug output created by the daemon" > I found myself distrustful of the docs, as googling around for some of the error messages I'd been seeing resulted in people finding the trace file in, e.g. %SYSTEM32%. (Personally, I wish it'd drop it next to the configuration files, under %ProgramData%) Also, when I tried running the bareos FD directly, flubbing the command-line, the list of supported parameters it responded with was different from what's in the docs. > > > > > Any suggestions on how I can get useful debug output? > > > > > > Apologies; I forgot to mention that I'm using Bareos 14.2.2. The > packaged installer in question is > > "winbareos-14.2.2.postvista-64-bit-r16.1.exe" > > What Windows Version do you have? > On this particular system, Windows 7 Professional x64. The issue is about to be moot, though; the host's network stack has pretty much committed suicide over the last few days, and we're doing an emergency replacement. over the next couple days. New OS will be Windows 8.1 Pro x64, of which I have many hosts already tied into Bareos and working. Old hardware is going to get wiped, have Cent7 installed and will serve as a remote storage daemon. Crossing my fingers that the hardware's fine. TFTR. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
