[opensuse-support] apache2 exits with PHP Fatal error: Unable to start pcre module in Unknown on line 0
Hi, After errors in upgrading apache2 or it's components (see my post here on Jan. 11 2020, 12:21) which was solved with help from Christian Boltz, apache2 refuses to start. That is, systemctl start apache2 return without error messages on the terminal, but systemctl status apache2 gives systemctl status apache2 ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-04-14 11:31:42 CEST; 8min ago Process: 102150 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=254) Main PID: 102150 (code=exited, status=254) Status: "Reading configuration..." apr 14 11:30:11 linux-mkay systemd[1]: Starting The Apache Webserver... apr 14 11:30:12 linux-mkay systemd[1]: Started The Apache Webserver. apr 14 11:30:12 linux-mkay systemd[1]: apache2.service: Main process exited, code=exited, status=254/n/a apr 14 11:31:42 linux-mkay systemd[1]: apache2.service: Reload operation timed out. Killing reload process. apr 14 11:31:42 linux-mkay systemd[1]: apache2.service: Failed with result 'exit-code' Conform advice of Cristian in before mentioned thread, I ran grep '^[^#]' /etc/sysconfig/apache2 APACHE_CONF_INCLUDE_FILES="" APACHE_CONF_INCLUDE_DIRS="" APACHE_MODULES="php7 authz_host actions alias auth_basic authn_file authz_user authz_groupfile autoindex cgi dir include log_config mime negotiation env setenvif status userdir asis imagemap perl wsgi-python3 authn_core version authz_core reqtimeout socache_shmcb wsgi rewrite ssl" APACHE_SERVER_FLAGS="SSL " APACHE_HTTPD_CONF="" APACHE_MPM="" APACHE_SERVERADMIN="" APACHE_SERVERNAME="" APACHE_START_TIMEOUT="2" APACHE_SERVERSIGNATURE="off" APACHE_LOGLEVEL="error" APACHE_ACCESS_LOG="/var/log/apache2/access_log combined" APACHE_USE_CANONICAL_NAME="off" APACHE_SERVERTOKENS="ProductOnly" APACHE_EXTENDED_STATUS="off" APACHE_EXTENDED_STATUS="off" so no irregularities here I think. /var/log/apache2/error_log gives one error message for each time I try to start apache2: PHP Fatal error: Unable to start pcre module in Unknown on line 0 Googling this message doesn't give results that I can do something with. Anyone any idea? regards, Jogchum -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op 14-04-2020 om 11:47 schreef Jogchum Reitsma:
Hi,
After errors in upgrading apache2 or it's components (see my post here on Jan. 11 2020, 12:21) which was solved with help from Christian Boltz, apache2 refuses to start.
That is, systemctl start apache2 return without error messages on the terminal, but systemctl status apache2 gives
systemctl status apache2 ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-04-14 11:31:42 CEST; 8min ago Process: 102150 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=254) Main PID: 102150 (code=exited, status=254) Status: "Reading configuration..."
<snip>
/var/log/apache2/error_log gives one error message for each time I try to start apache2:
PHP Fatal error: Unable to start pcre module in Unknown on line 0
Googling this message doesn't give results that I can do something with.
Anyone any idea?
regards, Jogchum
I believe it's not very "netiquette" to reply to one's own posts, but I noticed a message when upgrading to yesterday's TW snapshot, so I decided to add that here: %posttrans script 'kernel-firmware-mediatek-20200413-1.1.noarch.rpm' wordt uitgevoerd ........................................................................................................................................<62%>========================================================================================[-] Output of php7-pear-1.10.18-1.1.noarch.rpm %posttrans script: PHP Fatal error: Unable to start pcre module in Unknown on line 0 PHP Fatal error: Unable to start pcre module in Unknown on line 0 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Jogchum, et al -- ...and then Jogchum Reitsma said... % % Op 14-04-2020 om 11:47 schreef Jogchum Reitsma: % >Hi, % > % >After errors in upgrading apache2 or it's components (see my post % >here on Jan. 11 2020, 12:21) which was solved with help from % >Christian Boltz, apache2 refuses to start. % > ... % > % >Anyone any idea? % > % >regards, Jogchum % > % I believe it's not very "netiquette" to reply to one's own posts, While "TOFU" quoting is frowned upon, replying to yourself is fine. How else would you provide additional information? :-) % but I noticed a message when upgrading to yesterday's TW snapshot, % so I decided to add that here: [snip] Would that I could help you here! Best of luck :-) Have a great day :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 21/04/2020 15.59, Jogchum Reitsma wrote:
Op 14-04-2020 om 11:47 schreef Jogchum Reitsma:
...
/var/log/apache2/error_log gives one error message for each time I try to start apache2:
PHP Fatal error: Unable to start pcre module in Unknown on line 0
Googling this message doesn't give results that I can do something with.
Anyone any idea?
regards, Jogchum
I believe it's not very "netiquette" to reply to one's own posts,
On the contrary, it is the way to add new information.
but I noticed a message when upgrading to yesterday's TW snapshot, so I decided to add that here:
%posttrans script 'kernel-firmware-mediatek-20200413-1.1.noarch.rpm' wordt uitgevoerd ........................................................................................................................................<62%>========================================================================================[-]
Output of php7-pear-1.10.18-1.1.noarch.rpm %posttrans script: PHP Fatal error: Unable to start pcre module in Unknown on line 0 PHP Fatal error: Unable to start pcre module in Unknown on line 0
Problem is, the message says line one but not what file :-/ I would inspect every such file in your system: locate php | grep /srv -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Op dinsdag 21 april 2020 19:54:45 CEST schreef Carlos E. R.:
Problem is, the message says line one but not what file :-/
I would inspect every such file in your system:
locate php | grep /srv
Eh ......... knurpht@salt:~> locate php | grep srv | wc -l 186735 knurpht@salt:~> -- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 21/04/2020 20.03, Knurpht-openSUSE wrote:
Op dinsdag 21 april 2020 19:54:45 CEST schreef Carlos E. R.:
Problem is, the message says line one but not what file :-/
I would inspect every such file in your system:
locate php | grep /srv
Eh .........
knurpht@salt:~> locate php | grep srv | wc -l 186735 knurpht@salt:~>
Heh :-} If you have a better idea ;-) Start with the first file of each directory. Huh, "/srv" better than "srv" Other than that, I can suggest another mass weapon: strace or ltrace the entire apache startup, and find what file it is reading when it bails out. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Op 21-04-2020 om 20:12 schreef Carlos E. R.:
On 21/04/2020 20.03, Knurpht-openSUSE wrote:
Op dinsdag 21 april 2020 19:54:45 CEST schreef Carlos E. R.:
Problem is, the message says line one but not what file :-/
I would inspect every such file in your system:
locate php | grep /srv
Eh .........
knurpht@salt:~> locate php | grep srv | wc -l 186735 knurpht@salt:~>
Heh :-}
If you have a better idea ;-)
Start with the first file of each directory.
Huh, "/srv" better than "srv"
Hmm - locate php | grep /srv | wc -l 12116 is not that much less than locate php | grep srv | wc -l 12136 My numbers are some 15 times below that of Knurpht, but still to high to inspect each file manually, I would say.
Other than that, I can suggest another mass weapon: strace or ltrace the entire apache startup, and find what file it is reading when it bails out.
Good idea, seems to me! Never user strace, but after a quick google I started strace -f -o /tmp/strace.log -s 2048 -p 1 & systemctl start apache2 which logfile at line 20138 issued 87768 openat(AT_FDCWD, "/usr/lib64/php7/extensions/zlib.so", O_RDONLY|O_CLOEXEC) = 10 87768 read(10, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0pF\0\0\0\0\0\0@\0\0\0\0\0\0\0 \325\0\0\0\0\0\0\0\0\0\0@\08\0\t\0@\0\34\0\33\0\1\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 7\0\0\0\0\0\0 7\0\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\5\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0aT\0\0\0\0\0\0aT\0\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\4\0\0\0\0\240\0\0\0\0\0\0\0\240\0\0\0\0\0\0\0\240\0\0\0\0\0\0P\35\0\0\0\0\0\0P\35\0\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\6\0\0\0\360\276\0\0\0\0\0\0\360\316\0\0\0\0\0\0\360\316\0\0\0\0\0\0\30\25\0\0\0\0\0\0\240\25\0\0\0\0\0\0\0\20\0\0\0\0\0\0\2\0\0\0\6\0\0\0\300\315\0\0\0\0\0\0\300\335\0\0\0\0\0\0\300\335\0\0\0\0\0\0\360\1\0\0\0\0\0\0\360\1\0\0\0\0\0\0\10\0\0\0\0\0\0\0\4\0\0\0\4\0\0\08\2\0\0\0\0\0\08\2\0\0\0\0\0\08\2\0\0\0\0\0\0$\0\0\0\0\0\0\0$\0\0\0\0\0\0\0\4\0\0\0\0\0\0\0P\345td\4\0\0\0\240\254\0\0\0\0\0\0\240\254\0\0\0\0\0\0\240\254\0\0\0\0\0\0\204\2\0\0\0\0\0\0\204\2\0\0\0\0\0\0\4\0\0\0\0\0\0\0Q\345td\6\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\20\0\0\0\0\0\0\0R\345td\4\0\0\0\360\276\0\0\0\0\0\0\360\316\0\0\0\0\0\0\360\316\0\0\0\0\0\0\20\21\0\0\0\0\0\0\20\21\0\0\0\0\0\0\1\0\0\0\0\0\0\0\4\0\0\0\24\0\0\0\3\0\0\0GNU\0j\217\373\n\24C\253<\366\326:\357\310\223]\334\313\364m\223\0\0\0\0a\0\0\0z\0\0\0g\0\0\0\0\0\0\0\0\0\0\0:\0\0\0G\0\0\0o\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0T\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0#\0\0\0\0\0\0\0S\0\0\0\3\0\0\0\17\0\0\0>\0\0\0\0\0\0\0_\0\0\0M\0\0\0\0\0\0\0C\0\0\0j\0\0\0\\\0\0\0\0\0\0\0\2\0\0\0\0\0\0\0c\0\0\0\0\0\0\0x\0\0\0\0\0\0\0)\0\0\0F\0\0\0H\0\0\0L\0\0\0q\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0n\0\0\0k\0\0\0\0\0\0\0\f\0\0\0\0\0\0\0r\0\0\0A\0\0\0\0\0\0\0\37\0\0\0004\0\0\0\0\0\0\0", 832) = 832 87768 fstat(10, {st_mode=S_IFREG|0755, st_size=56352, ...}) = 0 87768 mmap(NULL, 58512, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 10, 0) = 0x7f0e538f4000 87768 mmap(0x7f0e538f8000, 24576, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 10, 0x4000) = 0x7f0e538f8000 87768 mmap(0x7f0e538fe000, 8192, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 10, 0xa000) = 0x7f0e538fe000 87768 mmap(0x7f0e53900000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 10, 0xb000) = 0x7f0e53900000 87768 close(10) = 0 87768 mprotect(0x7f0e53900000, 8192, PROT_READ) = 0 87768 futex(0x7f0e5715cd58, FUTEX_WAKE_PRIVATE, 2147483647) = 0 87768 write(2, "PHP Fatal error: Unable to start pcre module in Unknown on line 0\n", 67) = 67 so I would think zlib.so is the offending item. I commented out "extension=zlib.so" in /etc/php7/conf.d/zlib.ini to disable use of zlib by PHP, but that gies no solution. I'll keep on digging, but I'm open for any new ideas! Thanks so far! regards, Jogchum -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 22/04/2020 12.28, Jogchum Reitsma wrote:
Op 21-04-2020 om 20:12 schreef Carlos E. R.:
On 21/04/2020 20.03, Knurpht-openSUSE wrote:
Op dinsdag 21 april 2020 19:54:45 CEST schreef Carlos E. R.:
...
My numbers are some 15 times below that of Knurpht, but still to high to inspect each file manually, I would say.
Perhaps you only have to look at the first line of each file.
Other than that, I can suggest another mass weapon: strace or ltrace the entire apache startup, and find what file it is reading when it bails out.
Good idea, seems to me! Never user strace, but after a quick google I started
There are several ?trace tools, each logs different output. I don't know which is the best one in this case.
strace -f -o /tmp/strace.log -s 2048 -p 1 & systemctl start apache2
Perhaps edit "/usr/lib/systemd/system/apache2.service" instead. And you have to capture all children as well - no, I don't remember trace options to notice if you already did ;-)
which logfile at line 20138 issued
87768 openat(AT_FDCWD, "/usr/lib64/php7/extensions/zlib.so", O_RDONLY|O_CLOEXEC) = 10 87768 read(10, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0pF\0\0\0\0\0\0@\0\0\0\0\0\0\0 \325\0\0\0\0\0\0\0\0\0\0@\08\0\t\0@\0\34\0\33\0\1\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 7\0\0\0\0\0\0 7\0\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\5\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0aT\0\0\0\0\0\0aT\0\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\4\0\0\0\0\240\0\0\0\0\0\0\0\240\0\0\0\0\0\0\0\240\0\0\0\0\0\0P\35\0\0\0\0\0\0P\35\0\0\0\0\0\0\0\20\0\0\0\0\0\0\1\0\0\0\6\0\0\0\360\276\0\0\0\0\0\0\360\316\0\0\0\0\0\0\360\316\0\0\0\0\0\0\30\25\0\0\0\0\0\0\240\25\0\0\0\0\0\0\0\20\0\0\0\0\0\0\2\0\0\0\6\0\0\0\300\315\0\0\0\0\0\0\300\335\0\0\0\0\0\0\300\335\0\0\0\0\0\0\360\1\0\0\0\0\0\0\360\1\0\0\0\0\0\0\10\0\0\0\0\0\0\0\4\0\0\0\4\0\0\08\2\0\0\0\0\0\08\2\0\0\0\0\0\08\2\0\0\0\0\0\0$\0\0\0\0\0\0\0$\0\0\0\0\0\0\0\4\0\0\0\0\0\0\0P\345td\4\0\0\0\240\254\0\0\0\0\0\0\240\254\0\0\0\0\0\0\240\254\0\0\0\0\0\0\204\2\0\0\0\0\0\0\204\2\0\0\0\0\0\0\4\0\0\0\0\0\0\0Q\345td\6\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\20\0\0\0\0\0\0\0R\345td\4\0\0\0\360\276\0\0\0\0\0\0\360\316\0\0\0\0\0\0\360\316\0\0\0\0\0\0\20\21\0\0\0\0\0\0\20\21\0\0\0\0\0\0\1\0\0\0\0\0\0\0\4\0\0\0\24\0\0\0\3\0\0\0GNU\0j\217\373\n\24C\253<\366\326:\357\310\223]\334\313\364m\223\0\0\0\0a\0\0\0z\0\0\0g\0\0\0\0\0\0\0\0\0\0\0:\0\0\0G\0\0\0o\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0T\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0#\0\0\0\0\0\0\0S\0\0\0\3\0\0\0\17\0\0\0>\0\0\0\0\0\0\0_\0\0\0M\0\0\0\0\0\0\0C\0\0\0j\0\0\0\\\0\0\0\0\0\0\0\2\0\0\0\0\0\0\0c\0\0\0\0\0\0\0x\0\0\0\0\0\0\0)\0\0\0F\0\0\0H\0\0\0L\0\0\0q\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0n\0\0\0k\0\0\0\0\0\0\0\f\0\0\0\0\0\0\0r\0\0\0A\0\0\0\0\0\0\0\37\0\0\0004\0\0\0\0\0\0\0", 832) = 832 87768 fstat(10, {st_mode=S_IFREG|0755, st_size=56352, ...}) = 0 87768 mmap(NULL, 58512, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 10, 0) = 0x7f0e538f4000 87768 mmap(0x7f0e538f8000, 24576, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 10, 0x4000) = 0x7f0e538f8000 87768 mmap(0x7f0e538fe000, 8192, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 10, 0xa000) = 0x7f0e538fe000 87768 mmap(0x7f0e53900000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 10, 0xb000) = 0x7f0e53900000 87768 close(10) = 0 87768 mprotect(0x7f0e53900000, 8192, PROT_READ) = 0 87768 futex(0x7f0e5715cd58, FUTEX_WAKE_PRIVATE, 2147483647) = 0 87768 write(2, "PHP Fatal error: Unable to start pcre module in Unknown on line 0\n", 67) = 67
so I would think zlib.so is the offending item.
That seems weird. But it is opening and reading that file.
I commented out "extension=zlib.so" in /etc/php7/conf.d/zlib.ini to disable use of zlib by PHP, but that gies no solution.
I'll keep on digging, but I'm open for any new ideas!
Thanks so far!
regards, Jogchum
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Op dinsdag 14 april 2020 11:47:09 CEST schreef Jogchum Reitsma:
Hi,
After errors in upgrading apache2 or it's components (see my post here on Jan. 11 2020, 12:21) which was solved with help from Christian Boltz, apache2 refuses to start.
That is, systemctl start apache2 return without error messages on the terminal, but systemctl status apache2 gives
systemctl status apache2 ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-04-14 11:31:42 CEST; 8min ago Process: 102150 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=254) Main PID: 102150 (code=exited, status=254) Status: "Reading configuration..."
apr 14 11:30:11 linux-mkay systemd[1]: Starting The Apache Webserver... apr 14 11:30:12 linux-mkay systemd[1]: Started The Apache Webserver. apr 14 11:30:12 linux-mkay systemd[1]: apache2.service: Main process exited, code=exited, status=254/n/a apr 14 11:31:42 linux-mkay systemd[1]: apache2.service: Reload operation timed out. Killing reload process. apr 14 11:31:42 linux-mkay systemd[1]: apache2.service: Failed with result 'exit-code'
Conform advice of Cristian in before mentioned thread, I ran
grep '^[^#]' /etc/sysconfig/apache2 APACHE_CONF_INCLUDE_FILES="" APACHE_CONF_INCLUDE_DIRS="" APACHE_MODULES="php7 authz_host actions alias auth_basic authn_file authz_user authz_groupfile autoindex cgi dir include log_config mime negotiation env setenvif status userdir asis imagemap perl wsgi-python3 authn_core version authz_core reqtimeout socache_shmcb wsgi rewrite ssl" APACHE_SERVER_FLAGS="SSL " APACHE_HTTPD_CONF="" APACHE_MPM="" APACHE_SERVERADMIN="" APACHE_SERVERNAME="" APACHE_START_TIMEOUT="2" APACHE_SERVERSIGNATURE="off" APACHE_LOGLEVEL="error" APACHE_ACCESS_LOG="/var/log/apache2/access_log combined" APACHE_USE_CANONICAL_NAME="off" APACHE_SERVERTOKENS="ProductOnly" APACHE_EXTENDED_STATUS="off" APACHE_EXTENDED_STATUS="off"
so no irregularities here I think.
/var/log/apache2/error_log gives one error message for each time I try to start apache2:
PHP Fatal error: Unable to start pcre module in Unknown on line 0
Googling this message doesn't give results that I can do something with.
Anyone any idea?
regards, Jogchum Can you show rpm -qa | grep pcre ?
-- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op 21-04-2020 om 20:26 schreef Knurpht-openSUSE:
rpm -qa | grep pcre
rpm -qa | grep pcre libpcre1-32bit-8.42-3.2.x86_64 libpcreposix0-8.42-3.2.x86_64 libpcre2-16-0-10.34-1.2.x86_64 libpcre2-8-0-10.34-1.2.x86_64 libpcre1-8.42-3.2.x86_64 pcre-devel-8.42-3.2.x86_64 libpcrecpp0-8.42-3.2.x86_64 libpcre16-0-8.42-3.2.x86_64 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op dinsdag 21 april 2020 20:40:58 CEST schreef Jogchum Reitsma:
Op 21-04-2020 om 20:26 schreef Knurpht-openSUSE:
rpm -qa | grep pcre
rpm -qa | grep pcre libpcre1-32bit-8.42-3.2.x86_64 libpcreposix0-8.42-3.2.x86_64 libpcre2-16-0-10.34-1.2.x86_64 libpcre2-8-0-10.34-1.2.x86_64 libpcre1-8.42-3.2.x86_64 pcre-devel-8.42-3.2.x86_64 libpcrecpp0-8.42-3.2.x86_64 libpcre16-0-8.42-3.2.x86_64 This is from my VPS, running multiple websites and -services
:~> rpm -qa | grep pcre libpcre2-16-0-10.34-1.2.x86_64 libpcre2-32-0-10.34-1.2.x86_64 libpcre1-8.42-3.2.x86_64 libpcre1-32bit-8.42-3.2.x86_64 libpcreposix0-8.42-3.2.x86_64 <=== might this be the culprit? pcre-devel-8.42-3.2.x86_64 pcre2-devel-10.34-1.2.x86_64 libpcre16-0-8.42-3.2.x86_64 libpcre2-posix2-10.34-1.2.x86_64 libpcre2-8-0-10.34-1.2.x86_64 libpcrecpp0-8.42-3.2.x86_64 -- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (4)
-
Carlos E. R. -
David T-G -
Jogchum Reitsma -
Knurpht-openSUSE