DivisionByZeroError - Problem to access Status Page on PHP 8.2

Hello @adrianopulz,

I faced the same issue after upgrading our environment to PHP 8.1.

Our Redis instance is on the Azure platform and by simple debugging of $info variable I found that our server does not provide the required properties in the output.

You can simply check it by changing the code like this

'value' => $this->t('@read read (@percent_read%), @write written (@percent_write%), @commands commands in @connections connections.', [
'@read' => json_encode($info),          
//'@read' => format_size($info['total_net_output_bytes'] ?? $info['Stats']['total_net_output_bytes']),
         // '@percent_read' => round(100 / (($info['total_net_output_bytes'] ?? $info['Stats']['total_net_output_bytes']) + ($info['total_net_input_bytes'] ?? $info['Stats']['total_net_input_bytes'])) * ($info['total_net_output_bytes'] ?? $info['Stats']['total_net_output_bytes'])),
         // '@write' => format_size($info['total_net_input_bytes'] ?? $info['Stats']['total_net_input_bytes']),
         // '@percent_write' => round(100 / (($info['total_net_output_bytes'] ?? $info['Stats']['total_net_output_bytes']) + ($info['total_net_input_bytes'] ?? $info['Stats']['total_net_input_bytes'])) * ($info['total_net_input_bytes'] ?? $info['Stats']['total_net_input_bytes'])),
          //'@commands' => $info['total_commands_processed'] ?? $info['Stats']['total_commands_processed'],
        //  '@connections' => $info['total_connections_received'] ?? $info['Stats']['total_connections_received'],
        ]),

So, looks like the issue is not related to the PHP version update, maybe just partially when the PHP generates a fatal error after throwing the exception.

But you can resolve that at least temporarily while you reconfigure your Redis server.

I've tested several versions of Docker images with Redis and even used Windows ported version but I've not faced the issue experienced on the Azure platform. All tested versions had all the necessary attributes to display.

Tested locally Redis versions: 3.0.504 - 6.0.14 (Not reproducing)
Drupal core: 9.4.8
PHP version: 8.1.14

Attaching the patch. Hope it will help you.

Normal info layout in the local environment.

Temporary fix layout.

Hi @ysamoylenko!

Yeah, that looks great. I'm using Azure Redis as well.
The $info needs to be verified before using it to avoid PHP errors.

Thanks for the patch. =)

Hi guys,

Thanks for your contribution

@ysamoylenko, your patch works very well.

Changed status to RTBC.

+++ b/src/Controller/ReportController.php
@@ -212,14 +212,16 @@ class ReportController extends ControllerBase {
+        'value' => $info['total_net_output_bytes'] || $info['Stats']['total_net_output_bytes'] ?

are the array keys empty or not set? this will cause php notices if they are not set.

Lets wrap it in an !empty() to be extra careful.

Also seems to be overlapping/very related to ✨ Azure/AWS: Take into account CONFIG command may not work Needs review

Hello @Berdir,

Thank you for your response.

These array keys do not exist in the $info array.

I am adding a new patch with a non-empty evaluation.

According to the mentioned issue, it looks similar but for another section of the report.

In our environment, I have not faced it.

it seems patch needs reroll for 1.8

Patch for 1.8 version

We are also having this fatal error with PHP8.3.12 and Redis 1.8
On BO: /admin/reports/redis
DivisionByZeroError: Division by zero in Drupal\redis\Controller\ReportController->overview() (line 219 of /var/www/html/web/modules/contrib/redis/src/Controller/ReportController.php).

+1 for patch #13. also experiencing this issue.

Please can the patch at comment #13 please be added to a production release. It is necessary to allow the module to work with Azure Cache for Redis. Tested successfully from Azure App Service with Drupal 10.3.

Thanks for the fix. I can confirm the patch at #13 works for me in an Azure hosted environment with Drupal `v10.4.5` using Redis `v1.9.0` and Predis `v1.1.10`. I would be very interested in seeing it merged so I don't have to manually track this issue anymore.