[Bug 1454887] Re: package clamav-milter 0.98.7+dfsg-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
HOJE, 29.08.2015, às 22h., quando reiniciando o computador porque ele simplesmente pára, aconteceu mensagem: - - - - - - - - - - - - - - - - Relatório de erros Desculpe, ocorreu um problema durante a instalação do programa. Pacote: clamav-milter 0.98.7+dfsg-0ubuntu0.14.04.1 ^ Envie um relatório de erros para ajudar a corrigir este problema - - - - - - - - - - - - - - - - ANTES, às 21h45 aproximadamente, quando realizando uma atualização pelo Atualizador de Programas, versão 1:0.196.13, em determinado momento ele apresentou mensagem: - - - - - - - - - - - - - - - - Atualizador de programas Falha na operação do pacote A instalação ou remoção de pacote de software falhou. - - - - - - - - - - - - - - - - Favor retornar para mim: "edgardo.pr...@gmail.com" (ex= "eprado"cpovo.net") -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1454887 Title: package clamav-milter 0.98.7+dfsg-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1454887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 59695] Re: High frequency of load/unload cycles on some hard disks may shorten lifetime
For me, it's that the OS leaves insane hardware mfr defaults of hdparm -B=128 in place even on AC power. I believe this was fixed in 12.04 but is back for some reason in 14.04 for me... Installing TLP changes to B=254 on AC and retains the B=128 on battery (with the addition of clustering hdd writes to help prevent excessive disk activity and thus load/unload cycles), so provides essentially the same fix with added benefits of actual power saving on battery ethan “A society grows great when its elders plant trees whose shade they know they shall never sit in.” -- an ironic Greek proverb On Sat, Aug 29, 2015 at 6:48 AM, Nick B. wrote: > What is your test case? Are you sure this is the same bug? > > On Friday, August 28, 2015 01:21:14 AM Aaahh Ahh wrote: > > Back at it in Ubuntu 15.10 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/59695 > > Title: > High frequency of load/unload cycles on some hard disks may shorten > lifetime > > Status in acpi-support: > Invalid > Status in acpi-support package in Ubuntu: > Fix Released > Status in linux-meta package in Ubuntu: > Invalid > Status in pm-utils package in Ubuntu: > Fix Released > Status in acpi-support source package in Hardy: > Fix Released > Status in linux-meta source package in Hardy: > Invalid > Status in pm-utils source package in Hardy: > Fix Released > Status in acpi-support source package in Intrepid: > Fix Released > Status in linux-meta source package in Intrepid: > Invalid > Status in pm-utils source package in Intrepid: > Fix Released > Status in acpi-support source package in Jaunty: > Fix Released > Status in linux-meta source package in Jaunty: > Invalid > Status in pm-utils source package in Jaunty: > Fix Released > Status in acpi-support package in Baltix: > Fix Released > Status in acpi-support package in Debian: > Fix Released > Status in pm-utils package in Fedora: > Invalid > Status in laptop-mode-tools package in Mandriva: > Unknown > Status in Suse: > Fix Released > > Bug description: > The kernel wiki gathers info about drives with too aggressive power > saving defaults. A script called "storage-fixup" is also available. > > https://ata.wiki.kernel.org/index.php/Known_issues#Drives_which_perform_frequent_head_unloads_under_Linux > > > This is not a support forum. Please do not use it as such (even though > it has been used as such already). > > You can scan through the bug for links to the Ubuntu forums where > many, many different questions have been asked, answered, and re- > answered. The temporary workaround is just below. > > See https://wiki.ubuntu.com/PowerManagement for an overview about what > is involved and for a remedy. > > SRU justification: current behavior may lead to premature disk failure > in laptops due to excessive unnecessary drive parking. Fix will > disable disk cycling by default when on AC power, by correcting an > error in the hdparm logic of acpi-support. > > For jaunty, this issue is addressed in acpi-support 0.115. > > TEST CASE: > > 1. With acpi-support 0.109 (hardy) or 0.114 (intrepid) installed and > laptop-mode *not* enabled in either /etc/default/laptop-mode or > /etc/default/acpi-support, monitor the load cycle count of your hard drive > by running 'sudo smartctl -a /dev/sda|grep Load_Cycle_Count' over an > interval of several minutes, and observe that it is incrementing. (If it > does not increment, your hard drive's manufacturer defaults are sane and > you are not affected by this problem.) > 2. install acpi-support from hardy-proposed or intrepid-proposed > 3. while connected to AC power, monitor 'sudo smartctl -a /dev/sda|grep > Load_Cycle_Count' again to confirm that the number is no longer incrementing > 4. (assuming that the system is a laptop:) disconnect the system from AC > power, and confirm that the number is incrementing again > 5. enable laptop mode by setting ENABLE_LAPTOP_MODE=true in > /etc/default/laptop-mode and running 'sudo /etc/init.d/laptop-mode restart' > 6. reconnect the system to AC power and confirm that the > Load_Cycle_Count stops incrementing. > 7. suspend and resume the system and confirm that the Load_Cycle_Count > is still not incrementing. > > REGRESSION POTENTIAL: > > As this patch causes "hdparm -B 128" and "hdparm -B 254" to be invoked > automatically on systems where it was not being run before, there is > some risk that this change will have a measurable impact on the disk > throughput, power consumption, and temperature of some hard drives. > Nevertheless, it is believed that these APM power settings are the > sensible default settings for the vast majority of hard drives and > that the current behavior poses a significant risk to the longevity of > hard drives used in a wide range of laptop models, so this update > should only be blocked if it results in confirmed hardware
Re: [Bug 1486865] Re: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main)
Mathieu Trudel-Lapierre wrote: > Having a new rrdtool and not lagging behind would be good, I think. I'll > complete the bug on Monday when I am back home, we just need to list things > from the upstream ChangeLog. Here it is: RRDtool 1.5.4 - 2015-08-09 == Bug Fixes - * parse floating point numbers according to C locale in rrdtool create arguments, regardles of the systems locale setting. * include missing rrd_rados.h into distribution archive * make rrdtool work on ARM again * make rrdtool test suit pass on 32bit OSs * fix --grid-dash option regression in graph * fix systemd support * fix link dependency for libpng since we are using functions directly * fix python modulename * fix rrdtool tune to accept U in minimum and maximum options * fi * rrd_parsetime now uses a mutex lock to become threadsafe * rrd_xport is now threadsafe * stop using MAX_PATH and make everything dynamic and make rrdtool work on Gnu HURD ... thanks nirgal! Features * new RPN operators: STEPWIDTH, NEWDAY, NEWWEEK, NEWMONTH and NEWWEEK together they allow to draw graphs where a rate is converted back to absolute numbers and accumulated over a periode. RRDtool 1.5.3 - 2015-04-30 == Bug Fixes - * Brought commmand-line options and documentation back into sync. * Make LINE dashes option work again RRDtool 1.5.2 - 2015-04-23 == Bug Fixes - * paramters in VDEF are vnames and not data source names, hence they can be 255 chars long and not only 20 RRDtool 1.5.1 - 2015-04-22 == Bug Fixes - * parse numbers up to 40 characters long .. * fix install rules for Python and Lua * include missing VERSION and LICENSE file * unlink before rename in rrd_create when running on WIN32 RRDtool 1.5.0 - 2015-04-16 == New Features * automatic x-axis labels that work from 1s to 30y on a single chart * librados integration * new datasource types: DCOUNTER and DDERIVE (they work the same as the original DS, except that they can deal with floatingpoint numbers). * compile without graphics libraries: ./configure --disable-rrd_graph * updated windows port (see WIN32-BUILD-TIPS.txt) * single step RRAs for MIN,MAX,LAST are generated virtually from an AVERAGE RRA * ignore updates in the past with rrdtool update --skip-past-updates * ignore a LINE when scaling a chart using the skipscale option * detect 32bit timeoverflows * massive performance boost for charts with more than 100 DEF line by switching form a linear search to a HASH when searching for data * improved cross compilation support * .Net bindings * allow rrdtool graph to silently skip non-existing source files using the --use-nan-for-all-missing-data option * restore from a pipe (rrdtool restore - y.rrd) * in rrdtool create, row count and step can be defined in absolute time * all new "create on steroids" can pull both data and configuration from existing rrd files * use rrdtool graph to chart arbitrary data via a callback function for data fetching support is integrated in the perl bindings. * re-written parser for rrdtool graph commands. It now follows a simple key value pattern, compatible with the previous syntax. * MEDIAN op for CDEF expressions * DEPTH,INDEX,COPY,ROL ops for CDEF (as seen in PostScript) * gradient AREA backgrounds * no more locale magic while reading numeric data. Bugfixes all the bugs fixed in 1.4.x during 1.5 development RRDtool 1.4.9 - 2014-09-29 == New Features * allows rrdrestore to read input from stdin * add documentation for RRDs::xport * RPN operators MINNAN and MAXNAN * --left-axis-format option to rrd_graph Bugfixes * properly verify validity of user suplied format strings * remove graph functions from python module when compiled without graphing support * verify that only short integers are used in COMPUTE rpn expressions * eliminate duplicate setlocale calls * fixed endless loop and double frees in rrd_restore * fixed missing variable initializations in rrd_graph * fixed JSON output format to actually be valid JSON * detect failing fallocate and fall back to seeking * fixed format string in ruby bindings -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rrdtool in Ubuntu. https://bugs.launchpad.net/bugs/1486865 Title: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rrdtool/+bug/1486865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1489675] Re: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build [error: ‘new_sync_read’ undeclared here (not in a function)]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: open-vm-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1489675 Title: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build [error: ‘new_sync_read’ undeclared here (not in a function)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1489675/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 59695] Re: High frequency of load/unload cycles on some hard disks may shorten lifetime
What is your test case? Are you sure this is the same bug? On Friday, August 28, 2015 01:21:14 AM Aaahh Ahh wrote: > Back at it in Ubuntu 15.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/59695 Title: High frequency of load/unload cycles on some hard disks may shorten lifetime To manage notifications about this bug go to: https://bugs.launchpad.net/acpi-support/+bug/59695/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
Oh, I see... I was using OOM as an example. I this case, it appears the missing /etc/dnsmasq.conf file might be the culprit. So first start of lxc-net, dnsmasq never starts. After that, it will never start, unless a hard reboot is done. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 59695] Re: High frequency of load/unload cycles on some hard disks may shorten lifetime
Maybe installing TLP is a workaround? http://askubuntu.com/questions/285434/is-there-a-power-saving- application-similar-to-jupiter -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/59695 Title: High frequency of load/unload cycles on some hard disks may shorten lifetime To manage notifications about this bug go to: https://bugs.launchpad.net/acpi-support/+bug/59695/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
Ok, so I did some more testing. It appears that the problem isn't
specific to the dev_loss_tmo and fast_io_fail_tmo setting. This is
evidenced by the terminal log below. In multipath.conf (which we know
for certain is being read, as the created multipath map gets the correct
alias), I instruct it to use the ALUA hardware handler for all devices.
However, for some reason, this is ignored, and the EMC hardware handler
is used instead:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor ".*"
product ".*"
hardware_handler "1 alua"
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
root@ucstest-osl2:~# multipath -v 2
create: bootvolume (3600601603a71320022967e0a1f38e411) undef DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=1 status=undef
| |- 0:0:0:0 sda 8:0 undef ready running
| `- 1:0:1:0 sdd 8:48 undef ready running
`-+- policy='round-robin 0' prio=0 status=undef
|- 0:0:1:0 sdb 8:16 undef ready running
`- 1:0:0:0 sdc 8:32 undef ready running
=
This does *NOT* happen on RHEL-based distros - on those, changing the
hardware_handler in multipath.conf in this way works as expected.
So why does it use the EMC hardware_handler? Well, there's a built-in
default device section that matches the array in question. So this
appears to override my user-specified config from multipath.conf:
=
root@ucstest-osl2:~# multipathd -k'show config' | grep -B10 -A4 '1 emc'
device {
vendor "DGC"
product ".*"
product_blacklist "LUNZ"
path_grouping_policy group_by_prio
getuid_callout "/lib/udev/scsi_id --whitelisted
--device=/dev/%n"
path_selector round-robin 0
path_checker emc_clariion
checker emc_clariion
features "1 queue_if_no_path"
hardware_handler "1 emc"
prio emc
failback immediate
no_path_retry 60
}
=
If I copy the entire default device config into /etc/multipath.conf and
only change the hardware_handler setting, then it starts working:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor "DGC"
product ".*"
product_blacklist "LUNZ"
path_grouping_policy group_by_prio
getuid_callout "/lib/udev/scsi_id --whitelisted
--device=/dev/%n"
path_selector "round-robin 0"
path_checker emc_clariion
checker emc_clariion
features "1 queue_if_no_path"
hardware_handler "1 alua"
prio emc
failback immediate
no_path_retry 60
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
root@ucstest-osl2:~# multipath -v 2
create: bootvolume (3600601603a71320022967e0a1f38e411) undef DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=undef
|-+- policy='round-robin 0' prio=1 status=undef
| |- 0:0:0:0 sda 8:0 undef ready running
| `- 1:0:1:0 sdd 8:48 undef ready running
`-+- policy='round-robin 0' prio=0 status=undef
|- 0:0:1:0 sdb 8:16 undef ready running
`- 1:0:0:0 sdc 8:32 undef ready running
=
It would appear that for some reason, in order to override default
device settings in Ubuntu there must be an *exact* string match between
the user-supplied «vendor» and «product» settings. If I change e.g.
«product» in multipath.conf to ".*.*", then it starts using the built-in
defaults again, ignoring multipath.conf. I consider this behaviour very
dangerous - consider that if the admin has a working config (due to
exact matching vendor/product settings), and then the package gets
updated and extends the built-in defaults to incorporate some new model
matching the same profile/settings). At this point the admin's working
config will stop being used, possibly causing disruptive problems. I
therefore strongly suggest you figure out why it behaves differently in
Ubuntu and RHEL, and adopt the RHEL behaviour which really is the only
sensible one.
In any case, now that I know how to ensure my multipath.conf settings
are being used, I re-tried adding dev_loss_tmo and fast_io_fail_tmo, but
it still doesn't work:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor "DGC"
product ".*"
product_blacklist "LUNZ"
path_grouping_policy group_by_prio
getuid_callout "/lib/udev/scsi_id --whitelisted
--device=/dev/%n"
path_selector "round-robin 0"
path_checker emc_clariion
checker emc_clar
[Bug 1490110] [NEW] package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
Public bug reported: Error during do-releas-update -d from 15.04 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu7 Architecture: amd64 Date: Sat Aug 29 10:13:04 2015 DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2015-08-13 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: lxc Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1490110 Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1490110 Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
