Bug#1037247: Upgrade to 2.5.5-3+deb10u5 breaks puppet-agent
Package: ruby2.5 Version: 2.5.5-3+deb10u5 After upgrading... Unpacking libruby2.5:amd64 (2.5.5-3+deb10u5) over (2.5.5-3+deb10u4) ... Unpacking ruby2.5 (2.5.5-3+deb10u5) over (2.5.5-3+deb10u4) ... ...in Debian 10 (same for i386 and amd64) puppet-agent stopped working and throws errors like Error: /File[/var/lib/puppet/locales]: Failed to generate additional resources using 'eval_generate': Failed to open TCP connection to : (Connection refused - connect(2) for "" port ) Puppet server name is set correctly in /etc/puppet/puppet.conf but empty in above error message. Downgrading both packages to 2.5.5-3+deb10u4 resolves this issue. -- Regards, Paweł Bogusławski IB Development Team E:d...@ib.pl
Bug#1027975: any_executor.hpp does not compile with -fno-rtti under gcc
Package: libboost1.74-dev Version: 1.74.0-9 Consider patching in debian package also: https://github.com/chriskohlhoff/asio/issues/533 https://github.com/manticoresoftware/manticoresearch/issues/977#issuecomment-1372125274 -- Regards, Paweł Bogusławski IB Development Team E:d...@ib.pl
Bug#1025165: No opus transcoding available after asterisk install
) 46 audio silk silk8 (SILK Codec (8 KHz)) 47 audio silk silk12 (SILK Codec (12 KHz)) 48 audio silk silk16 (SILK Codec (16 KHz)) 49 audio silk silk24 (SILK Codec (24 KHz)) 30 audio g719 g719 (ITU G.719) 36 video h263p h263p (H.263+ video) 37 video h264 h264 (H.264 video) 21 audio g729 g729 (G.729A) 11 audio slin slin (16 bit Signed Linear PCM) 12 audio slin slin12 (16 bit Signed Linear PCM (12kHz)) 13 audio slin slin16 (16 bit Signed Linear PCM (16kHz)) 14 audio slin slin24 (16 bit Signed Linear PCM (24kHz)) 15 audio slin slin32 (16 bit Signed Linear PCM (32kHz)) 16 audio slin slin44 (16 bit Signed Linear PCM (44kHz)) 17 audio slin slin48 (16 bit Signed Linear PCM (48kHz)) 18 audio slin slin96 (16 bit Signed Linear PCM (96kHz)) 19 audio slin slin192 (16 bit Signed Linear PCM (192kHz)) 5 audio ulaw ulaw (G.711 u-law) 20 audio lpc10 lpc10 (LPC10) 29 audio testlaw testlaw (G.711 test-law) 45 audio none none ( codec) 44 image t38 t38 (T.38 UDPTL Fax) 1 audio amr amr (AMR) 2 audio amrwb amrwb (AMR-WB) 41 video vp9 vp9 (VP9 video) 40 video vp8 vp8 (VP8 video) 7 audio gsm gsm (GSM) 39 video mpeg4 mpeg4 (MPEG4 video) 25 audio ilbc ilbc (iLBC) 42 text red red (T.140 Realtime Text with redundancy) 43 text t140 t140 (Passthrough T.140 Realtime Text) 31 audio opus opus (Opus Codec) 32 image jpeg jpeg (JPEG image) 9 audio g726aal2 g726aal2 (G.726 AAL2) 3 audio codec2 codec2 (Codec 2) 28 audio siren14 siren14 (ITU G.722.1 Annex C, (Siren14, licensed from Polycom)) -- Regards, Paweł Bogusławski IB Development Team E:d...@ib.pl
Bug#1020565: Redundant atop log rotation
Package: atop Version: 2.6.0-2 Installing atop in Debian 11 adds atop-rotate.service that restarts atop at midnight and rotates its log. Same task is still fired using /etc/cron.d/atop when systemd is present... 0 0 * * * root [ -d "/run/systemd/system" ] && systemctl restart atop ...and atop is restarted+rotated twice -> races may occur. Please consider: * removing above line from /etc/cron.d/atop, * randomizing rotation schedule to avoid resource congestions (all systems rotating in same time). Randomization docs: https://www.freedesktop.org/software/systemd/man/systemd.timer.html#RandomizedDelaySec= Randomization example: [Timer] AccuracySec=10s RandomizedDelaySec=600s FixedRandomDelay=true -- Regards, Paweł Bogusławski IB Development Team E:d...@ib.pl
Bug#996581: Unnecessarry syslog message on rootless exim4 shutdown
Package: exim4-daemon-heavy Version: 4.94.2-7 When stopping (i.e. with "kill -SIGTERM ") rootless exim4 (run with uid/gid 1234/1234), syslog message is generated exim: only uid=0 or uid=101 can use -oP and -oPX (uid=1234 euid=1234 | 1234) even if this process was started without -oP/-oPX, with just /usr/sbin/exim -bdf -q5m No such problem with identical exim4 config in buster (exim4-daemon-heavy 4.92-8+deb10u6). -- Regards, Paweł Bogusławski IB Development Team E: d...@ib.pl
Bug#995586: Lack of /usr/lib/tmpfiles.d/podman.conf
Package: podman Version: 3.0.1+dfsg1-3+b2 Just was hit by https://github.com/containers/podman/issues/3759 in bullseye. Podman was generating "Error adding network: failed to allocate for range 0..." errors and containers were not starting. Manually creating /usr/lib/tmpfiles.d/podman.conf from libpod-3.0.1+dfsg1/contrib/tmpfile/podman.conf and rebooting resolved the issue. Please verify and cosider adding /usr/lib/tmpfiles.d/podman.conf to package. -- Regards, Paweł Bogusławski IB Development Team E: d...@ib.pl
Bug#981057: [Pkg-utopia-maintainers] Bug#981057: network-manager does not verify server certificate name on EAP-TLS WIFI connections
W dniu 25.01.2021 o 20:37, Michael Biebl pisze: I have no setup to verify this so it would be best if you file this directly upstream as this doesn't seem to be a downstream issue. Issue resolved in https://mail.gnome.org/archives/networkmanager-list/2021-January/msg00014.html -- Regards, Paweł Bogusławski IB Development Team E: d...@ib.pl
Bug#981057: network-manager does not verify server certificate name on EAP-TLS WIFI connections
Package: network-manager Version: 1.14.6-2+deb10u1 network manager configured for EAP-TLS verification in WIFI connection config ignores server certificate verifiaction parameters other than CA ca-cert. With example wifi connection config... [connection] id=myssid uuid=---- type=wifi read-only=TRUE [wifi] mode=infrastructure ssid=myssid [wifi-security] key-mgmt=wpa-eap [802-1x] ca-cert=/etc/ssl/certs/myca.pem client-cert=/etc/ssl/client-wifi-cert.pem eap=tls; identity=myclient private-key=/etc/ssl/client-wifi-key.pem private-key-password=notused system-ca-certs=false subject-match=anywrongname altsubject-matches=DNS:anywrongname domain-suffix-match=anywrongname [ipv4] method=auto [ipv6] method=ignore ...network manager connects successfully to AP that use tls server cert with Subject: CN = myssid Subject Alternative Name: DNS:myssid but it should not because of "match" requirements. Please verify and consider fixing. -- Regards, Paweł Bogusławski IB Development Team E: d...@ib.pl
Bug#979316: Random container killing
Package: docker.io Version: 18.09.1+dfsg1-7.1+deb10u2 We observe the occasional container kills in buster (containers from one image type only). No OOMs or other errors present; ausearch (configured to log kills with kill_signals key) says when problem occurs: node=mynode type=PROCTITLE msg=audit(01/05/21 07:40:04.371:973017) : proctitle=runc --root /var/run/docker/runtime-runc/moby --log-format json delete --force 51a8f7df39d42c228a4d34dbc798efc8a2f35f98f9d37f22f node=mynode type=OBJ_PID msg=audit(01/05/21 07:40:04.371:973017) : opid=27268 oauid=unset ouid=cybo-front oses=-1 obj==docker-default (enforce) ocomm=finish node=mynmode type=SYSCALL msg=audit(01/05/21 07:40:04.371:973017) : arch=x86_64 syscall=kill success=yes exit=0 a0=0x6a84 a1=SIGKILL a2=0x0 a3=0x0 items=0 ppid=1648 pid=6986 auid=unset uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none) ses=unset comm=runc exe=/usr/sbin/runc subj==unconfined key=kill_signals 51a8f7df39d42c228a4d34dbc798efc8a2f35f98f9d37f22f is killed container id. Syslog says: 2021-01-05 07:40:04 dockerd[1430]: time="2021-01-05T07:40:04.360641039+01:00" level=warning msg="cleaning up after killed shim" id=51a8f7df39d42c228a4d34dbc798efc8a2f35f98f9d37f22f9eba692d20efd97 namespace=moby 2021-01-05 07:40:04 dockerd[1430]: time="2021-01-05T07:40:04.360467155+01:00" level=info msg="shim reaped" id=51a8f7df39d42c228a4d34dbc798efc8a2f35f98f9d37f22f9eba692d20efd97 Looks like a bug described on https://github.com/moby/moby/issues/38768 Please verify and consider fixing. -- Regards, Paweł Bogusławski IB Development Team E: d...@ib.pl
Bug#978637: Bug in multiple ldaps URIs handling
Package: libnet-ldap-perl Version: 1:0.6500+dfsg-1 According to https://rt.cpan.org/Public/Bug/Display.html?id=118477 when creating a new ldaps:// connection using multiple URIs in the connection string (faiover in case of communication problems), it will only succeed if the connection to the first server succeeds. If the connection to the first server fails (i.e. first LDAP server is down or has invalid cert), connection to all subsequent servers will fail too. Problem was fixed by upstream in https://github.com/perl-ldap/perl-ldap/pull/58/files Please fix also in Debian packages. -- Regards, Paweł Bogusławski IB Development Team E: d...@ib.pl
Bug#959956: No out of space check_snmp_storage warning on btrfs
Package: nagios-snmp-plugins Version: 2.0.0-1 Hello, We've noticed out of space condition in one of btrfs filesystems monitored with check_snmp_storage; problem was not detected by check_snmp_storage. Filesystem status: root@mysrv:~# btrfs fi df -b /mnt Data, single: total=194688, used=194688 System, DUP: total=8388608, used=16384 System, single: total=4194304, used=0 Metadata, DUP: total=484835328, used=163921920 Metadata, single: total=8388608, used=0 GlobalReserve, single: total=16777216, used=0 root@mysrv:~# df -B1 /mnt Filesystem 1B-blocks Used Available Use% Mounted on /dev/mapper/myvg 3221225472 2566848512 0 100% /mnt Net-snmp snmp infos for this fs: hrStorageTable (used by check_snmp_storage): iso.3.6.1.2.1.25.2.3.1.1.69 = INTEGER: 69 // hrStorageIndex iso.3.6.1.2.1.25.2.3.1.2.69 = OID: iso.3.6.1.2.1.25.2.1.4 // hrStorageType iso.3.6.1.2.1.25.2.3.1.3.69 = STRING: "/mnt" // hrStorageDescr iso.3.6.1.2.1.25.2.3.1.4.69 = INTEGER: 4096// hrStorageAllocationUnits iso.3.6.1.2.1.25.2.3.1.5.69 = INTEGER: 786432 // hrStorageSize iso.3.6.1.2.1.25.2.3.1.6.69 = INTEGER: 626672 // hrStorageUsed dskTable (not used by check_snmp_storage): iso.3.6.1.4.1.2021.9.1.1.19 = INTEGER: 19 // dskIndex iso.3.6.1.4.1.2021.9.1.2.19 = STRING: "/mnt" // dskPath iso.3.6.1.4.1.2021.9.1.3.19 = STRING: "/dev/mapper/myvg" // dskDevice iso.3.6.1.4.1.2021.9.1.4.19 = INTEGER: -1 // dskMinimum iso.3.6.1.4.1.2021.9.1.5.19 = INTEGER: 10 // dskMinPercent iso.3.6.1.4.1.2021.9.1.6.19 = INTEGER: 3145728// dskTotal (Total size of the disk/partion (kBytes)) iso.3.6.1.4.1.2021.9.1.7.19 = INTEGER: 0 // dskAvail (Available space on the disk) iso.3.6.1.4.1.2021.9.1.8.19 = INTEGER: 2506688// dskUsed (Used space on the disk) iso.3.6.1.4.1.2021.9.1.9.19 = INTEGER: 80 // dskPercent (Percentage of space used on disk) iso.3.6.1.4.1.2021.9.1.10.19 = INTEGER: 0 // dskPercentNode (Percentage of inodes used on disk) iso.3.6.1.4.1.2021.9.1.11.19 = Gauge32: 3145728 // dskTotalLow Total size of the disk/partion (kBytes). Together with dskTotalHigh composes 64-bit number) iso.3.6.1.4.1.2021.9.1.12.19 = Gauge32: 0 // dskTotalHigh (Total size of the disk/partion (kBytes). Together with dskTotalLow composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.13.19 = Gauge32: 0 // dskAvailLow (Available space on the disk (kBytes). Together with dskAvailHigh composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.14.19 = Gauge32: 0 // dskAvailHigh (Available space on the disk (kBytes). Together with dskAvailLow composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.15.19 = Gauge32: 2506688 // dskUsedLow (Used space on the disk (kBytes). Together with dskUsedHigh composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.16.19 = Gauge32: 0 // dskUsedHigh (Used space on the disk (kBytes). Together with dskUsedLow composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.100.19 = INTEGER: 1// dskErrorFlag (Error flag signaling that the disk or partition is under the minimum required space configured for it.) iso.3.6.1.4.1.2021.9.1.101.19 = STRING: "/mnt: less than 10% free (= 0%)" // dskErrorMsg (A text description providing a warning and the space left on the disk.) The cause of problem is that in btrfs free space may be less than total-used and by default check_snmp_storage checks used space which was in this case about 80% (with 0% available in the same time and OS was throwing OOS errors on write). The solution is to configure warn/crit levels for %free not %used and use avail from dskTable because hrStorageTable does not provide this info (check_snmp_storage calculates free=total-used which is wrong for btrfs as above). Attached please find patch generated for upstream source https://raw.githubusercontent.com/dnsmichi/manubulon-snmp/master/plugins/check_snmp_storage.pl that works ok for us (this allows one to use new -u switch to use dskTable and its avail info instead of default hrStorageTable and its free=total-used calculation). This also adds a few spaces to plugin output for better message readability. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/ diff -Nur a/check_snmp_storage.pl b/check_snmp_storage.pl --- a/check_snmp_storage.pl 2020-05-07 14:00:20.145179580 +0200 +++ b/check_snmp_storage.pl 2020-05-07 12:53:08.0 +0200 @@ -1,11 +1,11 @@ #!/usr/bin/perl -w ## check_snmp_storage ##
Bug#954938: Occasional spice console freezes on boot after kernel upgrade
Package: linux-image-amd64 Version: 4.19+105+deb10u3 After upgrading kernel from 4.19+105+deb10u1 to 4.19+105+deb10u3 in debian 10 vm (qemu, kvm, virt-manager, qxl graphics) there are occassional spice text console image corruptions during system boot (boot with all text messages displayed, without quiet nor splash kernel parameters). Corrupted console contains many random characters witch different colors and does not update (freezes just before switching to high resolution text mode). Boot continues normally and one can unfreeze first console switching to second console and back (Ctrl+Alt+F2 and then Ctrl+Alt+F1). After a few minutes syslog starts to receive messages like below (repeating every 2 minutes): 2020-03-25 15:50:04 myhost kernel: [ 484.596112] INFO: task kworker/1:1:42 blocked for more than 120 seconds. 2020-03-25 15:50:04 myhost kernel: [ 484.596116] Not tainted 4.19.0-8-amd64 #1 Debian 4.19.98-1 2020-03-25 15:50:04 myhost kernel: [ 484.596118] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2020-03-25 15:50:04 myhost kernel: [ 484.596120] kworker/1:1 D042 2 0x8000 2020-03-25 15:50:04 myhost kernel: [ 484.596149] Workqueue: events drm_fb_helper_dirty_work [drm_kms_helper] 2020-03-25 15:50:04 myhost kernel: [ 484.596152] Call Trace: 2020-03-25 15:50:04 myhost kernel: [ 484.596163] ? __schedule+0x2a2/0x870 2020-03-25 15:50:04 myhost kernel: [ 484.596168] schedule+0x28/0x80 2020-03-25 15:50:04 myhost kernel: [ 484.596177] qxl_ring_push+0x15e/0x1e0 [qxl] 2020-03-25 15:50:04 myhost kernel: [ 484.596184] ? finish_wait+0x80/0x80 2020-03-25 15:50:04 myhost kernel: [ 484.596190] qxl_push_command_ring_release+0x64/0x90 [qxl] 2020-03-25 15:50:04 myhost kernel: [ 484.596197] qxl_draw_opaque_fb+0x25a/0x3f0 [qxl] 2020-03-25 15:50:04 myhost kernel: [ 484.596203] ? __switch_to_asm+0x35/0x70 2020-03-25 15:50:04 myhost kernel: [ 484.596208] qxlfb_framebuffer_dirty+0xeb/0x180 [qxl] 2020-03-25 15:50:04 myhost kernel: [ 484.596214] ? syscall_return_via_sysret+0x33/0x83 2020-03-25 15:50:04 myhost kernel: [ 484.596227] drm_fb_helper_dirty_work+0x14e/0x160 [drm_kms_helper] 2020-03-25 15:50:04 myhost kernel: [ 484.596236] process_one_work+0x1a7/0x3a0 2020-03-25 15:50:04 myhost kernel: [ 484.596241] worker_thread+0x30/0x390 2020-03-25 15:50:04 myhost kernel: [ 484.596245] ? create_worker+0x1a0/0x1a0 2020-03-25 15:50:04 myhost kernel: [ 484.596249] kthread+0x112/0x130 2020-03-25 15:50:04 myhost kernel: [ 484.596252] ? kthread_bind+0x30/0x30 2020-03-25 15:50:04 myhost kernel: [ 484.596257] ret_from_fork+0x35/0x40 No such problem in exactly same VM but with older kernel 4.19+105+deb10u1. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/
Bug#953532: spamassassin package installation error without gpg-agent
Package: spamassassin Version: 3.4.2-1+deb10u2 spamassassin package installation without gpg-agent installed throws an error: root@mysys:~# apt-get install spamassassin [...] Adding new user `debian-spamd' (UID 116) with group `debian-spamd' ... Not creating home directory `/var/lib/spamassassin'. gpg: failed to start agent '/usr/bin/gpg-agent': No such file or directory gpg: can't connect to the agent: No such file or directory gpg: process '/usr/bin/gpg --homedir='/var/lib/spamassassin/sa- update-keys' --batch --no-tty --status-fd=1 -q --logger-fd=1 -- import' finished: exit 2 dpkg: error processing package spamassassin (--configure): installed spamassassin package post-installation script subprocess returned error exit status 2 No such problem if gpg-agent is installed before spamassassin (missing package dependency?). -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/
Bug#950312: pidgin-awayonlock dependency correction
Package: pidgin-awayonlock Version: 0.5.2-1 pidgin-awayonlock deb package in buster depends on gnome-screensaver (>= 2.26) | kscreensaver (>= 4.2) but according to comment on https://packages.debian.org/pl/sid/gnome-screensaver gnome-shell does not require gnome-screensaver, so consider changing depencencies to gnome-shell | gnome-screensaver (>= 2.26) | kscreensaver (>= 4.2) pidgin-awayonlock works ok for us without gnome-screensaver installed. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/
Bug#948856: gdm3 screensaver issues in smartcard mode
Package: gdm3 Version: 3.30.2-3 gdm3 in buster when configured for login with smartcards in /etc/gdm3/greeter.dconf-defaults... [org/gnome/login-screen] enable-smartcard-authentication=true enable-password-authentication=false ...has problem with unlocking shield screen - ESC button does not work there (only on login screen, not user session lock screen). One must use mouse to drag shield or press ESC just after mouse click... In smartcard login mode there is also ugly screen blink just before starting screensaver (dimming out) in gdm3 and in user session. No such problems when smartcard login is disabled i.e. [org/gnome/login-screen] enable-smartcard-authentication=false enable-password-authentication=true Installation of newer gdm3 version from testing... dpkg -i libgdm1_3.34.1-1_amd64.deb gir1.2-gdm-1.0_3.34.1-1_amd64.deb gdm3_3.34.1-1_amd64.deb ...does not resolve these issues. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/
Bug#928171: closed by Michael Biebl (Re: Bug#928171: rsyslog.service does not create PID file reguired by logrotate script)
invoke-rc.d rsyslog rotate (used in /etc/logrotate.d/rsyslog and /usr/lib/rsyslog/rsyslog-rotate) throws error in buster if no rsyslogd pid exists. Please verify and fix if confirmed. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/ Dnia 2019-04-29, pon o godzinie 11:18 +, Debian Bug Tracking System pisze: > This is an automatic notification regarding your Bug report > which was filed against the rsyslog package: > > #928171: rsyslog.service does not create PID file reguired by logrotate script > > It has been closed by Michael Biebl . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Michael Biebl > by > replying to this email. > >
Bug#928171: closed by Michael Biebl (Re: Bug#928171: rsyslog.service does not create PID file reguired by logrotate script)
Ok /usr/lib/rsyslog/rsyslog-rotate uses systemctl not invoke-rc.d - sorry. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/ Dnia 2019-04-29, pon o godzinie 13:24 +0200, IB Development Team pisze: > invoke-rc.d rsyslog rotate > > (used in /etc/logrotate.d/rsyslog and /usr/lib/rsyslog/rsyslog-rotate) > throws error in buster if no rsyslogd pid exists. > > Please verify and fix if confirmed. >
Bug#928171: rsyslog.service does not create PID file reguired by logrotate script
Package: rsyslog Version: 8.1901.0-1 Logrotate does not notify rsyslog to close its files on rotation because lack of PID file; consider changing -ExecStart=/usr/sbin/rsyslogd -n -iNONE +ExecStart=/usr/sbin/rsyslogd -n -i /run/rsyslogd.pid in /usr/lib/systemd/system/rsyslog.service like in https://github.com/rsyslog/rsyslog-pkg-ubuntu/issues/79 Regards, Pawel IB Development Team https://dev.ib.pl/
Bug#927801: File backup default value does not work in site.pp
Package: puppet-master
Version: 5.5.10-2
Global setting
File { backup => false }
in site.pp does not disable creating file backups on puppet client (backups are
created in /var/lib/puppet/clientbucket but should not).
No such problem in Jessie/Stretch.
Regards,
Pawel
IB Development Team
https://dev.ib.pl/
Bug#897427: More testing
Hi, Same error in Debian 8 amd64 if trying to start one guest with two virtio nics. Guest will start ok if one nic is removed. No such problems after booting with previous 3.16.0-5-amd64 kernel. Regards, Pawel
Bug#861821: Possible cause
Hi, The problem seems to bo related to: https://lists.launchpad.net/kernel-packages/msg184109.html https://lkml.org/lkml/2014/10/9/339 Fixes present in newer kernels... https://github.com/torvalds/linux/commit/764f612c6c3c231b9c12cfae7c328ccc9c453258 https://github.com/torvalds/linux/commit/7f60dcaaf91e911002007c7ae885ff6ef0f36c0d ...are not present in Jessie 3.16 kernel sources. Please verify and fix in Jessie kernel as it may cause (rare but sill) very serious problems (i.e. system outages). Regards, Pawel IB Development Team https://dev.ib.pl/
Bug#861821: Rare general protection faults in Jessie when mylvmbackup is trying to mount snapshotted LV with XFS filesystem
kernel: [283314.415398] [] ? chunk_io+0xf0/0x100 [dm_snapshot] 2017-05-03 00:03:03kernel: [283314.415398] [] ? generic_make_request+0xb0/0x100 2017-05-03 00:03:03kernel: [283314.415398] [] ? dm_lookup_exception+0x50/0x50 [dm_snapshot] 2017-05-03 00:03:03kernel: [283314.415398] [] ? persistent_commit_exception+0xcd/0x150 [dm_snapshot] 2017-05-03 00:03:03kernel: [283314.415398] [] ? copy_callback+0xa5/0x130 [dm_snapshot] 2017-05-03 00:03:03kernel: [283314.415398] [] ? run_complete_job+0x5d/0xb0 [dm_mod] 2017-05-03 00:03:03kernel: [283314.415398] [] ? kcopyd_put_pages+0x40/0x40 [dm_mod] 2017-05-03 00:03:03kernel: [283314.415398] [] ? process_jobs+0x92/0x120 [dm_mod] 2017-05-03 00:03:03kernel: [283314.415398] [] ? do_work+0x36/0x70 [dm_mod] 2017-05-03 00:03:03kernel: [283314.415398] [] ? process_one_work+0x143/0x430 2017-05-03 00:03:03kernel: [283314.415398] [] ? worker_thread+0x113/0x4f0 2017-05-03 00:03:03kernel: [283314.415398] [] ? __schedule+0x2b1/0x6f0 2017-05-03 00:03:03kernel: [283314.415398] [] ? rescuer_thread+0x2d0/0x2d0 2017-05-03 00:03:03kernel: [283314.415398] [] ? kthread+0xbd/0xe0 2017-05-03 00:03:03kernel: [283314.415398] [] ? kthread_create_on_node+0x180/0x180 2017-05-03 00:03:03kernel: [283314.415398] [] ? ret_from_fork+0x58/0x90 2017-05-03 00:03:03kernel: [283314.415398] [] ? kthread_create_on_node+0x180/0x180 2017-05-03 00:03:03kernel: [283314.415398] Code: 3f 44 89 4c 24 28 48 89 4c 24 30 e8 bd 5a 03 00 8b 7c 24 44 48 8b 74 24 38 4c 8b 44 24 20 44 8b 4c 24 28 48 8b 4c 24 30 49 89 07 <48> 8b 10 83 e2 03 40 f6 c6 03 0f 85 b2 01 00 00 48 09 f2 89 78 2017-05-03 00:03:03kernel: [283314.415398] RIP [] __blk_bios_map_sg+0x1de/0x400 2017-05-03 00:03:03kernel: [283314.415398] RSP 2017-05-03 00:03:03kernel: [283314.487465] ---[ end trace c61d1f486cfc3a7d ]--- 2017-05-03 00:03:03kernel: [283314.489156] BUG: unable to handle kernel paging request at ffd8 2017-05-03 00:03:03kernel: [283314.491210] IP: [] kthread_data+0xc/0x20 2017-05-03 00:03:03kernel: [283314.492285] PGD 1816067 PUD 1818067 PMD 0 2017-05-03 00:03:03kernel: [283314.493012] Oops: [#2] SMP This hung guest system (cold reset required). Problem is rare - two occurences in last 2 months in one system only (mylvmbackup runs once every 24h there; no problems most of time). No such problems noticed with mylvmbackup on Wheezy. Please verify and consider fixing in Jessie. Regards, Pawel IB Development Team https://dev.ib.pl/
Bug#808113: Fix smartcard certificate removal and update
Package: opensc Version: 0.14.0-2 Hi, There is a bug in opensc that blocks certificate update and removal. This problem was fixed in https://github.com/OpenSC/OpenSC/commit/de42deaae10dd0a198b61902169c7f4e2cb8e6da Please verify and consider fixing in Jessie. Regards, Pawel IB Development Team https://dev.ib.pl/
Bug#802885: XFS growing problem in Jessie
Package: linux-image-3.16.0-4-amd64 Version: 3.16.7-ckt11-1+deb8u4 Hi, There is a bug in kernel versions from v3.7 to v3.17 which causes new XFS allocation groups added by growfs to be unavailable for inode allocation: http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_receive_No_space_left_on_device_after_xfs_growfs.3F This may lead to bad things on production systems when online growing XFS won't be enough to avoid out of space situations. We've just hit such problem on Debian 8 system with kernel linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u4 (workaround with remounting worked for us). Please verify and consider fixing in Jessie. Regards, Pawel IB Development Team https://dev.ib.pl/ -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/
Bug#790440: default installation shows internal LDAP OUs
Hi, The problem with basedn as item in the list at / level does not exist anymore in jessie. Seems it was an OpenLDAP issue resolved in http://metadata.ftp-master.debian.org/changelogs//main/o/openldap/openldap_2.4.40+dfsg-1_changelog I think you can close #790440. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782531: fusiondirectory problems with prototype.js and basedn
Package: fusiondirectory Version: 1.0.8.2-3 Hi, Two problems found in fusiondirectory in jessie: (1) After installation javascript-common.conf is not enabled in /etc/apache2/conf-enabled and fusiondirectory cannot get prototype.js. (2) Object lists (i.e. Users, Groups, Systems) in jessie fresh openldap+fusiondirectory installation display basedn as item in the list at / level. No such behaviour in http://demo.fusiondirectory.org/. Please verify and fix. Thank you. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781791: /var/run/puppet permissions mismatch
Package: puppet-common Version: 3.7.2-3 Hi, Puppet initscripts setup /var/run/puppet dir 0755 puppet puppet Same if puppet agent is executed without this dir existing and rundir=/var/run/puppet set in puppet.conf. But in /usr/lib/tmpfiles.d/puppet-common.conf there is root group specified 0755 puppet root This makes permissions flapping; puppet group should be probably specified in /usr/lib/tmpfiles.d/puppet-common.conf also. Please verify and fix. Thank you. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780214: fusiondirectory-plugin-cyrus does not save sieve script
Package: fusiondirectory-plugin-cyrus
Version: 1.0.8.2-3
Hi,
When you try to save sieve vacation using fusiondirectory-plugin-cyrus
(cyrus-imapd, Jessie), you'll get FD errors like
Cannot store SIEVE script: script errors:
line 3: vacation MUST be enabled with require
Fix that works for us:
--- sieve_script.tpl_ 2015-03-10 17:43:21.0 +0100
+++ sieve_script.tpl2015-03-10 17:50:43.33200 +0100
@@ -1,8 +1,6 @@
-{if $content}
###FUSIONDIRECTORY
require [fileinto, reject, vacation];
-{/if}
{if $spamfilter}
# Sort mails with higher spam level
if header :contains X-Spam-Level {$spamlevel} {literal}{{/literal}
Please verify and fix. Thank you.
--
Regards,
Pawel Boguslawski
IB Development Team
https://dev.ib.pl/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779653: Wrong path to systemctl in start-dirsrv and stop-dirsrv
Package: 389-ds-base Version: 1.3.3.5-3 Hi, File /usr/bin/systemctl specified in /usr/sbin/start-dirsrv /usr/sbin/stop-dirsrv does not exist. Should be /bin/systemctl probably. Please verify and fix. Thank you. -- Regards, Pawel Boguslawski IB Development Team https://dev.ib.pl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766364: libkrb5-3 poll with negative values
Package: libkrb5-3
Version: 1.10.1+dfsg-5+deb7u2
Hi,
We use Debian 7 with libapache2-mod-auth-kerb and krb5-user packages for SSO. Installed libkrb5-3
version is 1.10.1+dfsg-5+deb7u2.
Sometimes, when KDC communication problems occur, some apache (prefork) processes hang with 100% cpu
utilization (high sy level in top) - even on serving static content like CSS files.
We tried to strace few hug apache PIDs - all of them are polling with negative
values (decreasing):
[...]
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
[...]
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293539) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293540) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293540) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293540) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293540) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
[...]
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293540) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293540) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293540) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293541) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293541) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
poll([{fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 2, -3293541) = 2 ([{fd=17,
revents=POLLIN|POLLERR|POLLHUP}, {fd=19, revents=POLLIN}])
[...]
Only killing hung apache child procs help. Similar problem was resolved in
http://krbdev.mit.edu/rt/Ticket/Display.html?id=7553
https://github.com/krb5/krb5/commit/74bee54227deb64a41c2e79f57dd2a2c5ea010a3
but not in krb5_1.10.1+dfsg-5+deb7u2 sources.
Similar problem was resolved in RedHat also:
https://rhn.redhat.com/errata/RHBA-2013-0319.html
Problem is rather serious and may cause web services outages so please verify
and fix in stable.
Thank you,
Pawel
IB Development Team
http://dev.ib.pl/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747285: sphinxsearch logrotation problem
Package: sphinxsearch Version: 2.0.4-1.1 Hi, Current sphinxsearch version 2.0.4-1.1 in Wheezy has a bug described on page http://sphinxsearch.com/bugs/view.php?id=1171 After logrotating sphinx logs in Wheezy, lsof says: # lsof | grep /var/log/sphinxsearch searchd 15663 sphinxsearch4u REG 253,1239821144154 /var/log/sphinxsearch/searchd.log-20140504 (deleted) searchd 15664 sphinxsearch4u REG 253,12 1101144134 /var/log/sphinxsearch/searchd.log [...] Please consider fixing this bug in Wheezy also. Regards, Pawel IB Development Team http://dev.ib.pl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747287: Feature Request: sphinxsearch with syslog enabled
Package: sphinxsearch Version: 2.0.4-1.1 Hi, Current sphinxsearch version 2.0.4-1.1 in Wheezy does not support syslog mode as described on http://sphinxsearch.com/docs/archives/2.0.4/conf-log.html (lack of '--with-syslog' compile option maybe?). With log = syslog in sphinx.conf, restarting /etc/init.d/sphinxsearch restart produces error FATAL: failed to open log file 'searchd.log': Permission denied Please consider adding syslog support to sphinxsearch package. Regards, Pawel IB Development Team http://dev.ib.pl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740433: Samhain IgnoreAdded/IgnoreMissing regexp bug
Package: samhain Version: 2.8.3a-1+deb7u1 Hi, Current samhain version 2.8.3a-1+deb7u1 used in Wheezy has a bug that was already fixed in samhain 3.1.0; in samhain-3.1.0/docs/Changelog we can see: Fix IgnoreAdded to anchor regex at beginning of path (reported by R.Lindner) and in src/sh_ignore.c there is ^ added to all regexps like this: + len = 2 + strlen(addpath); + reg_expr = SH_ALLOC(len); + sl_strlcpy(reg_expr, ^, len); + sl_strlcat(reg_expr, addpath, len); #ifdef HAVE_REGEX_H - status = regcomp((new-preg), addpath, REG_NOSUB|REG_EXTENDED); + status = regcomp((new-preg), reg_expr, REG_NOSUB|REG_EXTENDED); What's the problem? If you specify in /etc/samhain/samhainrc for example IgnoreAdded = /tmp/ IgnoreMissing = /tmp/ and expect samhain to apply it to /tmp/* stuff only, you'll be surprised that all adds/dels in other subdirs like /root/tmp/ /var/lib/mysupersecretapp/tmp/ will be ignored also. Not good. We think it's real security issue so please consider fixing this bug in Wheezy also. Regards, Pawel IB Development Team http://dev.ib.pl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731982: XFS + NFS4 occasional hangups
Package: linux-image-3.2.0-4-amd64 Version: 3.2.46-1 Hello, During extensive testing of NFS4 file server (Debian 7 guest on VMware / Proxmox VE-KVM) that shares XFS filesystems over network we've hit problem with occasional system hangups caused by nfsd and xfsaild processes. When this issue occurs, 2 from 4 cpus are 100% loaded (one with nfsd, second with xfsaild) and two other CPU-s are trying to handle other processes but i/o wait is almost 100% for those CPU-s and system is unusable (sometimes it's possible to ssh into system after long waiting, sometimes it's not possible; scp seems to work better in this situation, console is always blank and unresponsible, pings work ok). top output during hangup: top - 00:55:20 up 13:44, 3 users, load average: 34.00, 34.01, 33.93 Tasks: 175 total, 9 running, 164 sleeping, 0 stopped, 2 zombie %Cpu0 : 0.0 us,100.0 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu1 : 0.3 us, 0.7 sy, 0.0 ni, 0.0 id, 98.7 wa, 0.0 hi, 0.0 si, 0.3 st %Cpu2 : 0.0 us, 0.0 sy, 0.0 ni, 0.0 id, 99.7 wa, 0.0 hi, 0.0 si, 0.3 st %Cpu3 : 0.0 us,100.0 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 4061340 total, 2122328 used, 1939012 free, 2072 buffers KiB Swap: 524284 total,0 used, 524284 free, 1165292 cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 15094 root 20 0 23312 1708 1140 R 0.7 0.0 0:00.11 top 1242 root 20 0 000 S 0.3 0.0 0:09.71 xfsaild/dm-4 14895 sshl 20 0 71176 2396 1564 S 0.3 0.1 0:00.33 sshd 1 root 20 0 10648 808 672 S 0.0 0.0 0:01.78 init 2 root 20 0 000 S 0.0 0.0 0:00.00 kthreadd 3 root 20 0 000 S 0.0 0.0 1:29.80 ksoftirqd/0 5 root 20 0 000 S 0.0 0.0 0:00.00 kworker/u:0 [...] See attached /proc/sched_debug dump from hangup time, that indicates nfsd and xfsaild as cpu0 and cpu3 holders. We've managed to recreate this issue a few times (every test requred VM restoring from backup and 6-24 hours of intensive NFS operations to hit hangup) and every time xfsaild proces in sched_debug was connected with dm-5 device on our system (see xfsaild/dm-5 in attached sched_debug dump). The very last messages that syslog managed to send to remote syslog server were always like in attached syslog.txt extract. Device dm-5 was bound to XFS filesystem with high agcount (agcount=81 was effect of growing this FS from small to bigger size); xfs_info output for this FS: meta-data=/dev/mapper/vg1-tmpisize=256agcount=81, agsize=16320 blks = sectsz=512 attr=2 data = bsize=4096 blocks=1310720, imaxpct=25 = sunit=64 swidth=128 blks naming =version 2 bsize=4096 ascii-ci=0 log =internal bsize=4096 blocks=1216, version=2 = sectsz=512 sunit=64 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 After reformatting this XFS filesystem (agcount=4 after reformatting) and repeating tests, we didn't manage to hit this issue any more, so problem may be connected with XFS and high agcount and intensive operations on such XFS filesystem (maybe some races in kernel code near XFS?). Regards, Pawel IB Development Team http://dev.ib.pl/ Sched Debug Version: v0.10, 3.2.0-4-amd64 #1 ktime : 47413060.422986 sched_clk : 48401420.774630 cpu_clk : 47413060.423095 jiffies : 4306745560 sched_clock_stable : 0 sysctl_sched .sysctl_sched_latency: 18.00 .sysctl_sched_min_granularity: 2.25 .sysctl_sched_wakeup_granularity : 3.00 .sysctl_sched_child_runs_first : 0 .sysctl_sched_features : 24119 .sysctl_sched_tunable_scaling: 1 (logaritmic) cpu#0, 1995.190 MHz .nr_running: 4 .load : 2048 .nr_switches : 87608906 .nr_load_updates : 10669061 .nr_uninterruptible: 320 .next_balance : 4306.745619 .curr-pid : 2344 .clock : 25463350.262748 .cpu_load[0] : 2048 .cpu_load[1] : 2048 .cpu_load[2] : 2048 .cpu_load[3] : 2048 .cpu_load[4] : 2048 cfs_rq[0]:/ .exec_clock: 0.00 .MIN_vruntime : 1394281.606368 .min_vruntime : 1394290.559425 .max_vruntime : 1394281.606368 .spread
