[SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora 35. First I don''t see a F35 RPM. After upgrading Apache works just fine for loading plain HTML pages but webmail gets an internal server error, 500. I enabled debug logging and below is what I see in the SSl error logs with these 2 lines having errors: AH02008: SSL library error 1 in handshake (server OURDOMAIN:443) SSL Library Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown (SSL alert number 46) In context: [Tue Jan 04 16:13:33.661487 2022] [ssl:info] [pid 77902:tid 77948] [client 108.54.237.13:1092] AH01964: Connection to child 210 established (server OURDOMAIN:443) [Tue Jan 04 16:13:33.661714 2022] [ssl:debug] [pid 77902:tid 77948] ssl_engine_kernel.c(2425): [client 108.54.237.13:1092] AH02645: Server name not provided via TLS extension (using default/first virtual host) [Tue Jan 04 16:13:33.661869 2022] [core:debug] [pid 77902:tid 77948] protocol.c(2449): [client 108.54.237.13:1092] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:13:33.672615 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(570): AH00837: socache_shmcb_remove (0x3c -> subcache 28) [Tue Jan 04 16:13:33.672649 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(954): AH00852: possible match at idx=2, data=438 [Tue Jan 04 16:13:33.672659 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(959): AH00853: shmcb_subcache_remove removing matching entry [Tue Jan 04 16:13:33.672669 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(585): AH00839: leaving socache_shmcb_remove successfully [Tue Jan 04 16:13:33.672683 2022] [ssl:info] [pid 77902:tid 77948] [client 108.54.237.13:1092] AH02008: SSL library error 1 in handshake (server OURDOMAIN:443) [Tue Jan 04 16:13:33.672715 2022] [ssl:info] [pid 77902:tid 77948] SSL Library Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown (SSL alert number 46) [Tue Jan 04 16:13:33.672731 2022] [ssl:info] [pid 77902:tid 77948] [client 108.54.237.13:1092] AH01998: Connection closed to child 210 with abortive shutdown (server OURDOMAIN:443) [Tue Jan 04 16:13:33.683683 2022] [ssl:info] [pid 77902:tid 77937] [client 108.54.237.13:1095] AH01964: Connection to child 199 established (server OURDOMAIN:443) [Tue Jan 04 16:13:33.683823 2022] [ssl:debug] [pid 77902:tid 77937] ssl_engine_kernel.c(2425): [client 108.54.237.13:1095] AH02645: Server name not provided via TLS extension (using default/first virtual host) [Tue Jan 04 16:13:33.683876 2022] [core:debug] [pid 77902:tid 77937] protocol.c(2449): [client 108.54.237.13:1095] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:13:33.701176 2022] [ssl:debug] [pid 77902:tid 77937] ssl_engine_kernel.c(2254): [client 108.54.237.13:1095] AH02041: Protocol: TLSv1.3, Cipher: TLS_AES_256_GCM_SHA384 (256/256 bits) [Tue Jan 04 16:13:33.701312 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0xe3 -> subcache 3) [Tue Jan 04 16:13:33.701329 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(745): AH00842: expiring 1 and reclaiming 0 removed socache entries [Tue Jan 04 16:13:33.701338 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(765): AH00843: we now have 0 socache entries [Tue Jan 04 16:13:33.701350 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(862): AH00847: insert happened at idx=3, data=(677:709) [Tue Jan 04 16:13:33.701360 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=3/1, data_pos/data_used=677/201 [Tue Jan 04 16:13:33.701370 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully [Tue Jan 04 16:13:33.701494 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0x43 -> subcache 3) [Tue Jan 04 16:13:33.701511 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(862): AH00847: insert happened at idx=4, data=(878:910) [Tue Jan 04 16:13:33.701519 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=3/2, data_pos/data_used=677/402 [Tue Jan 04 16:13:33.701528 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully [Tue Jan 04 16:13:33.701713 2022] [ssl:debug] [pid 77902:tid 77937] ssl_engine_kernel.c(415): [client 108.54.237.13:1095] AH02034: Initial (No.1) HTTPS request received for child 199 (server OURDOMAIN:443) [Tue Jan 04 16:13:33.701903 2022] [authz_core:debug] [pid 77902:tid 77937] mod_authz_core.c(815): [client 108.54.237.13:1095] AH01626: authorization result of Require all granted: granted [Tue Jan
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
On Tue, January 4, 2022 9:17 pm, Robert Kudyba wrote: > PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora > 35. First I don''t see a F35 RPM. With PHP 8 you're probably going to need a newer version of SquirrelMail. > After upgrading Apache works just fine > for loading plain HTML pages but webmail gets an internal server error, > 500. More than likely the SSL connection problem is happening at a layer above SquirrelMail. I'd first try to get a static page to load using that same certificate/domain and then try SquirrelMail, also keeping an eye on the PHP logs as well. > I enabled debug logging and below is what I see in the SSl error logs with > these 2 lines having errors: > AH02008: SSL library error 1 in handshake (server OURDOMAIN:443) > SSL Library Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert > certificate unknown (SSL alert number 46) -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora > > 35. First I don''t see a F35 RPM. > > With PHP 8 you're probably going to need a newer version of SquirrelMail. > Does that mean having to compile from source? > After upgrading Apache works just fine > > for loading plain HTML pages but webmail gets an internal server error, > > 500. > > More than likely the SSL connection problem is happening at a layer above > SquirrelMail. I'd first try to get a static page to load using that same > certificate/domain and then try SquirrelMail, also keeping an eye on the > PHP logs as well. > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and string offset access syntax with curly braces is no longer supported in */usr/share/squirrelmail/functions/strings.php* on line *634* ssl error logs now show this: [Tue Jan 04 16:47:38.970635 2022] [ssl:info] [pid 138303:tid 138340] [client 108.54.237.13:4417] AH01964: Connection to child 201 established (server OURDOMAIN:443) [Tue Jan 04 16:47:38.970943 2022] [ssl:debug] [pid 138303:tid 138340] ssl_engine_kernel.c(2395): [client 108.54.237.13:4417] AH02043: SSL virtual host for servername OURDOMAIN found [Tue Jan 04 16:47:38.971163 2022] [core:debug] [pid 138303:tid 138340] protocol.c(2449): [client 108.54.237.13:4417] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:47:38.982151 2022] [ssl:debug] [pid 138303:tid 138340] ssl_engine_kernel.c(2254): [client 108.54.237.13:4417] AH02041: Protocol: TLSv1.3, Cipher: TLS_AES_256_GCM_SHA384 (256/256 bits) [Tue Jan 04 16:47:38.982295 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0x7b -> subcache 27) [Tue Jan 04 16:47:38.982312 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(745): AH00842: expiring 1 and reclaiming 0 removed socache entries [Tue Jan 04 16:47:38.982323 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(765): AH00843: we now have 0 socache entries [Tue Jan 04 16:47:38.982338 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(862): AH00847: insert happened at idx=0, data=(0:32) [Tue Jan 04 16:47:38.982347 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=0/1, data_pos/data_used=0/225 [Tue Jan 04 16:47:38.982356 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully [Tue Jan 04 16:47:38.982614 2022] [ssl:debug] [pid 138303:tid 138340] ssl_engine_kernel.c(415): [client 108.54.237.13:4417] AH02034: Initial (No.1) HTTPS request received for child 201 (server OURDOMAIN:443) [Tue Jan 04 16:47:38.982818 2022] [authz_core:debug] [pid 138303:tid 138340] mod_authz_core.c(815): [client 108.54.237.13:4417] AH01626: authorization result of Require all granted: granted [Tue Jan 04 16:47:38.982835 2022] [authz_core:debug] [pid 138303:tid 138340] mod_authz_core.c(815): [client 108.54.237.13:4417] AH01626: authorization result of : granted [Tue Jan 04 16:47:38.983049 2022] [proxy:debug] [pid 138303:tid 138340] mod_proxy.c(1503): [client 108.54.237.13:4417] AH01143: Running scheme unix handler (attempt 0) [Tue Jan 04 16:47:38.983068 2022] [proxy_ajp:debug] [pid 138303:tid 138340] mod_proxy_ajp.c(755): [client 108.54.237.13:4417] AH00894: declining URL fcgi://localhost/usr/share/squirrelmail/src/login.php [Tue Jan 04 16:47:38.983080 2022] [proxy_fcgi:debug] [pid 138303:tid 138340] mod_proxy_fcgi.c(1054): [client 108.54.237.13:4417] AH01076: url: fcgi://localhost/usr/share/squirrelmail/src/login.php proxyname: (null) proxyport: 0 [Tue Jan 04 16:47:38.983130 2022] [proxy_fcgi:debug] [pid 138303:tid 138340] mod_proxy_fcgi.c(1063): [client 108.54.237.13:4417] AH01078: serving URL fcgi://localhost/usr/share/squirrelmail/src/login.php [Tue Jan 04 16:47:38.983152 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2531): AH00942: FCGI: has acquired connection for (*) [Tue Jan 04 16:47:38.983166 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2587): [client 108.54.237.13:4417] AH00944: connecting fcgi://localhost/usr/share/squirrelmail/src/login.php to localhost:8000 [Tue Jan 04 16:47:38.983178 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2623): [client 108.54.237.13:4417] AH02545: fcgi: has determined UDS as /run/php-fpm/www.sock [Tue Jan 04 16:47:38.983273 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2810): [client 108.54.237.13:4417] AH00947: connected /usr/share/squirrelmail/src/login.php to httpd-UDS:0 [Tue Jan 04 16:47:38.983340 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(3177): AH02823: FCGI: connection established with Unix domain socket /run/php-fpm/www.sock (*) [Tue Jan 04 16:47:38.985967 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2546): AH00943: FCGI: has released connection for (*) [Tue Jan 04 16:47:39.905828 20
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote: >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on >> Fedora >> > 35. First I don''t see a F35 RPM. >> >> With PHP 8 you're probably going to need a newer version of >> SquirrelMail. > > Does that mean having to compile from source? PHP is not a compiled language. It's just a matter of putting the source code on your server. It is possible that you could grab a tarball of 1.4.23-svn from our website and unpack that right on top of what you have, but that could get messy depending what the RPM author did or did not do with the source or configuration. Try placing the new tarball in a parallel directory, copy over the configuration and plugins, and see how that goes. > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and > string > offset access syntax with curly braces is no longer supported in > */usr/share/squirrelmail/functions/strings.php* on line *634* That error indicates that in fact you need a newer version of SquirrelMail. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski wrote: > > > On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote: > >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on > >> Fedora > >> > 35. First I don''t see a F35 RPM. > >> > >> With PHP 8 you're probably going to need a newer version of > >> SquirrelMail. > > > > Does that mean having to compile from source? > > PHP is not a compiled language. It's just a matter of putting the source > code on your server. It is possible that you could grab a tarball of > 1.4.23-svn from our website and unpack that right on top of what you have, > but that could get messy depending what the RPM author did or did not do > with the source or configuration. Try placing the new tarball in a > parallel directory, copy over the configuration and plugins, and see how > that goes. > Right, duh of course. So putting them in a place like /usr/share/squirrelmail2 would be ok. Do I just re-run conf.pl? Which files hold the settings? > > > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and > > string > > offset access syntax with curly braces is no longer supported in > > */usr/share/squirrelmail/functions/strings.php* on line *634* > > That error indicates that in fact you need a newer version of SquirrelMail Will the new version you mentioned fix these? - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500
On Tue, January 4, 2022 10:17 pm, Robert Kudyba wrote: > On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski > wrote: > >> >> >> On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote: >> >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on >> >> Fedora >> >> > 35. First I don''t see a F35 RPM. >> >> >> >> With PHP 8 you're probably going to need a newer version of >> >> SquirrelMail. >> > >> > Does that mean having to compile from source? >> >> PHP is not a compiled language. It's just a matter of putting the >> source >> code on your server. It is possible that you could grab a tarball of >> 1.4.23-svn from our website and unpack that right on top of what you >> have, >> but that could get messy depending what the RPM author did or did not do >> with the source or configuration. Try placing the new tarball in a >> parallel directory, copy over the configuration and plugins, and see how >> that goes. >> > > Right, duh of course. So putting them in a place like > /usr/share/squirrelmail2 would be ok. Do I just re-run conf.pl? Which > files > hold the settings? Yes, you can re-run conf.pl or just copy over config.php from your other installation and most things will probably work fine assuming the RPM isn't heavily modified. Sometimes there can be custom configuration changes in config_local.php as well. Once copied over, you can still run conf.pl to make changes from there. >> >> > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and >> > string >> > offset access syntax with curly braces is no longer supported in >> > */usr/share/squirrelmail/functions/strings.php* on line *634* >> >> That error indicates that in fact you need a newer version of >> SquirrelMail > > Will the new version you mentioned fix these? Yes -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
