New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zero exit code and ERROR at same time #2479
Comments
@geksi The 'modinfo' ERRORS are no fatal errors if you do not use these kernel modules (most likely). I agree the messages are misleading and perhaps we better use a different kind of message - any suggestion? Also, be aware, that you can define another TMPDIR location in the
@jsmeix Your input is more then welcome - no rush for now as you are on a holiday break. |
Only FYI before I actually do my "stay away from the Internet vacation": I think As long as ReaR's exit code is zero there is no error from ReaR. I think this issue is essentially same as Both issues are example cases of our general issue |
@geksi |
Explain that error messages in ReaR's log may not come from ReaR itself but from programs that are called by ReaR because stdout and stderr are redirected into ReaR’s log file, cf. #2479
Regarding https://github.com/rear/rear/blob/master/doc/user-guide/05-integration.adoc
The Error() function does
cf. https://github.com/rear/rear/blob/master/usr/share/rear/lib/_input-output-functions.sh#L551
cf. https://github.com/rear/rear/blob/master/usr/share/rear/lib/_input-output-functions.sh#L695 |
@geksi is your question sufficient answered? |
Yes, thank you! |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
2.4
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
RHEL 7.8
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
VMware
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86
Description of the issue (ideally so that others can reproduce it):
Not sure, if it is a bug...
rear mkrescue generates multiple errors (s. below) and writes "rear mkrescue finished with zero exit code" to the
/var/log/messages
at the same time.On the other hand, according to the monitoring guidelines the logfile should be monitored for "ERROR" strings:
https://github.com/rear/rear/blob/master/doc/user-guide/05-integration.adoc
This causes the "rear mkrescue" to be marked as "failed" in monitoring tool even though a rescue image was created.
MODULES=( 'all_modules' )
But for it more space is needed in $TMPDIR (must be extended from 3 GB to 4 GB) to avoid "no space left on device"
The text was updated successfully, but these errors were encountered: