Suma PHP 8.2.15 compatibility and install questions

44 views
Skip to first unread message

heathe...@gmail.com

unread,
Mar 22, 2024, 5:05:43 PM3/22/24
to Suma: mobile library assessment toolkit
Hi,

Is Suma compatible with PHP 8.2.15?  Our server admin asked me to try to run Suma on this version before downgrading.  I'm running into various problems with getting this running and am wondering if PHP is the issue. 

When I try to access the reports I'm getting this error:

Notice!

There was a problem generating the report. Please try again or contact your system administrator.

Error Code: 500

Error Message: cURL error 7: (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)


When I try to view our initiatives, I get this error:

PDO Exception: Syntax error or access violation: 1064 error in SQL syntax. check for the right syntax for MariaDB server to use near ')' at line 1 in /var/app/Suma/service/vendor/.shardj/zf1-future/library/Zend/Db/Statement/Pdo.php:228


Thanks,

Heather


Gavin Spomer

unread,
Mar 22, 2024, 7:05:03 PM3/22/24
to Suma: mobile library assessment toolkit
FWIT, I don't think the PHP version is the issue. I have our production version running on PHP 8.2.13 and reports are working. 

Gavin Spomer
Systems Programmer
Brooks Library
Central Washington University

heathe...@gmail.com

unread,
Apr 4, 2024, 10:33:54 AM4/4/24
to Suma: mobile library assessment toolkit
Thanks Gavin. I appreciate your feedback.

Jason Casden

unread,
Apr 8, 2024, 4:42:06 PM4/8/24
to suma-mobile-library...@googlegroups.com
Hi Heather,

This looks like an error with SQL syntax, which is strange. I noticed that you are using MariaDB--is this the same database and version that you are using in production now? I suspect that the issue is in that neck of the woods. 

Also, are you running the latest Suma version (v4.1.0)?


Thanks,
Jason

--
You received this message because you are subscribed to the Google Groups "Suma: mobile library assessment toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to suma-mobile-library-asses...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/suma-mobile-library-assessment-toolkit/49786415-772c-4bc7-a6ce-336157837ab3n%40googlegroups.com.

Gardner Treneman

unread,
Apr 29, 2024, 10:01:43 AM4/29/24
to Suma: mobile library assessment toolkit
I'm also running into the same " Error Message: cURL error 7 " when I'm trying to look at reports.
Brand new install.
If this was a SQL syntax error - where would I edit it?

Jason Casden

unread,
Apr 29, 2024, 10:43:00 AM4/29/24
to suma-mobile-library...@googlegroups.com
Interesting--thanks for reporting. First, we'll need to try to get a stack trace. Could you set `SUMA_DEBUG` to true in `web/config/config.yaml`?

You may need to modify line 26 of `service/web/index.php` as well since benign notices are currently sometimes causing problems. If you run into any issues, try changing:

$SUMA_ERROR_REPORTING  = E_ERROR | E_WARNING | E_PARSE | E_NOTICE;

to

$SUMA_ERROR_REPORTING  = E_ERROR | E_WARNING | E_PARSE;

Hopefully this will result in a more detailed error message that leads us to the actual SQL.

Thanks,
Jason

heathe...@gmail.com

unread,
Apr 29, 2024, 10:47:30 AM4/29/24
to Suma: mobile library assessment toolkit
It turns out in my case that SELinux was installed on the server and I wasn't aware of it.   

To get cURL working on our test instance, I ran: 
setsebool httpd_can_network_connect true  

httpd_can_network_connect
When disabled, this Boolean prevents HTTP scripts and modules from initiating a connection to a network or remote port. Enable this Boolean to allow this access.
but as I'm not a security expert, understand that this may be a security risk and you should do some follow-up before running this on production.  In the end, we turned off SELinux and made these servers inaccessible to outside our network.

Heather

Gardner Treneman

unread,
May 1, 2024, 3:26:51 PM5/1/24
to Suma: mobile library assessment toolkit
@Jason - I was a bit ahead of you and set SUMA_DEBUG to 'true' - hoping that would help. It didn't.
I did change the index.php line. But something I have run into when installing Suma was copies of the file in other locations? There's a index.php located:
  • /html/sumaserver/index.php
  • /Suma/service/web/index.php
  • /sumaserver/web/index.php
All of these looked exactly the same. So I changed all of them. That didn't help.

**But Heather's boolean setting for apache did the trick! Also, much like them, I am not a security person, so I'll ask my ITS folks what they think.

Reply all
Reply to author
Forward
0 new messages