[Enterprise-support] [Bug 1988227] [NEW] Removing /etc/apache2/conf-available/javascript-common.conf causes crash when upgrading from focal
Public bug reported: With apache2 and javascript-common installed, if /etc/apache2/conf- available/javascript-common.conf is deleted then the command a2enconf javascript-common will fail causing apache2 to crash when upgrading. This is similar to LP: #1986959 and its duplicates, though not the same given the symlink error stated: ERROR: /etc/apache2/conf-enabled/javascript-common.conf is a dangling symlink! To reproduce, you can run the following commands: # lxc launch images:ubuntu/focal test-apache2 # lxc exec test-apache2 bash # apt update && apt dist-upgrade -y # apt install ubuntu-release-upgrader-core apport pciutils apache2 javascript-common -y # rm /etc/apache2/conf-available/javascript-common.conf # do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: apache2 2.4.52-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 000-default.conf: Error: [Errno 40] Too many levels of symbolic links: '/etc/apache2/sites-enabled/000-default.conf' Apache2ConfdDirListing: False Apache2Modules: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message httpd (pid 3909) already running ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Aug 30 21:26:42 2022 Dmesg: ErrorMessage: installed apache2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: apache2 Title: package apache2 2.4.52-1ubuntu4.1 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-30 (0 days ago) error.log: [Tue Aug 30 21:24:00.367235 2022] [mpm_event:notice] [pid 2530:tid 140097858546752] AH00489: Apache/2.4.41 (Ubuntu) configured -- resuming normal operations [Tue Aug 30 21:24:00.367323 2022] [core:notice] [pid 2530:tid 140097858546752] AH00094: Command line: '/usr/sbin/apache2' [Tue Aug 30 21:25:24.067795 2022] [mpm_event:notice] [pid 2530:tid 140097858546752] AH00491: caught SIGTERM, shutting down [Tue Aug 30 21:25:24.101614 2022] [mpm_event:notice] [pid 3909:tid 140294896139392] AH00489: Apache/2.4.41 (Ubuntu) configured -- resuming normal operations [Tue Aug 30 21:25:24.101704 2022] [core:notice] [pid 3909:tid 140294896139392] AH00094: Command line: '/usr/sbin/apache2' ** Affects: apache2 (Ubuntu) Importance: Undecided Assignee: Lena Voytek (lvoytek) Status: In Progress ** Affects: javascript-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy ** Changed in: apache2 (Ubuntu) Status: New => In Progress ** Changed in: apache2 (Ubuntu) Assignee: (unassigned) => Lena Voytek (lvoytek) ** Also affects: javascript-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to apache2 in Ubuntu. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1988227 Title: Removing /etc/apache2/conf-available/javascript-common.conf causes crash when upgrading from focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1988227/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : enterprise-support@lists.launchpad.net Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
[Enterprise-support] [Bug 1988224] [NEW] apache stuck and child processes fail to start
Public bug reported: Since updating the LTS server version from 20.04 to 22.04, I've had problems with apache 2.4.52 (2.4.52-1ubuntu4.1) in mpm_event mode. The child processes for apache fail to start after a period of time. The webserver is unreachable. In netstat there are many CLOSE_WAIT and ESTABLISHED entries. The error_log says: [Tue Aug 30 12:59:38.451188 2022] [http2:warn] [pid 687247:tid 139925644072832] AH10291: h2_workers: cleanup, 1 idle workers did not exit after 5 seconds. # ps xau |grep apache root 899 0.0 0.4 86712 40116 ?Ss Aug25 0:33 /usr/sbin/apache2 -k start www-data 901 0.0 0.0 3736 156 ?Ss Aug25 0:15 /usr/bin/htcacheclean -d 120 -p /var/cache/apache2/mod_cache_disk -l 300M -n www-data 687242 0.0 0.3 87020 30104 ?S02:00 0:00 /usr/sbin/apache2 -k start Other processes are gone. The problem is known and already fixed in 2.4.53, see: https://bz.apache.org/bugzilla/show_bug.cgi?id=65769 I haven't found anything that this problem has already been fixed in the ubuntu version of apache. That's why I'm making this bug report. Many Thanks. ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: apache2 -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to apache2 in Ubuntu. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1988224 Title: apache stuck and child processes fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1988224/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : enterprise-support@lists.launchpad.net Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
[Enterprise-support] [Bug 1988217] [NEW] FTBFS with GCC 12
Public bug reported: squid's "upstream-test-suite" dep8 test is currently FTBFSing with GCC 12 on Kinetic: libtool: compile: g++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/etc/squid.conf\" -DDEFAULT_SQUID_DATA_DIR=\"/usr/share\" -DDEFAULT_SQUID_CONFIG_DIR=\"/etc\" -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Wshadow -Woverloaded-virtual -Werror -pipe -D_REENTRANT -I/usr/include/libxml2 -I/usr/include/p11-kit-1 -g -O2 -ffile-prefix-map=/tmp/autopkgtest.6E1e0D/build.pFL/src=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -march=native -c File.cc -fPIC -DPIC -o .libs/File.o In file included from ../../src/base/File.h:12, from File.cc:10: ../../src/sbuf/SBuf.h:48:34: error: 'template struct std::iterator' is deprecated [-Werror=deprecated-declarations] 48 | class SBufIterator : public std::iterator | ^~~~ In file included from /usr/include/c++/12/string:45, from /usr/include/c++/12/stdexcept:39, from ../../src/base/TextException.h:14, from ../../src/sbuf/SBuf.h:15: /usr/include/c++/12/bits/stl_iterator_base_types.h:127:34: note: declared here 127 | struct _GLIBCXX17_DEPRECATED iterator | ^~~~ cc1plus: all warnings being treated as errors ** Affects: squid (Ubuntu) Importance: Critical Assignee: Sergio Durigan Junior (sergiodj) Status: In Progress ** Tags: ftbfs server-todo update-excuse -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to squid in Ubuntu. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1988217 Title: FTBFS with GCC 12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1988217/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : enterprise-support@lists.launchpad.net Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
[Enterprise-support] [Bug 1988144] Re: klist not showing tgt after reboot
** Package changed: ubuntu => krb5 (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to krb5 in Ubuntu. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1988144 Title: klist not showing tgt after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1988144/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : enterprise-support@lists.launchpad.net Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
[Enterprise-support] [Bug 1988144] [NEW] klist not showing tgt after reboot
You have been subscribed to a public bug: Hello, iam not sure if this is a bug, but iam noticed a different behaviour of kinit/klist between Ubuntu 18.04 and 22.04 I already talked to sam hartman who is maintainer of krb5 packages at debian and he told that basically there is no difference between different version of kinit/klist and one should dig in Ubuntu environment. Let me decribe the notice: We use kinit/klist/krb5 keytab as base for sssd and ssh access controlled by AD. In Ubuntu 18.04 LTS i could do: "kinit myprincipal" and created a valid tgt. This tgt was stable and survived a reboot which can be viewed by "klist". I log in as unprivileged user, doing "sudo -i" and see: myhost: # klist Ticket cache: FILE:/tmp/krb5cc_27465975_uqBiyq File /tmp/krb5cc_27465975_uqBiyq is existent and owned by my unprivileged username and group domainusers. Ubuntu 18.04 LTS is using 1.16-2ubuntu0.2 of krb5-user. i have to say, that first login as unprivileged user is done by using ssh-keypair, so no sssd is involved. But by using "sudo -i" sssd is used and worked like expected. Now we switched to Ubuntu 22.04 LTS, Version of krb5-user is 1.19.2-2 Doing kinit myprincipal on 22.04 leads to: myhost: # klist Ticket cache: FILE:/tmp/krb5cc_0 File /tmp/krb5cc_0 is owned by root:root After reboot i can still login successful as unprivileged user make "sudo -i" and klist says: myhost: # klist klist: No credentials cache found (filename: /tmp/krb5cc_0 File /tmp/krb5cc_0 is gone (deleted from unknown), but i see a file /tmp/krb5cc_27465975_nGySkP which is owned by my unprivileged username and group is domainusers. is this expected? It seems that newer klist always wants to use the default name /tmp/krb5cc_0. It creates tgt with this name and tries to read this filename. but after reboot file is recreated with different name and default klist command fails. First login as unprivilged user was done with ssh-keypair without sssd, but "sudo -i" uses sssd agin. Whole thing only works like in 18.04 if you dont use ssh-keypairs and do all logins by hand with manually login, so sssd is forced to use in every step. What do you think? Is this a bug or wrong use? Behaviour of 18.04 was absolutely satisfying. Thanks, Hans ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- klist not showing tgt after reboot https://bugs.launchpad.net/bugs/1988144 You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to krb5 in Ubuntu. -- Mailing list: https://launchpad.net/~enterprise-support Post to : enterprise-support@lists.launchpad.net Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
