Commits today appears to cause Dehydrated to exit with non-zero exit code? #280

New Issue

2025-12-29T01:21:02+01:00

adam commented

2025-12-29 01:21:02 +01:00

Originally created by @taylorotwell on GitHub (Feb 14, 2018).

One of the changes made today appears to have started making Dehydrated start exiting with a non-zero status even when everything goes fine. We are seeing the problem on Laravel Forge.

Originally created by @taylorotwell on GitHub (Feb 14, 2018). One of the changes made today appears to have started making Dehydrated start exiting with a non-zero status even when everything goes fine. We are seeing the problem on Laravel Forge.

adam closed this issue

2025-12-29 01:21:03 +01:00

adam commented

2025-12-29 01:21:03 +01:00

@lukas2511 commented on GitHub (Feb 14, 2018):

Mh... Can you run something like bash -x dehydrated -c and post the last few lines before it exits?

@lukas2511 commented on GitHub (Feb 14, 2018): Mh... Can you run something like `bash -x dehydrated -c` and post the last few lines before it exits?

adam commented

2025-12-29 01:21:04 +01:00

@lukas2511 commented on GitHub (Feb 14, 2018):

I think this is related to the recent addition of the "hook-bricker". I did one more change in dcdb2940fb, if that doesn't fix your problem your hook script probably is broken. It should ignore unknown hooks and exit cleanly, otherwise dehydrated won't work.

@lukas2511 commented on GitHub (Feb 14, 2018): I think this is related to the recent addition of the "hook-bricker". I did one more change in dcdb2940fbc4b8468cbbe75ea7725cf0a3306262, if that doesn't fix your problem your hook script probably is broken. It should ignore unknown hooks and exit cleanly, otherwise dehydrated won't work.

adam commented

2025-12-29 01:21:04 +01:00