Saturday morning I started a series of updates on my only -current system. In addition to all of the slackware packages (except X and a few other superfluous packages, which are not installed), I updated Nextcloud from 17 to 18.0.1. After all that, the Apache error_log during startup shows it is missing php libraries curl, mbstring and wddx. In addition, it reports the Imagick is compiled against Image Magick 1801, but 1802 is installed. The end result is that the Nextcloud server is running and can be accessed from a desktop, but none of the mobile devices can access it. They all get 503 errors.

Are there more updates for these in the pipeline, or how do I get these onto this server?

As have been said countless times, please report issues about a full Slackware installation, after having applied all available updates. The superfluous packages won't bite you but that will save a lot of time for people trying to help.

4 members found this post helpful.

In the 27 years since I first used Slackware to replace SLS, I have never done a full install. There is simply too much flotsam and jetsam there to waste my limited time and resources on. I know that this distribution has been going downhill lately, particularly with the recent switch to a toy database engine. But if you really can't even include all of the relevant components within each package, then perhaps it is time for me to take another look at some of the BSD distributions.

1 members found this post helpful.

actually it's just you that decided deliberately to switch to current instead of upgrading just php and if you don't know how to handle the continuos update cycle of the developing version of Slackware (*not* a rolling release) maybe you better have stayed with stable...

good luck!

2 members found this post helpful.

With a full install, you would not not be wasting your, and our time.
What toy database engine? Slackwareswitched nothing.

I think your issues are easily resolved by inspecting missing libraries and installing the required packages. That has not changed in 27 years.

1 members found this post helpful.

Have you made sure to install (or to port the changes from) any .new config files in httpd or php? That's that I'd look into first. I suspect that's at least part of the problem since you mention wddx, which is no longer an included extension, *and* is no longer listed in php.ini.

2 members found this post helpful.

One Apache startup error with PHP in -current seems to be:

"httpd: Syntax error on line 522 of /etc/http/httpd.conf: Syntax error on line 6 of /etc/httpd/mod_php.conf: cannot load lib64 lib64/httpd/modules/libphp5.so into server: /usr/lib64/httpd/modules/libphp5.so: cannot load shared object file: No such file or directory"

The library in -current's /usr/lib64/httpd/modules is libphp7.so

I don't know if this accounts for any other issues. I don't really use Apache: I just fired it up because I needed it for a SQL training course.

Did you ever run slackpkg new-config after upgrading to -current? This just looks to be that you're still loading the mod_php.conf file from 14.2 and there's a good chance you have /etc/httpd/mod_php.conf.new sitting there that has the correct library name.

Ah, thanks. Exactly the issue: the mod_php.conf dated from the end of 2015. Now it all runs.

Looks like SQL is not the only thing I get to have training in today.