LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Trouble after upgradepkg httpd in Slackware 14.2 (https://www.linuxquestions.org/questions/slackware-14/trouble-after-upgradepkg-httpd-in-slackware-14-2-a-4175634436/)

Mig21 07-19-2018 07:18 AM

Trouble after upgradepkg httpd in Slackware 14.2
 
I just did the security upgrade for the latest Slackware and after that Apache failed to restart. I got this in its error_log:

[Thu Jul 19 08:13:10.395352 2018] [mpm_event:notice] [pid 27081:tid 139640228599680] AH00494: SIGHUP received. Attempting to restart
httpd: Syntax error on line 149 of /etc/httpd/httpd.conf: Cannot load lib64/httpd/modules/mod_mpm_event.so into server: /usr/lib64/httpd/modules/mod_mpm_event.so: undefined symbol: ap_queue_info_wait_for_idler

Seems like maybe the new version of apache required a newer version of APR which should have been but wasn't updated at the same time.

Does anyone have a quick solution for this? I guess I'll attempt a downgrade as an emergency fix.

Mig21 07-19-2018 07:21 AM

For now I downloaded https://mirrors.slackware.com/slackw...0-x86_64-1.txz and did an upgradepkg with it. Seems to be running ok.

petslack 07-19-2018 10:59 AM

Hi Mig21,

Try to use the httpd version from 14.2 repo with slackpkg upgrade httpd, it has version 2.4.34 and some bugfixes as well.
After that issue a httpd -V to check APR version matches or try to disable mpm-event module in httpd.conf if you don't need it.

Mig21 07-19-2018 01:23 PM

I'd rather not start using slackpkg, I'm generally quite happy with Slackware's lack of a fancy package management system.

bassmadrigal 07-19-2018 01:47 PM

Did you just upgrade apache or have you upgraded all the packages that are in patches/? It is possible that apache would crap out if it relies on a newer version of a program that you don't have installed.

If you did install all the new patches, did you check for a /etc/httpd/httpd.conf.new file? If this is there, it means that the conf file included in the new package doesn't match your existing one. That could be because you modified the conf file, but it could also mean that Pat or upstream did. If you do have it, it'd be wise to run a diff on it and make any changes that are necessary.

While I know you said you don't want to use slackpkg, it does have a handy search for new config files. You can simply run slackpkg new-config and it will look for any .new files and will present you options on what to do. I always select prompt and then look at the diff of each one. If it seems like it is just upstream changes, I'll tell slackpkg to overwrite it, but if it's just my changes, I'll tell slackpkg to discard the new one. If there's upstream changes along with my own changes, I'll make a note of the file, tell slackpkg to ignore it, and manually change it.

ponce 07-19-2018 01:48 PM

FWIW I updated httpd to 2.4.34 on slackware64-14.2 together with the rest on the stuff in /patches and it seems to start fine with the default configuration

Code:

# httpd -V
Server version: Apache/2.4.34 (Unix)
Server built:  Jul 18 2018 17:16:51
Server's Module Magic Number: 20120211:79
Server loaded:  APR 1.5.2, APR-UTIL 1.5.4
Compiled using: APR 1.5.2, APR-UTIL 1.5.4
Architecture:  64-bit
Server MPM:    event
  threaded:    yes (fixed thread count)
    forked:    yes (variable process count)
Server compiled with....
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=256
 -D HTTPD_ROOT="/usr"
 -D SUEXEC_BIN="/usr/bin/suexec"
 -D DEFAULT_PIDLOG="/var/run/httpd.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="/etc/httpd/mime.types"
 -D SERVER_CONFIG_FILE="/etc/httpd/httpd.conf"
# httpd -M               
Loaded Modules:
 core_module (static)
 so_module (static)
 http_module (static)
 mpm_event_module (shared)
 authn_file_module (shared)
 authn_core_module (shared)
 authz_host_module (shared)
 authz_groupfile_module (shared)
 authz_user_module (shared)
 authz_core_module (shared)
 access_compat_module (shared)
 auth_basic_module (shared)
 reqtimeout_module (shared)
 filter_module (shared)
 mime_module (shared)
 log_config_module (shared)
 env_module (shared)
 headers_module (shared)
 setenvif_module (shared)
 version_module (shared)
 unixd_module (shared)
 status_module (shared)
 autoindex_module (shared)
 dir_module (shared)
 alias_module (shared)


petslack 07-19-2018 03:16 PM

Quote:

Originally Posted by Mig21 (Post 5881260)
I'd rather not start using slackpkg, I'm generally quite happy with Slackware's lack of a fancy package management system.

So just download and upgrade to the latest patch for httpd from the mirror and be happy. :)
https://mirrors.slackware.com/slackw..._slack14.2.txz


All times are GMT -5. The time now is 07:33 AM.