Skip to content
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

Cascading errors when amanda cannot parse a log file #189

Open
opoplawski opened this issue Aug 30, 2022 · 0 comments
Open

Cascading errors when amanda cannot parse a log file #189

opoplawski opened this issue Aug 30, 2022 · 0 comments

Comments

@opoplawski
Copy link
Contributor

I just discovered that our backups were suffering failures due to not being able to parse log files. I suspect that this originated with and out of disk space condition that caused a log file to be truncated. This led to subsequent runs failing with:

 ** (process:20892): CRITICAL **: 04:20:30.170: '' at /usr/lib64/perl5/vendor_perl/Amanda/DB/Catalog.pm line 839.

This would then cascade because the log file what process was producing would be truncated when it died.

I've filed #188 to at least make the original message helpful in finding where the problem is. Some additional questions:

  • Do we have to die here? Can we somehow recover from the error?
  • If we have to die - can we avoid truncating the log file? Perhaps by making some more file handles autoflush?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant