[Bug 1788459] Re: gssproxy in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
** Also affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Also affects: libselinux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gssproxy in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd + gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788459] [NEW] gssproxy in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Public bug reported: I have apache configured to perform a kerberized NFS4 mount using rpc.gssd and gssproxy. If I request a web page that requires NFS4 access, then gssproxy crashes, reporting a segfault in libselinux.so.1 and the web request generates a 403 error. gssproxy[6267]: segfault at 0 ip 7f2f5bb1951a sp 7ffe861da150 error 4 in libselinux.so.1[7f2f5bb0d000+25000] If I run gssproxy at debug level = 3, and then load a web page, I can see the uid/principal request for www-data come in from rpc.gssd: # gssproxy -d --debug-level=3 -i -C /etc/gssproxy [2018/08/22 17:51:40]: Debug Enabled (level: 3) [2018/08/22 17:52:06]: Client [2018/08/22 17:52:06]: (/usr/sbin/rpc.gssd) [2018/08/22 17:52:06]: connected (fd = 10)[2018/08/22 17:52:06]: (pid = 4548) (uid = 33) (gid = 33)Segmentation fault (core dumped) Since gssproxy is required to initiate kerberos principals for any local application services - Ubuntu 18.04 does not currently support running application services with NFS4 kerberos dependencies. This has a fairly significant impact on anyone attempting to implement kerberos on Ubuntu 18.04 Ubuntu 18.04.1 LTS gssproxy 0.8.0-1 libselinux1:amd64 2.7-2build2 libgssrpc4:amd64 1.16-2build1 ** Affects: gssproxy (Ubuntu) Importance: Undecided Status: New ** Tags: kerberos nfs4 security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787429] Re: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155
>From the logs the kernel bug seems to be affecting JAVA rather than tomcat7 itself. We also have the same problem occurring with our JetBrains License Server crashed this morning - generating the same kernel errors. JetBrains has a commercial JAVA web application service, not tomcat7, and it is configured to run with Oracle Java 1.8.0. Our tomcat7 instances are running with the Ubuntu package for OpenJDK 1.7.0_181 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787429 Title: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787429] Re: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155
I have completed the apport-collect, and attached some kernel logs, changing status to confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787429 Title: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787429] Re: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155
Restarted rolling back to 3.13.0-153-generic and tomcat7 starts fine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787429 Title: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787429] Re: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155
Bug is reproduceable here - affected all of our tomcat7 instances running on trusty... tomcat7 crashes silently without logging anything, but the kernel logs show the following: Aug 16 04:13:38 tomcat1 kernel: [ 33.596382] java: Corrupted page table at address 7f499768d000 Aug 16 04:13:38 tomcat1 kernel: [ 33.597926] PGD 8000baaad067 PUD b7171067 PMD b7122067 PTE 80003e17c225 Aug 16 04:13:38 tomcat1 kernel: [ 33.599259] Bad pagetable: 000d [#1] SMP Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] Modules linked in: nfsv3 nfsv4 ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables cirrus ttm drm_kms_helper drm syscopyarea sysfillrect sysimgblt i2c_piix4 kvm_intel kvm serio_raw mac_hid lp parport nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache nls_utf8 isofs 8139too psmouse 8139cp floppy e1000 mii pata_acpi Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] CPU: 2 PID: 2097 Comm: java Not tainted 3.13.0-155-generic #205-Ubuntu Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] task: 880138af ti: 880035472000 task.ti: 880035472000 Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] RIP: 0033:[<7f498d06baba>] [<7f498d06baba>] 0x7f498d06baba Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] RSP: 002b:7f499767d398 EFLAGS: 00010206 Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] RAX: 0003 RBX: 0007f0006ce0 RCX: 0007301b2860 Aug 16 04:13:38 tomcat1 kernel: [ 33.600313] RDX: 4051 RSI: 0007301b2860 RDI: 7f499000a800 Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] RBP: 7f499767d3f8 R08: R09: 0017 Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] R10: 7f499684f9e0 R11: e603650f R12: Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] R13: 7f499767d3b0 R14: 7f499767d418 R15: 7f499000a800 Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] FS: 7f4997680700() GS:88013fd0() knlGS: Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] CS: 0010 DS: ES: CR0: 80050033 Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] CR2: 7f499768d000 CR3: 35666000 CR4: 0670 Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] RIP [<7f498d06baba>] 0x7f498d06baba Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] RSP <7f499767d398> Aug 16 04:13:38 tomcat1 kernel: [ 33.617526] ---[ end trace af21bf1ea2985973 ]--- Aug 16 04:13:38 tomcat1 kernel: [ 33.646647] BUG: Bad page map in process java pte:80003e17c225 pmd:b7122067 Aug 16 04:13:38 tomcat1 kernel: [ 33.648392] addr:7f499768d000 vm_flags:0871 anon_vma: (null) mapping: (null) index:7f499768d Aug 16 04:13:38 tomcat1 kernel: [ 33.648400] CPU: 1 PID: 2111 Comm: java Tainted: G D 3.13.0-155-generic #205-Ubuntu Aug 16 04:13:38 tomcat1 kernel: [ 33.648404] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Aug 16 04:13:38 tomcat1 kernel: [ 33.648410] 8800356f1a98 8173983f 7f499768d000 Aug 16 04:13:38 tomcat1 kernel: [ 33.648412] 8801357ef0c0 8800356f1ae8 8117e374 80003e17c225 Aug 16 04:13:38 tomcat1 kernel: [ 33.648415] b7122067 0007f499768d 8800b7122468 8800356f1c58 Aug 16 04:13:38 tomcat1 kernel: [ 33.648416] Call Trace: Aug 16 04:13:38 tomcat1 kernel: [ 33.648432] [] dump_stack+0x64/0x80 Aug 16 04:13:38 tomcat1 kernel: [ 33.648459] [] print_bad_pte+0x1a4/0x250 Aug 16 04:13:38 tomcat1 kernel: [ 33.648468] [] vm_normal_page+0x6e/0x80 Aug 16 04:13:38 tomcat1 kernel: [ 33.648476] [] unmap_page_range+0x3e6/0x830 Aug 16 04:13:38 tomcat1 kernel: [ 33.648487] [] unmap_single_vma+0x81/0xf0 Aug 16 04:13:38 tomcat1 kernel: [ 33.648494] [] unmap_vmas+0x49/0x90 Aug 16 04:13:38 tomcat1 kernel: [ 33.648504] [] exit_mmap+0x9c/0x170 Aug 16 04:13:38 tomcat1 kernel: [ 33.648519] [] ? __delayacct_add_tsk+0x153/0x170 Aug 16 04:13:38 tomcat1 kernel: [ 33.648535] [] mmput+0x5c/0x120 Aug 16 04:13:38 tomcat1 kernel: [ 33.648541] [] do_exit+0x264/0xa60 Aug 16 04:13:38 tomcat1 kernel: [ 33.648546] [] ? hrtimer_cancel+0x1a/0x30 Aug 16 04:13:38 tomcat1 kernel: [ 33.648561] [] ? futex_wait+0x1b2/0x290 Aug 16 04:13:38 tomcat1 kernel: [ 33.648568] [] do_group_exit+0x3f/0xb0 Aug 16 04:13:38 tomcat1 kernel: [ 33.648580] [] get_signal_to_deliver+0x1d0/0x700 Aug 16 04:13:38 tomcat1 kernel: [ 33.648599] [] do_signal+0x48/0xa30 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787429 Title: Tomcat 7.0.52-1ubuntu0.15 not start with Kernel 3.13.0-155 To manage
[Bug 1687267] Re: kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
Sequence of events: 1) Firefox freezes. 2) Tries to force close firefox in KDE 3) Window freezes 4) Tries to kill FF using pkill 5) Does not know pkill's commands so tries to open man pkill 6) man freezes inside of terminal emulator 7) Whole system freezes. Keyboard lights do not toggle, no disk activity, can not switch to other consoles using Ctr + Alt + F1 8) Force reset of system. kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129! invalid opcode: [#1] SMP Modules linked in: bnep binfmt_misc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass joydev input_leds crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic pcbc aesni_intel snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep aes_x86_64 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi hci_uart shpchp snd_seq snd_seq_device snd_timer snd mei_me crypto_simd intel_pch_thermal soundcore btbcm mei glue_helper cryptd btqca btintel intel_cstate bluetooth intel_rapl_perf acpi_als kfifo_buf industrialio mac_hid acpi_pad intel_lpss_acpi intel_lpss parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mxm_wmi i915 i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt ptp fb_sys_fops pps_core drm ahci libahci wmi i2c_hid video pinctrl_sunrisepoint hid pinctrl_intel fjes CPU: 1 PID: 12522 Comm: firefox Not tainted 4.10.0-20-generic #22-Ubuntu Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, BIOS P1.00 07/01/2015 task: 8b7a27681700 task.stack: a5aa46ea4000 RIP: 0010:__migration_entry_wait+0x16a/0x180 RSP: :a5aa46ea7d68 EFLAGS: 00010246 RAX: 0017c0048078 RBX: f66e08999ab0 RCX: f66e08999ab0 RDX: 0001 RSI: 8b7a2666a008 RDI: f66e06618040 RBP: a5aa46ea7d80 R08: 8b7c53513e00 R09: 8b7c53513e00 R10: 7f3b6d400119 R11: 0206 R12: f66e06618040 R13: 3e198601 R14: a5aa46ea7e30 R15: 8b7a27a9d708 FS: 7f3b6e7be740() GS:8b7c6ec4() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f3b03001588 CR3: 000227afb000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: migration_entry_wait+0x74/0x80 do_swap_page+0x5b3/0x770 ? futex_wake+0x90/0x170 handle_mm_fault+0x873/0x1360 __do_page_fault+0x23e/0x4e0 do_page_fault+0x22/0x30 page_fault+0x28/0x30 RIP: 0033:0x5578da41de4b RSP: 002b:7ffe5edb51a0 EFLAGS: 00010246 RAX: 7f3b05701688 RBX: 7f3b6d400118 RCX: 7f3b03001580 RDX: 7f3b02601790 RSI: 7f3b05801790 RDI: 7f3b02601790 RBP: 7f3b02601790 R08: 6000 R09: 7f3b04300710 R10: 7f3b6d400119 R11: 0206 R12: 7f3b6d400110 R13: 7f3b6d400118 R14: 7f3b05801790 R15: 7f3b04300350 Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb RIP: __migration_entry_wait+0x16a/0x180 RSP: a5aa46ea7d68 ---[ end trace c3166351e2a21ab7 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687267 Title: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301015] Re: Networking does not restart
The other serious technical issue is that with networking restart no longer supported either an init.d or upstart, there is no way to address automated restarting any of the dependent network services that would normally be restarted as a group (like nfs). Any automated build process is going to need to deal with configuration of not only the interface devices (ifup/ifdown), but also the restart of dependent network services to ensure that they are all updated with configuration changes (that's the whole purpose of init.d, upstart and systemd - to control the management and boot order of services and network dependencies, including the restarting of them). I understand that Ubuntu is moving to systemd in future releases, but that isn't available in any of their current LTS releases and enterprise environments cannot move major infrastructure to another OS release that only has a 9 month support window. Ubuntu 14.04 LTS is going to be the major OS release used in enterprise environments till April 2019 - networking can't be left unsupported in both init.d and upstart until 16.04 comes out. With 10.04 LTS EOL shortly, this needs to be addressed rather than forcing enterprise institutions to update only to 12.04 LTS which expires in 2 years. Please escalate this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301015 Title: Networking does not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301015] Re: Networking does not restart
I would like to officially request escalation of this issue up to next
level of Ubuntu support - it is currently listed as confirmed, high
and unassigned. Ubuntu 10.04 LTS is very soon EOL, and this
functional requirement is currently removed from the current LTS version
with no migration path in place.
It has been flagged as a hot item for over a year and seems to be
being ignored by Ubuntu development staff for what seems to be
ideological reasons.
/etc/init.d/networking has been an essential method for anyone doing
large scale headless server deployments to generically handle scripted
network management of physical and virtual servers. In these
environments, individual hosts could have completely different network
interfaces on every individual machine. Anyone, in this case also
includes the authors of officially deployed deb application packages
delivered with Ubuntu 14.04 that currently don't work...
This bug breaks cloud deployments of Ubuntu in Opennebula as delivered
natively in deb's with Ubuntu 14.04. The network contextualization
scripts delivered in opennebula-context_4.2.0-2_all.deb use service
networking to dynamically assign virtual machines IP addresses on the
fly at boot time.Without a fix, no Ubuntu 14.04 VM's running in an
Opennebula Cloud can get an IP addresses - this has been the case since
the OS version was released.
How many other network related applications are impacted by this change
that were never tested for removal of this functionality?
As an organization that is focused on supporting virtualization and
cloud server infrastructure (as opposed to only GUI desktops and
phones), I would have expected development staff to have a better
understanding of the impact of this type of issue and would have given
it more attention than it has - or at least develop alternate
functionality that meets the same functional requirements.
#last lines of /etc/one-context.d/00-network as delivered in Ubuntu 14.04
opennebula-context_4.2.0-2_all.deb
# ifup/down eth0 won't work - the virtual machine can have any number of
dynamically assigned
# interfaces at boot time
...
configure_network()
{
gen_network_configuration /etc/network/interfaces
service networking stop
sleep 1
service networking start
sleep 2
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301015
Title:
Networking does not restart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301015] Re: Networking does not restart
ifdown/ifup requires that every interface be detected before hand and restarted individually on multi-homed hosts and hypervisors. For hypervisors in a cloud environment this includes virtual bridges as well. The init script method available till this release of the OS allowed restarting all interfaces and bridges on any host via a single command remotely. With this change, now each machine may need a different network shutdown/startup/restart process unique to its particular configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301015 Title: Networking does not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312366] [NEW] package cfengine2 2.2.10-4build2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: attempted to perform a do-release-upgrade to get to trusty eventually, going from 10.04 to precise when upgrade fails on cfengine2. Attempted to continue upgrading to trusty and that fails as well because of cfengine2. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: cfengine2 2.2.10-4build2 ProcVersionSignature: Ubuntu 2.6.32-33.72-server 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-server x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Thu Apr 24 11:39:43 2014 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu-Server 10.04.3 LTS Lucid Lynx - Release amd64 (20110719.2) MarkForUpload: True SourcePackage: cfengine2 Title: package cfengine2 2.2.10-4build2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2014-04-24 (0 days ago) ** Affects: cfengine2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312366 Title: package cfengine2 2.2.10-4build2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1312366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
