OLS 1.8.2 - admin panel stops working (permission denied)

[nirkons]

after using lsup method described here
https://docs.openlitespeed.org/installation/upgrade/
to upgrade to 1.8.2

server works, website is loading, however, all listeners/virtual hosts appear as down
and server error log contains:

`

2024-09-13 12:09:11.222380	NOTICE	[378710] [:45832:HTTP2-93#_AdminVHost] [STDERR] PHP Warning: filemtime(): stat failed for /dev/shm/ols/status/.status in /usr/local/lsws/admin/html.open/lib/SInfo.php on line 36
2024-09-13 12:09:11.219504	NOTICE	[378710] [:45832:HTTP2-91#_AdminVHost] [STDERR] PHP Warning: file_get_contents(/dev/shm/ols/status/.status): failed to open stream: Permission denied in /usr/local/lsws/admin/html.open/lib/SInfo.php on line 175
2024-09-13 12:09:11.207232	NOTICE	[378710] [:45832:HTTP2-91#_AdminVHost] [STDERR] PHP Warning: filemtime(): stat failed for /dev/shm/ols/status/.status in /usr/local/lsws/admin/html.open/lib/SInfo.php on line 36
2024-09-13 12:09:11.094028	ERROR	[378713] Failed to open the real time report: /dev/shm/ols/status/.rtreport.4!
2024-09-13 12:09:11.094080	ERROR	[378711] Failed to open the real time report: /dev/shm/ols/status/.rtreport.2!
2024-09-13 12:09:11.093928	ERROR	[378712] Failed to open the real time report: /dev/shm/ols/status/.rtreport.3!
2024-09-13 12:09:11.076233	ERROR	[378710] Failed to open the real time report: /dev/shm/ols/status/.rtreport!
2024-09-13 12:09:10.091786	ERROR	[378711] Failed to open the real time report: /dev/shm/ols/status/.rtreport.2!
2024-09-13 12:09:10.091867	ERROR	[378712] Failed to open the real time report: /dev/shm/ols/status/.rtreport.3!
2024-09-13 12:09:10.091930	ERROR	[378713] Failed to open the real time report: /dev/shm/ols/status/.rtreport.4!

`

I checked the permissions for /dev/shm/ols/status/
and they are www-data:www-data

they revert to that after every litespeed restart,
for debugging I tried setting the permissions to lsadm:lsadm even in the lsws service, but that did not work.
not sure what I'm missing

reverting to 1.8.1 using lsup script resolves the issue.

thanks

[rperper]

This might be best handled if you could open a ticket with us. This will give us an opportunity to investigate in detail. Thanks!