| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Almalinux 9.4 |
| — | — |
| Webmin version | 2.202 |
| Virtualmin version | 7.20.2 |
| Webserver version | Nginx version 1.20.1 |
| Related packages | Roundcube |
Getting this error:
ERROR: Wrong ‘error_reporting’ option value and it wasn’t possible to set it to required value (30711). Check your PHP configuration (including php_admin_flag).
But php-fpm error is allowed on virtual server config. Everything is Default.
Thanks in advance.
Just tested on a spare VS (also Nginx webserver) and it installed no issues. On another quite active VS it has been installed for years and is also chirping with emails all day. /(all using version 1.6.7)
where did the error show up/come from? during the webapp install description?
No, after installation is complete.
Whats PHP version?
where precisely? there must be some extra information in a log somewhere.
Roundcube is pretty robust and pretty good at reporting errors. If my PHP (I am very rusty skills I recall) it reports its errors through an (ini_set/ini_get) setting - during setup/initialisation so could be as simple as failure to access a file.
Using PHP 8.0
15-Sep-2024 06:34:30] ERROR: [/etc/php-fpm.conf:565] Array are not allowed in the global section
15-Sep-2024 06:34:30] ERROR: failed to load configuration file '/etc/php-fpm.conf'
15-Sep-2024 06:34:30] ERROR: FPM initialization failed
m.service: Main process exited, code=exited, status=78/CONFIG
Setting any error type to display from Webmin > Tools > php config > php-fpm config > error logging, I get this error FPM initialization error. I have to manually remove php_admin_value[log_errors] = On from the fpm default config to restart FPM successfully.
Thank you for going extra mile for me, I am also trying to get started with version 1.6.7 even tried with the LTS version but same error.
On the /etc/php.ini config file the logging option is set to:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
Found The Solution:
Roundcube requires that php_admin_value[error_reporting] = E_ALL & ~E_NOTICE & ~E_STRICT to be set on the virtual server php-fpm config file. Otherwise it will throw this error: ERROR: Wrong ‘error_reporting’ option value and it wasn’t possible to set it to required value (30711). Check your PHP configuration (including php_admin_flag)
Found this calculator for when you look at phpinfo
Mine is set at 22527 = error_reporting = E_ALL & ~E_STRICT & ~E_DEPRECATED
I I don’t see any errors in the php log when I use roundcube.
I use Apache, so there maybe a difference.
No difference, same on Nginx.
Roundcube has always been an essential install on any VM I have set up and is installed before anything else (but immediately after Virtualmin - of course!) PHP these days is not used - so I just accept the default install
and it’s configuration. I only have one client who needs PHP for anything else. Nearly all of them use NodeJS or Go these days.
But I am glad you have found a solution and for pointing us all in the direction.
That’s new to me 
I wonder what wordpress and dozens like it will switch too.
OK, to clarify: I have only one client that still uses (or has any interest in PHP as a programming language) And as you are already probably aware I am not interested in any client with an interest in WP.
Roundcube is a different matter - IMO it is a solid program and I almost don’t care which language it uses - it seems to keep up to date and I am happy installing it on any VS.
As I indicated most of those who I now get involved with have little interest in PHP and seem to be asking for help with NodeJS apps and even Go or Rust
I spent too many years developing and managing PHP projects (all now history pre- v.7) and mostly forgotten since retirement!
No prob. I sell hosting and it sounds like your more in the development side of things. My client are not developers and do not program and prob know little of php or nodejs.
Getting off topic anyways.
true, so easy to do. but was good to see the initial problem was solved.
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.