Bug 1423471

Can't reproduce that here, and your report is very light on details.

Was 3.4.1 OK?  The changes in 3.4.2 aren't all that significant so that would help to narrow down the issue.

Does amdump provide an exit code?  Run "amdump XXXX; echo $?".

Is there anything relevant in /var/log/amanda?

Does "ausearch -m avc" show anything relating to amanda?

Does "amcheck --client-verbose XXX" tell you anything?

Your amanda.conf and disklist might also be useful to have on hand, but I doubt that there's any obvious issue in there.

Yes, 3.4.1 works as expected, no problem.

$ amdump XXXXX; echo $? (XXXXX is my config)
9

Nothing in the logs, like error of something.

$ ausearch -m avc
<no matches>

$ amcheck --client-verbose XXXXX

Everything with OK:

The only relevant thing I can see is in log this line

"WARNING driver WARNING: got empty schedule from planner"

Exit code 9 means "error || RESULT_MISSING" which is pretty much what I'd expect from what you describe.

Unfortunately I'm out of ideas.  I know there are some selinux issues with 3.4 in general but if 3.4.1 worked and ausearch doesn't turn anything up then I guess it isn't that.  I will report your problem upstream to see if they have any requests, though they may not be able to do much without the verbose logs and config file.

Created attachment 1255849 [details]
Use function that doesn't segfault when one of its arguments is NULL

From: Jean-Louis Martineau <JMartineau>
Message-ID: <bcf3a408-d9c6-4b4d-66de-61a7126cd089>

I just had a similar case, it was caused by segfault of planner.

You can verify with eg. "journalctl -b | grep planner". If it shows something like "kernel: planner[22396]: segfault at 0 ip 00007f600d98647a sp 00007ffecb94c238 error 4 in libc-2.23.so[7f600d8ea000+1b9000]", it's probably the same issue. Planner gets segfault, can't deliver schedule, therefore "got empty schedule from planner".

Proposed patch from JLM attached.

Ah, so this is the same thing.  A segfault wasn't mentioned in this report.

Let me apply that patch and do a test build for you.

amanda-3.4.2-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b2412dfc61

amanda-3.4.2-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b5c7cd045

I can confirm the segfault

kernel: planner[11717]: segfault at 0 ip 00007efe681bda66 sp 00007fff9870f178 error 4 in libc-2.24.so[7efe6806e000+1bd000]

For some reason I missed this, I'm going to test the update

The updated rpm works as expected, I don't have anymore the segfault in planner and the backup finish successful.

Please give testing feedback directly on the update if you can.

done.

amanda-3.4.2-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b5c7cd045

amanda-3.4.2-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b2412dfc61

amanda-3.4.2-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0ac18bda03

amanda-3.4.2-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-41e61e4f94

This was never closed because the above updates were superseded by an update to 3.4.3 which didn't reference this bug.  We're on 3.4.4 now and unless it regressed this should be fixed.