Level 53
Have a look at this post to solve your issue.
Jul 9, 2018
5
Level 2
Forge & Horizon: Process exited too quickly
Hi,
I have created a server using Laravel Forge and I am using Horizon. So I have added the daemon "php artisan horizon".
Sometimes, Horizon completely stops working. I have to remove the daemon and re-add it to make the queues working again. This is a big problem, as I rely on a lot of background processes.
The error the daemon shows is "Process exited too quickly". The only error I see in the laravel.log file is the following:
[2018-07-08 10:38:29] production.ERROR: ERR Error running script (call to f_9bd406a64e43e31f0dde2849660e8cd56f340b85): @user_script:2: @user_script: 2: -MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error. {"exception":"[object] (Predis\Response\ServerException(code: 0): ERR Error running script (call to f_9bd406a64e43e31f0dde2849660e8cd56f340b85): @user_script:2: @user_script: 2: -MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error. at /home/forge/*/vendor/predis/predis/src/Client.php:370)
However I don't know what this is and I can't find anything on it either. Laravel Forge support is not responding on my problem.
Does anyone have an idea how to solve this?
Thanks in advance,
Level 2
I had Forge install redis etc. This should be setup correctly right? The link you provided states that there must be a new folder, but why does the default one not suffice?
Also, after a server reboot everything works again. Anyone an idea?
Level 2
For future reference: it was a memory problem. Redis used too much memory, so it had no memory left to perform certain operations.
Level 7
Hi @eelcol I’am having the same issue. Sometimes horizon stops working and when I look at deamons status
‘’’ daemon-37304 FATAL Exited too quickly (process log may have details)’’’
And when I restart only the php artisan horizon deamon it works. How can I fix this?
Level 2
Can you check the memory usage of your server? I fixed the problem by lowering the "job trimming times" in config/horizon.php and clearing all the stored keys using the redis-cli (FLUSHALL) (this will remove all jobs in the queue!). Also, an upgrade of the server's memory also works.
So in my case, the problem was a lack of memory. I have solved it by saving less data to the memory, and increasing the amount of memory of the server.
Please or to participate in this conversation.