Good morning It seems like everything is just fine again. Last night I removed the "Max Wait Time" from the job resource and everything works again (every job is OK).
I have probably used the "Max Wait Time" wrong in my configuration. What about to make a "Migrate from ver >= ver" section in the user guide where it will be listed the configuration changes and other thing that is importent between the version. Some of the other Open Source system I'm using has this feature and it making the upgrade job much easier and safer. It is probably not so important between the "major updates, 1.x to 2.x" but between 2.0.3 to 2.2.0, 2.2.0 -> 2.2.3 has been nice. Perhaps you guys have allready written that, perhaps I have miss it. Regards, Christian Sakshaug Christian Sakshaug skrev: > Hey > > Have tested some more now, it seems that jobs that I was getting error > after "normal schedule" is working when I have a small number of > concurrent jobs running. > > I wonder what have been change since 2.0.3 that could have this affects? > > I have been reading the changelog and documentation and I can not find > anything special except the "critical bug fixed in 2.2.3" that trigger > my upgrade at the first place. > > Actually I have 3 different bacula site-location that have been in used > for some times now without troubles. I have upgrade two of those with > 2.2.3 and I having trouble with both. But with the third (running 2.0.3) > everything is working great/normal. > > > Regards > Christian Sakshaug ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
