Menu
▾
▴
Re: [Bacula-devel] VSS related DIR crash and XP reboot
|
From: Dan L. <da...@la...> - 2006-01-29 16:00:18
|
On 29 Jan 2006 at 10:44, Thomas Simmons wrote: > Dan Langille wrote: > > Hi folks, > > > > I upgraded a XP Home box to use the 1.38.4 client today. I also > > added in the VSS option. During the first run (using 1.38.5 > > Director, etc), I ran a message command in the console, and the > > Director had gone away. > > > > *mes > > 28-Jan 15:20 bconsole: Error: bnet.c:426 Write error sending 3 bytes > > to Director daemon:bacula.unixathome.org:9101: ERR=Broken pipe > > > > I restarted the Director. Going into bconsole, this was the first > > message I saw: > > > > *mes > > 28-Jan 15:20 bconsole: Error: bnet.c:426 Write error sending 3 bytes > > to Director daemon:bacula.unixathome.org:9101: ERR=Broken pipe > > > > I restarted the job and went out. > > > > Later that day, I got a phone call from a distressed 16 year old > > studying for exams who told me that the XP computer had restarted and > > she'd lost the document she's been writing. > > > > Checking the job logs: > > > > *run job=pepper yes > > Job started. JobId=7348 > > *mes > > 28-Jan 15:22 bacula-dir: No prior Full backup Job record found. > > 28-Jan 15:22 bacula-dir: No prior or suitable Full backup found. > > Doing FULL backup. > > 28-Jan 15:22 bacula-dir: Start Backup JobId 7348, Job=pepper.2006-01- > > 28_15.22.53 > > *mes > > 28-Jan 15:23 polo-sd: Volume "FILE-0001" previously written, moving > > to end of data. > > 28-Jan 15:23 polo-sd: Spooling data ... > > 28-Jan 15:24 pepper-fd: Cannot open c:/Documents and > > Settings/Dan/NTUSER.DAT: ERR=The process cannot access the file > > because it is being used by another process. > > . > > 28-Jan 15:24 pepper-fd: Cannot open c:/Documents and > > Settings/Dan/ntuser.dat.LOG: ERR=The process cannot access the file > > because it is being used by another process. > > . > > 28-Jan 15:26 pepper-fd: Cannot open c:/Documents and > > Settings/OtherUserKatrina/Local Settings/Application > > Data/Microsoft/Windows/UsrClass.dat: ERR=The process cannot access > > the file because it is being used by another process. > > . > > 28-Jan 15:26 pepper-fd: Cannot open c:/Documents and > > Settings/OtherUser/Local Settings/Application > > Data/Microsoft/Windows/UsrClass.dat.LOG: ERR=The process cannot > > access the file because it is being used by another process. > > . > > *mes > > 28-Jan 15:38 pepper-fd: Cannot open c:/Documents and > > Settings/OtherUser/NTUSER.DAT: ERR=The process cannot access the file > > because it is being used by another process. > > . > > 28-Jan 15:38 pepper-fd: Cannot open c:/Documents and > > Settings/OtherUser/ntuser.dat.LOG: ERR=The process cannot access the > > file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/LocalService/Local Settings/Application > > Data/Microsoft/Windows/UsrClass.dat: ERR=The process cannot access > > the file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/LocalService/Local Settings/Application > > Data/Microsoft/Windows/UsrClass.dat.LOG: ERR=The process cannot > > access the file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/LocalService/NTUSER.DAT: ERR=The process cannot access the > > file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/LocalService/ntuser.dat.LOG: ERR=The process cannot access > > the file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/NetworkService/Local Settings/Application > > Data/Microsoft/Windows/UsrClass.dat: ERR=The process cannot access > > the file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/NetworkService/Local Settings/Application > > Data/Microsoft/Windows/UsrClass.dat.LOG: ERR=The process cannot > > access the file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/NetworkService/NTUSER.DAT: ERR=The process cannot access the > > file because it is being used by another process. > > . > > 28-Jan 15:46 pepper-fd: Cannot open c:/Documents and > > Settings/NetworkService/ntuser.dat.LOG: ERR=The process cannot access > > the file because it is being used by another process. > > . > > 28-Jan 15:50 polo-sd: Committing spooled data to Volume "FILE-0001". > > Despooling 6,197,327,755 bytes ... > > 28-Jan 16:10 polo-sd: Sending spooled attrs to the Director. > > Despooling 3,198,410 bytes ... > > 28-Jan 16:11 bacula-dir: Bacula 1.38.5 (18Jan06): 28-Jan-2006 > > 16:11:52 > > JobId: 7348 > > Job: pepper.2006-01-28_15.22.53 > > Backup Level: Full (upgraded from Incremental) > > Client: "pepper-fd" Windows XP,MVS,NT 5.1.2600 > > FileSet: "pepper files" 2006-01-28 14:49:11 > > Pool: "Default" > > Storage: "File" > > Scheduled time: 28-Jan-2006 15:22:53 > > Start time: 28-Jan-2006 15:22:55 > > End time: 28-Jan-2006 16:11:52 > > Priority: 10 > > FD Files Written: 8,859 > > SD Files Written: 8,859 > > FD Bytes Written: 6,189,446,123 > > SD Bytes Written: 6,191,287,331 > > Rate: 2107.4 KB/s > > Software Compression: None > > Volume name(s): FILE-0001 > > Volume Session Id: 57 > > Volume Session Time: 1138108315 > > Last Volume Bytes: 18,548,046,572 > > Non-fatal FD errors: 14 > > SD Errors: 0 > > FD termination status: OK > > SD termination status: OK > > Termination: Backup OK -- with warnings > > > > 28-Jan 16:11 bacula-dir: Begin pruning Jobs. > > 28-Jan 16:11 bacula-dir: No Jobs found to prune. > > 28-Jan 16:11 bacula-dir: Begin pruning Files. > > 28-Jan 16:11 bacula-dir: Pruned Files from 1 Jobs for client pepper- > > fd from catalog. > > 28-Jan 16:11 bacula-dir: End auto prune. > > > > The end time for the job is interesting. I got the phone call at > > 16:14 telling me that the computer had restarted. I talked her > > through shutting down the bacula-fd client, just in case. > > > > I think that timing is too close to just be a coincidence. She says > > the XP system did not crash. It did a shutdown and then restarted. I > > don't want to ask for any more details just now. ;) > > > > Any ideas/suggestions/comments? > > Dan, > XP is configured by default to restart when a fatal error occurs instead of blue-screen. I've had this happen > several times and users swear the system just "shutdown and restart". You can disable this "feature". > > Right Click "My Computer" > Properties > Advanced Tab > Startup and Recovery Settings, and uncheck "System > Failure" Automatically restart. Thanks. I also changed "Write debugging information" to none. It's a dump file, and from what I've read, it's only of use to Microsoft. > I don't know if this is what happended but the system logs should tell > you. Enter "eventvwr" into the Start>Run box, and look in the system > log at 16:14 on that day. This should tell you exactly why it > shutdown, and if due to error, which program caused it. From the system log: At 15:01, there is a "TCP/IP has read the security limit imposed on the number of concurrent TCP connect attempts". I'm guessing that is Limeware. 16:14:38 "Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Multiprocessor Free.". 16:14:38 "The Event log server was started". etc. 16:14:39 "The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0x9c4a874c, 0x00000000, 0x804f1766, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini012806-01.dmp. After that, it's all just normal start up stuff. The Application and Security logs didn't have anything significant. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ |