On 07/06/17 02:59 AM, Stefan G. Weichinger wrote: > Am 2017-05-29 um 12:23 schrieb Jose M Calhariz: >> Hi, >> >> I have a private server of amanda. It is the second time that the >> planner enter in loop and I have to kill for the amdump to finish. >> >> What logs are relevant to help fix the problem? >> >> From the report: >> >> NOTES: >> (...) >> driver: WARNING: got empty schedule from planner >> taper: tape Daily2-11 kb 110099818 fm 16 [OK] >> (...) > I also have a 3.4.4 server (on gentoo linux) with a hanging planner. > Maybe the upcoming 3.4.5 solves that, unsure from reading the git log. > > I completely forgot about this bug, so it is not fixed.
Guys, If i don't reply to a bug report, send it again!!! And please, learn to send good bug report, just telling a process loop is not enough.It is always better to send more information that nothing. Don't ask what to send, send the most information you can, if something is missing, I will ask for. You said the planner is looping, why not send the planner debug file, that is the minimum. An strace of the planner process A gdb stacktrace of all threads. The amdump (or amdump.1) log file. As the loop in the planner can be triggered by a bug in another process, all error you get from any other processes. Jean-Louis This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been delivered to you by mistake, then do not copy or deliver this message to anyone. Instead, destroy it and notify me by reply e-mail
