Re: dns lookup behavior

[Paolo Galtieri]

On 2/21/22 15:56, Jamie Fargen wrote:




dig 172.16.96.20


Do you mean dig -x 172.16.96.20


dig 1.1.1.1 doesn't return the host name:




dig -x 172.16.96.20

returns

; <<>> DiG 9.16.24-RH <<>> -x 172.16.96.20
;; global options: +cmd
;; connection timed out; no servers could be reached

but

dig centos8-opstcore-vm.homenet172-16-96.com

returns

; <<>> DiG 9.16.24-RH <<>> centos8-opstcore-vm.homenet172-16-96.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31140
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;centos8-opstcore-vm.homenet172-16-96.com. IN A

;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16-96.com. 259200 IN A 172.16.96.20

;; Query time: 2 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Feb 22 16:04:46 PST 2022
;; MSG SIZE  rcvd: 85

Paolo

You can see running dig followed by an IP doesn't return anything, to 
do a reverse DNS lookup, or to resolve the hostname from the IP, you 
can see in the second example dig -x followed by the IP returns the 
hostname one.one.one.one.


$ dig 1.1.1.1

; <<>> DiG 9.16.24-RH <<>> 1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42214
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.1.1.1. IN A

;; AUTHORITY SECTION:
. 60 IN SOA a.root-servers.net . 
nstld.verisign-grs.com . 2022022101 
1800 900 604800 86400


;; Query time: 241 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 18:53:50 EST 2022
;; MSG SIZE  rcvd: 111


# dig -x 1.1.1.1

; <<>> DiG 9.16.24-RH <<>> -x 1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63485
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.1.1.1.in-addr.arpa. IN PTR

;; ANSWER SECTION:
1.1.1.1.in-addr.arpa. 1131 IN PTR one.one.one.one.

;; Query time: 74 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 18:53:57 EST 2022
;; MSG SIZE  rcvd: 78


; <<>> DiG 9.16.24-RH <<>> 172.16.96.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47273
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;172.16.96.20.            IN    A

;; AUTHORITY SECTION:
.            6751    IN    SOA a.root-servers.net
. nstld.verisign-grs.com
. 2022022101 1800 900 604800 86400

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 14:39:02 PST 2022
;; MSG SIZE  rcvd: 116

dig centos8-opstcore-vm.homenet172-16-96.com


; <<>> DiG 9.16.24-RH <<>>
centos8-opstcore-vm.homenet172-16-96.com

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26457
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;centos8-opstcore-vm.homenet172-16-96.com
. IN A

;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16-96.com
. 4778 IN A
172.16.96.20

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 14:40:16 PST 2022
;; MSG SIZE  rcvd: 85

I tried stopping and restarting systemd-resolved to no avail as
well as restarting the network interface also to no avail.

What's curious is for example

host 192.168.10.2 will return a host name most likely because it's
cached.

host 172.16.96.20 results in host not found on one F34 system and
no servers could be reached on the other F34 system

I ran wireshark on the DNS server and it showed the query to
127.0.0.53 with the hostname and a response of the ip address. 
But a query to 127.0.0.53 with the ip address returned a not found
error.


At first I didn't like this new way to manage DNS, but I am
finding some of the features to work very well. Like the split
dns feature is working really well with the multiple vpn clients
run simultaneously, no more hacking on /etc/resolv.conf each time
a new VPN is started, it just works.


1 - https://fedoraproject.org/wiki/Changes/systemd-resolved

 Regards,
-Jamie

___
users 

[389-users] Re: OpenLDAP import into 389 Directory Server failing

[Jason W. Lewis]

Mark,
Thanks for that.  I have gone through those docs already, and I’m still running 
into it.  My 389-ds-base package is version 1.4.4.17.

--
Jason Lewis

Systems Administrator



From: Mark Reynolds 
Date: Tuesday, February 22, 2022 at 16:08
To: "General discussion list for the 389 Directory server project." 
<389-users@lists.fedoraproject.org>, "Jason W. Lewis" 
Subject: Re: [389-users] OpenLDAP import into 389 Directory Server failing


External email – Please make sure you trust the source before clicking links or 
opening attachments.

What version of 389-ds-base are you using?

Check out these docs if you haven't already:

https://www.port389.org/docs/389ds/howto/howto-openldap-migration.html

https://www.port389.org/docs/389ds/design/openldap2ds.html

Thanks,

Mark
On 2/22/22 3:59 PM, Jason W. Lewis wrote:
After RHEL, etc dropped OpenLDAP, I’ve begun testing with 389 Directory Server. 
Currently, I’m trying to use openldap_to_ds to import slapd.d config and an 
LDIF export to import my old database into the new server.
I’ve created a new instance in 389-ds named terminal-config. I’ve tried the 
following variations on the idea, all of which gave me the same results:

  1.  exported the LDIF from OpenLDAP 2.4 on Oracle Linux 7 and CentOS 6 
servers.
  2.  Rewrote all files being imported to make sure they weren’t corrupt.
  3.  used relative and absolute path names to the files
  4.  Tried importing with a new instance (as mentioned above) and no instance 
at all
  5.  When using dscreate to make the new instance, I’ve tried setting it up 
differently (allowed sample entries and not, etc)
No matter what I do, this is what I get when I try:
[root@ldaptest ~]# openldap_to_ds terminal-config /root/slapd.d  
/root/terminals.ldif
Examining OpenLDAP Configuration ...
Traceback (most recent call last):
  File "/usr/sbin/openldap_to_ds", line 250, in 
result = do_migration(inst, log, args, skip_overlays)
  File "/usr/sbin/openldap_to_ds", line 178, in do_migration
config = olConfig(args.slapd_config, log)
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in __init__
for db in dbs
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in 
for db in dbs
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 112, in __init__
self.suffix = ensure_str(self.config[1]['olcSuffix'][0])
KeyError: 'olcSuffix'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/openldap_to_ds", line 257, in 
log.error("Error: %s" % " - ".join(str(val) for val in msg.values()))
AttributeError: 'str' object has no attribute 'values'
[root@ldaptest ~]#

Any thoughts on what could be causing this?

--
[Micro Electronics Inc]

Jason Lewis

Systems Administrator

jwle...@microcenter.com

|

[signature_251198827]

614-777-2728




[Micro Center Secure Email]

CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is 
intended exclusively for the person or entity to which it is addressed and may 
contain confidential and/or privileged material. If you are not the intended 
recipient, you are not authorized to read, print, retain, copy or disseminate 
this message or any part of it. If you receive this message in error, please 
contact the sender by reply e-mail and destroy all copies of the original 
message and attachments. Thank you





___

389-users mailing list -- 
389-users@lists.fedoraproject.org

To unsubscribe send an email to 
389-users-le...@lists.fedoraproject.org

Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

--

Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: OpenLDAP import into 389 Directory Server failing

[Mark Reynolds]

What version of 389-ds-base are you using?

Check out these docs if you haven't already:

https://www.port389.org/docs/389ds/howto/howto-openldap-migration.html

https://www.port389.org/docs/389ds/design/openldap2ds.html

Thanks,

Mark

On 2/22/22 3:59 PM, Jason W. Lewis wrote:


After RHEL, etc dropped OpenLDAP, I’ve begun testing with 389 
Directory Server. Currently, I’m trying to use openldap_to_ds to 
import slapd.d config and an LDIF export to import my old database 
into the new server.


I’ve created a new instance in 389-ds named terminal-config. I’ve 
tried the following variations on the idea, all of which gave me the 
same results:


  * exported the LDIF from OpenLDAP 2.4 on Oracle Linux 7 and CentOS 6
servers.
  * Rewrote all files being imported to make sure they weren’t corrupt.
  * used relative and absolute path names to the files
  * Tried importing with a new instance (as mentioned above) and no
instance at all
  * When using dscreate to make the new instance, I’ve tried setting
it up differently (allowed sample entries and not, etc)

No matter what I do, this is what I get when I try:

[root@ldaptest ~]# openldap_to_ds terminal-config /root/slapd.d 
/root/terminals.ldif


Examining OpenLDAP Configuration ...

Traceback (most recent call last):

File "/usr/sbin/openldap_to_ds", line 250, in 

result = do_migration(inst, log, args, skip_overlays)

File "/usr/sbin/openldap_to_ds", line 178, in do_migration

config = olConfig(args.slapd_config, log)

File 
"/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in __init__


for db in dbs

File 
"/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in 


for db in dbs

File 
"/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 112, in __init__


self.suffix = ensure_str(self.config[1]['olcSuffix'][0])

KeyError: 'olcSuffix'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/usr/sbin/openldap_to_ds", line 257, in 

log.error("Error: %s" % " - ".join(str(val) for val in msg.values()))

AttributeError: 'str' object has no attribute 'values'

[root@ldaptest ~]#

Any thoughts on what could be causing this?

--

Micro Electronics Inc



Jason Lewis

Systems Administrator

jwle...@microcenter.com 



|



signature_251198827



614-777-2728

Micro Center Secure Email

CONFIDENTIALITY NOTICE: This e-mail message including attachments, if 
any, is intended exclusively for the person or entity to which it is 
addressed and may contain confidential and/or privileged material. If 
you are not the intended recipient, you are not authorized to read, 
print, retain, copy or disseminate this message or any part of it. If 
you receive this message in error, please contact the sender by reply 
e-mail and destroy all copies of the original message and attachments. 
Thank you



___
389-users mailing list --389-users@lists.fedoraproject.org
To unsubscribe send an email to389-users-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report 
it:https://pagure.io/fedora-infrastructure


--
Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] OpenLDAP import into 389 Directory Server failing

[Jason W. Lewis]

After RHEL, etc dropped OpenLDAP, I’ve begun testing with 389 Directory Server. 
Currently, I’m trying to use openldap_to_ds to import slapd.d config and an 
LDIF export to import my old database into the new server.
I’ve created a new instance in 389-ds named terminal-config. I’ve tried the 
following variations on the idea, all of which gave me the same results:

  *   exported the LDIF from OpenLDAP 2.4 on Oracle Linux 7 and CentOS 6 
servers.
  *   Rewrote all files being imported to make sure they weren’t corrupt.
  *   used relative and absolute path names to the files
  *   Tried importing with a new instance (as mentioned above) and no instance 
at all
  *   When using dscreate to make the new instance, I’ve tried setting it up 
differently (allowed sample entries and not, etc)
No matter what I do, this is what I get when I try:
[root@ldaptest ~]# openldap_to_ds terminal-config /root/slapd.d  
/root/terminals.ldif
Examining OpenLDAP Configuration ...
Traceback (most recent call last):
  File "/usr/sbin/openldap_to_ds", line 250, in 
result = do_migration(inst, log, args, skip_overlays)
  File "/usr/sbin/openldap_to_ds", line 178, in do_migration
config = olConfig(args.slapd_config, log)
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in __init__
for db in dbs
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in 
for db in dbs
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 112, in __init__
self.suffix = ensure_str(self.config[1]['olcSuffix'][0])
KeyError: 'olcSuffix'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/openldap_to_ds", line 257, in 
log.error("Error: %s" % " - ".join(str(val) for val in msg.values()))
AttributeError: 'str' object has no attribute 'values'
[root@ldaptest ~]#

Any thoughts on what could be causing this?

--
[Micro Electronics Inc]

Jason Lewis

Systems Administrator

jwle...@microcenter.com

|

[signature_251198827]

614-777-2728




[Micro Center Secure Email]

CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is 
intended exclusively for the person or entity to which it is addressed and may 
contain confidential and/or privileged material. If you are not the intended 
recipient, you are not authorized to read, print, retain, copy or disseminate 
this message or any part of it. If you receive this message in error, please 
contact the sender by reply e-mail and destroy all copies of the original 
message and attachments. Thank you


___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Perl is now failing for me

[James Szinger]

On Mon, 21 Feb 2022 00:22:13 -0800
Samuel Sieb  wrote:

> On 2/20/22 21:00, Fulko Hew wrote:
> > Thanks for pointing out that app, but I fail to see how having me
> > make an RPM for a
> > Fedora-unsupported module avoids the problem of incompatibilities 
> > between newer
> > Fedora sources packages and locally sourced packages (or locally
> > CPAN installed modules)
> > Or am I missing something?  
> 
> The benefit is that it's managed by the package manager, so it's easy
> to cleanly add, remove, and update it.  The alternative methods dump
> the files in various places and when a problem happens, you have to
> figure out where those problem files are.

A big advantage is that the package manager will complain if you
attempt an incompatible update.  You will know right away that you
need to fix something (even though DNF’s error messages can be hard to
decipher).

I learned this the hard way and haven’t used CPAN since.  Cpansec is
great (as is cpan2port).

Jim
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Re[2]: Perl is now failing for me

[George N. White III]

On Tue, 22 Feb 2022 at 12:28, M. Fioretti  wrote:

> On Tue, Feb 22, 2022 09:05:54 AM -0400, George N. White III wrote:
>
> [...]
> - All I know is that is that it is sorely needed ONE front-end in
> Linux where one can say, as it was in the golden age of .rpm and .deb,
> "I need this software. I couldn't care less, and there's nothing bad
> with it, of which language, build environment, packaging
> format... this software came from. Just find the damn thing and
> install it yourself, with any dependency, while I take a nap".
>
> - I don't know if conda is the right theoretical answer. I just know
> that until there is no awareness from developers and distro
> integrators (more the former than the latter, probably) of the mess
> they have put users in, and the will to fix it with conda or anything
> else, nothing will change
>

Linux distros have to focus on the most commonly used packages.
Debian may be the exception -- there you can get packages with
a smaller user base if someone steps forward to do the work,
including contributing to libraries they require.

Cross-distro packagers don't want to make it easy for users
to switch back to distro packages (hence python versus
python3).  Conda-forge is more open to allowing packages
with a limited user base.


>
> funny historical note about conda: they "stole" (note the quotes, no
> problem with that) the miniconda name from the RULE project I and
> others started twenty years ago:
>
> https://www.slideshare.net/mfioretti/rule-ld-roma2004


I vaguely remember RULE.   I used to work in a group that ran
ocean remote sensing workshops for post-doc level scientists
from developing countries.  At one time participants had Windows
PC's and the course used a linux VM from NASA.  I demoed a
bare-metal installation on an old PC and advised participants
to look for an old unloved and unwanted PC at their home institution
on which they could install linux.

Name clashes can often be avoided if people would check that a
proposed name is not already in use, and b) consistently use something
unique like their organization name as a prefix.   If nothing is done such
clashes will only increase with time.


> and also https://spazioinwind.libero.it/marco_web/RULE/installer.html (I
> have a full static archive of the original RULE website, went offline
> when I switched VPS, will restore it asap)
>

Try a goggle search for "python snap library" and imagine a student whose
instructor said "for today's homework, install the python snap library and
use
it to ".

If your requirements match those of sufficiently large audience, you might
consider organiziing a Fedora spin.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: help cascading routers F34

[Roger Heflin]

I always have my router doing all of the firewall functions and as
such put that firewalls ip address into the external router as DMZ and
make sure there is some sort of reservation in the external router so
that the DHCP ip address going my router does not change, so that the
external vendor supplied router just passes everything through to my
router.

On Mon, Feb 21, 2022 at 6:39 PM Jack Craig  wrote:
>
>
>
> for the last several yrs, i've used att's pace 5238ac cascaded to my 
> nighthawk R8000.
>
> pace wifi off, all wifi from nighthawk.
>
> recently got a bandwidth update (internet-24 to internet-50)
> and att swapped the pace for arris bgw210-700
>
> now i cant get the cascaded setup to work.
>
> i've been googling all week w/no joy...
>
> any wisdom out there??
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: ssd keeps dying (OT)

[Go Canes]

On Tue, Feb 22, 2022 at 11:19 AM Neal Becker  wrote:
> [...] e.g. erasing the partition table on the drive (I don't have another 
> machine handy to verify this), [...]

If it was just erasing the partition table the drive would still be
visible using lsblk, and you could re-partition it with fdisk, etc.


You mentioned a surge suppressor strip - any chance it has already
suppressed a surge in the past?  If so, it might not be functioning as
a surge suppressor anymore.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: ssd keeps dying (OT)

[Roger Heflin]

The 2 crucial bx drives I was losing, I replaced with an older smaller
mx drive and that one has been working just fine for a couple of
months, thinking about my issue and Neal's issue here is what springs
to mind.

So in my case, if mine was a power supply issue, it would have to be
that something about the new ssds is excessively sensitive to power or
ground loops.   The thought of my issue being a power supply
issue/sata issue burning the device did occur to me.  And that issue I
have is heavily reported in the 1-star reviews for the crucial device,
several people having more  than 1 failure and returning the device
for refund.  The people that have the failure seem to be able to
repeat, and I assume others work just fine.   So it would seem that
there must be some component used in recent ssd's may be super
sensitive to something either power supply wise or sata port wise, or
the design has a internal grounding issue and is sensitive to ground
loop wise that does not cause an issue with the older devices (I have
2 older SSD's and 8 hard drives that have been running in said machine
for months to years just fine).  I would think on an NVME device that
it would be well grounded to the motherboard/case.  In my case my ssds
were in a plastic drive holder so the only ground would have been via
the sata connection and the power supply, and so if the drive design
had components expecting a screw hole ground that won't exist in some
cases, and could have floating voltages then that might damage
something.

How was your nvme drive mounted in your case?   On mine the normal
screw holes were not connected to ground (plastic drive case) so the
"chassis" of the drive would not have been externally grounded, and
had said drive unit chassis not had a direct connect to to power or
SATA ground that could end up with floating voltages on the drive
chassis and any components tied to it internally.

And ground loops are tricky.  I have a wind meter on my roof hooked to
a device that counts it's rotations, and that serial port device would
randomly stop working requiring a reset of the usb-to-serial
communication to get it to function again (I had a cron job to
reload/reset the usb nightly because it was happening often enough). I
guessed ground loop ran a ground wire to house ground and grounded the
hw device doing the counting years ago, and that solved the issue.

On Tue, Feb 22, 2022 at 9:47 AM George N. White III  wrote:
>
> On Tue, 22 Feb 2022 at 10:04, Neal Becker  wrote:
>>
>> Thanks Richard.  Yes, I talked with Titan; they suggested trying the 
>> pcie-m.2 adapter.  I will try them again.
>> I have not checked for bios updates.  Not sure how to go about that (last 
>> time I did that it required an msdos floppy disc).
>>
>> Haven't tried the SSDs in another device because I don't have one.  But the 
>> fact that replacing the SSD causes it to work, where it wasn't working 
>> before, tells me they were damaged.  I have at least once power off/on the 
>> workstation, and the bios did not find any ssd to boot from.  So power cycle 
>> didn't fix it, but replace ssd did fix it.
>>
>> I will try Titan again later today, but just looking for ideas.
>
>
> With this history, I'd probably replace the workstation power supply.   I 
> would also scan the
> the system board for capacitors on bulging tops or overheated components.
>
> Are there any externally powered devices connected to the workstation (other 
> than the monitor)?
>
> Are you in an area with frequent lightning storms?  How stable is your power? 
>  Is the system
> connected to a UPS?
>
> I had a similar experience with spinning disks in a system that contained a 
> drive-bay radio receiver
> and was connected to a satellite dish and GPS receiver on the roof, and an 
> antenna controller.  Everything
> was powered by a high quality UPS.  I added a heavy wire connecting the 
> antenna controller case to the
> workstation case and the failures stopped.
>
> I gather you now have space for two m.2 SSD's.   If you haven't discarded the 
> non-working devices,
> it would be interesting to see if any are detected and what smartmontools 
> says about them, but
> you also have the option to put /var on a separate drive.  Smartmon tools can 
> monitor a drive and
> report any problems it detects, but you may also want to run self-tests 
> periodically.
>
>
>>
>>
>> Thanks,
>> Neal
>>
>> On Tue, Feb 22, 2022 at 8:44 AM Richard Shaw  wrote:
>>>
>>> On Tue, Feb 22, 2022 at 7:34 AM Neal Becker  wrote:

 I know this is a bit OT, but you guys are great at answering all questions.

 I bought a workstation from Titan computers around 1/2020 (dual EPYC cpu). 
  After about 1 year it stopped working.  I could ssh to it, and almost any 
 command would return Input/Output error.  Unfortunately journalctl gave 
 input/output error so I can't see logs.  cat /proc/partitions did not show 
 any nvme device (the root device) on which the OS was 

Re: Re[2]: Perl is now failing for me

[M. Fioretti]

On Tue, Feb 22, 2022 09:05:54 AM -0400, George N. White III wrote:

>   I end up spending a lot of time testing new Python versions and
> new libraries to ensure they are still working properly (new
> versions often have problems,  but they generally get fixed without
> my help)...
>
> I agree that it has become much more difficult to port a complex
> system to linux due to differences in what libraries are packed and
> in the configure options used for a given library on different
> distributions

George,

thanks for sharing your use case, you're doing really interesting
work. All I can add is:

- while being surely more complex than what an average Linux newbie
  needs, what I do is simpler than what you do, and still I too must
  waste too much time

- thanks for confirming that there is a serious problem

- All I know is that is that it is sorely needed ONE front-end in
Linux where one can say, as it was in the golden age of .rpm and .deb,
"I need this software. I couldn't care less, and there's nothing bad
with it, of which language, build environment, packaging
format... this software came from. Just find the damn thing and
install it yourself, with any dependency, while I take a nap".

- I don't know if conda is the right theoretical answer. I just know
that until there is no awareness from developers and distro
integrators (more the former than the latter, probably) of the mess
they have put users in, and the will to fix it with conda or anything
else, nothing will change

funny historical note about conda: they "stole" (note the quotes, no
problem with that) the miniconda name from the RULE project I and
others started twenty years ago:

https://www.slideshare.net/mfioretti/rule-ld-roma2004

and also https://spazioinwind.libero.it/marco_web/RULE/installer.html (I
have a full static archive of the original RULE website, went offline
when I switched VPS, will restore it asap)

Marco
-- 
Help me write my NEXT MILLION WORDS for digital awareness:
https://stop.zona-m.net/2021/10/funding-2021-2022/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: ssd keeps dying (OT)

[Neal Becker]

Well I suspected the PS, but the guy I spoke with at Titan said some other
things would fail before the SSD if that was the problem.

The power should be pretty stable, and I did connect to a good transient
suppressor strip.  Anyway there was no lightning when it died, which was in
the past 24 hours.  I had been watching smartmon every few days and it
showed no error and temps <37C.

Titan has suggested installing a sata SSD (eliminate the m.2) and I'm going
to try that.  He suggested it might be a software issue, that something
might be e.g. erasing the partition table on the drive (I don't have
another machine handy to verify this), but this seems really unlikely.  I
just installed F35 and a moderate set of scientific packages, no
proprietary software.  The only access in via ssh inside of vpn and I have
the only account.

On Tue, Feb 22, 2022 at 10:47 AM George N. White III 
wrote:

> On Tue, 22 Feb 2022 at 10:04, Neal Becker  wrote:
>
>> Thanks Richard.  Yes, I talked with Titan; they suggested trying the
>> pcie-m.2 adapter.  I will try them again.
>> I have not checked for bios updates.  Not sure how to go about that (last
>> time I did that it required an msdos floppy disc).
>>
>> Haven't tried the SSDs in another device because I don't have one.  But
>> the fact that replacing the SSD causes it to work, where it wasn't working
>> before, tells me they were damaged.  I have at least once power off/on the
>> workstation, and the bios did not find any ssd to boot from.  So power
>> cycle didn't fix it, but replace ssd did fix it.
>>
>> I will try Titan again later today, but just looking for ideas.
>>
>
> With this history, I'd probably replace the workstation power supply.   I
> would also scan the
> the system board for capacitors on bulging tops or overheated components.
>
> Are there any externally powered devices connected to the workstation
> (other than the monitor)?
>
> Are you in an area with frequent lightning storms?  How stable is your
> power?  Is the system
> connected to a UPS?
>
> I had a similar experience with spinning disks in a system that contained
> a drive-bay radio receiver
> and was connected to a satellite dish and GPS receiver on the roof, and an
> antenna controller.  Everything
> was powered by a high quality UPS.  I added a heavy wire connecting the
> antenna controller case to the
> workstation case and the failures stopped.
>
> I gather you now have space for two m.2 SSD's.   If you haven't discarded
> the non-working devices,
> it would be interesting to see if any are detected and what smartmontools
> says about them, but
> you also have the option to put /var on a separate drive.  Smartmon tools
> can monitor a drive and
> report any problems it detects, but you may also want to run self-tests
> periodically.
>
>
>
>>
>> Thanks,
>> Neal
>>
>> On Tue, Feb 22, 2022 at 8:44 AM Richard Shaw 
>> wrote:
>>
>>> On Tue, Feb 22, 2022 at 7:34 AM Neal Becker  wrote:
>>>
 I know this is a bit OT, but you guys are great at answering all
 questions.

 I bought a workstation from Titan computers around 1/2020 (dual EPYC
 cpu).  After about 1 year it stopped working.  I could ssh to it, and
 almost any command would return Input/Output error.  Unfortunately
 journalctl gave input/output error so I can't see logs.  cat
 /proc/partitions did not show any nvme device (the root device) on which
 the OS was installed.

 I replaced the SSD with a samsung 980 pro.  Reinstalled fedora.  It
 then worked a few weeks, then the exact same symptoms.

 I replaced the SSD with another samsung 980 pro, this time with
 heatsink.  Reinstalled fedora.  It worked a few weeks.  Then same symptoms.

 Then I replaced with a 4th samsung 980 pro, but this time instead of
 using the M.2 socket I used a pcie-m.2 adapter (in case something was wrong
 with the m.2 socket).  Also added a surge protector outlet for good
 measure. Reinstalled.  Watched the smartctl.  No errors.  Temperature was
 always low.

 Now it's failed again, exactly same symptoms.

 Any ideas?

>>>
>>> I remember your other email about a month or so ago and thought it was
>>> really strange. Have you tried the drives in another system to confirm
>>> they're truly dead?
>>>
>>> I would check for BIOS updates just for good measure. Other than that,
>>> have you had any communication with Titan about it?
>>>
>>> Thanks,
>>> Richard
>>> ___
>>> users mailing list -- users@lists.fedoraproject.org
>>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>>> Do not reply to spam on the list, report it:
>>> 

Re: ssd keeps dying (OT)

[George N. White III]

On Tue, 22 Feb 2022 at 10:04, Neal Becker  wrote:

> Thanks Richard.  Yes, I talked with Titan; they suggested trying the
> pcie-m.2 adapter.  I will try them again.
> I have not checked for bios updates.  Not sure how to go about that (last
> time I did that it required an msdos floppy disc).
>
> Haven't tried the SSDs in another device because I don't have one.  But
> the fact that replacing the SSD causes it to work, where it wasn't working
> before, tells me they were damaged.  I have at least once power off/on the
> workstation, and the bios did not find any ssd to boot from.  So power
> cycle didn't fix it, but replace ssd did fix it.
>
> I will try Titan again later today, but just looking for ideas.
>

With this history, I'd probably replace the workstation power supply.   I
would also scan the
the system board for capacitors on bulging tops or overheated components.

Are there any externally powered devices connected to the workstation
(other than the monitor)?

Are you in an area with frequent lightning storms?  How stable is your
power?  Is the system
connected to a UPS?

I had a similar experience with spinning disks in a system that contained a
drive-bay radio receiver
and was connected to a satellite dish and GPS receiver on the roof, and an
antenna controller.  Everything
was powered by a high quality UPS.  I added a heavy wire connecting the
antenna controller case to the
workstation case and the failures stopped.

I gather you now have space for two m.2 SSD's.   If you haven't discarded
the non-working devices,
it would be interesting to see if any are detected and what smartmontools
says about them, but
you also have the option to put /var on a separate drive.  Smartmon tools
can monitor a drive and
report any problems it detects, but you may also want to run self-tests
periodically.



>
> Thanks,
> Neal
>
> On Tue, Feb 22, 2022 at 8:44 AM Richard Shaw  wrote:
>
>> On Tue, Feb 22, 2022 at 7:34 AM Neal Becker  wrote:
>>
>>> I know this is a bit OT, but you guys are great at answering all
>>> questions.
>>>
>>> I bought a workstation from Titan computers around 1/2020 (dual EPYC
>>> cpu).  After about 1 year it stopped working.  I could ssh to it, and
>>> almost any command would return Input/Output error.  Unfortunately
>>> journalctl gave input/output error so I can't see logs.  cat
>>> /proc/partitions did not show any nvme device (the root device) on which
>>> the OS was installed.
>>>
>>> I replaced the SSD with a samsung 980 pro.  Reinstalled fedora.  It then
>>> worked a few weeks, then the exact same symptoms.
>>>
>>> I replaced the SSD with another samsung 980 pro, this time with
>>> heatsink.  Reinstalled fedora.  It worked a few weeks.  Then same symptoms.
>>>
>>> Then I replaced with a 4th samsung 980 pro, but this time instead of
>>> using the M.2 socket I used a pcie-m.2 adapter (in case something was wrong
>>> with the m.2 socket).  Also added a surge protector outlet for good
>>> measure. Reinstalled.  Watched the smartctl.  No errors.  Temperature was
>>> always low.
>>>
>>> Now it's failed again, exactly same symptoms.
>>>
>>> Any ideas?
>>>
>>
>> I remember your other email about a month or so ago and thought it was
>> really strange. Have you tried the drives in another system to confirm
>> they're truly dead?
>>
>> I would check for BIOS updates just for good measure. Other than that,
>> have you had any communication with Titan about it?
>>
>> Thanks,
>> Richard
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>> Do not reply to spam on the list, report it:
>> https://pagure.io/fedora-infrastructure
>>
>
>
> --
> *Those who don't understand recursion are doomed to repeat it*
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 

Re: ssd keeps dying (OT)

[Roger Heflin]

By dead you mean it just quits answering on the bus at all?

I had a recent crucial 2TB SSD issue.  The first one failed in under
10 days, I got a replacement and the 2nd one pretty much did the same
thing at about the same time so, I returned it for a refund.

It makes me think that whatever is going on with them is something in
the SSD controller related in some way, and maybe both have the same
controller.   I have previously had a SSD firmware bug cause
consistent failures at a given power on hours valu (5+ years ago)e,
and I also know in there have been some of that same sort of power on
hours defect in other brands that "die" at some POH value.

I would check to see if they have any firmware updates for the drive.
  Some of the POH failures leave the drive permanently dead, and some
stay up long enough (after hitting the magic number of POH hours) to
get firmware updated (self test after xxx POH hours would fail, but
did not run until it was powered on for an hour after being reset).

There seem to be a lot of ways to screw up SSD firmware such that the
devices die.

On Tue, Feb 22, 2022 at 8:04 AM Neal Becker  wrote:
>
> Thanks Richard.  Yes, I talked with Titan; they suggested trying the pcie-m.2 
> adapter.  I will try them again.
> I have not checked for bios updates.  Not sure how to go about that (last 
> time I did that it required an msdos floppy disc).
>
> Haven't tried the SSDs in another device because I don't have one.  But the 
> fact that replacing the SSD causes it to work, where it wasn't working 
> before, tells me they were damaged.  I have at least once power off/on the 
> workstation, and the bios did not find any ssd to boot from.  So power cycle 
> didn't fix it, but replace ssd did fix it.
>
> I will try Titan again later today, but just looking for ideas.
>
> Thanks,
> Neal
>
> On Tue, Feb 22, 2022 at 8:44 AM Richard Shaw  wrote:
>>
>> On Tue, Feb 22, 2022 at 7:34 AM Neal Becker  wrote:
>>>
>>> I know this is a bit OT, but you guys are great at answering all questions.
>>>
>>> I bought a workstation from Titan computers around 1/2020 (dual EPYC cpu).  
>>> After about 1 year it stopped working.  I could ssh to it, and almost any 
>>> command would return Input/Output error.  Unfortunately journalctl gave 
>>> input/output error so I can't see logs.  cat /proc/partitions did not show 
>>> any nvme device (the root device) on which the OS was installed.
>>>
>>> I replaced the SSD with a samsung 980 pro.  Reinstalled fedora.  It then 
>>> worked a few weeks, then the exact same symptoms.
>>>
>>> I replaced the SSD with another samsung 980 pro, this time with heatsink.  
>>> Reinstalled fedora.  It worked a few weeks.  Then same symptoms.
>>>
>>> Then I replaced with a 4th samsung 980 pro, but this time instead of using 
>>> the M.2 socket I used a pcie-m.2 adapter (in case something was wrong with 
>>> the m.2 socket).  Also added a surge protector outlet for good measure. 
>>> Reinstalled.  Watched the smartctl.  No errors.  Temperature was always low.
>>>
>>> Now it's failed again, exactly same symptoms.
>>>
>>> Any ideas?
>>
>>
>> I remember your other email about a month or so ago and thought it was 
>> really strange. Have you tried the drives in another system to confirm 
>> they're truly dead?
>>
>> I would check for BIOS updates just for good measure. Other than that, have 
>> you had any communication with Titan about it?
>>
>> Thanks,
>> Richard
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>> Do not reply to spam on the list, report it: 
>> https://pagure.io/fedora-infrastructure
>
>
>
> --
> Those who don't understand recursion are doomed to repeat it
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: ssd keeps dying (OT)

[Neal Becker]

Thanks Richard.  Yes, I talked with Titan; they suggested trying the
pcie-m.2 adapter.  I will try them again.
I have not checked for bios updates.  Not sure how to go about that (last
time I did that it required an msdos floppy disc).

Haven't tried the SSDs in another device because I don't have one.  But the
fact that replacing the SSD causes it to work, where it wasn't working
before, tells me they were damaged.  I have at least once power off/on the
workstation, and the bios did not find any ssd to boot from.  So power
cycle didn't fix it, but replace ssd did fix it.

I will try Titan again later today, but just looking for ideas.

Thanks,
Neal

On Tue, Feb 22, 2022 at 8:44 AM Richard Shaw  wrote:

> On Tue, Feb 22, 2022 at 7:34 AM Neal Becker  wrote:
>
>> I know this is a bit OT, but you guys are great at answering all
>> questions.
>>
>> I bought a workstation from Titan computers around 1/2020 (dual EPYC
>> cpu).  After about 1 year it stopped working.  I could ssh to it, and
>> almost any command would return Input/Output error.  Unfortunately
>> journalctl gave input/output error so I can't see logs.  cat
>> /proc/partitions did not show any nvme device (the root device) on which
>> the OS was installed.
>>
>> I replaced the SSD with a samsung 980 pro.  Reinstalled fedora.  It then
>> worked a few weeks, then the exact same symptoms.
>>
>> I replaced the SSD with another samsung 980 pro, this time with
>> heatsink.  Reinstalled fedora.  It worked a few weeks.  Then same symptoms.
>>
>> Then I replaced with a 4th samsung 980 pro, but this time instead of
>> using the M.2 socket I used a pcie-m.2 adapter (in case something was wrong
>> with the m.2 socket).  Also added a surge protector outlet for good
>> measure. Reinstalled.  Watched the smartctl.  No errors.  Temperature was
>> always low.
>>
>> Now it's failed again, exactly same symptoms.
>>
>> Any ideas?
>>
>
> I remember your other email about a month or so ago and thought it was
> really strange. Have you tried the drives in another system to confirm
> they're truly dead?
>
> I would check for BIOS updates just for good measure. Other than that,
> have you had any communication with Titan about it?
>
> Thanks,
> Richard
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
*Those who don't understand recursion are doomed to repeat it*
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: ssd keeps dying (OT)

[Richard Shaw]

On Tue, Feb 22, 2022 at 7:34 AM Neal Becker  wrote:

> I know this is a bit OT, but you guys are great at answering all questions.
>
> I bought a workstation from Titan computers around 1/2020 (dual EPYC
> cpu).  After about 1 year it stopped working.  I could ssh to it, and
> almost any command would return Input/Output error.  Unfortunately
> journalctl gave input/output error so I can't see logs.  cat
> /proc/partitions did not show any nvme device (the root device) on which
> the OS was installed.
>
> I replaced the SSD with a samsung 980 pro.  Reinstalled fedora.  It then
> worked a few weeks, then the exact same symptoms.
>
> I replaced the SSD with another samsung 980 pro, this time with heatsink.
> Reinstalled fedora.  It worked a few weeks.  Then same symptoms.
>
> Then I replaced with a 4th samsung 980 pro, but this time instead of using
> the M.2 socket I used a pcie-m.2 adapter (in case something was wrong with
> the m.2 socket).  Also added a surge protector outlet for good measure.
> Reinstalled.  Watched the smartctl.  No errors.  Temperature was always low.
>
> Now it's failed again, exactly same symptoms.
>
> Any ideas?
>

I remember your other email about a month or so ago and thought it was
really strange. Have you tried the drives in another system to confirm
they're truly dead?

I would check for BIOS updates just for good measure. Other than that, have
you had any communication with Titan about it?

Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

ssd keeps dying (OT)

[Neal Becker]

I know this is a bit OT, but you guys are great at answering all questions.

I bought a workstation from Titan computers around 1/2020 (dual EPYC cpu).
After about 1 year it stopped working.  I could ssh to it, and almost any
command would return Input/Output error.  Unfortunately journalctl gave
input/output error so I can't see logs.  cat /proc/partitions did not show
any nvme device (the root device) on which the OS was installed.

I replaced the SSD with a samsung 980 pro.  Reinstalled fedora.  It then
worked a few weeks, then the exact same symptoms.

I replaced the SSD with another samsung 980 pro, this time with heatsink.
Reinstalled fedora.  It worked a few weeks.  Then same symptoms.

Then I replaced with a 4th samsung 980 pro, but this time instead of using
the M.2 socket I used a pcie-m.2 adapter (in case something was wrong with
the m.2 socket).  Also added a surge protector outlet for good measure.
Reinstalled.  Watched the smartctl.  No errors.  Temperature was always low.

Now it's failed again, exactly same symptoms.

Any ideas?

Thanks,
Neal
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: WAS: Kinda OT: Email clients -- NOW: Storage formats

[Patrick O'Callaghan]

On Tue, 2022-02-22 at 13:30 +1030, Tim via users wrote:
> Of the few folders mine does store locally, it's in maildir.  I don't
> know if that's user-selectable, though.  The preferences window even
> says it's maildir for the default "on this computer" folder, but that
> folder's not editable (there's only an enable/disable entire folder
> option for it).
> 
> I suspect though, that internally it sticks with maildir for storing
> any mail it's fetched itself.  All the local mail folders I see in
> ~/.local/share/evolution/mail/ are maildir.

IIRC it's the default for the account, but can be changed at setup
time.

https://help.gnome.org/users/evolution/stable/mail-account-management.html.en#mail-common-account-types

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Re[2]: Perl is now failing for me

[George N. White III]

On Tue, 22 Feb 2022 at 06:31, M. Fioretti  wrote:

> On Mon, Feb 21, 2022 09:21:05 AM -0400, George N. White III wrote:
>
>
> > Open source makes it easy for people to innovate, and we need to
> > encourage experimentation, but we can't have  experiments in linux
> > distros.
>
> George,
>
> the core of that post of mine is that what you say has become
> impossible. That is, it has become IMPOSSIBLE, for users with more
> than really basic needs, who still are many more than developers
> buthave other ways to serve the community, to NOT "experiment",
> wasting against their will much more time than it was the case 10
> years ago, whatever distro they choose.
>
> >
> https://stop.zona-m.net/2022/01/the-sorry-sorry-state-of-linux-packaging/
> >
> > CPAN, CTAN, CRAN etc. exist because they support multiple OS's.
>
> Whatever. The reality still is that they and their equivalents for
> other languages have made it impossible for anyone on any OS to have a
> unified front end for package management. And this is not progress wrt
> 10/15 years ago, no matter how one puts it.
>

I cobbled together a moderately complex software system, originally
developed on
SGI IRIX64.  One part of the system is built around a C++ library that
comes and goes from distributions.  There are several Fortran programs
that use an error handling package which never fully made the transition to
Fortran 90.   The system also relies on a number of POSIX tools, awk, join,
sed, etc.It also required a much more complex NASA package that has not
be ported to Windows (and never will be because it contains support for
legacy satellite platforms that would be enormously expensive to port
to Windows) to extract input data and a couple large programs that
are available from distros but built without options I need.   I replaced
the one program from the NASA package with a Python script for use
on Windows, but it depends on several large Python libraries.  I end up
spending a lot of time testing new Python versions and new libraries to
ensure they are still working properly (new versions often have problems,
but they generally get fixed without my help).

Porting the system to a new linux distro means working out which libraries
aren't packaged.   This can be tricky as there are often newer
drop-replacements
for legacy libraries (aes versus sz is the most recent example).

>
> > Packages are messy and likely always will be.
>
> Packages are MUCH messier now than before, without any real reason I
> can recognize as such, and for users this is NOT progress, that's my
> whole point. And I am not talking newbies. I used to compile from
> sources tens of packages, back in the 90's/early 00s.
>

I agree that it has become much more difficult to port a complex system
to linux due to differences in what libraries are packed and in the
configure
options used for a given library on different distributions.   There is
also the
problem that some distros enable options that don't actually work because
they rely on a newer version of other distro package.


>
> Today, I am forced to spend MORE time than back then to restore a
> system that does what I need every time I upgrade the distro, because:
>
> a) compiling everything from source would be consume even more time,
> much more than when "config, make, make install" and manual dependency
> solving was enough
>

The NASA package I use provides binaries built on CENTOS, but also
sources so you can build it on distros that aren't compatible.   If the
majority
of users weren't forced by their institutions to use Windows I would
consideri making my package an add-on, su using the NASA libraries and
build system (python build scripts for each library that run cmake or
configure
as required).


>
> b) so the least worst way to cope is to endure (every time with
>different, often undocumented gotchas) ten different packaging
>systems who couldn't care less to acknowledge that people could
>need sw from different communities
>

Many groups are now using conda-forge and adding packages for
the stuff they need.

>
> Sure, software becomes more complex over time. But this doesn't mean
> that what we have today makes sense.
>

I participate in a couple user forums.   At one time the forums were
dominated
by questions over details of the algorithms and bug reports.   Now, there
are
many problems related to packing and version conflicts.  Linux distros
generally reserve "python" for python 2.7, and python3 for the current
system python 3.x version, but Anaconda uses "python".   There are
often multiple python packages with the same or similar names.

Sure that doesn't make sense, but there is no mechanism to force
Anaconda to use "python3" or to require unique names for python
packages.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 

Re: WAS: Kinda OT: Email clients -- NOW: Storage formats

[Patrick O'Callaghan]

On Mon, 2022-02-21 at 11:55 -0600, c. marlow wrote:
> 
> I meant to ask you Patrick:
> 
> What format does Evolution use to store emails in?
> 
> Like for instance... Claws uses the MH format where it stores all
> emails
> as individual numbered files.

It's configurable. It can use the old MBOX format but the best option
for local mail is probably Maildir, which keeps a separate file for
each message and is lock-free.

See https://en.wikipedia.org/wiki/Maildir

If you have detailed questions, I'd suggest asking on the Evolution
list (evolution-l...@gnome.org). You can check the archives at:

https://mail.gnome.org/archives/evolution-list/

When posting on the list, be sure to mention your version of Evolution
(Help->About).

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: does i am able to build a python program for rpm using '''python setup.py bdist_rpm''' with dependency python in virtual using '''python3 -m pip install --user env venv '''

[Dorian ROSSE]

Dear Gordon,


Can I create with this line of command :

'''python3 -m pip install env venv ''' then the other line of command,

Thanks you in advance for your answer,

Regards.


Dorian Rosse.

From: Gordon Messmer 
Sent: Sunday, February 20, 2022 8:29:46 PM
To: users@lists.fedoraproject.org 
Subject: Re: does i am able to build a python program for rpm using '''python 
setup.py bdist_rpm''' with dependency python in virtual using '''python3 -m pip 
install --user env venv '''

On 2/20/22 01:39, Dorian ROSSE wrote:
> does i am able to build a python program for rpm using '''python
> setup.py bdist_rpm''' with dependency python in virtual using
> '''python3 -m pip install --user env venv ''',


I think those two things are mostly unrelated.  The rpm created by
bdist_rpm will target the system installation of Python, not a user's
venv.  If you want to create something that can be installed in a venv
by pip, I believe you'd want to create a "wheel".
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Re[2]: Perl is now failing for me

[M. Fioretti]

On Mon, Feb 21, 2022 09:21:05 AM -0400, George N. White III wrote:


> Open source makes it easy for people to innovate, and we need to
> encourage experimentation, but we can't have  experiments in linux
> distros.

George,

the core of that post of mine is that what you say has become
impossible. That is, it has become IMPOSSIBLE, for users with more
than really basic needs, who still are many more than developers
buthave other ways to serve the community, to NOT "experiment",
wasting against their will much more time than it was the case 10
years ago, whatever distro they choose.

>  https://stop.zona-m.net/2022/01/the-sorry-sorry-state-of-linux-packaging/
> 
> CPAN, CTAN, CRAN etc. exist because they support multiple OS's.

Whatever. The reality still is that they and their equivalents for
other languages have made it impossible for anyone on any OS to have a
unified front end for package management. And this is not progress wrt
10/15 years ago, no matter how one puts it.

> Packages are messy and likely always will be.

Packages are MUCH messier now than before, without any real reason I
can recognize as such, and for users this is NOT progress, that's my
whole point. And I am not talking newbies. I used to compile from
sources tens of packages, back in the 90's/early 00s.

Today, I am forced to spend MORE time than back then to restore a
system that does what I need every time I upgrade the distro, because:

a) compiling everything from source would be consume even more time,
much more than when "config, make, make install" and manual dependency
solving was enough

b) so the least worst way to cope is to endure (every time with
   different, often undocumented gotchas) ten different packaging
   systems who couldn't care less to acknowledge that people could
   need sw from different communities

Sure, software becomes more complex over time. But this doesn't mean
that what we have today makes sense.

Marco
-- 
Help me write my NEXT MILLION WORDS for digital awareness:
https://stop.zona-m.net/2021/10/funding-2021-2022/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure