4 \section*{Bacula Frequently Asked Questions}
5 \label{_ChapterStart48}
6 \index[general]{Questions!Bacula Frequently Asked }
7 \index[general]{Bacula Frequently Asked Questions }
8 \addcontentsline{toc}{section}{Bacula Frequently Asked Questions}
10 These are questions that have been submitted over time by the
14 \ilink{the bugs section}{_ChapterStart4} of this document for a list
15 of known bugs and solutions.
17 \subsection*{Frequently Asked Questions}
18 \addcontentsline{toc}{section}{Frequently Asked Questions}
23 \item [What is {\bf Bacula}? ]
24 \index[general]{What is Bacula? }
25 {\bf Bacula} is a network backup and restore program.
27 \item [Does Bacula support Windows?]
28 \index[general]{Does Bacula support Windows? }
29 Yes, Bacula compiles and runs on Windows machines (Win98, WinMe, WinXP,
30 WinNT, and Win2000). We provide a binary version of the Client (bacula-fd),
31 but have not tested the Director nor the Storage daemon. Note, Win95 is no
32 longer supported because it doesn't have the GetFileAttributesExA API call.
35 \item [What language is Bacula written in?]
36 \index[general]{What language is Bacula written in? }
37 It is written in C++, but it is mostly C code using only a limited set of the
38 C++ extensions over C. Thus Bacula is completely compiled using the C++
39 compiler. There are several modules, including the Win32 interface that are
40 written using the object oriented C++ features. Over time, we are slowly
41 adding a larger subset of C++.
44 \item [On what machines does Bacula run? ]
45 \index[general]{On what machines does Bacula run? }
46 {\bf Bacula} builds and executes on RedHat Linux (versions RH7.1-RHEL 3.0,
47 SuSE, Gentoo, Debian, Mandrake, ...), FreeBSD, Solaris, Alpha, SGI (client),
48 NetBSD, OpenBSD, Mac OS X (client), and Win32 (client).
50 Bacula has been my only backup tool for over four years backing up 5 machines
51 nightly (3 Linux boxes running RedHat, a WinXP machine, and a WinNT machine).
55 \item [Is Bacula Stable? ]
56 \index[general]{Is Bacula Stable? }
57 Yes, it is remarkably stable, but remember, there are still a lot of
58 unimplemented or partially implemented features. With a program of this size
59 (100,000+ lines of C++ code not including the SQL programs) there are bound
60 to be bugs. The current test environment (a twisted pair local network and a
61 HP DLT backup tape) is rather ideal, so additional testing on other sites is
62 necessary. The File daemon has never crashed -- running months at a time with
63 no intervention. The Storage daemon is remarkably stable with most of the
64 problems arising during labeling or switching tapes. Storage daemon crashes
65 are rare. The Director, given the multitude of functions it fulfills is also
66 relatively stable. In a production environment, it rarely if ever crashes. Of
67 the three daemons, the Director is the most prone to having problems. It
68 frequently runs several months with no problems.
70 There are a number of reasons for this stability.
73 \item The program was largely written by one person to date
75 \item The program constantly is checking the chain of allocated
76 memory buffers to ensure that no overruns have occurred. \\
77 \item All memory leaks (orphaned buffers) are reported each time the
79 \item Any signal (segmentation fault, ...) generates a
80 traceback that is emailed to the developer. This permits quick resolution of
81 bugs even if they only show up rarely in a production system.\\
82 \item There is a reasonably comprehensive set of regression tests
83 that avoids re-creating the most common errors in new versions of
87 \label{AuthorizationErrors}
89 \item [I'm Getting Authorization Errors. What is Going On? ]
90 \index[general]{I'm Getting Authorization Errors. What is Going On? }
91 For security reasons, Bacula requires that both the File daemon and the
92 Storage daemon know the name of the Director as well as his password. As a
93 consequence, if you change the Director's name or password, you must make
94 the corresponding change in the Storage daemon and in the File daemon
97 During the authorization process, the Storage daemon and File daemon also
98 require that the Director authenticate itself, so both ends require the other
99 to have the correct name and password.
101 If you have edited the conf files and modified any name or any password, and
102 you are getting authentication errors, then your best bet is to go back to
103 the original conf files generated by the Bacula installation process. Make
104 only the absolutely necessary modifications to these files -- e.g. add the
105 correct email address. Then follow the instructions in the
106 \ilink{ Running Bacula}{_ChapterStart1} chapter of this manual. You
107 will run a backup to disk and a restore. Only when that works, should you
108 begin customization of the conf files.
110 Another reason that you can get authentication errors is if you are running
111 Multiple Concurrent Jobs in the Director, but you have not set them in the
112 File daemon or the Storage daemon. Once you reach their limit, they will
113 reject the connection producing authentication (or connection) errors.
115 If you are having problems connecting to a Windows machine that previously
116 worked, you might try restarting the Bacula service since Windows frequently
117 encounters networking connection problems.
119 Here is sort of a picture of what names/passwords in which files/Resources
122 \includegraphics{./Conf-Diagram.eps}
124 In the left column, you will find the Director, Storage, and Client
125 resources, with their names and passwords -- these are all in {\bf
126 bacula-dir.conf}. In the right column are where the corresponding values
127 should be found in the Console, Storage daemon (SD), and File daemon (FD)
130 \label{AccessProblems}
132 \item [Bacula Runs Fine but Cannot Access a Client on a Different Machine.
134 \index[general]{Bacula Runs Fine but Cannot Access a Client on a Different
136 There are several reasons why Bacula could not contact a client on a
137 different machine. They are:
140 \item It is a Windows Client, and the client died because of an improper
141 configuration file. Check that the Bacula icon is in the system tray and the
142 the menu items work. If the client has died, the icon will disappear only
143 when you move the mouse over the icon.
144 \item The Client address or port is incorrect or not resolved by DNS. See if
145 you can ping the client machine using the same address as in the Client
147 \item You have a firewall, and it is blocking traffic on port 9102 between
148 the Director's machine and the Clients machine (or on port 9103 between the
149 Client and the Storage daemon machines).
150 \item Your password or names are not correct in both the Director and the
151 Client machine. Try configuring everything identical to how you run the
152 client on the same machine as the Director, but just change the Address. If
153 that works, make the other changes one step at a time until it works.
158 \item [My Catalog is Full of Test Runs, How Can I Start Over? ]
159 \index[general]{My Catalog is Full of Test Runs, How Can I Start Over? }
160 If you are using MySQL do the following:
164 cd <bacula-source>/src/cats
171 If you are using SQLite, do the following:
175 Delete bacula.db from your working directory.
176 cd <bacula-source>/src/cats
183 Then write an EOF on each tape you used with {\bf Bacula} using:
187 mt -f /dev/st0 rewind
192 where you need to adjust the device name for your system.
195 \item [I Run a Restore Job and Bacula Hangs. What do I do?]
196 \index[general]{I Run a Restore Job and Bacula Hangs. What do I do? }
197 On Bacula version 1.25 and prior, it expects you to have the correct tape
198 mounted prior to a restore. On Bacula version 1.26 and higher, it will ask
199 you for the tape, and if the wrong one it mounted, it will inform you.
201 If you have previously done an {\bf unmount} command, all Storage daemon
202 sessions (jobs) will be completely blocked from using the drive unmounted, so
203 be sure to do a {\bf mount} after your unmount. If in doubt, do a second {\bf
204 mount}, it won't cause any harm.
207 \item [I Cannot Get My Windows Client to Start Automatically? ]
208 \index[general]{I Cannot Get My Windows Client to Start Automatically? }
209 You are probably having one of two problems: either the Client is dying due
210 to an incorrect configuration file, or you didn't do the Installation
211 commands necessary to install it as a Windows Service.
213 For the first problem, see the next FAQ question. For the second problem,
215 \ilink{ Windows Installation instructions}{_ChapterStart7} in this
220 \item [My Windows Client Immediately Dies When I Start It ]
221 \index[general]{My Windows Client Immediately Dies When I Start It }
222 The most common problem is either that the configuration file is not where it
223 expects it to be, or that there is an error in the configuration file. You
224 must have the configuration file in {\bf
225 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf}.
227 To {\bf see} what is going on when the File daemon starts on Windows, do the
232 Start a DOS shell Window.
234 bacula-fd -d100 -c c:\bacula\bin\bacula-fd.conf
239 This will cause the FD to write a file {\bf bacula.trace} in the current
240 directory, which you can examine and determine the problem.
243 \item [When I Start the Console, the Error Messages Fly By. How can I see
245 \index[general]{When I Start the Console, the Error Messages Fly By. How can I seethem? }
246 Either use a shell window with a scroll bar, or use the gnome-console. In any
247 case, you probably should be logging all output to a file, and then you can
248 simply view the file using an editor or the {\bf less} program. To log all
249 output, I have the following in my Director's Message resource definition:
253 append = "/home/kern/bacula/bin/log" = all, !skipped
258 Obviously you will want to change the filename to be appropriate for your
262 \item [I didn't realize that the backups were not working on my Windows
263 Client. What should I do? ]
264 \index[general]{I didn't realize that the backups were not working on my Windows
265 Client. What should I do? }
266 You should be sending yourself an email message for each job. This will avoid
267 the possibility of not knowing about a failed backup. To do so put something
272 Mail = yourname@yourdomain = all, !skipped
277 in your Director's message resource. You should then receive one email for
278 each Job that ran. When you are comfortable with what is going on (it took me
279 9 months), you might change that to:
283 MailOnError = yourname@yourdomain = all, !skipped
288 then you only get email messages when a Job errors as is the case for your
291 You should also be logging the Director's messages, please see the previous
292 FAQ for how to do so.
295 \item [All my Jobs are scheduled for the same time. Will this cause
297 \index[general]{All my Jobs are scheduled for the same time. Will this cause
299 No, not at all. Bacula will schedule all the Jobs at the same time, but will
300 run them one after another unless you have increased the number of
301 simultaneous jobs in the configuration files for the Director, the File
302 daemon, and the Storage daemon. The appropriate configuration record is {\bf
303 Maximum Concurrent Jobs = nn}. At the current time, we recommend that you
304 leave this set to {\bf 1} for the Director.
307 \item [Can Bacula Backup My System To Files instead of Tape? ]
308 \index[general]{Can Bacula Backup My System To Files instead of Tape? }
309 Yes, in principle, Bacula can backup to any storage medium as long as you
310 have correctly defined that medium in the Storage daemon's Device resource.
311 For an example of how to backup to files, please see the
312 \ilink{Pruning Example}{PruningExample} in the Recycling
313 chapter of this manual. Also, there is a whole chapter devoted to
314 \ilink{Backing Up to Disk}{_ChapterStart39}.
317 \item [Can Bacula Backup and Restore Files Greater than 2 Giga bytes in
319 \index[general]{Can Bacula Backup and Restore Files Greater than 2 Giga bytes in
321 If your operating system permits it, and you are running Bacula version 1.26
322 or later, the answer is yes. To the best of our knowledge all client system
323 supported by Bacula can handle files larger than 2 Giga bytes.
326 \item [I Started A Job then Decided I Really Did Not Want to Run It. Is
327 there a better way than {\bf ./bacula stop} to stop it?]
328 \index[general]{I Started A Job then Decided I Really Did Not Want to
329 Run It. Is there a better way than ./bacula stop to stop it? } Yes,
330 you normally should use the Console command {\bf cancel} to cancel a Job
331 that is either scheduled or running. If the Job is scheduled, it will
332 be marked for cancellation and will be canceled when it is scheduled to
333 start. If it is running, it will normally terminate after a few
334 minutes. If the Job is waiting on a tape mount, you may need to do a
335 {\bf mount} command before it will be canceled.
338 \item [Why have You Trademarked the Name
339 Bacula\raisebox{.6ex}{{\footnotesize \textsuperscript{\textregistered}}}?]
340 \index[general]{Why have You Trademarked the Name
341 Bacula\textsuperscript{\textregistered}? }
342 We have trademarked the name Bacula to ensure that all media written by any
343 program named Bacula will always be compatible. Anyone may use the name
344 Bacula, even in a derivative product as long as it remains totally compatible
345 in all respects with the program defined here.
348 \item [Why is Your Online Document for Version 1.35 of Bacula when the
349 Currently Release Version is 1.34?]
350 \index[general]{Why is Your Online Document for Version 1.35 of Bacula when the
351 Currently Release Version is 1.34? }
352 As Bacula is being developed, the document is also being enhanced, more often
353 than not it has clarifications of existing features that can be very useful
354 to our users, so we publish the very latest document. Fortunately it is rare
355 that there are confusions with new features.
357 If you want to read a document that pertains only to a specific version,
358 please use the one distributed in the source code.
362 \item [How Can I Be Sure that Bacula Really Saves and Restores All Files? ]
363 \index[general]{How Can I Be Sure that Bacula Really Saves and Restores
364 All Files? } It is really quite simple, but took me awhile to figure
365 out how to ``prove'' it. First make a Bacula Rescue disk, see the
366 \ilink{Disaster Recovery Using Bacula}{_ChapterStart38} of this manual.
367 Second, you run a full backup of all your files on all partitions.
368 Third, you run an Verify InitCatalog Job on the same FileSet, which
369 effectively makes a record of all the files on your system. Fourth, you
370 run a Verify Catalog job and assure yourself that nothing has changed
371 (well, between an InitCatalog and Catalog one doesn't expect anything).
372 Then do the unthinkable, write zeros on your MBR (master boot record)
373 wiping out your hard disk. Now, restore your whole system using your
374 Bacula Rescue disk and the Full backup you made, and finally re-run the
375 Verify Catalog job. You will see that with the exception of the
376 directory modification and access dates and the files changed during the
377 boot, your system is identical to what it was before you wiped your hard
381 \item [I did a Full backup last week, but now in running an Incremental,
382 Bacula says it did not find a FULL backup time, so it did a FULL backup. Why?]
383 \index[general]{I did a Full backup last week, but now in running an
384 Incremental, Bacula says it did not find a FULL backup time, so it did a
385 FULL backup. Why? } Before doing an Incremental or a Differential
386 backup, Bacula checks to see if there was a prior Full backup of the
387 same Job that terminated successfully. If so, it uses the date that
388 full backup started as the time for comparing if files have changed. If
389 Bacula does not find a successfully full backup, it proceeds to do one.
390 Perhaps you canceled the full backup, or it terminated in error. In
391 such cases, the full backup will not be successful. You can check by
392 entering {\bf list jobs} and look to see if there is a prior Job with
393 the same Name that has Level F and JobStatus T (normal termination).
395 Another reason why Bacula may not find a suitable Full backup is that
396 every time you change the FileSet, Bacula will require a new Full
397 backup. This is necessary to ensure that all files are properly backed
398 up in the case where you have added more files to the FileSet.
399 Beginning with version 1.31, the FileSets are also dated when they are
400 created, and this date is displayed with the name when you are listing
401 or selecting a FileSet. For more on backup levels see below.
403 \label{filenamelengths}
404 \item [How Can You Claim to Handle Unlimited Path and Filename Lengths
405 when All Other Programs Have Fixed Limits?]
406 \index[general]{How Can You Claim to Handle Unlimited Path and Filename
407 Lengths when All Other Programs Have Fixed Limits? } Most of those
408 other programs have been around for a long time, in fact since the
409 beginning of Unix, which means that they were designed for rather small
410 fixed length path and filename lengths. Over the years, these
411 restrictions have been relaxed allowing longer names. Bacula on the
412 other hand was designed in 2000, and so from the start, Path and
413 Filenames have been keep in buffers that start at 256 bytes in length
414 but can grow as needed to handle any length. Most of the work is
415 carried out by lower level routines making the coding rather easy.
418 \item [What Is the Really Unique Feature of Bacula? ]
419 \index[general]{What Is the Really Unique Feature of Bacula? } Well, it
420 is hard to come up with unique features when backup programs for Unix
421 machines have been around since the 1960s. That said, I believe that
422 Bacula is the first and only program to use a standard SQL interface to
423 its catalog database. Although this adds a bit of complexity and
424 possibly overhead, it provides an amazingly rich set of features that
425 are easy to program and enhance. The current code has barely scratched
426 the surface in this regard (version 1.31).
428 The second feature, which gives a lot of power and flexibility to Bacula
429 is the Bootstrap record definition.
431 The third unique feature, which is currently (1.30) unimplemented, and
432 thus can be called vaporware :-), is Base level saves. When
433 implemented, this will enormously reduce tape usage.
437 \item [If I Do Run Multiple Simultaneous Jobs, How Can I Force One
438 Particular Job to Run After Another Job? ]
439 \index[general]{If I Do Run Multiple Simultaneous Jobs, How Can I Force One
440 Particular Job to Run After Another Job? }
441 Yes, you can set Priorities on your jobs so that they run in the order you
443 \ilink{the Priority record}{Priority} in the Job resource.
447 \item [I Am Not Getting Email Notification, What Can I Do? ]
449 \index[general]{I Am Not Getting Email Notification, What Can I Do? }
450 The most common problem is that you have not specified a fully qualified
451 email address and your bsmtp server is rejecting the mail. The next most
452 common problem is that your bsmtp server doesn't like the syntax on the From
453 part of the message. For more details on this and other problems, please see
455 \ilink{ Getting Email Notification to Work}{email} section of the
456 Tips chapter of this manual. The section
457 \ilink{ Getting Notified of Job Completion}{notification} of the Tips
458 chapter may also be useful. For more information on the {\bf bsmtp} mail
460 \ilink{bsmtp in the Volume Utility Tools chapter}{bsmtp} of this
465 \item [I Change Recycling, Retention Periods, or File Sizes in my Pool
466 Resource and they Still Don``t Work.]
467 \index[general]{I Change Recycling, Retention Periods, or File Sizes in my Pool
468 Resource and they Still Don"t Work. }
469 The different variables associated with a Pool are defined in the Pool
470 Resource, but are actually read by Bacula from the Catalog database. On
471 Bacula versions prior to 1.30, after changing your Pool Resource, you must
472 manually update the corresponding values in the Catalog by using the {\bf
473 update pool} command in the Console program. In Bacula version 1.30, Bacula
474 does this for you automatically every time it starts.
476 When Bacula creates a Media record (Volume), it uses many default values from
477 the Pool record. If you subsequently change the Pool record, the new values
478 will be used as a default for the next Volume that is created, but if you
479 want the new values to apply to existing Volumes, you must manually update
480 the Volume Catalog entry using the {\bf update volume} command in the Console
483 \label{CompressionNotWorking}
484 \item [I Have Configured Compression On, But None of My Files Are
486 \index[general]{I Have Configured Compression On, But None of My Files Are
488 There are two kinds of compression. One is tape compression. This is done by
489 the tape drive hardware, and you either enable or disable it with system
490 tools such as {\bf mt}. This compression works independently of Bacula.
492 Bacula also has compression code, which is normally used only when backing up
493 to file Volumes. There are two conditions for this ''software`` to be
497 \item You must have the zip development libraries loaded on your system when
498 building Bacula and Bacula must find this library, normally {\bf
499 /usr/lib/libz.a}. On RedHat systems, this library is provided by the {\bf
502 If the library is found by Bacula during the {\bf ./configure} it will be
503 in dicated on the {\bf config.out} line by:
512 \item You must add the {\bf compression=gzip} option on your Include
513 statement in the Director's configuration file.
517 \item [Bacula is Asking for a New Tape After 2 GB of Data but My Tape
519 \index[general]{Bacula is Asking for a New Tape After 2 GB of Data but My Tape
521 There are several reasons why Bacula will request a new tape.
524 \item There is an I/O error on the tape. Bacula prints an error message and
525 requests a new tape. Bacula does not attempt to continue writing after an I/O
527 \item Bacula encounters and end of medium on the tape. This is not always
528 distinguishable from an I/O error.
529 \item You have specifically set some size limitation on the tape. For example
530 the {\bf Maximum Volume Bytes} or {\bf Maximum Volume Files} in the
531 Director's Pool resource, or {\bf Maximum Volume Size} in the Storage
532 daemon's Device resource.
535 \label{LevelChanging}
537 \item [Bacula is Not Doing the Right Thing When I Request an Incremental
539 \index[general]{Bacula is Not Doing the Right Thing When I Request an Incremental
541 As explained in one of the previous questions, Bacula will automatically
542 upgrade an Incremental or Differential job to a Full backup if it cannot find
543 a prior Full backup or a suitable Full backup. For the gory details on
544 how/when Bacula decides to upgrade levels please see the
545 \ilink{Level record}{Level} in the Director's configuration
546 chapter of this manual.
548 If after reading the above mentioned section, you believe that Bacula is not
549 correctly handling the level (Differential/Incremental), please send us the
550 following information for analysis:
553 \item Your Director's configuration file.
554 \item The output from {\bf list jobs} covering the period where you are
556 \item The Job report output from the prior Full save (not critical).
557 \item An {\bf llist jobid=nnn} where nnn is the JobId of the prior Full save.
559 \item The Job report output from the save that is doing the wrong thing (not
561 \item An {\bf llist jobid=nnn} where nnn is the JobId of the job that was not
563 \item An explanation of what job went wrong and why you think it did.
566 The above information can allow us to analyze what happened, without it,
567 there is not much we can do.
570 \item [I am Backing Up an Offsite Machine with an Unreliable Connection.
571 The Director Waits Forever for the Client to Contact the SD. What Can I Do.]
572 \index[general]{I am Backing Up an Offsite Machine with an Unreliable Connection.
573 The Director Waits Forever for the Client to Contact the SD. What Can I Do. }
574 Bacula was written on the assumption that it will have a good TCP/IP
575 connection between all the daemons. As a consequence, the current Bacula
576 doesn't deal with faulty connection very well. This situation is slowly being
579 There are several things you can do to improve the situation.
582 \item Upgrade to version 1.32 and use the new SDConnectTimeout record. For
587 SD Connect Timeout = 5 min
592 in the FileDaemon resource.
593 \item Run these kinds of jobs after all other jobs.
597 \item [When I ssh into a machine and start Bacula then attempt to exit,
599 \index[general]{When I ssh into a machine and start Bacula then attempt to exit,
601 This happens because Bacula leaves stdin, stdout, and stderr open for debug
602 purposes. To avoid it, the simplest thing to do is to redirect the output of
603 those files to {\bf /dev/null} or another file in your startup script (the
604 RedHat autostart scripts do this automatically). For example, you start the
609 bacula-dir -c bacula-dir.conf ... 0>\&1 2>\&1 >/dev/null
614 and likewise for the other daemons.
616 \label{RetentionPeriods}
618 \item [I'm confused by the different Retention periods: File Retention,
619 Job Retention, Volume Retention. Why are there so many?]
620 \index[general]{I'm confused by the different Retention periods: File Retention,
621 Job Retention, Volume Retention. Why are there so many? }
622 Yes, this certainly can be confusing. The basic reason for so many is to
623 allow flexibility. The File records take quite a lot of space in the catalog,
624 so they are typically records you want to remove rather quickly. The Job
625 records, take very little space, and they can be useful even without the File
626 records to see what Jobs actually ran and when. One must understand that if
627 the File records are removed from the catalog, you cannot use the {\bf
628 restore} command to restore an individual file since Bacula no longer knows
629 where it is. However, as long as the Volume Retention period has not expired,
630 the data will still be on the tape, and can be recovered from the tape.
632 For example, I keep a 30 day retention period for my Files to keep my catalog
633 from getting too big, but I keep my tapes for a minimum of one year, just in
636 \label{MaxVolumeSize}
637 \item [Why Does Bacula Ignore the MaxVolumeSize Set in my Pool?]
638 \index[general]{Why Does Bacula Ignore the MaxVolumeSize Set in my Pool? }
639 The MaxVolumeSize that Bacula uses comes from the Media record, so most
640 likely you changed your Pool, which is used as the default for creating Media
641 records, {\bf after} you created your Volume. Check what is in the Media
650 If it doesn't have the right value, you can use:
660 \label{ConnectionRefused}
661 \item [In connecting to my Client, I get ''ERR:Connection Refused. Packet
662 Size too big from File daemon:192.168.1.4:9102`` Why?]
663 \index[general]{In connecting to my Client, I get &htmlQuoteERR:Connection Refused.
664 Packet Size too big from File daemon:192.168.1.4:9102&htmlQuote Why? }
665 This is typically a communications error resulting from one of the following:
669 \item Old versions of Bacula, usually a Win32 client, where two threads were
670 using the same I/O packet. Fixed in more recent versions. Please upgrade.
671 \item Some other program such as an HP Printer using the same port (9102 in
675 If it is neither of the above, please submit a bug report at
676 \elink{bugs.bacula.org}{http://bugs.bacula.org}.
678 Another solution might be to run the daemon with the debug option by:
682 Start a DOS shell Window.
684 bacula-fd -d100 -c c:\bacula\bin\bacula-fd.conf
689 This will cause the FD to write a file {\bf bacula.trace} in the current
690 directory, which you can examine and determine the problem.