[GH-ISSUE #753] Fatal error: Maximum execution time #543

Closed
opened 2026-02-26 02:33:30 +03:00 by kerem · 7 comments
Owner

Originally created by @gerroon on GitHub (Jun 6, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/753

I finaly was able to 60.000 songs to the databse. The sync was successful but now I cant login, with the errors below from apache (proxying it). It loads for a while then logs me out in Waterfox.

Before adding the songs, I had no such issue at all. I could login in a milisec.

Debian Testing
Apache/2.4.33 (Debian)
Database client version: libmysql - mysqlnd 5.0.12-dev - 20150407 - Id: 38fea24f2847fa7519001be390c98ae0acafe387
PHP extension: mysqliDocumentation curlDocumentation mbstringDocumentation
PHP version: 7.1.16-1+b2


Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66

Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66
[Wed Jun 06 15:50:16.977242 2018] [php7:error] [pid 7292] [client 192.168.1.100:41046] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 150, referer: http://192.168.5.106:9112/
[Wed Jun 06 15:50:22.415219 2018] [proxy:warn] [pid 7271] AH03408: HTTP: reusable backend connection is not empty: forcibly closed

Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66
[Wed Jun 06 15:51:07.719793 2018] [proxy:warn] [pid 7292] AH03408: HTTP: reusable backend connection is not empty: forcibly closed
[Wed Jun 06 15:51:32.283357 2018] [proxy:warn] [pid 27901] AH03408: HTTP: reusable backend connection is not empty: forcibly closed

Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66


Originally created by @gerroon on GitHub (Jun 6, 2018). Original GitHub issue: https://github.com/koel/koel/issues/753 I finaly was able to 60.000 songs to the databse. The sync was successful but now I cant login, with the errors below from apache (proxying it). It loads for a while then logs me out in Waterfox. Before adding the songs, I had no such issue at all. I could login in a milisec. Debian Testing Apache/2.4.33 (Debian) Database client version: libmysql - mysqlnd 5.0.12-dev - 20150407 - $Id: 38fea24f2847fa7519001be390c98ae0acafe387 $ PHP extension: mysqliDocumentation curlDocumentation mbstringDocumentation PHP version: 7.1.16-1+b2 ``` Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66 Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66 [Wed Jun 06 15:50:16.977242 2018] [php7:error] [pid 7292] [client 192.168.1.100:41046] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 150, referer: http://192.168.5.106:9112/ [Wed Jun 06 15:50:22.415219 2018] [proxy:warn] [pid 7271] AH03408: HTTP: reusable backend connection is not empty: forcibly closed Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66 [Wed Jun 06 15:51:07.719793 2018] [proxy:warn] [pid 7292] AH03408: HTTP: reusable backend connection is not empty: forcibly closed [Wed Jun 06 15:51:32.283357 2018] [proxy:warn] [pid 27901] AH03408: HTTP: reusable backend connection is not empty: forcibly closed Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 66 ```
kerem closed this issue 2026-02-26 02:33:30 +03:00
Author
Owner

@gerroon commented on GitHub (Jun 6, 2018):

Also these


[Wed Jun 06 16:06:50.156512 2018] [php7:error] [pid 900] [client 192.168.1.100:46278] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 188, referer: http://192.168.5.106:9112/
[Wed Jun 06 16:06:50.157674 2018] [php7:error] [pid 900] [client 192.168.1.100:46278] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 32768 bytes) in /media/DRIVE/BUILD/koel/vendor/symfony/debug/Exception/FatalErrorException.php on line 1, referer: http://192.168.5.106:9112/
[Wed Jun 06 16:06:56.572239 2018] [php7:error] [pid 905] [client 192.168.1.101:52777] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 188, referer: http://192.168.5.106:9112/
[Wed Jun 06 16:06:56.573379 2018] [php7:error] [pid 905] [client 192.168.1.101:52777] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 32768 bytes) in /media/DRIVE/BUILD/koel/vendor/symfony/debug/Exception/FatalErrorException.php on line 1, referer: http://192.168.5.106:9112/
[Wed Jun 06 16:07:15.892339 2018] [core:warn] [pid 889] AH00045: child process 900 still did not exit, sending a SIGTERM
[Wed Jun 06 16:07:15.892407 2018] [core:warn] [pid 889] AH00045: child process 905 still did not exit, sending a SIGTERM


<!-- gh-comment-id:395214399 --> @gerroon commented on GitHub (Jun 6, 2018): Also these ``` [Wed Jun 06 16:06:50.156512 2018] [php7:error] [pid 900] [client 192.168.1.100:46278] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 188, referer: http://192.168.5.106:9112/ [Wed Jun 06 16:06:50.157674 2018] [php7:error] [pid 900] [client 192.168.1.100:46278] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 32768 bytes) in /media/DRIVE/BUILD/koel/vendor/symfony/debug/Exception/FatalErrorException.php on line 1, referer: http://192.168.5.106:9112/ [Wed Jun 06 16:06:56.572239 2018] [php7:error] [pid 905] [client 192.168.1.101:52777] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /media/DRIVE/BUILD/koel/vendor/laravel/framework/src/Illuminate/Cache/FileStore.php on line 188, referer: http://192.168.5.106:9112/ [Wed Jun 06 16:06:56.573379 2018] [php7:error] [pid 905] [client 192.168.1.101:52777] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 32768 bytes) in /media/DRIVE/BUILD/koel/vendor/symfony/debug/Exception/FatalErrorException.php on line 1, referer: http://192.168.5.106:9112/ [Wed Jun 06 16:07:15.892339 2018] [core:warn] [pid 889] AH00045: child process 900 still did not exit, sending a SIGTERM [Wed Jun 06 16:07:15.892407 2018] [core:warn] [pid 889] AH00045: child process 905 still did not exit, sending a SIGTERM ```
Author
Owner

@phanan commented on GitHub (Jun 7, 2018):

Try increasing your PHP memory and execution time, as hinted by the errors themselves.

<!-- gh-comment-id:395361022 --> @phanan commented on GitHub (Jun 7, 2018): Try increasing your PHP memory and execution time, as hinted by the errors themselves.
Author
Owner

@gerroon commented on GitHub (Jun 7, 2018):

@phanan

I already set memory limit to 2048M in php.ini and added php_value max_execution_time 300 in .htaccess in koel folder. It did not seem to help.

It sometimes loads the page, a bit like a russian roulette but it takes a long time to load it when it does, like minutes. Loading the initial page takes time if it does, logging in takes a long time when it does. Allt his started to happening after I added all my songs so it was not an initial problem.

<IfModule mod_rewrite.c>
.......
        php_value memory_limit 2048M
        php_value set_time_limit 0
</IfModule>


<IfModule php7_module>
      php_value max_execution_time 300
</IfModule>
<!-- gh-comment-id:395450277 --> @gerroon commented on GitHub (Jun 7, 2018): @phanan I already set memory limit to 2048M in php.ini and added php_value max_execution_time 300 in .htaccess in koel folder. It did not seem to help. It sometimes loads the page, a bit like a russian roulette but it takes a long time to load it when it does, like minutes. Loading the initial page takes time if it does, logging in takes a long time when it does. Allt his started to happening after I added all my songs so it was not an initial problem. ``` <IfModule mod_rewrite.c> ....... php_value memory_limit 2048M php_value set_time_limit 0 </IfModule> <IfModule php7_module> php_value max_execution_time 300 </IfModule> ```
Author
Owner

@phanan commented on GitHub (Jun 7, 2018):

The errors say otherwise, so maybe you'll want to check your configuration. I can't debug for you, though.

<!-- gh-comment-id:395456576 --> @phanan commented on GitHub (Jun 7, 2018): The errors say otherwise, so maybe you'll want to check your configuration. I can't debug for you, though.
Author
Owner

@gerroon commented on GitHub (Jun 7, 2018):

@phanan

Yes I made those changes after those errors. What I am saying that changing the those settings seems to help a bit like letting me login only half the time, and it takes like 5 mins to load the page on a local network.

<!-- gh-comment-id:395467808 --> @gerroon commented on GitHub (Jun 7, 2018): @phanan Yes I made those changes after those errors. What I am saying that changing the those settings seems to help a bit like letting me login only half the time, and it takes like 5 mins to load the page on a local network.
Author
Owner

@gerroon commented on GitHub (Jun 7, 2018):

@phanan

I replaced the current repo (had over 60.000 songs) with one that has around 17.000. Not it is much more snappy, loading takes couple seconds.

Is it possible that 60.000+ songs is too much of an issue for Koel?

<!-- gh-comment-id:395516088 --> @gerroon commented on GitHub (Jun 7, 2018): @phanan I replaced the current repo (had over 60.000 songs) with one that has around 17.000. Not it is much more snappy, loading takes couple seconds. Is it possible that 60.000+ songs is too much of an issue for Koel?
Author
Owner

@phanan commented on GitHub (Jun 7, 2018):

Is it possible that 60.000+ songs is too much of an issue for Koel?

I'd think so.

<!-- gh-comment-id:395530882 --> @phanan commented on GitHub (Jun 7, 2018): > Is it possible that 60.000+ songs is too much of an issue for Koel? I'd think so.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#543
No description provided.