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

PHP Fatal error: escapeshellarg() #200

Open
Sparticuz opened this issue Nov 9, 2018 · 8 comments
Open

PHP Fatal error: escapeshellarg() #200

Sparticuz opened this issue Nov 9, 2018 · 8 comments
Labels

Comments

@Sparticuz
Copy link
Contributor

PHP Fatal error: escapeshellarg(): Argument exceeds the allowed length of 2097152 bytes in /usr/bin/greyhole on line 1060

I received this error after reducing num_copies on my shares to 1, then running a fsck.

@gboudreau
Copy link
Owner

In what context did the error appear ? In the logs ? On the command line ?

@Sparticuz
Copy link
Contributor Author

I was running greyhole with --daemon at the time, so it appeared both on the command line after greyhole crashed, and in the logs.

@Sparticuz
Copy link
Contributor Author

My guess is it's trying to delete alot of duplicated files and overflowing escapeshellarg()

@gboudreau
Copy link
Owner

Which greyhole version?

@Sparticuz
Copy link
Contributor Author

Sparticuz commented Nov 9, 2018 via email

@gboudreau
Copy link
Owner

It is using escapeshellarg() in order to prepare the third argument that will be sent to a log hook. So that means you have hooks defined, and the data Greyhole is trying to send to your hook script is too large. My guess is that it's the fsck hook. So maybe just disable that hook temporarily, and check the fsck result by sending it by email, or checking the file it writes in /usr/share/greyhole/fsck_files.log.

@gboudreau
Copy link
Owner

Of note: fsck_files.log is only created if the option to send an email is enabled, or if a fsck hook is configured. So since you have a fsck hook configured, you should already have this file in /usr/share/greyhole/.

@Sparticuz
Copy link
Contributor Author

The hook is a hook into Slack, so it very well might be 'too large'. I don't see a fsck_files.log. Let me try it again, I'm running --fsck -e

@gboudreau gboudreau added the Bug label Apr 5, 2020
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