Bug#1051862: (Debian) Bug#1051862: server flooded with xen_mc_flush warnings with xen 4.17 + linux 6.1

2023-09-14 Thread Radoslav Bodó
Hi all, hopefully it's ok to reply-all at this point On 9/13/23 23:38, Hans van Kranenburg wrote: I have a few quick additional questions already: 1. For clarification.. From your text, I understand that only this one single server is showing the problem after the Debian version upgrade.

Bug#1051862: server flooded with xen_mc_flush warnings with xen 4.17 + linux 6.1

2023-09-13 Thread Radoslav Bodó
Package: xen-system-amd64 Version: 4.17.1+2-gb773c48e36-1 Severity: important Hello, after upgrade from Bullseye to Bookworm one of our dom0's became unusable due to logs/system being continuously flooded with warnings from arch/x86/xen/multicalls.c:102 xen_mc_flush, and the system become

Bug#1022126: mpt3sas broken with xen dom0

2022-11-06 Thread Radoslav Bodó
to be a bit more precise (sorry for being a bit sloopy). we don't see same error with `swiotlb buffer` but rather ``` mpt3sas_cm0: failure at drivers/scsi/mpt3sasg/mpt3sas_scsih.c:11069/_scsih_probe()! ``` as reported in `1023...@bugs.debian.org` ``` # dmesg | grep mpt [0.233229]

Bug#1022126: mpt3sas driver does not load

2022-11-06 Thread Radoslav Bodó
Hello, we are facing very same issue (kernel 5.10.149-2 does not load driver with same error message) on Dell R440 with ME4012 disk array attached via HBA (taken from working 5.10.136-1) [3.744036] mpt3sas_cm0: FW Package Ver(15.17.09.06) [3.744740] mpt3sas_cm0: LSISAS3008:

Bug#1023183: mpt3sas driver does not load

2022-11-06 Thread Radoslav Bodó
Hello, we are facing very same issue (kernel 5.10.149-2 does not load driver with same error message) on Dell R440 with ME4012 disk array attached via HBA (taken from working 5.10.136-1) [3.744036] mpt3sas_cm0: FW Package Ver(15.17.09.06) [3.744740] mpt3sas_cm0: LSISAS3008:

Bug#995871: consider pickup security fix for https://bugs.php.net/bug.php?id=54350

2021-10-07 Thread Radoslav Bodó
Package: php7.4 Version: 7.4.21-1+deb11u1 Severity: important Hello, recently a PoC for https://bugs.php.net/bug.php?id=54350 has been made public https://github.com/mm0r1/exploits/blob/master/php-filter-bypass/exploit.php Current package is vulnerable, and the exploit seem to be very stable in

Bug#981243: libboost-log1.74.0 prevents debootsrap to finish correctly

2021-02-28 Thread Radoslav Bodó
> Adrian Bunk (2021-02-28): >> This is a bug in debootstrap which should really use a dependency >> solver like apt, but AFAIK noone is working on this. > > Well debootstrap's goal is what it says in the name, which is > bootstrapping. Just install a base system first and install whatever >

Bug#981825: debian/buster64 no longer works correctly with vbguest plugin

2021-02-04 Thread Radoslav Bodó
Package: cloud.debian.org Hello, vagrant box debian/buster64 10.4.0 no longer works as expected most likely due to repository changes where kernel headers are no longer present Localy I've resolved the issue by updating base box image with the new kernel, but I guess it might be useful either

Bug#981243: libboost-log1.74.0 prevents debootsrap to finish correctly

2021-01-28 Thread Radoslav Bodó
Package: libboost-log1.74.0 Version: 1.74.0-8 Severity: important Hello, as we are preparing ourselves for the new release, we've found that debootstrap installation process gets interrupted possibly by libboost (coming along with puppet/facter). The process does not finish correctly and leaves

Bug#977371: facter segfault inside libleatherman/libboost-filesystem

2020-12-14 Thread Radoslav Bodó
I've also found bugreport for same bug in boost package https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977351

Bug#977371: facter segfault inside libleatherman/libboost-filesystem

2020-12-14 Thread Radoslav Bodó
Package: facter Version: 3.14.12-1+b1 Severity: important Hello, recently our CI starts to fail with new facter version 3.14.12-1+b1 with segfault somewhere in some directory listing code, where 3.11.0-4.1 works fine. The issue is reproducible in our custom VM (Xen based Bullseye VM) and also i

Bug#975970: [pkg-bacula-devel] Bug#975970: bacula-director-mysql broken SQL schema for mariadb-server-10.5

2020-11-27 Thread Radoslav Bodó
> enough SQL do be dangerous), would you please open a bug report at > https://bugs.bacula.org and report the bug Id back here? aye aye sir https://bugs.bacula.org/view.php?id=2584 bodik

Bug#975970: bacula-director-mysql broken SQL schema for mariadb-server-10.5

2020-11-27 Thread Radoslav Bodó
> I don't really have an exact explanation but at least the schema seem to > be created ... I've been a little bit too rash, database gets created but director was unable to run a single job ... ``` 27-Nov 19:40 xxx JobId 0: Fatal error: sql_create.c:83 Create DB Job record INSERT INTO Job

Bug#975970: bacula-director-mysql broken SQL schema for mariadb-server-10.5

2020-11-27 Thread Radoslav Bodó
> Yes, I can confirm the problem. Getting this solved may prove > interesting, as upstream does not officially support MariaDB. thank you for very quick response > 2) After disabling those checks, there is still a different error in > bacula.Job and bacula.Pool: > > , > | Error in foreign

Bug#975970: bacula-director-mysql broken SQL schema for mariadb-server-10.5

2020-11-27 Thread Radoslav Bodó
Package: bacula-director-mysql Version: 9.6.6-2 Severity: important After recent version bump of mariadb-server in Bullseye, the schema in bacula-director-mysql: /usr/share/dbconfig-common/data/bacula-director-mysql/install/mysql is no longer compatible with the database server ``` #

Bug#866952: Xen 4.8 crashes...

2019-01-23 Thread Radoslav Bodó
thanks for your concern. Currently I'm fine with the workaround I've right now. Debian Buster (and new xen version) will be released sometimes this year, so I would reopen a new bug if the problem persist on the server after upgrade ... Thank you and best regards bodik Dne 01/23/2019 v 09:31 PM

Bug#866952: Workaround: limit cpu's of dom0

2017-09-15 Thread Radoslav Bodó
I'm facing the same issue on Dell R510 with up to date firmware. Workaround posted by Joachim Braun 's worked > dom0_max_vcpus=4 dom0_vcpus_pin Best regards bodik