b416
-
Posts
73 -
Joined
Reputation Activity
-
b416 got a reaction from sobrenome in Support php 8.1
the background task started by cron every minute fails with php 8.1
-
b416 got a reaction from Brainy S. in Auto upgrade 4.6.9 beta3 - 4.6.9 issue
I had it too.
As a workaround, I downloaded the complete version and copied the files over, then /admin/upgrade.
-
b416 got a reaction from Afrodude in Auto upgrade 4.6.9 beta3 - 4.6.9 issue
I had it too again with the new patch.
After the error, it was complaining about the modified files, but going to /admin/upgrade resolved the issue.
-
b416 got a reaction from Adriano Faria in Auto upgrade 4.6.9 beta3 - 4.6.9 issue
I had it too.
As a workaround, I downloaded the complete version and copied the files over, then /admin/upgrade.
-
b416 reacted to Adlago in Auto upgrade 4.6.9 beta3 - 4.6.9 issue
Error log:
DivisionByZeroError: Division by zero (0) #0 /home/database/public_html/consults/system/Helpers/MultipleRedirect/MultipleRedirect.php(93): IPS\core\modules\admin\system\_upgrade->IPS\core\modules\admin\system\{closure}(Array) #1 /home/database/public_html/consults/applications/core/modules/admin/system/upgrade.php(1047): IPS\Helpers\_MultipleRedirect->__construct(Object(IPS\Http\Url\Internal), Object(Closure), Object(Closure)) #2 /home/database/public_html/consults/system/Helpers/Wizard/Wizard.php(181): IPS\core\modules\admin\system\_upgrade->_upgrade(Array) #3 /home/database/public_html/consults/applications/core/modules/admin/system/upgrade.php(109): IPS\Helpers\_Wizard->__toString() #4 /home/database/public_html/consults/system/Dispatcher/Controller.php(101): IPS\core\modules\admin\system\_upgrade->manage() #5 /home/database/public_html/consults/applications/core/modules/admin/system/upgrade.php(54): IPS\Dispatcher\_Controller->execute() #6 /home/database/public_html/consults/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\system\_upgrade->execute() #7 /home/database/public_html/consults/admin/index.php(13): IPS\_Dispatcher->run() #8 {main}
-
b416 got a reaction from bosss in 4.6.9 Beta 2 upgrade broken
Yes, it's working now.
Thanks for the reactivity
-
b416 got a reaction from Marc Stridgen in 4.6.9 Beta 2 upgrade broken
Yes, it's working now.
Thanks for the reactivity
-
b416 got a reaction from bosss in 4.6.9 Beta 2 upgrade broken
I tried to upgrade from Beta 1 and it has a strange behaviour :
- upgrade start, downloads and extracts the files then says manual action required, go to client area to download
- when I download the Beta 2 files from client area and apply them, I click on Continue, nothing happens
- I go then to /admin/upgrade it says 'There are no applications available to upgrade'
- back to AdminCP Support, it complains that some files were modified (yes, the ones I uploaded because instructed to do so)
- download the 'unmodified' files and apply them and I am back to Beta 1...
Done this a dozen times on my test site. Something is wrong with this update.
-
b416 got a reaction from sobrenome in Elasticsearch Version 7 & IPB?
7.10.1 now...
and Invision is still silent
-
b416 got a reaction from sobrenome in Elasticsearch Version 7 & IPB?
7.10.2
really, invision ?
can't you even explain ?
-
b416 got a reaction from sobrenome in Elasticsearch Version 7 & IPB?
another new version... 7.11.1
and invision is still silent.... what a shame
-
b416 got a reaction from Joey_M in Redis sock configuration
Here is my redis configuration, it works like a charm :
Of course, you have to configure redis to listen on the socket instead of network port in /etc/redis/redis.conf :
# Accept connections on the specified port, default is 6379 (IANA #815344). # If port 0 is specified Redis will not listen on a TCP socket. port 0 # Unix socket. # # Specify the path for the Unix socket that will be used to listen for # incoming connections. There is no default, so Redis will not listen # on a unix socket when not specified. # unixsocket /run/redis/redis-server.sock unixsocketperm 766
-
b416 got a reaction from AlexJ in Redis sock configuration
Here is my redis configuration, it works like a charm :
Of course, you have to configure redis to listen on the socket instead of network port in /etc/redis/redis.conf :
# Accept connections on the specified port, default is 6379 (IANA #815344). # If port 0 is specified Redis will not listen on a TCP socket. port 0 # Unix socket. # # Specify the path for the Unix socket that will be used to listen for # incoming connections. There is no default, so Redis will not listen # on a unix socket when not specified. # unixsocket /run/redis/redis-server.sock unixsocketperm 766