Summary: | www-servers/apache-2.4.35 - Failed to set capabilities on file `/var/tmp/portage/www-servers/apache-2.4.35/image//usr/sbin/suexec' (Operation not supported) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | eike |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Juergen Rose
2018-09-27 10:41:35 UTC
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9ee9937deef58e61f21052300c45f8cfcd7d335d commit 9ee9937deef58e61f21052300c45f8cfcd7d335d Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2018-09-27 11:15:17 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2018-09-27 11:16:54 +0000 apache-2.eclass: Work around broken AC_ARG_ENABLE logic. Bug: https://bugs.gentoo.org/667148 eclass/apache-2.eclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) The above commit only fixes the USE="suexec-caps -suexec-syslog" issue. Te underlying issue still is not fixed but will only occur with USE="suexec-caps suexec-syslog". Any chance you don't have XATTR enabled for your filesystem(s)? (In reply to Lars Wendler (Polynomial-C) from comment #2) > The above commit only fixes the USE="suexec-caps -suexec-syslog" issue. > Te underlying issue still is not fixed but will only occur with > USE="suexec-caps suexec-syslog". > Any chance you don't have XATTR enabled for your filesystem(s)? XATTR seems to be enabled for ext filesystems: root@condor:/root(28)# zgrep -i xattr /proc/config CONFIG_EXT2_FS_XATTR=y CONFIG_REISERFS_FS_XATTR=y CONFIG_TMPFS_XATTR=y # CONFIG_SQUASHFS_XATTR is not set CONFIG_CIFS_XATTR=y /var/tmp is a ext2 filesystem: root@condor:/root(29)# df -T Filesystem Type 1K-blocks Used Available Use% Mounted on none tmpfs 3530620 1788 3528832 1% /run udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 3530620 74720 3455900 3% /dev/shm /dev/md126 ext4 131980708 50516904 74736540 41% / tmpfs tmpfs 3530620 0 3530620 0% /sys/fs/cgroup /dev/sda5 ext2 23797 204 22365 1% /mnt/rescue /dev/mapper/vg1-distfiles ext2 16772008 13675304 2257844 86% /usr/local/portage/distfiles_condor /dev/mapper/vg1-src ext4 61796348 9282900 49351340 16% /usr/src_condor /dev/mapper/vg1-tmp ext2 11712068 33412 11083712 1% /tmp /dev/mapper/vg1-portage ext2 3668770 737666 2721389 22% /usr/portage_condor /dev/mapper/vg1-home ext4 528316088 479782060 21674100 96% /home /dev/mapper/vg1-var ext3 8125880 4723788 2982668 62% /var /dev/mapper/vg1-opt ext3 8125880 1099088 6607364 15% /opt /dev/mapper/vg1-vtmp ext2 33027952 16489408 14860824 53% /var/tmp /dev/mapper/vg1-ftp xfs 134152192 117840168 16312024 88% /home/ftp tmpfs tmpfs 706124 32 706092 1% /run/user/1203 tmpfs tmpfs 706124 0 706124 0% /run/user/0 But there is not any attrbut set for /var/tmp: root@condor:/root(27)# lsattr /var/tmp ------------------- /var/tmp/lost+found ------------------- /var/tmp/binpkgs ------------------- /var/tmp/alsaconf.cards ------------------- /var/tmp/cross ------------------- /var/tmp/emerge-webrsync ------------------- /var/tmp/gbrowse2 ------------------- /var/tmp/g-cpan ------------------- /var/tmp/genkernel ------------------- /var/tmp/kdecache-root ------------------- /var/tmp/kdecache-rose ------------------- /var/tmp/kdecache-rose1gqyAB ------------------- /var/tmp/kdecache-roselJECSk ------------------- /var/tmp/kdecache-roseTsrP7b ------------------- /var/tmp/kdecache-roseugizcr ------------------- /var/tmp/lmhttp.log ------------------- /var/tmp/logcheck ------------------- /var/tmp/paludis ------------------- /var/tmp/portage ------------------- /var/tmp/usb_inst.log ------------------- /var/tmp/usb_inst.tmp ------------------- /var/tmp/systemd-private-1059cf23f8f442ed9ddbb8ba2ad795c9-systemd-networkd.service-y3r3ks ------------------- /var/tmp/systemd-private-1059cf23f8f442ed9ddbb8ba2ad795c9-systemd-resolved.service-8JM3mQ ------------------- /var/tmp/systemd-private-1059cf23f8f442ed9ddbb8ba2ad795c9-clamd.service-4qrhVl ------------------- /var/tmp/tmpgxOdm6 ------------------- /var/tmp/systemd-private-1059cf23f8f442ed9ddbb8ba2ad795c9-ntpd.service-JZsDMZ ------------------- /var/tmp/systemd-private-1059cf23f8f442ed9ddbb8ba2ad795c9-colord.service-OJCTTB ------------------- /var/tmp/kdecache-rose_test ------------------- /var/tmp/kdecache-roses6GE73 On my other systems the "e" attribut is set and the filesystem is ext4. root@lynx:/root(1)# lsattr /var/tmp --------------e---- /var/tmp/lost+found --------------e---- /var/tmp/portage --------------e---- /var/tmp/systemd-private-95389bb7aa0648468282d3508569e76b-colord.service-WrwckW --------------e---- /var/tmp/genkernel --------------e---- /var/tmp/systemd-private-95389bb7aa0648468282d3508569e76b-rtkit-daemon.service-uk5GY2 --------------e---- /var/tmp/systemd-private-95389bb7aa0648468282d3508569e76b-ntpd.service-8jBkGP --------------e---- /var/tmp/systemd-private-95389bb7aa0648468282d3508569e76b-clamd.service-UNvGvv --------------e---- /var/tmp/systemd-private-95389bb7aa0648468282d3508569e76b-systemd-resolved.service-KtpNEN --------------e---- /var/tmp/systemd-private-95389bb7aa0648468282d3508569e76b-systemd-networkd.service-oeTXEH --------------e---- /var/tmp/systemd-private-95389bb7aa0648468282d3508569e76b-upower.service-el6bF4 root@lynx:/root(2)# df -T | grep /var/tmp /dev/nvme0n1p3 ext4 122569320 709364 115590672 1% /var/tmp /dev/mapper/vg-vtmp ext4 39089600 1071204 36072640 3% /mnt/backup/var/tmp If I understand this correctly the e flag is autmatically set for ext4 filesystems. Should I convert /var/tmp to ext4? After formatting /var/tmp as ext4 the issue disappeared. This still happens in my test chroot with 2.4.41 on hppa for the following build: * USE: apache2_modules_asis apache2_modules_auth_form apache2_modules_authn_anon apache2_modules_authn_dbd apache2_modules_authn_dbm apache2_modules_authz_core apache2_modules_authz_dbm apache2_modules_authz_owner apache2_modules_cache apache2_modules_dbd apache2_modules_deflate apache2_modules_dir apache2_modules_filter apache2_modules_ident apache2_modules_imagemap apache2_modules_include apache2_modules_lbmethod_byrequests apache2_modules_lbmethod_bytraffic apache2_modules_log_config apache2_modules_log_forensic apache2_modules_logio apache2_modules_mime apache2_modules_proxy apache2_modules_proxy_ajp apache2_modules_proxy_balancer apache2_modules_proxy_ftp apache2_modules_proxy_http apache2_modules_proxy_scgi apache2_modules_proxy_wstunnel apache2_modules_remoteip apach e2_modules_session apache2_modules_slotmem_shm apache2_modules_socache_shmcb apache2_modules_version apache2_modules_watchdog apache2_mpms_prefork elibc_glibc hppa kernel_linux ldap ssl static suexec suexec-caps suexec-syslog userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * * Selected MPM: prefork * * You can manipulate several configure options of suexec * through the following environment variables: * * SUEXEC_SAFEPATH: Default PATH for suexec (default: '/usr/local/bin:/usr/bin:/bin') * SUEXEC_CALLER: Name of the user Apache is running as (default: apache) * SUEXEC_DOCROOT: Directory in which suexec will run scripts (default: '/var/www') * SUEXEC_MINUID: Minimum UID, which is allowed to run scripts via suexec (default: 1000) * SUEXEC_MINGID: Minimum GID, which is allowed to run scripts via suexec (default: 100) * SUEXEC_USERDIR: User subdirectories (like /home/user/html) (default: public_html) * SUEXEC_UMASK: Umask for the suexec process (default: 077) The filesystem is like this: Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl |