[Bug 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
FWIW mine appears to have hung during a hidden (invisible to me) step where it was attempting to set a MOK. I had to first kill the existing dpkg, then edit /usr/sbin/update-secureboot-policy to change #!/bin/sh to #!/bin/bash (I was getting a local variable error), then manually run /usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update- secureboot-policy --enroll-key, then reboot, install the key, finish booting, and dpkg --configure -a. I have no idea if the terminal-gui app that is attempting to ask for a password for the MOK can be surfaced into the apt/dpkg configurating process, but that seems to be the missing link for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776076 Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1776076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
Hey folks, just piping in that I am also having this problem. I am on an encrypted disk, and the build of the kernel modules just hangs. Please let me know if there is anything I can provide to assist in debugging. Note that there appear to be two other related / duplicate bugs: 1769327 and 1775672. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776076 Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1776076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
I'm happy to create a new bug report for this, however before I do I wanted to follow up here first. I've been working on a bionic VM template this week and the issue has resurfaced. Client (18.04) reboots daily at 3:00 a.m., and somewhere between 30 minutes and 2 hours later, the CIFS mount point stops responding. Meanwhile other clients (16.04, and Windows) continue chugging along merrily. A reboot sometimes fixes the problem, and sometimes the problem has fixed itself by 8am when I arrive. Here's some syslog debug output after the machine finishes booting. Yesterday it cleared up on its own. Today the server is still down 10 hours later. I would blame Java, except that the whole mount point becomes non- responsive when this happens, not just for that one process. Jun 6 03:00:37 localhost systemd[1]: Reached target Multi-User System. Jun 6 03:00:37 localhost systemd[1]: Starting Execute cloud user/final scripts... Jun 6 03:00:37 localhost systemd[1]: Reached target Graphical Interface. Jun 6 03:00:37 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes... Jun 6 03:00:38 localhost systemd[1]: Started Update UTMP about System Runlevel Changes. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 running 'modules:final' at Wed, 06 Jun 2018 03:00:38 +. Up 23.72 seconds. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 finished at Wed, 06 Jun 2018 03:00:38 +. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 23.84 seconds Jun 6 03:00:38 localhost systemd[1]: Started Execute cloud user/final scripts. Jun 6 03:00:38 localhost systemd[1]: Reached target Cloud-init target. Jun 6 03:00:38 localhost systemd[1]: Startup finished in 2.806s (kernel) + 21.078s (userspace) = 23.885s. Jun 6 03:00:39 localhost kernel: [ 24.927412] TCP: ens160: Driver has suspect GRO implementation, TCP performance may be compromised. Jun 6 03:00:51 localhost systemd-timesyncd[574]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). Jun 6 03:14:28 localhost systemd[1]: Starting Message of the Day... Jun 6 03:14:30 localhost 50-motd-news[1699]: * Meltdown, Spectre and Ubuntu: What are the attack vectors, Jun 6 03:14:30 localhost 50-motd-news[1699]:how the fixes work, and everything else you need to know Jun 6 03:14:30 localhost 50-motd-news[1699]:- https://ubu.one/u2Know Jun 6 03:14:30 localhost systemd[1]: Started Message of the Day. Jun 6 03:15:48 localhost systemd[1]: Starting Cleanup of Temporary Directories... Jun 6 03:15:48 localhost systemd[1]: Started Cleanup of Temporary Directories. Jun 6 03:17:01 localhost CRON[1770]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:00:01 localhost CRON[1878]: (root) CMD (/mnt/www/config/backup_config.sh) Jun 6 04:17:01 localhost CRON[1916]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] failed to bind to LDAP server ldap://dc01.example.com: Can't contact LDAP server Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] connected to LDAP server ldap://dc02.example.com Jun 6 04:30:01 localhost CRON[1938]: (root) CMD (/usr/sbin/ntpdate time-a.nist.gov time-b.nist.gov 0.pool.ntp.org 1.pool.ntp.org) Jun 6 04:30:01 localhost CRON[1937]: (CRON) info (No MTA installed, discarding output) Jun 6 05:12:02 localhost kernel: [ 7906.798052] CIFS VFS: Server cifshost.example.com has not responded in 120 seconds. Reconnecting... Jun 6 05:12:02 localhost kernel: [ 7906.800726] CIFS VFS: Free previous auth_key.response = 3e802799 Jun 6 05:13:10 localhost kernel: [ 7975.657719] INFO: task java:1672 blocked for more than 120 seconds. Jun 6 05:13:10 localhost kernel: [ 7975.657741] Not tainted 4.15.0-22-generic #24-Ubuntu Jun 6 05:13:10 localhost kernel: [ 7975.657757] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 6 05:13:10 localhost kernel: [ 7975.657779] javaD0 1672 1 0x8000 Jun 6 05:13:10 localhost kernel: [ 7975.657781] Call Trace: Jun 6 05:13:10 localhost kernel: [ 7975.657788] __schedule+0x297/0x8b0 Jun 6 05:13:10 localhost kernel: [ 7975.657791] ? __wake_up+0x13/0x20 Jun 6 05:13:10 localhost kernel: [ 7975.657792] schedule+0x2c/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657795] io_schedule+0x16/0x40 Jun 6 05:13:10 localhost kernel: [ 7975.657798] wait_on_page_bit_common+0xd8/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657800] ? page_cache_tree_insert+0xe0/0xe0 Jun 6 05:13:10 localhost kernel: [ 7975.657801] __filemap_fdatawait_range+0xfa/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657803] filemap_write_and_wait+0x4d/0x90 Jun 6 05:13:10 localhost kernel: [ 7975.657826] cifs_flush+0x43/0x90 [cifs] Jun 6 05:13:10 localhost kernel: [ 7975.657830] filp_close+0x2f/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657832] __close_fd+0x85/0xa0 Jun 6 05:13:10 localhost
[Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
That did it for me on Xenial. root@client:~# uname -a Linux client 4.4.0-98-generic #121~lp1729337 SMP Thu Nov 2 20:53:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@client:~# mount | grep share //server/share on /mnt/share type cifs (rw,nosuid,nodev,relatime,vers=3.0,sec=ntlmssp,cache=strict,username=www-data,domain=ourdomain,uid=33,forceuid,gid=33,forcegid,addr=1.2.3.4,file_mode=0770,dir_mode=0770,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user) Interestingly, as FedeX pointed out, the option (unspecified in my fstab) of sec=ntlmssp has appeared as a new explicit parameter. Makes no difference to me, and it works, just FYI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
FWIW I can confirm that adding sec=ntlmsspi fixed our issue with 4.4.0-98. root@client:~# mount | grep share //server/share on /mnt/share type cifs (rw,nosuid,nodev,relatime,vers=3.0,sec=ntlmsspi,cache=strict,username=www-data,domain=ourdomain,uid=33,forceuid,gid=33,forcegid,addr=10.4.0.30,file_mode=0770,dir_mode=0770,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user) root@client:~# uname -a Linux client 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
Confirmed that 4.14-rc7 works fine, no error. root@cf03:~# uname -a Linux client 4.14.0-041400rc7-generic #201710292231 SMP Sun Oct 29 22:32:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@client:~# mount ... snip ... //server/share on /mnt/share type cifs (rw,nosuid,nodev,relatime,vers=3.0,cache=strict,username=www-data,domain=ourdomain,uid=33,forceuid,gid=33,forcegid,addr=1.2.3.4,file_mode=0770,dir_mode=0770,soft,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user) root@client:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
Sorry, it doesn't seem to have fixed the issue. I installed the image, extras, and both headers packages. No cloud or tools (they aren't installed in our system usually). root@client:~# uname -a Linux client 4.4.0-98-generic #121~lp1729337 SMP Wed Nov 1 14:29:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@client:~# dmesg ... snip ... [9.177979] CIFS VFS: validate protocol negotiate failed: -11 [9.178594] CIFS VFS: cifs_mount failed w/return code = -5 root@client:~# mount.cifs --verbose //server/share /mnt/share -o rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770,exec,soft,noserverino,vers=3.0 domain=ourdomain mount.cifs kernel mount options: ip=1.2.3.4,unc=\\server\share,file_mode=0770,dir_mode=0770,soft,noserverino,vers=3.0,uid=33,gid=33,user=www-data,,domain=ourdomain,pass= mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) root@client:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
@jsalisbury I've got one machine from our cluster that's not been downgraded so I can do any debugging or provide any additional information that you might need. Let me know if there's anything I can do to help. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729337] [NEW] CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
Public bug reported: We have a cluster of servers that applied a security update overnight and were unable to mount CIFS shares after upgrading to 4.4.0-98. The same machines on 4.4.0-97 were fine the night before, and are fine after downgrading. The only error message CIFS would report, even on verbose, was: [ 257.089876] CIFS VFS: validate protocol negotiate failed: -11 [ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5 Rebooting did not help. Nor did attempting to mount the share manually using mount -t cifs. Here's the offending line from our /etc/fstab (with hostnames sanitized): //server/share /mnt/share cifs rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770 ,exec,soft,noserverino,vers=3.0 0 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 1 07:56 seq crw-rw 1 root audio 116, 33 Nov 1 07:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 1 08:49:47 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1 InstallationDate: Installed on 2016-12-16 (319 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--template--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
