libapache2-mod-shib module doesn't work with 2.4.52
Bug #1974251 reported by
mesiu84
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache2 (Ubuntu) |
In Progress
|
Undecided
|
Bryce Harrington | ||
Jammy |
Incomplete
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Bryce Harrington |
Bug Description
ubuntu release: Jammy
apache version: 2.4.52-1ubuntu4
libapache2-
Apache 2.4.52 is unable to connect to shibboleth - shibd (version 3.3.0) process. Downgrade of shibboleth package (compiled from sources - 3.2.2) doesn't resolve the issue. Apache returns Error 302 each time when trying to open some webpage and in error log there is only this message:
Cannot connect to shibd process, a site adminstrator should be notified
Apache upgrade to 2.4.53 from PPA solves the problem.
Didn't found anything in apache changelog regarding that issue, but probably related to one of found bugs in 2.4.52
Related branches
~bryce/ubuntu/+source/apache2:merge-v2.4.53-2-kinetic
- Andreas Hasenack: Approve
- Canonical Server: Pending requested
- git-ubuntu import: Pending requested
-
Diff: 2824 lines (+2129/-60)10 files modifieddebian/apache2-bin.install (+1/-0)
debian/apache2-utils.ufw.profile (+14/-0)
debian/apache2.dirs (+1/-0)
debian/apache2.install (+1/-0)
debian/apache2.postrm (+2/-0)
debian/apache2.py (+48/-0)
debian/changelog (+2006/-2)
debian/control (+4/-2)
debian/index.html (+51/-56)
debian/source/include-binaries (+1/-0)
tags: | added: packaging |
Changed in apache2 (Ubuntu Jammy): | |
status: | New → Incomplete |
Changed in apache2 (Ubuntu Kinetic): | |
status: | Incomplete → In Progress |
assignee: | nobody → Bryce Harrington (bryce) |
milestone: | none → ubuntu-22.05 |
milestone: | ubuntu-22.05 → none |
To post a comment you must log in.
Thank you for providing this report and helping to make Ubuntu better. I was unable to reproduce this when trying to set up an apache webserver alongside shibd on Jammy. Would you be able to provide a list of the commands you used when setting up your system to help us debug the issue?
Thanks!