How to upgrade the GLIBCXX and GLIBC to the specific version
Hi, Would you pls help give tips about how to upgrade the GLIBCXX and GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian? I am using the Raspberry Pi 4B with the Raspbian OS “Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux”, which is Debian based OS. When running a SW I met the problem missing the required versions of GLIBCXX and GLIBC, with the details below. root@raspberrypi:/home/bitmap_overlap/linux-aarch64# ./blueriver_bitmap_streamer ./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./blueriver_bitmap_streamer) ./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./blueriver_bitmap_streamer) ./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./blueriver_bitmap_streamer) ./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./blueriver_bitmap_streamer) root@raspberrypi:/home/bitmap_overlap/linux-aarch64# Thanks. Best Regards Diego To view our privacy policy, including the types of personal information we collect, process and share, and the rights and options you have in this respect, see www.semtech.com/legal.
Re: which package to file a bug report ?
Marco Moock: Am Fri, 23 Feb 2024 13:59:41 +0100 schrieb Frank Weißer : The installer does format it as ext4, but shows ext2 and places that in fstab, what ends up in emergency mode. That's why I'm here That is definitely a bug. So we are at my original question: Which package to file a bug report ? readU Frank
Re: Debian 12.5.0 amd64 and OpenZFS bug #15526
On Tue 27/02/2024 at 04:52, Gareth Evans wrote: > https://github.com/openzfs/zfs/issues/15933 > > seems to suggest that or a similar issue is still ongoing with Open ZFS > 2.2.3 ... I wonder if that might be a regression, since what I think is the same issue as openzfs #15526 appeared to be resolved in ZFS 2.2.2 "I've been unable to reproduce this after upgrading to zfs-2.2.2" https://bugs.gentoo.org/917224 I imagine openzfs problems (and solutions) are likely to be the same across distributions? Kind regards, G
Re: Reportbug Assisance
Am Mon, 26 Feb 2024 22:49:55 -0500 schrieb Tom : > I originally filed this bug with the KDE team, but they asked me to > file with Debian. There was a decent amount of discussion which I > will link here: https://bugs.kde.org/show_bug.cgi?id=481746. I need > to know how to file this bug. Will I be filing under a package or one > of the other categories? bugreport kinfocenter
Re: Debian 12.5.0 amd64 and OpenZFS bug #15526
Replied to OP by mistake, reposting to list. On Sun 25/02/2024 at 05:34, David Christensen wrote: > debian-user: > > Is Debian 12.5.0 amd64 affected by OpenZFS bug #15526? > > https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso > > https://packages.debian.org/bookworm/zfs-dkms > > https://github.com/openzfs/zfs/issues/15526 Hi David, Given the complexity of the issues, I'm not sure if this truly answers your question, but https://github.com/openzfs/zfs/issues/15933 seems to suggest that or a similar issue is still ongoing with Open ZFS 2.2.3, which is later than the version currently available from bookworm or bookworm-backports. It seems bookworm-backports might eventually provide the solution, if at all, per the Debian wiki on ZFS: "it is recommended by Debian ZFS on Linux Team to install ZFS related packages from Backports archive. Upstream stable patches will be tracked and compatibility is always maintained." https://wiki.debian.org/ZFS Currently: $ apt policy zfs-dkms zfs-dkms: Installed: 2.2.2-4~bpo12+1 Candidate: 2.2.2-4~bpo12+1 Version table: *** 2.2.2-4~bpo12+1 100 100 https://deb.debian.org/debian bookworm-backports/contrib amd64 Packages 100 https://deb.debian.org/debian bookworm-backports/contrib i386 Packages 100 /var/lib/dpkg/status 2.1.11-1 500 500 https://deb.debian.org/debian bookworm/contrib amd64 Packages 500 https://deb.debian.org/debian bookworm/contrib i386 Packages Hope that helps. Gareth
Re: SOLVED Re: Disk corruption and performance issue.
On Mon, 26 Feb 2024, Andy Smith wrote:
Hi,
On Mon, Feb 26, 2024 at 06:25:53PM +, Tim Woodall wrote:
Feb 17 17:01:49 xen17 vmunix: [3.802581] ata1.00: disabling queued TRIM
support
Feb 17 17:01:49 xen17 vmunix: [3.805074] ata1.00: disabling queued TRIM
support
from libata-core.c
{ "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM |
ATA_HORKAGE_NO_NCQ_ON_ATI },
This fixed the disk corruption errors at the cost of dramatically
reducing performance. (I'm not sure why because manual fstrim didn't
improve things)
That's interesting. I have quite a few of these drives and haven't
noticed any problems. What kernel version introduced the above
workarounds?
$ sudo lsblk -do NAME,MODEL
NAME MODEL
sda SAMSUNG_MZ7KM1T9HAJM-5
sdb SAMSUNG_MZ7KM1T9HAJM-5
sdc Samsung_SSD_870_EVO_4TB
sdd Samsung_SSD_870_EVO_4TB
sde ST4000LM016-1N2170
sdf ST4000LM016-1N2170
sdg SuperMicro_SSD
sdh SuperMicro_SSD
Thanks,
Andy
Looks like the fix was brand new around sept 2021
https://www.neowin.net/news/linux-patch-disables-trim-and-ncq-on-samsung-860870-ssds-in-intel-and-amd-systems/
I was still seeing corruption in August 2022 but it's possible the fix
wasn't backported to whatever release I was running.
Tim.
Reportbug Assisance
I originally filed this bug with the KDE team, but they asked me to file with Debian. There was a decent amount of discussion which I will link here: https://bugs.kde.org/show_bug.cgi?id=481746. I need to know how to file this bug. Will I be filing under a package or one of the other categories? Thanks
Re: running Jami in Trixie - possible locale issue
On Mon, Feb 26, 2024 at 10:10:45PM -0500, Gremlin wrote: > On 2/26/24 20:28, Gary Dale wrote: > > > > > > $locale > > > > > > locale: Cannot set LC_CTYPE to default locale: No such > > > > > > file or directory > > > > > > locale: Cannot set LC_MESSAGES to default locale: No > > > > > > such file or directory > > > > > > locale: Cannot set LC_ALL to default locale: No such file or > > > > > > directory > > > > > > LANG=iu_CA.UTF-8 > > > > > > LANGUAGE=en_GB > > > > > > LC_CTYPE="iu_CA.UTF-8" > > > > > > LC_NUMERIC=en_CA.UTF-8 > > > > > > LC_TIME=en_CA.UTF-8 > > > > > > LC_COLLATE=en_CA.UTF-8 > > > > > > LC_MONETARY=en_CA.UTF-8 > > > > > > LC_MESSAGES="iu_CA.UTF-8" > > > > > > LC_PAPER="iu_CA.UTF-8" > > > > > > LC_NAME="iu_CA.UTF-8" > > > > > > LC_ADDRESS="iu_CA.UTF-8" > > > > > > LC_TELEPHONE="iu_CA.UTF-8" > > > > > > LC_MEASUREMENT=en_CA.UTF-8 > > > > > > LC_IDENTIFICATION="iu_CA.UTF-8" > > > > > > LC_ALL= > > $locale -a > > locale: Cannot set LC_CTYPE to default locale: No such file or directory > > locale: Cannot set LC_MESSAGES to default locale: No such file or directory > > C > > C.utf8 > > en_CA.utf8 > > en_US.utf8 > > fr_CA.utf8 > > POSIX > > > > > > Find out where LC_CTYPE and LC_MESSAGES is being set, they need changed. No, you're not reading it correctly. Look at LANG. Look at the double quotes around LC_CTYPE and LC_MESSAGES (among others). LC_CTYPE and LC_MESSAGES are *not* set. They are deduced from LANG. It's LANG that has the weird setting. All of the other iu_CA entries are double-quoted, so they are derived from it. > If it was me, I would set /etc/default/locale to > # File generated by update-locale > LANG=C.UTF-8 > > and remove all references/assignments to any LC_ in all shell > config files. > > then reboot and do a locale -a Rebooting doesn't do anything useful here. Simply logging out and back in would be sufficient. But there are two points of view here: 1) Why is Gary using locales that are not generated? 2) Why is Gary using *these specific* locales? I think you're approaching it from the point of view of "your settings are wrong, but you don't know where the settings are coming from, so find out, and fix them". Which is one valid POV. Another valid POV is "the settings are set the way Gary wants them, but the locales aren't generated, so generate them, and then it'll work". Only Gary can tell us which of these is the right approach. Maybe he's a fluent Inuktitut speaker. All I can say is that it's hard to believe that someone would *accidentally* have LANG set to iu_CA.UTF-8. Usually that's the kind of thing one would remember doing.
Re: running Jami in Trixie - possible locale issue
On 2/26/24 20:28, Gary Dale wrote: On 2024-02-26 17:31, Gremlin wrote: On 2/26/24 17:18, Gary Dale wrote: On 2024-02-26 16:03, Gremlin wrote: On 2/26/24 14:36, Gary Dale wrote: I'm running Debian/Trixie on an AMD64 system. I've installed jami from testing but it fails to start. When I run it from the command line, I get: $jami & [1] 7804 $ Using Qt runtime version: 6. 4.2 "notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2" "Using locale: en_GB" terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid [1]+ Aborted (core dumped) jami garydale@transponder:~/mnt/archives/2024/Lions Cl There might be something wrong with my locales but dpkg-reconfigure locales doesn't fix it. After running it, I still get this output: $locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=iu_CA.UTF-8 LANGUAGE=en_GB LC_CTYPE="iu_CA.UTF-8" LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=en_CA.UTF-8 LC_MESSAGES="iu_CA.UTF-8" LC_PAPER="iu_CA.UTF-8" LC_NAME="iu_CA.UTF-8" LC_ADDRESS="iu_CA.UTF-8" LC_TELEPHONE="iu_CA.UTF-8" LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION="iu_CA.UTF-8" LC_ALL= Please note that I have not selected iu_CA.utf8 nor en_GB in my locales. Any ideas on how to fix this? Thanks. Edit /etc/locale.gen and enable the locale(s) you wish to use. Then as root locale-gen dpkg-reconfigure locales Nope. /etc/locale.gen was already correct. Running the commands then rebooting leaves me with the same error messages. I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that also had no effect. The exact contents are: LANG="en_CA.UTF-8" export LANG You are making a mess, when about to make a mess stop until you have researched your issue. Start at the beginning not at the end.. Did you reboot or logout and login dpkg-reconfigure locales is suppose to set /etc/default/locales correctly, it runs update-locale if I remember correctly. cat /etc/locale.gen # This file lists locales that you wish to have built. You can find a list # of valid supported locales at /usr/share/i18n/SUPPORTED, and you can add # user defined locales to /usr/local/share/i18n/SUPPORTED. If you change # this file, you need to rerun locale-gen. # C.UTF-8 UTF-8 # aa_DJ ISO-8859-1 # aa_DJ.UTF-8 UTF-8 # aa_ER UTF-8 # aa_ER@saaho UTF-8 # aa_ET UTF-8 # af_ZA ISO-8859-1 # af_ZA.UTF-8 UTF-8 # agr_PE UTF-8 # ak_GH UTF-8 # am_ET UTF-8 # an_ES ISO-8859-15 # an_ES.UTF-8 UTF-8 # anp_IN UTF-8 # ar_AE ISO-8859-6 # ar_AE.UTF-8 UTF-8 # ar_BH ISO-8859-6 # ar_BH.UTF-8 UTF-8 # ar_DZ ISO-8859-6 # ar_DZ.UTF-8 UTF-8 # ar_EG ISO-8859-6 # ar_EG.UTF-8 UTF-8 # ar_IN UTF-8 # ar_IQ ISO-8859-6 # ar_IQ.UTF-8 UTF-8 # ar_JO ISO-8859-6 # ar_JO.UTF-8 UTF-8 # ar_KW ISO-8859-6 # ar_KW.UTF-8 UTF-8 # ar_LB ISO-8859-6 # ar_LB.UTF-8 UTF-8 # ar_LY ISO-8859-6 # ar_LY.UTF-8 UTF-8 # ar_MA ISO-8859-6 # ar_MA.UTF-8 UTF-8 # ar_OM ISO-8859-6 # ar_OM.UTF-8 UTF-8 # ar_QA ISO-8859-6 # ar_QA.UTF-8 UTF-8 # ar_SA ISO-8859-6 # ar_SA.UTF-8 UTF-8 # ar_SD ISO-8859-6 # ar_SD.UTF-8 UTF-8 # ar_SS UTF-8 # ar_SY ISO-8859-6 # ar_SY.UTF-8 UTF-8 # ar_TN ISO-8859-6 # ar_TN.UTF-8 UTF-8 # ar_YE ISO-8859-6 # ar_YE.UTF-8 UTF-8 # as_IN UTF-8 # ast_ES ISO-8859-15 # ast_ES.UTF-8 UTF-8 # ayc_PE UTF-8 # az_AZ UTF-8 # az_IR UTF-8 # be_BY CP1251 # be_BY.UTF-8 UTF-8 # be_BY@latin UTF-8 # bem_ZM UTF-8 # ber_DZ UTF-8 # ber_MA UTF-8 # bg_BG CP1251 # bg_BG.UTF-8 UTF-8 # bhb_IN.UTF-8 UTF-8 # bho_IN UTF-8 # bho_NP UTF-8 # bi_VU UTF-8 # bn_BD UTF-8 # bn_IN UTF-8 # bo_CN UTF-8 # bo_IN UTF-8 # br_FR ISO-8859-1 # br_FR.UTF-8 UTF-8 # br_FR@euro ISO-8859-15 # brx_IN UTF-8 # bs_BA ISO-8859-2 # bs_BA.UTF-8 UTF-8 # byn_ER UTF-8 # ca_AD ISO-8859-15 # ca_AD.UTF-8 UTF-8 # ca_ES ISO-8859-1 # ca_ES.UTF-8 UTF-8 # ca_ES@euro ISO-8859-15 # ca_ES@valencia UTF-8 # ca_FR ISO-8859-15 # ca_FR.UTF-8 UTF-8 # ca_IT ISO-8859-15 # ca_IT.UTF-8 UTF-8 # ce_RU UTF-8 # chr_US UTF-8 # ckb_IQ UTF-8 # cmn_TW UTF-8 # crh_UA UTF-8 # cs_CZ ISO-8859-2 # cs_CZ.UTF-8 UTF-8 # csb_PL UTF-8 # cv_RU UTF-8 # cy_GB ISO-8859-14 # cy_GB.UTF-8 UTF-8 # da_DK ISO-8859-1 # da_DK.UTF-8 UTF-8 # de_AT ISO-8859-1 # de_AT.UTF-8 UTF-8 # de_AT@euro ISO-8859-15 # de_BE ISO-8859-1 # de_BE.UTF-8 UTF-8 # de_BE@euro ISO-8859-15 # de_CH ISO-8859-1 # de_CH.UTF-8 UTF-8 # de_DE ISO-8859-1 # de_DE.UTF-8 UTF-8 # de_DE@euro ISO-8859-15 # de_IT ISO-8859-1 # de_IT.UTF-8 UTF-8 # de_LI.UTF-8 UTF-8 # de_LU ISO-8859-1 # de_LU.UTF-8 UTF-8 # de_LU@euro ISO-8859-15 # doi_IN UTF-8 # dsb_DE UTF-8 # dv_MV UTF-8 # dz_BT UTF-8 # el_CY ISO-8859-7 # el_CY.UTF-8 UTF-8 # el_GR ISO-8859-7 # el_GR.UTF-8 UTF-8 # el_GR@euro ISO-8859-7 # en_AG UTF-8 # en_AU ISO-8859-1 # en_AU.UTF-8 UTF-8 # en_BW ISO-8859-1 # en_BW.UTF-8 UTF-8 # en_CA ISO-8859-1 # en_CA.UTF-8
Re: running Jami in Trixie - possible locale issue
On 27/02/2024 08:28, Gary Dale wrote: $locale -a locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory What desktop environment do you use? Have you checked its settings? Did you choose locale in your display manager (in login dialog)? Inspect actual environment env | grep 'LC_\|LANG' systemctl --user show-environment | grep 'LC_\|LANG'
Re: running Jami in Trixie - possible locale issue
On Mon, Feb 26, 2024 at 08:28:01PM -0500, Gary Dale wrote: > > > > > $locale > > > > > locale: Cannot set LC_CTYPE to default locale: No such file > > > > > or directory > > > > > locale: Cannot set LC_MESSAGES to default locale: No such > > > > > file or directory > > > > > locale: Cannot set LC_ALL to default locale: No such file or directory > > > > > LANG=iu_CA.UTF-8 > > > > > LANGUAGE=en_GB > > > > > LC_CTYPE="iu_CA.UTF-8" > > > > > LC_NUMERIC=en_CA.UTF-8 > > > > > LC_TIME=en_CA.UTF-8 > > > > > LC_COLLATE=en_CA.UTF-8 > > > > > LC_MONETARY=en_CA.UTF-8 > > > > > LC_MESSAGES="iu_CA.UTF-8" > > > > > LC_PAPER="iu_CA.UTF-8" > > > > > LC_NAME="iu_CA.UTF-8" > > > > > LC_ADDRESS="iu_CA.UTF-8" > > > > > LC_TELEPHONE="iu_CA.UTF-8" > > > > > LC_MEASUREMENT=en_CA.UTF-8 > > > > > LC_IDENTIFICATION="iu_CA.UTF-8" > > > > > LC_ALL= You've got three different locales mentioned here: iu_CA.UTF-8 en_GB en_CA.UTF-8 > # locale -a > C > C.utf8 > en_CA.utf8 > en_US.utf8 > fr_CA.utf8 > POSIX Out of the three that you're trying to use, only one has been generated. Either generate the two that you're missing, or stop using them.
Re: running Jami in Trixie - possible locale issue
On 2024-02-26 17:31, Gremlin wrote: On 2/26/24 17:18, Gary Dale wrote: On 2024-02-26 16:03, Gremlin wrote: On 2/26/24 14:36, Gary Dale wrote: I'm running Debian/Trixie on an AMD64 system. I've installed jami from testing but it fails to start. When I run it from the command line, I get: $jami & [1] 7804 $ Using Qt runtime version: 6. 4.2 "notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2" "Using locale: en_GB" terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid [1]+ Aborted (core dumped) jami garydale@transponder:~/mnt/archives/2024/Lions Cl There might be something wrong with my locales but dpkg-reconfigure locales doesn't fix it. After running it, I still get this output: $locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=iu_CA.UTF-8 LANGUAGE=en_GB LC_CTYPE="iu_CA.UTF-8" LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=en_CA.UTF-8 LC_MESSAGES="iu_CA.UTF-8" LC_PAPER="iu_CA.UTF-8" LC_NAME="iu_CA.UTF-8" LC_ADDRESS="iu_CA.UTF-8" LC_TELEPHONE="iu_CA.UTF-8" LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION="iu_CA.UTF-8" LC_ALL= Please note that I have not selected iu_CA.utf8 nor en_GB in my locales. Any ideas on how to fix this? Thanks. Edit /etc/locale.gen and enable the locale(s) you wish to use. Then as root locale-gen dpkg-reconfigure locales Nope. /etc/locale.gen was already correct. Running the commands then rebooting leaves me with the same error messages. I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that also had no effect. The exact contents are: LANG="en_CA.UTF-8" export LANG You are making a mess, when about to make a mess stop until you have researched your issue. Start at the beginning not at the end.. Did you reboot or logout and login dpkg-reconfigure locales is suppose to set /etc/default/locales correctly, it runs update-locale if I remember correctly. cat /etc/locale.gen # This file lists locales that you wish to have built. You can find a list # of valid supported locales at /usr/share/i18n/SUPPORTED, and you can add # user defined locales to /usr/local/share/i18n/SUPPORTED. If you change # this file, you need to rerun locale-gen. # C.UTF-8 UTF-8 # aa_DJ ISO-8859-1 # aa_DJ.UTF-8 UTF-8 # aa_ER UTF-8 # aa_ER@saaho UTF-8 # aa_ET UTF-8 # af_ZA ISO-8859-1 # af_ZA.UTF-8 UTF-8 # agr_PE UTF-8 # ak_GH UTF-8 # am_ET UTF-8 # an_ES ISO-8859-15 # an_ES.UTF-8 UTF-8 # anp_IN UTF-8 # ar_AE ISO-8859-6 # ar_AE.UTF-8 UTF-8 # ar_BH ISO-8859-6 # ar_BH.UTF-8 UTF-8 # ar_DZ ISO-8859-6 # ar_DZ.UTF-8 UTF-8 # ar_EG ISO-8859-6 # ar_EG.UTF-8 UTF-8 # ar_IN UTF-8 # ar_IQ ISO-8859-6 # ar_IQ.UTF-8 UTF-8 # ar_JO ISO-8859-6 # ar_JO.UTF-8 UTF-8 # ar_KW ISO-8859-6 # ar_KW.UTF-8 UTF-8 # ar_LB ISO-8859-6 # ar_LB.UTF-8 UTF-8 # ar_LY ISO-8859-6 # ar_LY.UTF-8 UTF-8 # ar_MA ISO-8859-6 # ar_MA.UTF-8 UTF-8 # ar_OM ISO-8859-6 # ar_OM.UTF-8 UTF-8 # ar_QA ISO-8859-6 # ar_QA.UTF-8 UTF-8 # ar_SA ISO-8859-6 # ar_SA.UTF-8 UTF-8 # ar_SD ISO-8859-6 # ar_SD.UTF-8 UTF-8 # ar_SS UTF-8 # ar_SY ISO-8859-6 # ar_SY.UTF-8 UTF-8 # ar_TN ISO-8859-6 # ar_TN.UTF-8 UTF-8 # ar_YE ISO-8859-6 # ar_YE.UTF-8 UTF-8 # as_IN UTF-8 # ast_ES ISO-8859-15 # ast_ES.UTF-8 UTF-8 # ayc_PE UTF-8 # az_AZ UTF-8 # az_IR UTF-8 # be_BY CP1251 # be_BY.UTF-8 UTF-8 # be_BY@latin UTF-8 # bem_ZM UTF-8 # ber_DZ UTF-8 # ber_MA UTF-8 # bg_BG CP1251 # bg_BG.UTF-8 UTF-8 # bhb_IN.UTF-8 UTF-8 # bho_IN UTF-8 # bho_NP UTF-8 # bi_VU UTF-8 # bn_BD UTF-8 # bn_IN UTF-8 # bo_CN UTF-8 # bo_IN UTF-8 # br_FR ISO-8859-1 # br_FR.UTF-8 UTF-8 # br_FR@euro ISO-8859-15 # brx_IN UTF-8 # bs_BA ISO-8859-2 # bs_BA.UTF-8 UTF-8 # byn_ER UTF-8 # ca_AD ISO-8859-15 # ca_AD.UTF-8 UTF-8 # ca_ES ISO-8859-1 # ca_ES.UTF-8 UTF-8 # ca_ES@euro ISO-8859-15 # ca_ES@valencia UTF-8 # ca_FR ISO-8859-15 # ca_FR.UTF-8 UTF-8 # ca_IT ISO-8859-15 # ca_IT.UTF-8 UTF-8 # ce_RU UTF-8 # chr_US UTF-8 # ckb_IQ UTF-8 # cmn_TW UTF-8 # crh_UA UTF-8 # cs_CZ ISO-8859-2 # cs_CZ.UTF-8 UTF-8 # csb_PL UTF-8 # cv_RU UTF-8 # cy_GB ISO-8859-14 # cy_GB.UTF-8 UTF-8 # da_DK ISO-8859-1 # da_DK.UTF-8 UTF-8 # de_AT ISO-8859-1 # de_AT.UTF-8 UTF-8 # de_AT@euro ISO-8859-15 # de_BE ISO-8859-1 # de_BE.UTF-8 UTF-8 # de_BE@euro ISO-8859-15 # de_CH ISO-8859-1 # de_CH.UTF-8 UTF-8 # de_DE ISO-8859-1 # de_DE.UTF-8 UTF-8 # de_DE@euro ISO-8859-15 # de_IT ISO-8859-1 # de_IT.UTF-8 UTF-8 # de_LI.UTF-8 UTF-8 # de_LU ISO-8859-1 # de_LU.UTF-8 UTF-8 # de_LU@euro ISO-8859-15 # doi_IN UTF-8 # dsb_DE UTF-8 # dv_MV UTF-8 # dz_BT UTF-8 # el_CY ISO-8859-7 # el_CY.UTF-8 UTF-8 # el_GR ISO-8859-7 # el_GR.UTF-8 UTF-8 # el_GR@euro ISO-8859-7 # en_AG UTF-8 # en_AU ISO-8859-1 # en_AU.UTF-8 UTF-8 # en_BW ISO-8859-1 # en_BW.UTF-8 UTF-8 # en_CA ISO-8859-1 # en_CA.UTF-8 UTF-8 # en_DK ISO-8859-1 #
Re: SOLVED Re: Disk corruption and performance issue.
Hi,
On Mon, Feb 26, 2024 at 06:25:53PM +, Tim Woodall wrote:
> Feb 17 17:01:49 xen17 vmunix: [3.802581] ata1.00: disabling queued TRIM
> support
> Feb 17 17:01:49 xen17 vmunix: [3.805074] ata1.00: disabling queued TRIM
> support
>
>
> from libata-core.c
>
> { "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
> ATA_HORKAGE_ZERO_AFTER_TRIM |
> ATA_HORKAGE_NO_NCQ_ON_ATI },
>
> This fixed the disk corruption errors at the cost of dramatically
> reducing performance. (I'm not sure why because manual fstrim didn't
> improve things)
That's interesting. I have quite a few of these drives and haven't
noticed any problems. What kernel version introduced the above
workarounds?
$ sudo lsblk -do NAME,MODEL
NAME MODEL
sda SAMSUNG_MZ7KM1T9HAJM-5
sdb SAMSUNG_MZ7KM1T9HAJM-5
sdc Samsung_SSD_870_EVO_4TB
sdd Samsung_SSD_870_EVO_4TB
sde ST4000LM016-1N2170
sdf ST4000LM016-1N2170
sdg SuperMicro_SSD
sdh SuperMicro_SSD
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Re: running Jami in Trixie - possible locale issue
On 2/26/24 17:18, Gary Dale wrote: On 2024-02-26 16:03, Gremlin wrote: On 2/26/24 14:36, Gary Dale wrote: I'm running Debian/Trixie on an AMD64 system. I've installed jami from testing but it fails to start. When I run it from the command line, I get: $jami & [1] 7804 $ Using Qt runtime version: 6. 4.2 "notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2" "Using locale: en_GB" terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid [1]+ Aborted (core dumped) jami garydale@transponder:~/mnt/archives/2024/Lions Cl There might be something wrong with my locales but dpkg-reconfigure locales doesn't fix it. After running it, I still get this output: $locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=iu_CA.UTF-8 LANGUAGE=en_GB LC_CTYPE="iu_CA.UTF-8" LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=en_CA.UTF-8 LC_MESSAGES="iu_CA.UTF-8" LC_PAPER="iu_CA.UTF-8" LC_NAME="iu_CA.UTF-8" LC_ADDRESS="iu_CA.UTF-8" LC_TELEPHONE="iu_CA.UTF-8" LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION="iu_CA.UTF-8" LC_ALL= Please note that I have not selected iu_CA.utf8 nor en_GB in my locales. Any ideas on how to fix this? Thanks. Edit /etc/locale.gen and enable the locale(s) you wish to use. Then as root locale-gen dpkg-reconfigure locales Nope. /etc/locale.gen was already correct. Running the commands then rebooting leaves me with the same error messages. I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that also had no effect. The exact contents are: LANG="en_CA.UTF-8" export LANG You are making a mess, when about to make a mess stop until you have researched your issue. Start at the beginning not at the end.. Did you reboot or logout and login dpkg-reconfigure locales is suppose to set /etc/default/locales correctly, it runs update-locale if I remember correctly. cat /etc/locale.gen # This file lists locales that you wish to have built. You can find a list # of valid supported locales at /usr/share/i18n/SUPPORTED, and you can add # user defined locales to /usr/local/share/i18n/SUPPORTED. If you change # this file, you need to rerun locale-gen. # C.UTF-8 UTF-8 # aa_DJ ISO-8859-1 # aa_DJ.UTF-8 UTF-8 # aa_ER UTF-8 # aa_ER@saaho UTF-8 # aa_ET UTF-8 # af_ZA ISO-8859-1 # af_ZA.UTF-8 UTF-8 # agr_PE UTF-8 # ak_GH UTF-8 # am_ET UTF-8 # an_ES ISO-8859-15 # an_ES.UTF-8 UTF-8 # anp_IN UTF-8 # ar_AE ISO-8859-6 # ar_AE.UTF-8 UTF-8 # ar_BH ISO-8859-6 # ar_BH.UTF-8 UTF-8 # ar_DZ ISO-8859-6 # ar_DZ.UTF-8 UTF-8 # ar_EG ISO-8859-6 # ar_EG.UTF-8 UTF-8 # ar_IN UTF-8 # ar_IQ ISO-8859-6 # ar_IQ.UTF-8 UTF-8 # ar_JO ISO-8859-6 # ar_JO.UTF-8 UTF-8 # ar_KW ISO-8859-6 # ar_KW.UTF-8 UTF-8 # ar_LB ISO-8859-6 # ar_LB.UTF-8 UTF-8 # ar_LY ISO-8859-6 # ar_LY.UTF-8 UTF-8 # ar_MA ISO-8859-6 # ar_MA.UTF-8 UTF-8 # ar_OM ISO-8859-6 # ar_OM.UTF-8 UTF-8 # ar_QA ISO-8859-6 # ar_QA.UTF-8 UTF-8 # ar_SA ISO-8859-6 # ar_SA.UTF-8 UTF-8 # ar_SD ISO-8859-6 # ar_SD.UTF-8 UTF-8 # ar_SS UTF-8 # ar_SY ISO-8859-6 # ar_SY.UTF-8 UTF-8 # ar_TN ISO-8859-6 # ar_TN.UTF-8 UTF-8 # ar_YE ISO-8859-6 # ar_YE.UTF-8 UTF-8 # as_IN UTF-8 # ast_ES ISO-8859-15 # ast_ES.UTF-8 UTF-8 # ayc_PE UTF-8 # az_AZ UTF-8 # az_IR UTF-8 # be_BY CP1251 # be_BY.UTF-8 UTF-8 # be_BY@latin UTF-8 # bem_ZM UTF-8 # ber_DZ UTF-8 # ber_MA UTF-8 # bg_BG CP1251 # bg_BG.UTF-8 UTF-8 # bhb_IN.UTF-8 UTF-8 # bho_IN UTF-8 # bho_NP UTF-8 # bi_VU UTF-8 # bn_BD UTF-8 # bn_IN UTF-8 # bo_CN UTF-8 # bo_IN UTF-8 # br_FR ISO-8859-1 # br_FR.UTF-8 UTF-8 # br_FR@euro ISO-8859-15 # brx_IN UTF-8 # bs_BA ISO-8859-2 # bs_BA.UTF-8 UTF-8 # byn_ER UTF-8 # ca_AD ISO-8859-15 # ca_AD.UTF-8 UTF-8 # ca_ES ISO-8859-1 # ca_ES.UTF-8 UTF-8 # ca_ES@euro ISO-8859-15 # ca_ES@valencia UTF-8 # ca_FR ISO-8859-15 # ca_FR.UTF-8 UTF-8 # ca_IT ISO-8859-15 # ca_IT.UTF-8 UTF-8 # ce_RU UTF-8 # chr_US UTF-8 # ckb_IQ UTF-8 # cmn_TW UTF-8 # crh_UA UTF-8 # cs_CZ ISO-8859-2 # cs_CZ.UTF-8 UTF-8 # csb_PL UTF-8 # cv_RU UTF-8 # cy_GB ISO-8859-14 # cy_GB.UTF-8 UTF-8 # da_DK ISO-8859-1 # da_DK.UTF-8 UTF-8 # de_AT ISO-8859-1 # de_AT.UTF-8 UTF-8 # de_AT@euro ISO-8859-15 # de_BE ISO-8859-1 # de_BE.UTF-8 UTF-8 # de_BE@euro ISO-8859-15 # de_CH ISO-8859-1 # de_CH.UTF-8 UTF-8 # de_DE ISO-8859-1 # de_DE.UTF-8 UTF-8 # de_DE@euro ISO-8859-15 # de_IT ISO-8859-1 # de_IT.UTF-8 UTF-8 # de_LI.UTF-8 UTF-8 # de_LU ISO-8859-1 # de_LU.UTF-8 UTF-8 # de_LU@euro ISO-8859-15 # doi_IN UTF-8 # dsb_DE UTF-8 # dv_MV UTF-8 # dz_BT UTF-8 # el_CY ISO-8859-7 # el_CY.UTF-8 UTF-8 # el_GR ISO-8859-7 # el_GR.UTF-8 UTF-8 # el_GR@euro ISO-8859-7 # en_AG UTF-8 # en_AU ISO-8859-1 # en_AU.UTF-8 UTF-8 # en_BW ISO-8859-1 # en_BW.UTF-8 UTF-8 # en_CA ISO-8859-1 # en_CA.UTF-8 UTF-8 # en_DK ISO-8859-1 # en_DK.ISO-8859-15 ISO-8859-15 # en_DK.UTF-8 UTF-8 #
Re: running Jami in Trixie - possible locale issue
On 2024-02-26 16:03, Gremlin wrote: On 2/26/24 14:36, Gary Dale wrote: I'm running Debian/Trixie on an AMD64 system. I've installed jami from testing but it fails to start. When I run it from the command line, I get: $jami & [1] 7804 $ Using Qt runtime version: 6. 4.2 "notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2" "Using locale: en_GB" terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid [1]+ Aborted (core dumped) jami garydale@transponder:~/mnt/archives/2024/Lions Cl There might be something wrong with my locales but dpkg-reconfigure locales doesn't fix it. After running it, I still get this output: $locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=iu_CA.UTF-8 LANGUAGE=en_GB LC_CTYPE="iu_CA.UTF-8" LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=en_CA.UTF-8 LC_MESSAGES="iu_CA.UTF-8" LC_PAPER="iu_CA.UTF-8" LC_NAME="iu_CA.UTF-8" LC_ADDRESS="iu_CA.UTF-8" LC_TELEPHONE="iu_CA.UTF-8" LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION="iu_CA.UTF-8" LC_ALL= Please note that I have not selected iu_CA.utf8 nor en_GB in my locales. Any ideas on how to fix this? Thanks. Edit /etc/locale.gen and enable the locale(s) you wish to use. Then as root locale-gen dpkg-reconfigure locales Nope. /etc/locale.gen was already correct. Running the commands then rebooting leaves me with the same error messages. I also set up a ~/.bash_profile to set LANG to en_CA.UTF-8 but that also had no effect. The exact contents are: LANG="en_CA.UTF-8" export LANG
Re: medically smart watches
On Sunday 25 February 2024 06:33:26 pm gene heskett wrote: > On 2/25/24 14:19, Roy J. Tellason, Sr. wrote: > > On Sunday 25 February 2024 05:16:21 am gene heskett wrote: > >> I have no idea how many EE's there are here in the states, > >> 10,000+ probably. There are only around 130 CET's. > > > > More than that. My certificate number is PA-230... > > Mine is NB-116, so they must go by state, NB being Nebraska. Assuming an > average of 150/state, that would be 7500 of us. Where the heck are they > hiding? You are the only other one I have met since I got mine in '72. > Something doesn't add up. > > Cheers, Gene Heskett, CET. Dunno, maybe ask ISCET? (Apologies to the rest of you guys for the OT...) -- Member of the toughest, meanest, deadliest, most unrelenting -- and ablest -- form of life in this section of space, a critter that can be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters" - Information is more dangerous than cannon to a society ruled by lies. --James M Dakin
Re: SOLVED Re: Disk corruption and performance issue.
>>> You should not be running trim in a container/virtual machine >> Why not? That's, in my case, basically saying "you should not be running >> trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like >> to understand why. Enabling thin_provisioning and fstrim works and gets >> mapped to the underlying layers all the way down to the SSD. > > I guest you didn't understand the systemd timer that runs fstrim on > the host. How can the host properly run `fstrim` if it only sees a disk image and may not know how that image is divided into partitions/filesystems? Stefan
Re: SOLVED Re: Disk corruption and performance issue.
On 2/26/24 16:31, Tim Woodall wrote: On Mon, 26 Feb 2024, Gremlin wrote: re running fstrim in a vm. The Host system takes care of it I guess you've no idea what iscsi is. Because this makes no sense at all. systemd or no systemd. The physical disk doesn't have to be something the host system knows anything about. Here's a thread of someone wanting to do fstrim from a vm with iscsi mounted disks. https://serverfault.com/questions/1031580/trim-unmap-zvol-over-iscsi And another page suggesting you should. https://gist.github.com/hostberg/86bfaa81e50cc0666f1745e1897c0a56 8.10.2. Trim/Discard It is good practice to run fstrim (discard) regularly on VMs and containers. This releases data blocks that the filesystem isn't using anymore. It reduces data usage and resource load. Most modern operating systems issue such discard commands to their disks regularly. You only need to ensure that the Virtual Machines enable the disk discard option. I would guess that if you use sparse file backed storage to a vm you'd want the vm to run fstrim too but this isn't a setup I've ever used so perhaps it's nonsense. Never mind, arguing with me will not solve your issue.
Re: SOLVED Re: Disk corruption and performance issue.
On Mon, 26 Feb 2024, Gremlin wrote: re running fstrim in a vm. The Host system takes care of it I guess you've no idea what iscsi is. Because this makes no sense at all. systemd or no systemd. The physical disk doesn't have to be something the host system knows anything about. Here's a thread of someone wanting to do fstrim from a vm with iscsi mounted disks. https://serverfault.com/questions/1031580/trim-unmap-zvol-over-iscsi And another page suggesting you should. https://gist.github.com/hostberg/86bfaa81e50cc0666f1745e1897c0a56 8.10.2. Trim/Discard It is good practice to run fstrim (discard) regularly on VMs and containers. This releases data blocks that the filesystem isn't using anymore. It reduces data usage and resource load. Most modern operating systems issue such discard commands to their disks regularly. You only need to ensure that the Virtual Machines enable the disk discard option. I would guess that if you use sparse file backed storage to a vm you'd want the vm to run fstrim too but this isn't a setup I've ever used so perhaps it's nonsense.
Re: running Jami in Trixie - possible locale issue
On 2/26/24 14:36, Gary Dale wrote: I'm running Debian/Trixie on an AMD64 system. I've installed jami from testing but it fails to start. When I run it from the command line, I get: $jami & [1] 7804 $ Using Qt runtime version: 6. 4.2 "notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2" "Using locale: en_GB" terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid [1]+ Aborted (core dumped) jami garydale@transponder:~/mnt/archives/2024/Lions Cl There might be something wrong with my locales but dpkg-reconfigure locales doesn't fix it. After running it, I still get this output: $locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=iu_CA.UTF-8 LANGUAGE=en_GB LC_CTYPE="iu_CA.UTF-8" LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=en_CA.UTF-8 LC_MESSAGES="iu_CA.UTF-8" LC_PAPER="iu_CA.UTF-8" LC_NAME="iu_CA.UTF-8" LC_ADDRESS="iu_CA.UTF-8" LC_TELEPHONE="iu_CA.UTF-8" LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION="iu_CA.UTF-8" LC_ALL= Please note that I have not selected iu_CA.utf8 nor en_GB in my locales. Any ideas on how to fix this? Thanks. Edit /etc/locale.gen and enable the locale(s) you wish to use. Then as root locale-gen dpkg-reconfigure locales
Re: SOLVED Re: Disk corruption and performance issue.
On 2/26/24 14:40, Tim Woodall wrote: On Mon, 26 Feb 2024, Gremlin wrote: Are you using systemd ? No, I'm not You should not be running trim in a container/virtual machine Why not? That's, in my case, basically saying "you should not be running trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like to understand why. Enabling thin_provisioning and fstrim works and gets mapped to the underlying layers all the way down to the SSD. I guest you didn't understand the systemd timer that runs fstrim on the host. My underlying VG is less than 50% occupied, so I can trim the free space by creating a LV and then removing it again (I have issue_discards set) FWIW, I did issue fstrim in the VMs with no visible issues at all. Perhaps I got lucky? Here is some info: https://wiki.archlinux.org/title/Solid_state_drive I don't see VM or virtual machine anywhere on that page. Exactly, and you should not be running it in a VM/container. Which BTW systemd will not run fstrim in a container. The Host system takes care of it Well you can keep shooting yourself in the butt as long as you wish, I on the other hand tend not to do that as much I possibly can as I need to be able to set down at times.
Re: medically smart watches
>> Well, I was merely hoping that someone might finally have come up >> with a working solution ... > Stop smoking, lose weight, have a healthy diet and exercise. And most importantly: be lucky! Stefan
Re: medically smart watches
On Mon, Feb 26, 2024 at 2:47 PM hw wrote: > > Well, I was merely hoping that someone might finally have come up with > a working solution ... Stop smoking, lose weight, have a healthy diet and exercise. Jeff > On Mon, 2024-02-26 at 13:07 +, Andy Smith wrote: > > Hi, > > > > On Mon, Feb 26, 2024 at 12:24:34PM +0100, hw wrote: > > > How does the watch you got measure blood sugar? Doesn't that require > > > a blood sample? > > > > Some of them claim to extrapolate it from sweat, others claim to be > > able to estimate it from shining near-infrared at the blood vessels > > that are near the surface. Neither method has yet proven to be > > accurate, which is why they aren't certified as a medical device in > > UK. > > > > You can learn all about it by searching "non-invasive blood glucose > > monitoring"
Re: SOLVED Re: Disk corruption and performance issue.
On Mon, 26 Feb 2024, Gremlin wrote: Are you using systemd ? No, I'm not You should not be running trim in a container/virtual machine Why not? That's, in my case, basically saying "you should not be running trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like to understand why. Enabling thin_provisioning and fstrim works and gets mapped to the underlying layers all the way down to the SSD. My underlying VG is less than 50% occupied, so I can trim the free space by creating a LV and then removing it again (I have issue_discards set) FWIW, I did issue fstrim in the VMs with no visible issues at all. Perhaps I got lucky? Here is some info: https://wiki.archlinux.org/title/Solid_state_drive I don't see VM or virtual machine anywhere on that page.
running Jami in Trixie - possible locale issue
I'm running Debian/Trixie on an AMD64 system. I've installed jami from testing but it fails to start. When I run it from the command line, I get: $jami & [1] 7804 $ Using Qt runtime version: 6. 4.2 "notify server name: Plasma, vendor: KDE, version: 5.27.10, spec: 1.2" "Using locale: en_GB" terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid [1]+ Aborted (core dumped) jami garydale@transponder:~/mnt/archives/2024/Lions Cl There might be something wrong with my locales but dpkg-reconfigure locales doesn't fix it. After running it, I still get this output: $locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=iu_CA.UTF-8 LANGUAGE=en_GB LC_CTYPE="iu_CA.UTF-8" LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=en_CA.UTF-8 LC_MESSAGES="iu_CA.UTF-8" LC_PAPER="iu_CA.UTF-8" LC_NAME="iu_CA.UTF-8" LC_ADDRESS="iu_CA.UTF-8" LC_TELEPHONE="iu_CA.UTF-8" LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION="iu_CA.UTF-8" LC_ALL= Please note that I have not selected iu_CA.utf8 nor en_GB in my locales. Any ideas on how to fix this? Thanks.
Re: SOLVED Re: Disk corruption and performance issue.
On 2/26/24 13:25, Tim Woodall wrote:
TLDR; there was a firmware bug in a disk in the raid array resulting in
data corruption. A subsequent kernel workaround resulted in
dramatically reducing the disk performance. (probably just writes but I
didn't confirm)
Initially, under heavy disk load I got errors like:
Preparing to unpack .../03-libperl5.34_5.34.0-5_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-5) ...
dpkg-deb (subprocess): decompressing archive
'/tmp/apt-dpkg-install-zqY3js/03-libperl5.34_5.34.0-5_arm64.deb'
(size=4015516) member 'data.tar': lzma error: compressed data is corrupt
dpkg-deb: error: subprocess returned error exit status 2
dpkg: error processing archive
/tmp/apt-dpkg-install-zqY3js/03-libperl5.34_5.34.0-5_arm64.deb
(--unpack):
cannot copy extracted data for
'./usr/lib/aarch64-linux-gnu/libperl.so.5.34.0' to
'/usr/lib/aarch64-linux-gnu/libperl.so.5.34.0.dpkg-new': unexpected
end of file or stream
The checksum will have been verified by apt during the download but when
it comes to read the downloaded deb to unpack and install it doesn't get
the same data. The corruption can happen at both the writing (the file
on disk is corrupted) and the reading (the file on disk has the correct
checksum)
A second problem I got was 503 errors from apt-cacher-ng (which ran on
the same machine as the above error)
I initially assumed this was due to faulty memory, or possibly a faulty
CPU. But I assumed memory because the disk errors were happening in a VM
and no other VMs were affected. Because I always start the same VMs in
the same order I assumed they'd be using the same physical memory each
time.
However, nothing I could do would help track down where the memory
problem was. Everything worked perfectly except when using the disk
under load.
At this time I spent a significant amount of time migrating everything
important, including the big job that triggered this problem, off this
machine onto the pair. After that the corruption problems went away but
I continued to get periodic 503 errors from apt-cacher-ng.
I continued to worry at this on and off but failed to make any progress
in finding what was wrong. The version of the motherboard is no longer
available otherwise I'd probably have bought another one. During this
time I also spent quite a lot of time ensurning that it was much easier
to move VMs between my two machines. I'd underestimated how tricky this
would be if the dodgy machine failed totally which I became aware of
when I did migrate the VM having problems.
Late last year or early this year someone (possibly Andy Smith?) posted
a question about logical/physical sector sizes on SSDs. That set me off
investigating again as that's not something I'd thought of. That didn't
prove fruitful either but I did notice this in the kernel logs:
Feb 17 17:01:49 xen17 vmunix: [ 3.802581] ata1.00: disabling queued
TRIM support
Feb 17 17:01:49 xen17 vmunix: [ 3.805074] ata1.00: disabling queued
TRIM support
from libata-core.c
{ "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM |
ATA_HORKAGE_NO_NCQ_ON_ATI },
This fixed the disk corruption errors at the cost of dramatically
reducing performance. (I'm not sure why because manual fstrim didn't
improve things)
At this point I'd discovered that the big job that had been regularly
hitting corruption issues now completed. However, it was taking 19 hours
instead of 11 hours.
I ordered some new disks - I'd assumed both disks were affected but
while writing this I notice that that "disabling queued TRIM support"
prints twice for the same disk, not once per disk.
I thought one of these was my disk but looking again now I see I had
1000MX500 which doesn't actually match.
{ "Crucial_CT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM },
{ "Crucial_CT*MX100*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM },
While waiting for my disks I started looking at the apt-cacher-ng
503 problem - which has continued to bug me. I got lucky and discovered
a way I could almost always trigger it.
I managed to track that down to a race condition when updating the
Release files if multiple machines request the same file at the same
moment.
After finding a fix I found this bug reporting the same problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022043
There is now a patch attached to that bug that I've been running for a
few weeks without a single 503 error.
And Sunday I replaced the two disks with new ones. Today that big job
completed in 10h15m.
Another thing I notice, although I'm not sure I understand what is going
on, is that my iscsi disks all have
Thin-provisioning: No
This means tha fstrim on the vm doesn't work. Switching them to Yes and
it does. So I'm not exactly sure where the queued trim was coming from
> in the first place.
Are you using systemd ?
SOLVED Re: Disk corruption and performance issue.
TLDR; there was a firmware bug in a disk in the raid array resulting in
data corruption. A subsequent kernel workaround resulted in
dramatically reducing the disk performance. (probably just writes but I
didn't confirm)
Initially, under heavy disk load I got errors like:
Preparing to unpack .../03-libperl5.34_5.34.0-5_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-5) ...
dpkg-deb (subprocess): decompressing archive
'/tmp/apt-dpkg-install-zqY3js/03-libperl5.34_5.34.0-5_arm64.deb'
(size=4015516) member 'data.tar': lzma error: compressed data is corrupt
dpkg-deb: error: subprocess returned error exit status 2
dpkg: error processing archive
/tmp/apt-dpkg-install-zqY3js/03-libperl5.34_5.34.0-5_arm64.deb (--unpack):
cannot copy extracted data for
'./usr/lib/aarch64-linux-gnu/libperl.so.5.34.0' to
'/usr/lib/aarch64-linux-gnu/libperl.so.5.34.0.dpkg-new': unexpected end of
file or stream
The checksum will have been verified by apt during the download but when
it comes to read the downloaded deb to unpack and install it doesn't get
the same data. The corruption can happen at both the writing (the file
on disk is corrupted) and the reading (the file on disk has the correct
checksum)
A second problem I got was 503 errors from apt-cacher-ng (which ran on
the same machine as the above error)
I initially assumed this was due to faulty memory, or possibly a faulty
CPU. But I assumed memory because the disk errors were happening in a VM
and no other VMs were affected. Because I always start the same VMs in
the same order I assumed they'd be using the same physical memory each
time.
However, nothing I could do would help track down where the memory
problem was. Everything worked perfectly except when using the disk
under load.
At this time I spent a significant amount of time migrating everything
important, including the big job that triggered this problem, off this
machine onto the pair. After that the corruption problems went away but
I continued to get periodic 503 errors from apt-cacher-ng.
I continued to worry at this on and off but failed to make any progress
in finding what was wrong. The version of the motherboard is no longer
available otherwise I'd probably have bought another one. During this
time I also spent quite a lot of time ensurning that it was much easier
to move VMs between my two machines. I'd underestimated how tricky this
would be if the dodgy machine failed totally which I became aware of
when I did migrate the VM having problems.
Late last year or early this year someone (possibly Andy Smith?) posted
a question about logical/physical sector sizes on SSDs. That set me off
investigating again as that's not something I'd thought of. That didn't
prove fruitful either but I did notice this in the kernel logs:
Feb 17 17:01:49 xen17 vmunix: [3.802581] ata1.00: disabling queued TRIM
support
Feb 17 17:01:49 xen17 vmunix: [3.805074] ata1.00: disabling queued TRIM
support
from libata-core.c
{ "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM |
ATA_HORKAGE_NO_NCQ_ON_ATI },
This fixed the disk corruption errors at the cost of dramatically
reducing performance. (I'm not sure why because manual fstrim didn't
improve things)
At this point I'd discovered that the big job that had been regularly
hitting corruption issues now completed. However, it was taking 19 hours
instead of 11 hours.
I ordered some new disks - I'd assumed both disks were affected but
while writing this I notice that that "disabling queued TRIM support"
prints twice for the same disk, not once per disk.
I thought one of these was my disk but looking again now I see I had
1000MX500 which doesn't actually match.
{ "Crucial_CT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM },
{ "Crucial_CT*MX100*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM },
While waiting for my disks I started looking at the apt-cacher-ng
503 problem - which has continued to bug me. I got lucky and discovered
a way I could almost always trigger it.
I managed to track that down to a race condition when updating the
Release files if multiple machines request the same file at the same
moment.
After finding a fix I found this bug reporting the same problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022043
There is now a patch attached to that bug that I've been running for a
few weeks without a single 503 error.
And Sunday I replaced the two disks with new ones. Today that big job
completed in 10h15m.
Another thing I notice, although I'm not sure I understand what is going
on, is that my iscsi disks all have
Thin-provisioning: No
This means tha fstrim on the vm doesn't work. Switching them to Yes and
it does. So I'm not exactly sure where the queued trim was coming from
in the first place.
I also need to check the version of tgt in sid because there doesn't
seem to be an option to switch this in the config
Re: Useful Unix compatible commands
* Jonathan Matthew Gresham [24-02/25=Su 16:01 -0500]: > [...] I have been reading a Unix system administrators textbook. > ps -e > [...] > kill process > [...] > ls -R > [...] > If you know any more that can work on GNU compatible software or > Unix compatible software please indicate the commands in your reply. This is a decent introduction to the important commands: https://www.freecodecamp.org/news/the-linux-commands-handbook/
Re: Wifi - unable to connect.
Grzesiek Sójka writes:
[...]
> According to the instruction the settings should be:
> WPA2 Enterprise,
> PEAP,
> MSCHAPv2,
> no certificate.
>
> And my wpa config is:
> network={
> ssid="ssid"
> proto=RSN
> key_mgmt=WPA-EAP
> pairwise=CCMP
> auth_alg=OPEN
> eap=MSCHAPV2
> identity="uid"
> password="pas"
> mesh_fwding=1
> }
>
> Any suggestions?
What if:
network = {
ssid="ssid"
key_mgmt=WPA-EAP
eap=PEAP
identity="uid"
phase2="auth=MSCHAPV2"
mesh_fwding=1
password="pas"
}
KJ
Re: Pb routage NAT suite update/reboot
Bonjour, Le 19779ième jour après Epoch, Erwann Le Bras écrivait: [...] > * eth0 est l'interface interne, IP statique. > * eth1 est l'interface externe,connectée à une Freebox qui lui donne l'IP. > * tun0 est l'interface VPN [...] > * ip addr :* > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN > group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > 2: eth0: mtu 1500 qdisc fq_codel > state UNKNOWN group default qlen 1000 > link/ether 00:50:bf:d8:b9:1f brd ff:ff:ff:ff:ff:ff > altname enp5s3 > inet 192.168.2.1/24 brd 192.168.2.255 scope global eth0 > valid_lft forever preferred_lft forever > 3: *eth1*: mtu 1500 qdisc fq_codel > state UP group default qlen 1000 > link/ether *8e:a8:a4:c7:35:98* brd ff:ff:ff:ff:ff:ff > altname enp2s0 > inet *192.168.1.1*/24 metric 1024 brd 192.168.1.255 scope global > dynamic eth1 > valid_lft 42186sec preferred_lft 42186sec > 4: tun0: mtu 1500 qdisc > fq_codel state UNKNOWN group default qlen 500 > link/none > inet 192.168.3.1/24 scope global tun0 > valid_lft forever preferred_lft forever > Jusque là, rien de choquant :) > /etc/systemd/network/eth0.network > [Match] > Name=eth0 > #MACAddress=Adresse MAC de l'interface > > [Link] > #MACAddress=Changer l'adresse MAC > #MTUBytes=Changer la valeur du MTU > > [Network] > Address=192.168.2.1/24 > Gateway=192.168.2.1 Aïe ... Je pense que tu peux enlever 'Gateway' là, c'est probablement pour ça que tu as des soucis. Explications plus bas. [...] > *ip route* > default via 192.168.2.1 dev eth0 proto static > default via 192.168.1.254 dev eth1 proto dhcp src 192.168.1.1 metric > 1024 Voilà, tu as deux routes par défaut, la première (et probablement prioritaire) ne vas pas vers ta box, donc l'accès internet n'est pas opérationnel dans ce cas. > 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.1 metric 1024 [...] > 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.1 > 192.168.3.0/24 dev tun0 proto kernel scope link src 192.168.3.1 Ces 3 infos dans le routage sont suffisantes pour router l'interne vers eth0, le VPN vers tun0 et le réseau de la box par eth1. C'est aussi probablement pourquoi tu as des IP martiennes (du 192.168.1.x qui essaye de sortir par eth0 à cause de la directive gateway). Mes 2¢ -- A gift of a flower will soon be made to you.
Re: Wifi - unable to connect.
On Mon, Feb 26, 2024 at 12:03 PM Grzesiek Sójka wrote:
>
> Hi there,
>
> I'm trying to connect to wifi at work, unfortunately I get the following:
>
> wlan0: SME: Trying to authenticate with 24:81:3b:2a:0f:e1 (SSID='ssid'
> freq=2412 MHz)
> wlan0: Trying to associate with 24:81:3b:2a:0f:e1 (SSID='ssid' freq=2412
> MHz)
> wlan0: Associated with 24:81:3b:2a:0f:e1
> wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
> wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=PL
> wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
> wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=26
> wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 26 (MSCHAPV2) selected
> EAP-MSCHAPV2: Authentication succeeded
> wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
> wlan0: PMKSA-CACHE-ADDED 24:81:3b:2a:0f:e1 1
> wlan0: RSN: PMKID mismatch - authentication server may have derived
> different MSK?!
> wlan0: CTRL-EVENT-DISCONNECTED bssid=24:81:3b:2a:0f:e1 reason=1
> locally_generated=1
> BSSID 24:81:3b:2a:0f:e1 ignore list count incremented to 2, ignoring for
> 10 seconds
> wlan0: CTRL-EVENT-DSCP-POLICY clear_all
>
> According to the instruction the settings should be:
> WPA2 Enterprise,
> PEAP,
> MSCHAPv2,
> no certificate.
>
> And my wpa config is:
> network={
> ssid="ssid"
> proto=RSN
> key_mgmt=WPA-EAP
> pairwise=CCMP
> auth_alg=OPEN
> eap=MSCHAPV2
> identity="uid"
> password="pas"
> mesh_fwding=1
> }
>
> Any suggestions?
Not my area of expertise, but...
EAP success tells me you are authenticated using the shared secret or password.
WPA2 Enterprise and MSCHAPv2 look suspicious. I would use WPA2
Personal without MSCHAP and see if it produces a better result.
Jeff
Re: Pb routage NAT suite update/reboot
Bonsoir Le 26/02/2024 à 18:11, Erwann Le Bras a écrit : [...] *ip route* default via 192.168.2.1 dev eth0 proto static default via 192.168.1.254 dev eth1 proto dhcp src 192.168.1.1 metric 1024 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.1 metric 1024 192.168.1.1 dev eth1 proto dhcp scope host src 192.168.1.1 metric 1024 192.168.1.254 dev eth1 proto dhcp scope link src 192.168.1.1 metric 1024 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.1 192.168.3.0/24 dev tun0 proto kernel scope link src 192.168.3.1 (192.168.1.254 : Freebox) 2 routes par défaut est une erreur. Supprime la première Une fois réalisé, un ping vers la Frebox est OK ? [...] Les services fonctionnent bien, j'y ai accès depuis le réseau de la Freebox (192.168.1.0) mais pas depuis l'adresse externe (qui n'a pas changé). Donc un ping depuis la Freebox vers le réseau 192.168.2.0 est fonctionnel ? As tu rajouté une route pour que cela fonctionne car de mémoire la route par défaut doit être l'interface WAN de la FB ? J'exclus un dysfonctionnement de la Freebox, elle vient d'être changé. De ce que tu écris, la Freebox est en mode routeur. Si elle a été remplacée, vérifie dans ses réglages que les règles auxquelles tu t'attends soient encore en place et que la topologie est bien celle que tu veux. [...]
Pb routage NAT suite update/reboot
bonsoir la team! j'ai un serveur Debian (version stable) qui sert de passerelle entre mon réseau interne et l'extérieur. Il est en route en permanence et s'installe les mises à jour de sécurité, sans rebooter. * eth0 est l'interface interne, IP statique. * eth1 est l'interface externe,connectée à une Freebox qui lui donne l'IP. * tun0 est l'interface VPN Sur la Freebox, une DMZ redirige les flux entrants vers mon serveur pour ouvrir mon serveur sur l'extérieur (SSH, WEB, VPN...). IPTable fait le tri en entrée et assure le routage des paquets à l'extérieur et Fail2ban bannit les indésirables. Tout cela fonctionne depuis plusieurs années sans pb malgré les changements d'opérateur et de version Debian. Récemment, une maintenance matérielle (upgrade RAM) m'a contraint à le redémarrer après qq mois sans histoire. Au démarrage, rien ne va plus : extérieur difficilement joignable, NAT inopérant, DMZ HS (services non joignables depuis l'extérieur). Inversement, le serveur n'a plus accès à internet (ping HS) J'ai pensé à une régression du au noyau, un redémarrage en version 6.1.0-15 n'a rien donné. uname -a Linux quietty 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux J'ai trouvé des IP martiennes dans la syslog, je ne sais pas si c'est lié : 2024-02-26T16:51:24.146290+01:00 quietty kernel: [ 1180.427493] IPv4: martian source *192.168.1.1* from 45.155.91.29, on dev *eth1* 2024-02-26T16:51:24.146322+01:00 quietty kernel: [ 1180.427508] ll header: : *8e a8 a4 c7 35 98* 70 fc 8f 5e 60 da 08 00 2024-02-26T16:51:33.478276+01:00 quietty kernel: [ 1189.762277] IPv4: martian source *192.168.1.1* from 43.133.145.230, on dev *eth1* 2024-02-26T16:51:33.478309+01:00 quietty kernel: [ 1189.762292] ll header: : *8e a8 a4 c7 35 98* 70 fc 8f 5e 60 da 08 00 2024-02-26T16:51:36.742277+01:00 quietty kernel: [ 1193.025728] IPv4: martian source 1*92.168.1.1* from 179.105.36.19, on dev *eth1* 2024-02-26T16:51:36.742306+01:00 quietty kernel: [ 1193.025742] ll header: : *8e a8 a4 c7 35 98 *70 fc 8f 5e 60 da 08 00 2024-02-26T16:51:49.210275+01:00 quietty kernel: [ 1205.495322] IPv4: martian source *192.168.1.1* from 91.148.190.174, on dev *eth1* 2024-02-26T16:51:49.210305+01:00 quietty kernel: [ 1205.495335] ll header: : *8e a8 a4 c7 35 98* 70 fc 8f 5e 60 da 08 00 2024-02-26T16:51:58.990298+01:00 quietty kernel: [ 1215.272829] IPv4: martian source *192.168.1.1* from 176.111.174.29, on dev *eth1* 2024-02-26T16:51:58.990328+01:00 quietty kernel: [ 1215.272841] ll header: : *8e a8 a4 c7 35 9*8 70 fc 8f 5e 60 da 08 00 Je n'avais pas ça avant. Une recherche sur Internet ne m'a pas vraiment aidé. Quelques éléments techniques : * ip addr :* 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 00:50:bf:d8:b9:1f brd ff:ff:ff:ff:ff:ff altname enp5s3 inet 192.168.2.1/24 brd 192.168.2.255 scope global eth0 valid_lft forever preferred_lft forever 3: *eth1*: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether *8e:a8:a4:c7:35:98* brd ff:ff:ff:ff:ff:ff altname enp2s0 inet *192.168.1.1*/24 metric 1024 brd 192.168.1.255 scope global dynamic eth1 valid_lft 42186sec preferred_lft 42186sec 4: tun0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500 link/none inet 192.168.3.1/24 scope global tun0 valid_lft forever preferred_lft forever *configuration des interfaces :* /etc/systemd/network/eth0.network [Match] Name=eth0 #MACAddress=Adresse MAC de l'interface [Link] #MACAddress=Changer l'adresse MAC #MTUBytes=Changer la valeur du MTU [Network] Address=192.168.2.1/24 Gateway=192.168.2.1 DNS=192.168.2.1 127.0.0.1 Domains=vets.in IPv6PrivacyExtensions=false /etc/systemd/network/eth1.network [Match] Name=*eth1* [Network] DHCP=*ipv4* *ip route* default via 192.168.2.1 dev eth0 proto static default via 192.168.1.254 dev eth1 proto dhcp src 192.168.1.1 metric 1024 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.1 metric 1024 192.168.1.1 dev eth1 proto dhcp scope host src 192.168.1.1 metric 1024 192.168.1.254 dev eth1 proto dhcp scope link src 192.168.1.1 metric 1024 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.1 192.168.3.0/24 dev tun0 proto kernel scope link src 192.168.3.1 (192.168.1.254 : Freebox) *iptables -L -v* Chain INPUT (policy DROP 582 packets, 64731 bytes) pkts bytes target prot opt in out source destination 30176 2346K ACCEPT all -- lo any anywhere anywhere 3225 522K ACCEPT all -- eth0 any anywhere anywhere 820K 1189M ACCEPT all -- any any anywhere anywhere
Wifi - unable to connect.
Hi there,
I'm trying to connect to wifi at work, unfortunately I get the following:
wlan0: SME: Trying to authenticate with 24:81:3b:2a:0f:e1 (SSID='ssid'
freq=2412 MHz)
wlan0: Trying to associate with 24:81:3b:2a:0f:e1 (SSID='ssid' freq=2412
MHz)
wlan0: Associated with 24:81:3b:2a:0f:e1
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=PL
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=26
wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 26 (MSCHAPV2) selected
EAP-MSCHAPV2: Authentication succeeded
wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
wlan0: PMKSA-CACHE-ADDED 24:81:3b:2a:0f:e1 1
wlan0: RSN: PMKID mismatch - authentication server may have derived
different MSK?!
wlan0: CTRL-EVENT-DISCONNECTED bssid=24:81:3b:2a:0f:e1 reason=1
locally_generated=1
BSSID 24:81:3b:2a:0f:e1 ignore list count incremented to 2, ignoring for
10 seconds
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
According to the instruction the settings should be:
WPA2 Enterprise,
PEAP,
MSCHAPv2,
no certificate.
And my wpa config is:
network={
ssid="ssid"
proto=RSN
key_mgmt=WPA-EAP
pairwise=CCMP
auth_alg=OPEN
eap=MSCHAPV2
identity="uid"
password="pas"
mesh_fwding=1
}
Any suggestions?
--
Regards
Greg
Re: medically smart watches
On Mon Feb 26th, 2024, at 15:49, Gene Heskett wrote: > I have only one enabled radio, in a 3d printer, lists all the neighbors > wifi routers it scans for and I assume the neighbors can hear it, but > this things login id does not appear in its scan. Maybe its duff, IDK. > I seriously doubt the watch has a wifi radio. Even if it has, you cannot see it because it's a client, not a server (that's the way wifi works). > But w/o a bt > connection to the net, it can't even tell the time, its about a month > out of whack. > Even if you can pair it to your computer, I seriously doubt you can do anything because you'd need a program that is able to tell it what time it is (and I do not even talk about asking it about glucose levels -- but that's probably not a problem, because if it were that easy to do reliably, you'd find a lot of big-brand products doing it, and they would get a certification). Loïc
Re: medically smart watches
Well, I was merely hoping that someone might finally have come up with a working solution ... On Mon, 2024-02-26 at 13:07 +, Andy Smith wrote: > Hi, > > On Mon, Feb 26, 2024 at 12:24:34PM +0100, hw wrote: > > How does the watch you got measure blood sugar? Doesn't that require > > a blood sample? > > Some of them claim to extrapolate it from sweat, others claim to be > able to estimate it from shining near-infrared at the blood vessels > that are near the surface. Neither method has yet proven to be > accurate, which is why they aren't certified as a medical device in > UK. > > You can learn all about it by searching "non-invasive blood glucose > monitoring" > > Thanks, > Andy >
Re: medically smart watches
On Mon, 2024-02-26 at 09:48 -0500, gene heskett wrote: > On 2/26/24 06:25, hw wrote: > > On Sat, 2024-02-24 at 10:03 -0500, gene heskett wrote: > > > [...] > > > bluetooth, and It looks as if I have to buy a BT adaptor, so advise on > > > that front would be most welcome also. > > > [...] > > > > If you're locking for a bluetooth USB adapter: I have a 'Bluetooth > > 5.0' adapter from TP-Link which works with Fedora. I've been able to > > use it with a headset and an xbox controller. A smartphone and an IP > > phone also show up as devices, but I haven't tried to use them via > > bluetooth. > > > I have only one enabled radio, in a 3d printer, lists all the neighbors > wifi routers it scans for and I assume the neighbors can hear it, but > this things login id does not appear in its scan. Maybe its duff, IDK. Well, the IP phone is neat because you can pair a smartphone and use it to call contacts on your smartphone and talk through it instead of the smartphone. Smartphones aren't even useful for making phone calls because their sound quality is too bad for that, not to mention the endless latency that makes every call impossible. It's not surprising that you can't really hear anything with the speaker(s) and microphone(s) in smartphones being so tiny. > > [...] > > How does the watch you got measure blood sugar? Doesn't that require > > a blood sample? > > > That is what the FDA is pushing. This shines a uv led, and claims to be > able to measure by the color of the blood going by. But w/o a bt > connection to the net, it can't even tell the time, its about a month > out of whack. Pushing? It would sure be nice to have some sufficiently reliable device for measuring blood sugar that doesn't require test strips and doesn't need to be implanted or otherwise has to constantly remain attached your body. It's always a nightmare to get test strips, and you never get enough of them. Even if someone is trying to push the research and development, better don't hold your breath. Manufacturers are making way too much money with the test strips to go for anything else unless they can make more money with that than with the strips.
Re: Journald's qualities
On Mon, Feb 26, 2024 at 10:42 AM Mariusz Gronczewski wrote: > > Dnia 2024-02-26, o godz. 13:10:43 > Anssi Saari napisał(a): > > > Mariusz Gronczewski writes: > > > > > Offtopic but since Debian switched to systemd for DNS management on > > > VPNs and suc I need to restart it sometimes multiple times to just > > > get "right" DNS servers, because there appears to be no notion of > > > priority: > > > > > > https://github.com/systemd/systemd/issues/27543 > > > > > > so now any time I connect to work (just openvpn tunnel, nothing > > > fancy) I need to spam > > > > > > systemclt restart systemd-resolved ; sleep 1 ; cat /etc/resolv.conf > > > > > > few times till the dice rolls the right order of DNS servers... > > > > Interesting. I leaped on systemd-networkd and -resolved when I read > > years ago it added interface specific DNS support. So now my local DNS > > (dnsmasq in the router) handles my home network and what goes out via > > the VPN (i.e. tun0 or wg0 these days) uses the VPN's DNS. > > ... in what way? You need to resolve DNS first before you know which > interface the traffic is going out of. I _think_ that depends on the configuration. You can use local DNS for name resolution, or remote (VPN) DNS for name resolution. Sometimes both are used at the same time. I think that's called "split DNS" or "split brain DNS." > > Or if the > > VPN is off, the local DNS forwards queries to DHCP assigned DNS. I > > see no issues although I don't have the kind of VPN where some > > external traffic goes through it only but might work for that too. > > For me the default was that systemd-resolved dutifully spammed all > > DNS queries to all DNS servers through all interfaces. > > > > This interface specific DNS was a little hard to setup as I > > recall. Easier with WG than OpenVPN. > > > > Our case is basically that: > > * some of the records exist only on VPN DNS server (private domains > pointing to private IPs) > * some of the records exist on outside but the VPN DNS returns private > range IP addresses for it (so-called split-horizon DNS). > > So the only right way is to ask the first server on the list. That > worked before systemd-resolved came as Debian scripts just put the > VPN's DNS servers in the front. Now it is throw of the dice any time > the daemon is restarted. > > The proper way would be either to: > > * ask in order, with components registering the DNS server specifying > that priority so the daemon can result the sorted list > * have a way to do per-domain exception and do "if domain is > *.internal.example.com, ask VPN server's DNS" > > The second is possible in dnsmasq but not (AFAIK) in systemd. And > currently neither "make systemd a DNS resolver" nor "use > systemd-resolved provided DNS config" work reliably. Jeff
TESTE DE INTEGRIDADE SSD
Prezados, Gostaria de saber qual ferramenta no Debian ( Uso testing) faz o teste de integridade de SSD. -- *Rafael de Almeida Matias* Especialista em Segurança da Informação Tecnólogo em Redes de Computadores Técnico em Informática Currículo Lattes: https://goo.gl/RqclG4
Re: medically smart watches
On Mon, 2024-02-26 at 13:21 +0100, Hans wrote: > [...] > However, on my mobile a pairing password or number is not needed and for > pairing the special app is also not needed on the mobile. > > This let me conclude, some other thing I must have missed. > > For testing purposes I used kde in-built blue-tooth-manager and as well the > app "blueman" from Gnome. I had the feeling, blueman is working more stable > and smoother than the kde-built-in one. > > If someone knows, how to pair these (maybe I have to take notice of some > things), I will take a further look. Some devices can not be paired. Bluetooth sucks badly; it may or may not work and it's always been like that. Last time I bought something with bluetooth, it couldn't be paired and I got a discount. I don't need, nor want its bluetooth functionality at all, and it's better that it doesn't work because it may make it more difficult for potential attackers, so I got an even better deal than it already was.
Re: medically smart watches
Gene writes: > I have only one enabled radio, in a 3d printer, lists all the > neighbors wifi routers it scans for and I assume the neighbors can > hear it, but this things login id does not appear in its scan. Maybe > its duff, IDK. Bluetooth is not WiFi. Different protocols. https://en.wikipedia.org/wiki/Bluetooth -- John Hasler j...@sugarbit.com Elmwood, WI USA
RE: paquets Debian avec information de deboguage?
Bonjour, La page suivante du Wiki Debian devrait aider : https://wiki.debian.org/HowToGetABacktrace Cdlt, Fred. <>
Re: medically smart watches
On 2/26/24 07:21, Hans wrote: Am Montag, 26. Februar 2024, 12:24:34 CET schrieb hw: If you're locking for a bluetooth USB adapter: I have a 'Bluetooth 5.0' adapter from TP-Link which works with Fedora. I've been able to use it with a headset and an xbox controller. A smartphone and an IP phone also show up as devices, but I haven't tried to use them via bluetooth. I suppose, you have the same BT-dongle as mine. I own a cheap medical watch from China (KR80 same as Fair Boltt Smartwatch), which obviously presents many watches, as most watches are suing the same App on the mobile device regardless of the manufacturer. You find many videos on youtube related to the Fair Boltt watch. So I guess, they are all working same way. Here I have a Lenovo T520 with built-in bluetooth adapter and a TP-Link USB dongle. I can confirm, the built-in adapter does NOT see the watch, however, the TP- Link dongle does see it. Sadly I was not able to pair the watch, but I believe, I do not know the correct pairing number (1234 and ) did not work and on the watch is no option to set one. However, on my mobile a pairing password or number is not needed and for pairing the special app is also not needed on the mobile. This let me conclude, some other thing I must have missed. For testing purposes I used kde in-built blue-tooth-manager and as well the app "blueman" from Gnome. I had the feeling, blueman is working more stable and smoother than the kde-built-in one. If someone knows, how to pair these (maybe I have to take notice of some things), I will take a further look. I hope, this helped a little bit more. It does shine a bit of light on some of the problems to be aware of. Thanks Hans. Take care & stay well. Best Hans Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: medically smart watches
On 2/26/24 06:25, hw wrote: On Sat, 2024-02-24 at 10:03 -0500, gene heskett wrote: [...] bluetooth, and It looks as if I have to buy a BT adaptor, so advise on that front would be most welcome also. [...] If you're locking for a bluetooth USB adapter: I have a 'Bluetooth 5.0' adapter from TP-Link which works with Fedora. I've been able to use it with a headset and an xbox controller. A smartphone and an IP phone also show up as devices, but I haven't tried to use them via bluetooth. I have only one enabled radio, in a 3d printer, lists all the neighbors wifi routers it scans for and I assume the neighbors can hear it, but this things login id does not appear in its scan. Maybe its duff, IDK. However, a while ago I found that the xbox controller did have connection issues in that the connection seemed to get interrupted, so I went back to using an USB cable. I'm pretty sure it's a software problem because it worked fine at first. I don't know if it's been fixed since because my workstation only has 4 USB ports of which 3 are occupied and an USB cable extension is plugged into the 4th for the xbox controller. How does the watch you got measure blood sugar? Doesn't that require a blood sample? That is what the FDA is pushing. This shines a uv led, and claims to be able to measure by the color of the blood going by. But w/o a bt connection to the net, it can't even tell the time, its about a month out of whack. Thanks hw. Take care and stay well. . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Selective rotation of journald logs
Max Nikulin (12024-02-23): > I am realizing that the following is not an answer to the asked question. > The thread is no more than useless arguing anyway. > > Some ideas that might be useful in close cases: > - a bunch of filtering options and --output=export as a part of log rotation > to have selective copy of the journal in an alternative directory Hi. You know what? I think it is exactly the right answer. I think the principle for this thing is: journald maintains the current logs in a best-effort manner, but when it comes to archival, the needs and manners are too varied, it does not try to provide a ready-to-use solution, but journalctl provides all the tools necessary to implement what we want. If I am right, if it is indeed the way it is meant to be used, I just wish somebody would have bothered writing it in so many words at the start of a documentation. Thanks. -- Nicolas George
Re: Useful Unix compatible commands
Hellow Jonathan, Jonathan Matthew Gresham writes: > > ps -e > ls -R > ls -F Thanks, Byunghee from South Korea -- ^고맙습니다 _布德天下_ 감사합니다_^))//
Re: medically smart watches
Hi, On Mon, Feb 26, 2024 at 12:24:34PM +0100, hw wrote: > How does the watch you got measure blood sugar? Doesn't that require > a blood sample? Some of them claim to extrapolate it from sweat, others claim to be able to estimate it from shining near-infrared at the blood vessels that are near the surface. Neither method has yet proven to be accurate, which is why they aren't certified as a medical device in UK. You can learn all about it by searching "non-invasive blood glucose monitoring" Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: medically smart watches
Am Montag, 26. Februar 2024, 12:24:34 CET schrieb hw: > If you're locking for a bluetooth USB adapter: I have a 'Bluetooth > 5.0' adapter from TP-Link which works with Fedora. I've been able to > use it with a headset and an xbox controller. A smartphone and an IP > phone also show up as devices, but I haven't tried to use them via > bluetooth. > I suppose, you have the same BT-dongle as mine. I own a cheap medical watch from China (KR80 same as Fair Boltt Smartwatch), which obviously presents many watches, as most watches are suing the same App on the mobile device regardless of the manufacturer. You find many videos on youtube related to the Fair Boltt watch. So I guess, they are all working same way. Here I have a Lenovo T520 with built-in bluetooth adapter and a TP-Link USB dongle. I can confirm, the built-in adapter does NOT see the watch, however, the TP- Link dongle does see it. Sadly I was not able to pair the watch, but I believe, I do not know the correct pairing number (1234 and ) did not work and on the watch is no option to set one. However, on my mobile a pairing password or number is not needed and for pairing the special app is also not needed on the mobile. This let me conclude, some other thing I must have missed. For testing purposes I used kde in-built blue-tooth-manager and as well the app "blueman" from Gnome. I had the feeling, blueman is working more stable and smoother than the kde-built-in one. If someone knows, how to pair these (maybe I have to take notice of some things), I will take a further look. I hope, this helped a little bit more. Best Hans
Re: Journald's qualities
Dnia 2024-02-26, o godz. 13:10:43 Anssi Saari napisał(a): > Mariusz Gronczewski writes: > > > Offtopic but since Debian switched to systemd for DNS management on > > VPNs and suc I need to restart it sometimes multiple times to just > > get "right" DNS servers, because there appears to be no notion of > > priority: > > > > https://github.com/systemd/systemd/issues/27543 > > > > so now any time I connect to work (just openvpn tunnel, nothing > > fancy) I need to spam > > > > systemclt restart systemd-resolved ; sleep 1 ; cat /etc/resolv.conf > > > > few times till the dice rolls the right order of DNS servers... > > Interesting. I leaped on systemd-networkd and -resolved when I read > years ago it added interface specific DNS support. So now my local DNS > (dnsmasq in the router) handles my home network and what goes out via > the VPN (i.e. tun0 or wg0 these days) uses the VPN's DNS. ... in what way? You need to resolve DNS first before you know which interface the traffic is going out of. > Or if the > VPN is off, the local DNS forwards queries to DHCP assigned DNS. I > see no issues although I don't have the kind of VPN where some > external traffic goes through it only but might work for that too. > For me the default was that systemd-resolved dutifully spammed all > DNS queries to all DNS servers through all interfaces. > > This interface specific DNS was a little hard to setup as I > recall. Easier with WG than OpenVPN. > Our case is basically that: * some of the records exist only on VPN DNS server (private domains pointing to private IPs) * some of the records exist on outside but the VPN DNS returns private range IP addresses for it (so-called split-horizon DNS). So the only right way is to ask the first server on the list. That worked before systemd-resolved came as Debian scripts just put the VPN's DNS servers in the front. Now it is throw of the dice any time the daemon is restarted. The proper way would be either to: * ask in order, with components registering the DNS server specifying that priority so the daemon can result the sorted list * have a way to do per-domain exception and do "if domain is *.internal.example.com, ask VPN server's DNS" The second is possible in dnsmasq but not (AFAIK) in systemd. And currently neither "make systemd a DNS resolver" nor "use systemd-resolved provided DNS config" work reliably. -- Mariusz Gronczewski (XANi) GnuPG: 0xEA8ACE64 https://devrandom.eu
Re: medically smart watches
On Sat, 2024-02-24 at 10:03 -0500, gene heskett wrote: > [...] > bluetooth, and It looks as if I have to buy a BT adaptor, so advise on > that front would be most welcome also. > [...] If you're locking for a bluetooth USB adapter: I have a 'Bluetooth 5.0' adapter from TP-Link which works with Fedora. I've been able to use it with a headset and an xbox controller. A smartphone and an IP phone also show up as devices, but I haven't tried to use them via bluetooth. However, a while ago I found that the xbox controller did have connection issues in that the connection seemed to get interrupted, so I went back to using an USB cable. I'm pretty sure it's a software problem because it worked fine at first. I don't know if it's been fixed since because my workstation only has 4 USB ports of which 3 are occupied and an USB cable extension is plugged into the 4th for the xbox controller. How does the watch you got measure blood sugar? Doesn't that require a blood sample?
Re: Journald's qualities
Mariusz Gronczewski writes: > Offtopic but since Debian switched to systemd for DNS management on > VPNs and suc I need to restart it sometimes multiple times to just get > "right" DNS servers, because there appears to be no notion of priority: > > https://github.com/systemd/systemd/issues/27543 > > so now any time I connect to work (just openvpn tunnel, nothing fancy) > I need to spam > > systemclt restart systemd-resolved ; sleep 1 ; cat /etc/resolv.conf > > few times till the dice rolls the right order of DNS servers... Interesting. I leaped on systemd-networkd and -resolved when I read years ago it added interface specific DNS support. So now my local DNS (dnsmasq in the router) handles my home network and what goes out via the VPN (i.e. tun0 or wg0 these days) uses the VPN's DNS. Or if the VPN is off, the local DNS forwards queries to DHCP assigned DNS. I see no issues although I don't have the kind of VPN where some external traffic goes through it only but might work for that too. For me the default was that systemd-resolved dutifully spammed all DNS queries to all DNS servers through all interfaces. This interface specific DNS was a little hard to setup as I recall. Easier with WG than OpenVPN.
