Bug#1088378: collectd crashes when write_riemann plugin is enabled

2024-11-27 Thread Mariusz Gronczewski
On 27.11.2024 17:38, Bernd Zeimetz wrote: Hi Mariusz, On 2024-11-27 17:05, Mariusz Gronczewski wrote: I think it might be this one https://github.com/collectd/collectd/issues/4050 that was patched and backported to 5.12 at beginning of this year: https://github.com/collectd/collectd/pull

Bug#1088378: collectd crashes when write_riemann plugin is enabled

2024-11-27 Thread Mariusz Gronczewski
Package: collectd Version: 5.12.0-22 Severity: normal X-Debbugs-Cc: mgronczew...@efigence.com We're using collectd instance to translate from collectd protocol to riemann so config (in attachment) is pretty simple; with enabled write_riemann plugin we are getting segfault as soon as it starts

Bug#1016167: 389-ds-base: dscreate does not work due to race condition when starting and connecting to LDAP server instance

2022-07-28 Thread Mariusz Gronczewski
32.1-4+deb11u2 ii python3 3.9.2-3 ii python3-lib389 1.4.4.11-2 ii python3-selinux 3.1-3 ii python3-semanage 3.1-1+b2 ii python3-sepolicy 3.1-1 ii systemd 247.3-7 389-ds-base recommends no packages. 389-ds-b

Bug#981434: initramfs-tools: boot delayed by 30sec. due to /scripts/local-block loop

2021-01-31 Thread Mariusz Gronczewski
from triggering I also had set initramfs-tools/conf.d/resume: RESUME=none as I don't want resume in the first place -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#981433: grub-efi-amd64: Grub keeps adding resume= after package update, triggering other bugs in the process

2021-01-31 Thread Mariusz Gronczewski
initramfs-tools/conf.d/resume: RESUME=none (or is it wrong way?) it triggers bug #860533 causing extra 30s of boot time -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#720096: logrotate rsyslog bug

2020-11-24 Thread Mariusz Gronczewski
tting new connections, so it is a pretty severe problem. -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#932939: Reproduced bug 932939

2020-02-26 Thread Mariusz Gronczewski
er's shell. As with other examples, setting a single console makes it reliable -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#920345: [Pkg-freeradius-maintainers] Bug#920345: freeradius: running freeradius with debug(-X) option breaks systemd unit

2019-01-25 Thread Mariusz Gronczewski
> there are no communication channels, and no reverse dependencies of note? > > I’m not sure. > > > > If you could confirm with upstream that they are blessing use of -f and > > Type=simple as the default in Debian, I can make the change. > > > > Thanks, > > >

Bug#920345: [Pkg-freeradius-maintainers] Bug#920345: freeradius: running freeradius with debug(-X) option breaks systemd unit

2019-01-25 Thread Mariusz Gronczewski
upstream that they are blessing use of -f and > Type=simple as the default in Debian, I can make the change. > > Thanks, > > On Thu, Jan 24, 2019 at 4:49 PM Mariusz Gronczewski wrote: >> >> Well, there is, adding -f option by default means it will always run >>

Bug#920345: [Pkg-freeradius-maintainers] Bug#920345: freeradius: running freeradius with debug(-X) option breaks systemd unit

2019-01-24 Thread Mariusz Gronczewski
uggestion is — I just don’t see a way out of this situation. > > My personal recommendation is to not use /etc/default, but rather systemctl > edit to do any overrides, but that’s not Debian’s official line. > > On Thu, Jan 24, 2019 at 3:37 PM Mariusz Gronczewski wrote: >> >

Bug#920345: [Pkg-freeradius-maintainers] Bug#920345: freeradius: running freeradius with debug(-X) option breaks systemd unit

2019-01-24 Thread Mariusz Gronczewski
o enter restart loop, surely that isn't an expected behaviour ? On Thu, 24 Jan 2019 at 13:52, Michael Stapelberg wrote: > > Yes, this is expected. What change are you suggesting? > > On Thu, Jan 24, 2019 at 1:45 PM Mariusz Gronczewski wrote: >> >> Package: freeradius >

Bug#920345: freeradius: running freeradius with debug(-X) option breaks systemd unit

2019-01-24 Thread Mariusz Gronczewski
. Changing type to simple, and adding -f (run in foreground) option in unit file fixes that -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

2016-10-13 Thread Mariusz Gronczewski
2016-10-13 0:08 GMT+02:00 Samuel Thibault : > Mariusz Gronczewski, on Thu 13 Oct 2016 00:03:18 +0200, wrote: >> Hard to tell, server in question was installed from preseed file and >> it was only one having that package... > > Ok, perhaps /var/log/dpkg.log or /var/log/instal

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

2016-10-12 Thread Mariusz Gronczewski
ody depends on or > recommends. When removing brltty, does it not uninstall anything? > > Samuel Hard to tell, server in question was installed from preseed file and it was only one having that package... but I've recently installed its twin (same repos, same Puppet manifest, same purpose) a

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

2016-10-12 Thread Mariusz Gronczewski
got it as suprise dependency to... *something* but it is hard to tell what so at least that should be fixed -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#835342: curl or git clone commands throws "gnutls_handshake() failed" on https targets

2016-09-22 Thread Mariusz Gronczewski
Hi, I've hit same bug, Upgrading librtmp to latest (in testing, 2.4+20151223.gitfa8646d.1-1) fixed it for me. To be exact: Unpacking librtmp1:amd64 (2.4+20151223.gitfa8646d.1-1) over (2.4+20150115.gita107cef-1) -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#820796: netcfg: no way to pre-set domain and current ways of aquiring it resolve to "bad" domain

2016-04-12 Thread Mariusz Gronczewski
Package: netcfg Severity: important So currently domain= from boot options and netcfg/get_domain from preseed are being overwritten, which is error in itself, but even if my DHCP server is serving correct domain field, server gets configured with domain name "bad". I believe that is related t

Bug#820788: partman-auto: max partition size in recipe is ignored in LVM

2016-04-12 Thread Mariusz Gronczewski
Package: partman-auto Severity: normal I am using following preseed scheme to partition my disks (RAID1+ LVM), partition with highest priority "eats" all of the free space even tho it has a max size: d-i partman-auto-raid/recipe string \ 1 2 0 ext2 /boot\ /dev/sd

Bug#818969: allow-external-password-cache seems to be a problem

2016-03-22 Thread Mariusz Gronczewski
using #!/bin/bash export DISPLAY=:0 perl -pe'$|=1;s/allow-external-password-cache/broken/'| /usr/bin/pinentry-gnome3 seems to "fix" it, so whatever that option is doing should be probably be disabled by default -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#818969: correction

2016-03-22 Thread Mariusz Gronczewski
re-adding keys only helps intill gpg-agent is restarted -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#818969: Info received (seems like pinentry is returning it as "cached")

2016-03-22 Thread Mariusz Gronczewski
Okay, it seems like anything created in earlier version in .gnupg/private-keys-v1.d/ is broken **and** doesnt signal that in any meaningful way. After removing and re-adding all keys it works fine -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#818969: seems like pinentry is returning it as "cached"

2016-03-22 Thread Mariusz Gronczewski
PASSWORD_FROM_CACHE OK is that some uncleared cache problem ? i've been using 2.0.x befoe upgrade -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#818969: gnupg-agent: gpg-agent passes not yet available when used as ssh-agent

2016-03-22 Thread Mariusz Gronczewski
- [[Confidential data not shown]] 2016-03-22 12:51:39 gpg-agent[20069] DBG: error calling pinentry: No passphrase given 2016-03-22 12:51:39 gpg-agent[20069] DBG: chan_8 -> BYE 2016-03-22 12:51:39 gpg-agent[20069] failed to unprotect the secret key: No passphrase given -- Mariusz Gronczewski (XANi)

Bug#804353: puppet: disabled dnsmasq prevents puppet package from installing

2015-11-07 Thread Mariusz Gronczewski
Package: puppet Version: 3.8.3-1 Severity: normal After installing a package it can't be configured if dnsmasq is disabled in system: insserv: Service dnsmasq has to be enabled to start service puppet insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error process

Bug#727013: Bug #727013: [gnupg2] gpg2 cannot connect to pinentry, although it is installed

2015-09-25 Thread Mariusz Gronczewski
Also I've noticed that my password for key doesn't work (tried to enter it at least 5 times and failed everytime and I'm 100% sure it wasnt a typo), and downgrading to 2.0.28 helped -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#727013: Bug #727013: [gnupg2] gpg2 cannot connect to pinentry, although it is installed

2015-09-25 Thread Mariusz Gronczewski
but when I kill the daemon and run it from X11's terminal and then try to connect (after setting correct env of couse) I get pinentry correctly -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64

Bug#680660: [collectd] Bug#680660: collectd - runs as root without apparent reason

2012-07-16 Thread Mariusz Gronczewski
y to specify enabled capabilities per exec while allowing to run them on user root (possibly with IKnowThatIsUnsafe switch ;) ) -- Mariusz Gronczewski -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org