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

Where to find debug-level details for event_code = file_copy_failed? #263

Open
UNIVAC-Colonel-Panic opened this issue Mar 17, 2021 · 2 comments
Labels

Comments

@UNIVAC-Colonel-Panic
Copy link

v0.15.3

I'm aware of issue #81 (email notification) but my question is about what is written to the greyhole log file. I have log_level = DEBUG and see the following two lines in the log file:

Received hook with event_type = warning, event_code = file_copy_failed
Tokenize'd log: EVENT_DATE=Mar 16 17:15:00 ; LOG_LEVEL=WARN ; ACTION=fsck ; MESSAGE=Failed file copy (failed check: target filesize 0 != source filesize 174). Will mark this metadata file 'Gone'.

How do I find out what file -- or metadata file -- this is referring to?

I've tried to figure it out by the context of surrounding log file entries, but nothing seems to make sense except for other errors appearing for a drive I know is failing. I'd just like more details about the file itself.

@gboudreau
Copy link
Owner

Those lines were created by a hook, in /tmp/gh_log.txt (by default) which is unrelated to the log_level config option.

Look at the greyhole_log_file or greyhole_error_log_file options in your config. This is the daemon log that will contain the information you are looking for.

@UNIVAC-Colonel-Panic
Copy link
Author

My bad, I forgot there are two different logs. Thank you for your prompt reply. I haven't found the related lines in greyhole_log_file yet and it's a lower priority at the moment, however I will investigate this when I'm dealing with fewer crises :D and report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants