[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
I got: warning: /etc/sysctl.d/README(1): invalid syntax, continuing... warning: /etc/sysctl.d/README(2): invalid syntax, continuing... warning: /etc/sysctl.d/README(3): invalid syntax, continuing... warning: /etc/sysctl.d/README(4): invalid syntax, continuing... warning: /etc/sysctl.d/README(5): invalid syntax, continuing... warning: /etc/sysctl.d/README(6): invalid syntax, continuing... warning: /etc/sysctl.d/README(8): invalid syntax, continuing... warning: /etc/sysctl.d/README(9): invalid syntax, continuing... error: "Invalid argument" setting key "kernel.modules_disabled" error: permission denied on key 'kernel.sg-big-buff' error: permission denied on key 'kernel.random.poolsize' error: permission denied on key 'kernel.random.entropy_avail' error: permission denied on key 'kernel.random.boot_id' error: permission denied on key 'kernel.random.uuid' error: permission denied on key 'kernel.ngroups_max' error: permission denied on key 'kernel.cap_last_cap' error: permission denied on key 'kernel.bootloader_type' error: permission denied on key 'kernel.bootloader_version' error: permission denied on key 'kernel.ostype' error: permission denied on key 'kernel.osrelease' error: permission denied on key 'kernel.version' error: permission denied on key 'kernel.pty.nr' error: permission denied on key 'kernel.sched_domain.cpu0.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu0.domain1.name' error: permission denied on key 'kernel.sched_domain.cpu1.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu1.domain1.name' error: permission denied on key 'kernel.sched_domain.cpu2.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu2.domain1.name' error: permission denied on key 'kernel.sched_domain.cpu3.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu3.domain1.name' error: permission denied on key 'kernel.sched_domain.cpu4.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu4.domain1.name' error: permission denied on key 'kernel.sched_domain.cpu5.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu5.domain1.name' error: permission denied on key 'kernel.sched_domain.cpu6.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu6.domain1.name' error: permission denied on key 'kernel.sched_domain.cpu7.domain0.name' error: permission denied on key 'kernel.sched_domain.cpu7.domain1.name' error: permission denied on key 'vm.nr_pdflush_threads' error: "Invalid argument" setting key "vm.drop_caches" error: "Invalid argument" setting key "vm.percpu_pagelist_fraction" error: permission denied on key 'fs.inode-nr' error: permission denied on key 'fs.inode-state' error: permission denied on key 'fs.file-nr' error: permission denied on key 'fs.dentry-state' error: permission denied on key 'fs.aio-nr' error: "Invalid argument" setting key "fs.binfmt_misc.python3/2" error: "Invalid argument" setting key "fs.binfmt_misc.python3/2" error: "Invalid argument" setting key "fs.binfmt_misc.python3/2" error: "Invalid argument" setting key "fs.binfmt_misc.python3/2" error: "Invalid argument" setting key "fs.binfmt_misc.python3/2" error: "Invalid argument" setting key "fs.binfmt_misc.wine" error: "Invalid argument" setting key "fs.binfmt_misc.wine" error: "Invalid argument" setting key "fs.binfmt_misc.wine" error: "Invalid argument" setting key "fs.binfmt_misc.wine" error: "Invalid argument" setting key "fs.binfmt_misc.wine" error: "Invalid argument" setting key "fs.binfmt_misc.jarwrapper" error: "Invalid argument" setting key "fs.binfmt_misc.jarwrapper" error: "Invalid argument" setting key "fs.binfmt_misc.jarwrapper" error: "Invalid argument" setting key "fs.binfmt_misc.jarwrapper" error: "Invalid argument" setting key "fs.binfmt_misc.jarwrapper" error: "Invalid argument" setting key "fs.binfmt_misc.jar" error: "Invalid argument" setting key "fs.binfmt_misc.jar" error: "Invalid argument" setting key "fs.binfmt_misc.jar" error: "Invalid argument" setting key "fs.binfmt_misc.jar" error: "Invalid argument" setting key "fs.binfmt_misc.jar" error: "Invalid argument" setting key "fs.binfmt_misc.cli" error: "Invalid argument" setting key "fs.binfmt_misc.cli" error: "Invalid argument" setting key "fs.binfmt_misc.cli" error: "Invalid argument" setting key "fs.binfmt_misc.cli" error: "Invalid argument" setting key "fs.binfmt_misc.cli" error: "Invalid argument" setting key "fs.binfmt_misc.python2/7" error: "Invalid argument" setting key "fs.binfmt_misc.python2/7" error: "Invalid argument" setting key "fs.binfmt_misc.python2/7" error: "Invalid argument" setting key "fs.binfmt_misc.python2/7" error: "Invalid argument" setting key "fs.binfmt_misc.python2/7" error: "Invalid argument" setting key "fs.binfmt_misc.status" error: permission denied on key 'fs.quota.lookups' error: permission denied on key 'fs.quota.drops' error: permission denied on key 'fs.quota.reads' error: permission denied on key 'fs.quota.writes' error: permission
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
I got: error: "Invalid argument" setting key "kernel.msgmnb" in my procps.log This confirmed that Scalr client was the problem in: ./sysctl.d/100-scalr.conf Commenting out the defining line solved it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
(actually /etc/sysctl.d/100-scalr.conf - can't edit) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
I don't think procps should return an error when one of the sysctl.d/ files contains incorrect data. Printing the error would be useful especially if the exact file and value is mentioned, otherwise saying "oh, we failed" when in fact only one attribute failed to load is cumbersome. Just because iscsitarget package upgrade failed to remove it's sysctl.d config file is not fair to let other packages fail upgrade because of dependency on procps which did not start but otherwise did NOT affect it in any way (munin, for example, failed to be configured by apt-get dist- upgrade because of that) Don't know if this is the proper place to address this comment to package authors, so if any of you reading this consider I've written in the wrong place please direct me to the correct site/link! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
Thanks for the hint of running the config files one at a time using for i in /etc/sysctl.d/* /etc/sysctl.conf; do echo $i;sudo sysctl -e -p "$i";done With me it gave /etc/sysctl.conf error: "Invalid argument" setting key "fs.inotify.max_user_watches" Somehow there was an extra " after the number 10 rendering the update impossible. Thanks, it works again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
(copied from my comment in bug 1247921, since this is the exact bug I had, and more people are looking at this) I ran into this today, and eventually (thanks to strace!) figured out that I had a config file that didn't end with a newline. 30-SpiderOak, like several other people, actually. So what was getting fed to sysctl was actually fs.inotify.max_user_watches = 65536fs.inotify.max_user_watches = 65536 (yes, two files in a row were setting the same value, but the first one didn't end with a newline). So sysctl opened /proc/sys/fs/inotify/max_user_watches, and wrote "65536fs.inotify.max_user_watches = 65536" to it. Then printed an error, and exited with a non-zero status, making the upstart job fail. So, biggest problem here is that the upstart job shouldn't fail if you have one bad line in one config file. warning somehow would be excellent, but I think most people would rather not have their whole package upgrade chain blocked while they sort this out. Admittedly, I probably wouldn't have noticed it at all if it hadn't blocked dpkg, and I was only ok because other lines were also setting the same key. If this had been something important for security, I might not be arguing that the upstart job should be cat | sysctl; true Printing the key value would probably be a good idea, too, that would have saved me a bunch of debugging after I found where upstart stores its scripts and logs. (I feel old for being used to good old init.d scripts that I could run manually to see their output... Hey upstart, get off of my lawn. Although honestly the format of the files in /etc/init/ is very easy to understand, I found the script portion without any trouble so I could still just run what the script was trying to do.) I tried a bunch of different inputs to sysctl, including noticing that I got no errors if I fed it the config files one at a time with for i in /etc/sysctl.d/* /etc/sysctl.conf; do echo $i;sudo sysctl -e -p "$i";done. As I said, I didn't figure out that I had a file not ending in newline until I ran cat ... | sudo sysctl -e -p - 2>&1 | less I feel like this could have been a lot easier to debug with better error messages, even leaving aside that I had to learn my way around upstart at the beginning of this. Oh, and to figure out that the procps postinst script was trying to start an upstart job called procps. I wasn't 100% sure from the error messages. (although now that I look at the invoke-rc.d line, it does say it was the procps init script.) So, bottom line, procps init script should probably not fail when the only errors are invalid values for keys. It already ignores unknown keys, with the -e option. Maybe sysctl needs an option to ignore errors of the other kind? Although if a key exists, errors assigning to it are much more likely to be a problem, so you do want to at least warn, but don't want to ignore them or trainwreck dpkg / apt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
There are a few reports from people with stuck package upgrades, some in foreign languages in case that's relevant to anyone. I would guess most of them are duplicates of this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
After another unattended update of procps has failed this morning I figured out that "net.ipv4.tcp_mem in 30-iscsitarget.conf" causes an error and prevents procps from starting - like Ryan already said. Commenting out that line is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
/30-spideroak.conf was also a problem for me. There was a newline before EOF, but I had to change fs.inotify.max_user_watches from 65536 to 65535, and then was able to install procps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
Hi, all. I had this issue today and after read this thread I "cat"ed /etc/sysctl.d/30-SpiderOak.conf and I discovered that this file has no new line at the end. Just added a new line and then the upgrade worked ok. I deinstalled Spider Oak a time ago, so I think I can remove this file. I'm using elementaryOS: uname -a Linux jdelacamara-POSITIVO-BGH 3.2.0-55-generic #85-Ubuntu SMP Wed Oct 2 12:29:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
I also got burned by this with net.ipv4.tcp_mem in 30-iscsitarget.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
same solution here. in upstart/procps.log had error: "Invalid argument" setting key "fs.inotify.max_user_watches" which is the only entry in 30-spideroak.conf Thanks to all. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
I had the same as Vincent /etc/sysctl.d/30-spideroak.conf it did not have a new line at the end of the file After checking all .conf files and made sure they had a new line at the end of the file, upgrade now works. Other procedures mentioned on launchpad and forums ended up working because people added a new line not by changing variables. good find Timur -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
I also had this problem. In my case, the file /etc/sysctl.d/30-spideroak.conf was no finished by a newline. After adding the newline at the end, the upgrade of 'procps' worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
When upgrading procps from 1:3.2.8-11ubuntu6 to 1:3.2.8-11ubuntu6.2, the upgrade fails with the errors similar to the ones reported above: timur@test:~$ sudo apt-get install procps=1:3.2.8-11ubuntu6.2 Reading package lists... Done Building dependency tree Reading state information... Done procps is already the newest version. The following packages were automatically installed and are no longer required: linux-headers-3.2.0-51 linux-image-3.2.0-51-virtual linux-headers-3.2.0-51-virtual Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up procps (1:3.2.8-11ubuntu6.2) ... start: Job failed to start invoke-rc.d: initscript procps, action "start" failed. dpkg: error processing procps (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: procps E: Sub-process /usr/bin/dpkg returned an error code (1) Looking at the upstart logs from procps, the error is: error: "Invalid argument" setting key "net.ipv4.tcp_keepalive_intvl" The actual entry in /etc/sysctl.d is: net.ipv4.tcp_keepalive_intvl = 10 If I place a newline before the in the file, the script parses it correctly. If other reported cases are similar, then I'm guessing the bug is not in this package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
The 6.2 update only had a fix for a container environment. But that doesn't help other cases, such as 30-iscsitarget.conf which has a setting for net.ipv4.tcp_mem. The error message is: error: "Invalid argument" setting key "net.ipv4.tcp_mem" Another system of mine had a problem with 10-kernel-hardening.conf with setting for kernel.kptr_restrict. The 6.1 update caused a "permission denied" error and procps to fail. I wasn't yet able to verify whether the recent 6.2 update solves it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: procps (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
Sorry I fixed it with moving /etc/sysctl.d/30-iscsitarget.conf of the folder and then upgrading. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
