Bug#1004285: [DAViCal-devel] Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"

2022-02-18 Thread Benno Overeinder

Hi Florian,

Thank you for your email.  I haven't tested it with the git versions of 
AWL and DAViCal yet, but here is more are more lines from the apache log 
file.


After upgrading (again) to php8, the following lines are in the apache2 
error.log.  I hope the formatting stays okay.  I changed the IP address 
and username for the caldav.php references to the calendars.  Hope this 
helps.  If I have a bit more time, I can try the github version of AWL 
and DAViCal.


[Fri Feb 18 21:13:27.917136 2022] [mpm_prefork:notice] [pid 47871] 
AH00163: Apache/2.4.52 (Debian) OpenSSL/1.1.1m configured -- resuming 
normal operations
[Fri Feb 18 21:13:27.917271 2022] [core:notice] [pid 47871] AH00094: 
Command line: '/usr/sbin/apache2'
[Fri Feb 18 21:14:15.536261 2022] [mpm_prefork:notice] [pid 47871] 
AH00170: caught SIGWINCH, shutting down gracefully
[Fri Feb 18 21:14:15.642859 2022] [mpm_prefork:notice] [pid 49687] 
AH00163: Apache/2.4.52 (Debian) OpenSSL/1.1.1m configured -- resuming 
normal operations
[Fri Feb 18 21:14:15.642922 2022] [core:notice] [pid 49687] AH00094: 
Command line: '/usr/sbin/apache2'
[Fri Feb 18 21:14:58.422246 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: ***: ERROR:XML parsing error: Unknown (202) 
at line 4, column 26
[Fri Feb 18 21:14:58.422288 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: ***: ERROR:Error occurred 
in:\n\n 
/caldav.php/username/work/\n 
/caldav.php/username/home/\n\n
[Fri Feb 18 21:14:58.422294 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: ***: ERROR:XML namespace error but tags 
extracted, trying to continue
[Fri Feb 18 21:14:58.430957 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: BUG: :DAViCal Fatal Error: [0A000] 
SQLSTATE[0A000]: Feature not supported: 7 ERROR:  set-returning 
functions are not allowed in CASE\nLINE 4: ... expanded.g_id FROM 
(SELECT CASE WHEN $2 > 0 THEN expand_mem...\n 
  ^\nHINT:  You might be able to move 
the set-returning function into a LATERAL FROM item.\nQUERY:  \n  SELECT 
group_id FROM group_member WHERE member_id = $1\n  UNION\n  SELECT 
expanded.g_id FROM (SELECT CASE WHEN $2 > 0 THEN expand_memberships( 
group_id, $2 - 1) END AS g_id\n   FROM 
group_member WHERE member_id = $1) AS expanded\n 
WHERE expanded.g_id IS NOT NULL;\n\nCONTEXT:  SQL function 
"expand_memberships" during startup\nSQL statement "SELECT 
bit_or(subquery.privileges)FROM\n(\n  SELECT 
privileges FROM grants WHERE by_principal=in_grantor AND by_collection 
IS NULL\n  AND 
(to_principal=in_accessor OR to_principal IN (SELECT 
expand_memberships(in_accessor,in_depth)))\nUNION\n 
SELECT 32::BIT(24) AS privileges FROM 
expand_memberships(in_accessor,in_depth) WHERE expand_memberships = 
in_grantor\n) AS subquery"\nPL/pgSQL function 
pprivs(bigint,bigint,integer) line 14 at SQL statement at 
/usr/share/awl/inc/AwlDatabase.php:94
[Fri Feb 18 21:14:58.430975 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] = Stack Trace ===
[Fri Feb 18 21:14:58.430999 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: :Response status 500 for PROPFIND 
/caldav.php/username/
[Fri Feb 18 21:14:58.431005 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: :* Response Header 

[Fri Feb 18 21:14:58.431009 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: headers:-->Server: 1.1
[Fri Feb 18 21:14:58.431013 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: headers:-->DAV: 1, 2, 3, 
access-control, calendar-access, calendar-schedule
[Fri Feb 18 21:14:58.431017 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: headers:-->DAV: extended-mkcol, bind, 
addressbook, calendar-auto-schedule, calendar-proxy
[Fri Feb 18 21:14:58.431020 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: headers:-->X-DAViCal-Version: 
DAViCal/1.1.10; DB/1.3.3
[Fri Feb 18 21:14:58.431024 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: headers:-->Content-type: text/plain; 
charset="utf-8"
[Fri Feb 18 21:14:58.431027 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: : Response 

[Fri Feb 18 21:14:58.431064 2022] [php:notice] [pid 49689] [client 
192.168.1.1:64517] davical: LOG: response:-->DAViCal Fatal Error
[Fri Feb 18 21:14:58.725790 2022] [php:notice] [pid 49690] [client 
192.168.1.1:64518] davical: ***: ERROR:XML parsing error: Unknown (202) 
at line 4, column 26
[Fri Feb 18 21:14:58.725814 2022] [php:notice] [pid 49690] [client 
192.168.1.1:64518] davical: ***: ERROR:Error occurred 
in:\n\n 
/caldav.php/username/work/\n 
/caldav.php/username/home/\n\n
[Fri Feb 18 21:14:58.725820 2022] [php:notice] 

Bug#1004285: [DAViCal-devel] Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"

2022-02-16 Thread Florian Schlichting
Hi Benno,

> I have looked at the apache2 log files and checked the /etc/php and
> /etc/davical directories if there were any references to php7 instead
> of php/php8.  The apache2 log file reported
> 
> [Mon Jan 24 11:29:29.678647 2022] [php:notice] [pid 684] [client /IPv6 
> address/] davical: LOG: response:-->DAViCal Fatal Error

Andrew fixed many issues with PHP 8 over the last few days. Are you able
to test with git versions of AWL and DAViCal? Otherwise it would be
helpful if you can find a few more lines from your logs containing the
PHP backtrace identifying the exact place in the code where the fatal
error occurred, as well as the PHP error message.

Florian