[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
# Demonstration of fence_scsi fencing a node: (k)rafaeldtinoco@clubionic03:~/.../upstream$ cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp # iscsi auto eth1 iface eth1 inet static address 10.250.1.12/24 # private auto eth2 iface eth2 inet static address 10.250.3.12/24 # public auto eth3 iface eth3 inet static address 10.250.98.12/24 (k)rafaeldtinoco@clubionic03:~/.../upstream$ sudo iptables -A INPUT -i eth2 -j DROP (k)rafaeldtinoco@clubionic01:~$ crm_mon -1 Stack: corosync Current DC: clubionic01.private (version 1.1.19-1.1.19) - partition with quorum Last updated: Tue Mar 3 21:24:55 2020 Last change: Tue Mar 3 20:25:56 2020 by root via cibadmin on clubionic01.private 3 nodes configured 1 resource configured Online: [ clubionic01.private clubionic02.private ] OFFLINE: [ clubionic03.private ] Active resources: fence_clubionic(stonith:fence_scsi): Started clubionic01.private (k)rafaeldtinoco@clubionic03:~/.../upstream$ sudo sg_persist --in --read-keys --device=/dev/sda LIO-ORG cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x4, 2 registered reservation keys follow: 0x3abe 0x3abe0001 (k)rafaeldtinoco@clubionic03:~/.../upstream$ sudo dd if=/dev/zero of=/dev/sda bs=1M count=1 [ 3301.867294] print_req_error: critical nexus error, dev sda, sector 0 [ 3301.868543] Buffer I/O error on dev sda, logical block 0, lost async page write [ 3301.869956] Buffer I/O error on dev sda, logical block 1, lost async page write [ 3301.871430] Buffer I/O error on dev sda, logical block 2, lost async page write [ 3301.872929] Buffer I/O error on dev sda, logical block 3, lost async page write [ 3301.874448] Buffer I/O error on dev sda, logical block 4, lost async page write [ 3301.875963] Buffer I/O error on dev sda, logical block 5, lost async page write [ 3301.877486] Buffer I/O error on dev sda, logical block 6, lost async page write [ 3301.879000] Buffer I/O error on dev sda, logical block 7, lost async page write [ 3301.880481] Buffer I/O error on dev sda, logical block 8, lost async page write [ 3301.882014] Buffer I/O error on dev sda, logical block 9, lost async page write 1+0 records in 1+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0227557 s, 46.1 MB/s -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+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 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
Now I'm going to work with this package and check needed Pacemaker fixes. After that I'm going to propose both merges together. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+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 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
# For Ubuntu Bionic: Okay, after bisecting fence-scsi and monitoring all its functions I was able to isolate the patches that I need to take to bionic to make it compatible with existing version and, at the same time, operational: Note: all tests were conducted with Pacemaker v1.1.19-0ubuntu1 and this is not the default in Ubuntu Bionic. I have maintained "vanilla" Pacemaker v1.1.19 in order to better isolate all fixes for fence-agents. Now I'm able to create a fixed fence-agent package for Ubuntu Bionic AND fix Pacemaker. # Ubuntu Bionic SRU: Fence Agents v4.0.25 PLUS the following fixes/commits ordered by date: commit 81b8370844f5aecaee5e7178d82670c70399d824 Author: Oyvind Albrigtsen Date: Mon Jul 24 14:12:15 2017 fence_scsi: add FIPS support commit eae9d029b7073e7eb8c7ba4df9ec19b755a8f603 Author: Oyvind Albrigtsen Date: Wed Sep 27 12:26:38 2017 fix for ignored options commit c6f29a653114523e9ac3644aed958b4bb43f3b41 Author: Oyvind Albrigtsen Date: Wed Sep 27 12:42:39 2017 Maintain ABI compatibility for external agents commit 746fd55b061aa28b27aac5a1bb38714a95812592 Author: Reid Wahl Date: Fri Apr 6 18:31:30 2018 Low: fence_scsi: Remove period from cmd string commit bec154345d2291c9051c16277de9054387dc9707 Author: Oyvind Albrigtsen Date: Thu Apr 19 11:30:53 2018 fence_scsi: fix plug-parameter and keep support for nodename to avoid regressions commit 335aca4e54e4ec46b9b5d86ef30a7d9348e6a216 Author: Valentin Vidic Date: Wed May 23 12:51:23 2018 fence_scsi: fix python3 encoding error #206 commit f77297b654586bf539e78957f26cae1d22c6f081 Author: Oyvind Albrigtsen Date: Fri Nov 2 08:24:56 2018 fence_scsi: fix incorrect SCSI key when node ID is 10 or higher The last four digits of the SCSI key will be zero padded digit between -0009. commit 1c4a64ca803831b44c96c75022abe5bb8713cd1a Author: Oyvind Albrigtsen Date: Wed May 22 08:13:34 2019 fence_scsi: detect node ID using new format, and fallback to old format before failing -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+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 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
# Demonstration of fence_scsi agent working in Bionic: (k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo dpkg -i ./*.deb dpkg: warning: downgrading fence-agents from 4.4.0-2 to 4.0.25-2ubuntu1 (Reading database ... 85434 files and directories currently installed.) Preparing to unpack .../fence-agents_4.0.25-2ubuntu1_amd64.deb ... Unpacking fence-agents (4.0.25-2ubuntu1) over (4.4.0-2) ... Preparing to unpack .../fence-agents_4.4.0-2_amd64.deb ... Unpacking fence-agents (4.4.0-2) over (4.0.25-2ubuntu1) ... Setting up fence-agents (4.4.0-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... (k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo sg_persist --in --read-keys --device=/dev/sda LIO-ORG cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x0, there are NO registered reservation keys (k)rafaeldtinoco@clubionic01:~/.../upstream$ systemctl restart pacemaker (k)rafaeldtinoco@clubionic02:~/.../upstream$ crm_mon -1 Stack: corosync Current DC: clubionic03.private (version 1.1.19-1.1.19) - partition with quorum Last updated: Tue Mar 3 21:16:04 2020 Last change: Tue Mar 3 20:25:56 2020 by root via cibadmin on clubionic01.private 3 nodes configured 1 resource configured Online: [ clubionic01.private clubionic02.private clubionic03.private ] Active resources: fence_clubionic(stonith:fence_scsi): Started clubionic01.private (k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo sg_persist --in --read-keys --device=/dev/sda LIO-ORG cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x3, 3 registered reservation keys follow: 0x3abe 0x3abe0001 0x3abe0002 (k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo sg_persist -r /dev/sda LIO-ORG cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x3, Reservation follows: Key=0x3abe0001 scope: LU_SCOPE, type: Write Exclusive, registrants only -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865523 Title: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523/+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 1865511] Re: Clamav package should contain clamav-daemon
apt install clamav on eoan brings in: clamav clamav-base clamav-freshclam libclamav9 libltdl7 libtfm1 The freshclam daemon tries to download the databases right away: Tue Mar 3 20:01:42 2020 -> freshclam daemon 0.102.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) Tue Mar 3 20:01:42 2020 -> ClamAV update process started at Tue Mar 3 20:01:42 2020 Tue Mar 3 20:01:42 2020 -> daily database available for download (remote version: 25740) Tue Mar 3 20:02:12 2020 -> WARNING: Download failed (28) Tue Mar 3 20:02:12 2020 -> WARNING: Message: Timeout was reached Tue Mar 3 20:02:12 2020 -> WARNING: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd Tue Mar 3 20:02:12 2020 -> Trying again in 5 secs... While that is happening, clamscan won't work: root@e1:~# clamcsc^C root@e1:~# clamscan LibClamAV Error: cli_loaddbdir(): No supported database files found in /var/lib/clamav ERROR: Can't open file or directory Which is expected. It will keep trying. In my case, now it managed to download daily: Tue Mar 3 20:03:11 2020 -> Testing database: '/var/lib/clamav/tmp.3f047/clamav-323978c4ffb272b6b680262710a2e099.tmp-daily.cvd' ... Tue Mar 3 20:03:16 2020 -> Database test passed. Tue Mar 3 20:03:16 2020 -> daily.cvd updated (version: 25740, sigs: 2204413, f-level: 63, builder: raynman) And it's trying main again. That's a big file, over 100Mb in size. I believe that's why I'm getting timeouts, as I can't receive such a big file in 30s, which is the default ReceiveTimeout in /etc/clamav/freshclam.conf: ReceiveTimeout 30 Once I updated that to 300s, and restarted the freshclam daemon, it fetched the main database just fine: Tue Mar 3 20:08:15 2020 -> main database available for download (remote version: 59) Tue Mar 3 20:10:09 2020 -> Testing database: '/var/lib/clamav/tmp.393b2/clamav-bcd674e3559e38c5a502dfe72b8bf48c.tmp-main.cvd' ... Tue Mar 3 20:10:13 2020 -> Database test passed. Tue Mar 3 20:10:13 2020 -> main.cvd updated (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr) Tue Mar 3 20:10:13 2020 -> bytecode database available for download (remote version: 331) Tue Mar 3 20:10:15 2020 -> Testing database: '/var/lib/clamav/tmp.393b2/clamav-99166262d870f9b5d36574c18189bea1.tmp-bytecode.cvd' ... Tue Mar 3 20:10:15 2020 -> Database test passed. Tue Mar 3 20:10:15 2020 -> bytecode.cvd updated (version: 331, sigs: 94, f-level: 63, builder: anvilleg) Tue Mar 3 20:10:15 2020 -> ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf The last error about NotifyClamd is also expected, since I didn't install the clamd daemon. clamscan now works: root@e1:~# clamscan /root/.viminfo: OK /root/.profile: OK /root/.lesshst: OK /root/.bashrc: OK --- SCAN SUMMARY --- Known viruses: 6759121 Engine version: 0.102.2 Scanned directories: 1 Scanned files: 4 Infected files: 0 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 0.00:1) Time: 12.184 sec (0 m 12 s) Regarding this bug then: 1) clamav-data should no longer be mentioned in d/control indeed, as this package doesn't exist anymore. 2) clamav-freshclam could be made a bit better by increasing the ReceiveTimeout, but by how much I'm not sure. It depends on your internet connection. In my case, the main.cvd database was downloaded in about 2 minutes. Note that after this first download, only the dailies are necessary, which are much smaller. There is no need to install clamav-daemon to fix the above. It serves specific purposes, as outlined in its description. ** Summary changed: - Clamav package should contain clamav-daemon + Tweak freshclam ReceiveTimeout value for slow internet connections ** Changed in: clamav (Ubuntu) Status: New => Triaged ** Changed in: clamav (Ubuntu) Importance: Undecided => Low ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-3123 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1865511 Title: Tweak freshclam ReceiveTimeout value for slow internet connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1865511/+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 1865511] Re: Tweak freshclam ReceiveTimeout value for slow internet connections
Actually, looks like this was fixed already. The 30s ReceiveTimeout default value was being set in eoan's clamav-freshclam.postinst: [ -z "$ReceiveTimeout" ] && ReceiveTimeout=30 This was later changed to 0 in the package version 0.102.2+dfsg-1: clamav (0.102.2+dfsg-1) unstable; urgency=medium * Import 0.102.2 - CVE-2020-3123 (DoS may occur in the optional DLP feature) (Closes: 950944). * Update symbol file. * Set ReceiveTimeout to 0 which is upstream default. Which is in Ubuntu Focal. Therefore, this bug is fixed in that upcoming release. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1865511 Title: Tweak freshclam ReceiveTimeout value for slow internet connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1865511/+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 1865501] Re: libpcap-dev and derivatives missing libpcap.pc
This was fixed in 1.9.0-2: libpcap (1.9.0-2) unstable; urgency=medium [ Luca Boccassi ] * Install upstream pkg-config file (closes: #922219). Ubuntu Eoan (19.10) and later have this fix. I assume you are running disco or earlier. But those versions do not have the pc file in the upstream source code, as that was added just in version 1.9.0. So which ubuntu release are you running, and which version exactly of the libpcap packages do you have installed? ** Changed in: libpcap (Ubuntu) Status: New => Incomplete ** Bug watch added: github.com/the-tcpdump-group/libpcap/issues #374 https://github.com/the-tcpdump-group/libpcap/issues/374 ** Also affects: libpcap via https://github.com/the-tcpdump-group/libpcap/issues/374 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to libpcap in Ubuntu. https://bugs.launchpad.net/bugs/1865501 Title: libpcap-dev and derivatives missing libpcap.pc To manage notifications about this bug go to: https://bugs.launchpad.net/libpcap/+bug/1865501/+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 1864958] Re: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Setting the bug status to "incomplete" pending feedback from Lars' suggestions and requests. ** Changed in: mysql-8.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1864958 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1864958/+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 1833713] Re: Metadata is broken with dpdk bonding, jumbo frames and metadata from qdhcp
Does anybody know if upstream responded elsewhere? https://mail.openvswitch.org/pipermail/ovs-discuss/2019-July/048997.html shows no thread reply. Wouldn't it be best to open a bug instead? -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to dpdk in Ubuntu. https://bugs.launchpad.net/bugs/1833713 Title: Metadata is broken with dpdk bonding, jumbo frames and metadata from qdhcp To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1833713/+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 1863749] Re: NTRU Plugin Missing in Focal
We are past feature freeze, so this needs to become a Feature Freeze Exception bug if we still want this in focal. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1863749 Title: NTRU Plugin Missing in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1863749/+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
