Re: Local, system e-mails only delivered on reboot--SOLVED

[Barry]

> On 3 Jul 2024, at 21:47, Tim Evans  wrote:
> 
> DNS is the auto-gobbledegook F40 uses, which point the system to itself.

The resolv.conf file is created on each boot.

Configure how dns works with the /etc/systemd/resolve.conf and networkmanager 
to ignore the search from dhcp. Then it will stop turning up.

You van use resolvectl to see what is going on.

Barry


-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: nmcli and system-connections

[Samuel Sieb]

On 7/3/24 7:02 PM, Alex wrote:


 > However, I also have virtual interfaces on eth1:1 and others.
What are the next steps?

Interface aliases are pretty much deprecated (see the thread
about ifconfig), you’d just assign multiple IPs/prefixes to eth1.


I do see that now, after another few hours trying to make this work,
but do you have any idea why it wouldn't write the config files to
/etc/NetworkManager/system-connections?


I'm still not sure why the connections weren't migrated from the old 
format even after it said it did, but I did just get it to work.


I basically deleted all the ifcfg-* interface files, deleted all the 
connections with 'nmcli c delete " then started over from scratch. 
Apparently there's more stored somewhere else than what's just in the 
files located in /etc/NetworkManager/system-connections.


After deleting everything and rebooting, nmcli/NetworkManager basically 
created the two interfaces on this server automatically, although it 
still didn't create the /etc/NetworkManager/system-connections files.


I was then able to create a basic bridge and add "Wired Connection 1" to 
the bridge:

# nmcli connection modify "Wired Connection 1" master br0

I later renamed it to eno1.

This page was helpful:
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-a-network-bridge_configuring-and-managing-networking#configuring-a-network-bridge-by-using-nmcli_configuring-a-network-bridge
 



You might want to try installing "nm-connection-editor".  It's a nice 
graphical interface that handles most of the network options.


--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: nmcli and system-connections

[Alex]

>
>
>> > However, I also have virtual interfaces on eth1:1 and others. What are
>> the next steps?
>>
>> Interface aliases are pretty much deprecated (see the thread about
>> ifconfig), you’d just assign multiple IPs/prefixes to eth1.
>
>
> I do see that now, after another few hours trying to make this work, but
> do you have any idea why it wouldn't write the config files to
> /etc/NetworkManager/system-connections?
>

I'm still not sure why the connections weren't migrated from the old format
even after it said it did, but I did just get it to work.

I basically deleted all the ifcfg-* interface files, deleted all the
connections with 'nmcli c delete " then started over from scratch.
Apparently there's more stored somewhere else than what's just in the files
located in /etc/NetworkManager/system-connections.

After deleting everything and rebooting, nmcli/NetworkManager basically
created the two interfaces on this server automatically, although it still
didn't create the /etc/NetworkManager/system-connections files.

I was then able to create a basic bridge and add "Wired Connection 1" to
the bridge:
# nmcli connection modify "Wired Connection 1" master br0

I later renamed it to eno1.

This page was helpful:
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-a-network-bridge_configuring-and-managing-networking#configuring-a-network-bridge-by-using-nmcli_configuring-a-network-bridge
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: nmcli and system-connections

[Alex]

>
>
>
> > However, I also have virtual interfaces on eth1:1 and others. What are
> the next steps?
>
> Interface aliases are pretty much deprecated (see the thread about
> ifconfig), you’d just assign multiple IPs/prefixes to eth1.


I do see that now, after another few hours trying to make this work, but do
you have any idea why it wouldn't write the config files to
/etc/NetworkManager/system-connections?
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot--SOLVED

[Tim Evans]

On 7/3/24 5:52 PM, Tom Horsley wrote:

On Wed, 3 Jul 2024 16:45:30 -0400
Tim Evans wrote:


Se, we find where the bogus domain name comes from.  AND, changing it to
my actual domain name, then running the sendmail queue clears everything
out of the queue.


But will the network software put back the bogus resolv.conf behind your back
so the problem will just return? :-).


I expect that--will see on next reboot--but at least will know where to 
look next time.

--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot--SOLVED

[Jeffrey Walton]

On Wed, Jul 3, 2024 at 4:47 PM Tim Evans  wrote:
>
> On 7/3/24 4:10 PM, Tim via users wrote:
> > On Wed, 2024-07-03 at 10:04 -0400, Tim Evans wrote:
> >> Jul 03 09:45:07 kestrel sendmail[1526]: 45T7V2ou003307:
> >> to=, delay=4+06:14:04, xdelay=00:00:00,
> >> mailer=esmtp, pri=9500566, relay=kestrel.mynetworksettings.com.,
> >> dsn=4.4.1, stat=Deferred: Connection refused by
> >> kestrel.mynetworksettings.com.
> >
> > Is your computer's network configured by DHCP?
> > And is your ISP router the DHCP server?
> > And is it your DNS server, too?
> >
>
> Thanks, your questions have led me to an apparent solution.
>
> This system is my firwall/router, dual homed, on the protected internal
> network and the DMZ. Its internal network IP addresses is manually
> assigned; its external address gets its address via DHCP from the
> Verizon router. DNS is the auto-gobbledegook F40 uses, which point the
> system to itself.  /etc/resolve.conf contains:
>
> nameserver 127.0.0.53
> options edns0 trust-ad
> search mynetworksettings.com
>
> Se, we find where the bogus domain name comes from.  AND, changing it to
> my actual domain name, then running the sendmail queue clears everything
> out of the queue.

mynetworksettings.com smells very fishy.

Does `sudo grep -IR 'mynetworksettings.com' /etc` reveal any interesting hits?

Jeff
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot--SOLVED

[Tom Horsley]

On Wed, 3 Jul 2024 16:45:30 -0400
Tim Evans wrote:

> Se, we find where the bogus domain name comes from.  AND, changing it to 
> my actual domain name, then running the sendmail queue clears everything 
> out of the queue.

But will the network software put back the bogus resolv.conf behind your back
so the problem will just return? :-).
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: nmcli and system-connections

[Jonathan Billings]

On Jul 3, 2024, at 12:15, Alex  wrote:
> However, I also have virtual interfaces on eth1:1 and others. What are the 
> next steps?

Interface aliases are pretty much deprecated (see the thread about ifconfig), 
you’d just assign multiple IPs/prefixes to eth1. 

-- 
Jonathan Billings
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot--SOLVED

[Tim Evans]

On 7/3/24 4:10 PM, Tim via users wrote:

On Wed, 2024-07-03 at 10:04 -0400, Tim Evans wrote:

Jul 03 09:45:07 kestrel sendmail[1526]: 45T7V2ou003307:
to=, delay=4+06:14:04, xdelay=00:00:00,
mailer=esmtp, pri=9500566, relay=kestrel.mynetworksettings.com.,
dsn=4.4.1, stat=Deferred: Connection refused by
kestrel.mynetworksettings.com.


Is your computer's network configured by DHCP?
And is your ISP router the DHCP server?
And is it your DNS server, too?
  


Thanks, your questions have led me to an apparent solution.

This system is my firwall/router, dual homed, on the protected internal 
network and the DMZ. Its internal network IP addresses is manually 
assigned; its external address gets its address via DHCP from the 
Verizon router. DNS is the auto-gobbledegook F40 uses, which point the 
system to itself.  /etc/resolve.conf contains:


nameserver 127.0.0.53
options edns0 trust-ad
search mynetworksettings.com

Se, we find where the bogus domain name comes from.  AND, changing it to 
my actual domain name, then running the sendmail queue clears everything 
out of the queue.

--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot

[Tim via users]

On Wed, 2024-07-03 at 10:04 -0400, Tim Evans wrote:
> Jul 03 09:45:07 kestrel sendmail[1526]: 45T7V2ou003307: 
> to=, delay=4+06:14:04, xdelay=00:00:00, 
> mailer=esmtp, pri=9500566, relay=kestrel.mynetworksettings.com., 
> dsn=4.4.1, stat=Deferred: Connection refused by 
> kestrel.mynetworksettings.com.

Is your computer's network configured by DHCP?
And is your ISP router the DHCP server?
And is it your DNS server, too?
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.118.1.el7.x86_64 #1 SMP Wed Apr 24 16:01:50 UTC 2024 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 

-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot

[Tim Evans]

On 7/3/24 11:25 AM, George N. White III wrote:
On Wed, Jul 3, 2024 at 12:16 PM George N. White III > wrote:


On Wed, Jul 3, 2024 at 11:43 AM Tom Horsley mailto:horsley1...@gmail.com>> wrote:

On Wed, 3 Jul 2024 10:04:30 -0400
Tim Evans wrote:

 > Suggestions for further digging?  Thanks.

Probably not really helpful, but sendmail is utterly cryptic, I
started
using postfix years ago because it was easier to configure.


I did the same.   A web search for http://mynetworksettings.com>> suggests
it is a Verizon thing.

Found 
https://www.verizon.com/content/dam/support/pdf/user_guide/Verizon-Internet-Gateway-(ASK-NCM1100)-User-Manual-v1.pdf 
In "CONFIGURE the VERIZON INTERNET GATEWAY", it says you can use 
192.168.1.1 for  !


Well, this suggests the system is trying to relay its LOCAL e-mail via 
Verizon's router, as this system is my network's firewall/router. (Other 
F40 systems on the internal network don't show this behavior, and local 
e-mail is delivered properly.)

--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: install fedora 40 raid1+lvm

[Peter Boy]

> Am 03.07.2024 um 18:34 schrieb François Patte 
> :
> 
> Bonjour,
> 
> Where can I find some details on the installation of fedora 40, I would like 
> to have raid1 arrays and lvm.

For Fedora server you may have a look at: 
https://pboy.fedorapeople.org/InstGuideF33-Hetzner-en.pdf

Not really a guide but a rather detailed step-by-step description:
https://pagure.io/fedora-server/issue/89 
For GPT/UEFI systems and 

And 

https://pagure.io/fedora-server/issue/87
For GPT/BiosBoot systems


Feel free to ask about anything that’s unclear.




--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast






--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast




-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

livecd-iso-to-disk with data-persistence

[Meikel]

Hi folks,

on a Fedora 40 XFCE I'm running livecd-iso-to-disk to create a bootable 
stick with persistent home and persistent overlay. In the direcotry 
where I downloaded Fedora-Xfce-Live-x86_64-40-1.14.iso I run the 
following command:


    sudo livecd-iso-to-disk --efi --format --reset-mbr --nomac 
--unencrypted-home --home-size-mb 8192 --overlay-size-mb 16384 
Fedora-Xfce-Live-x86_64-40-1.14.iso /dev/sdc


I can boot another machine from that stick as expected. It feels as if 
home dir ist persistent, for example I configured keyboard layout and 
wifi password, and when I reboot from the USB stick those settings 
remain. From my understanding they are stored in the home directory. 
Furthermore I did


    date >> ~/persistent.txt

which also remains after reboot. But it feels as if the 'data 
persistence' doesn't work. I ran an dnf update and got errors:


sudo dnf -y update
...
(406/563): open-vm-tools-12.4.0-1.fc40.x86_64.rpm 2.5 MB/s | 871 kB 
00:00
(407/563): open-vm-tools-desktop-12.4.0-1.fc40.x86_64.rpm 1.4 MB/s | 163 
kB 00:00
(408/563): openexr-libs-3.1.10-6.fc40.x86_64.rpm 2.7 MB/s | 1.1 MB 
00:00

(409/563): orca-46.1-2.fc40.noarch.rpm 330 kB/s | 3.3 MB 00:10
[MIRROR] nvidia-gpu-firmware-20240610-1.fc40.noarch.rpm: Curl error 
(23): Failed writing received data to disk/application for 
https://fr2.rpmfind.net/linux/fedora/linux/updates/40/Everything/x86_64/Packages/n/nvidia-gpu-firmware-20240610-1.fc40.noarch.rpm 
[Failure writing output to destination]
[FAILED] nvidia-gpu-firmware-20240610-1.fc40.noarch.rpm: Curl error 
(23): Failed writing received data to disk/application for 
https://fr2.rpmfind.net/linux/fedora/linux/updates/40/Everything/x86_64/Packages/n/nvidia-gpu-firmware-20240610-1.fc40.noarch.rpm 
[Failure writing output to destination]
(411-412/563): mint-y-icons-1.7.5-1.fc40.noarch.rpm   
82% [ ] 7.9 MB/s 
| 844 MB 00:22 ETA
The downloaded packages were saved in cache until the next successful 
transaction.

You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
nvidia-gpu-firmware-20240610-1.fc40.noarch: Download failed: Curl error 
(23): Failed writing received data to disk/application for 
https://fr2.rpmfind.net/linux/fedora/linux/updates/40/Everything/x86_64/Packages/n/nvidia-gpu-firmware-20240610-1.fc40.noarch.rpm 
[Failure writing output to destination]


I verified with

    df -Th
    Filesystem  Type  Size  Used Avail Use% Mounted on
/dev/mapper/live-rw ext4  5.9G  5.8G   75M  99% /
devtmpfs devtmpfs  4.0M 0  4.0M   0% /dev
tmpfs tmpfs 1.9G 0  1.9G   0% /dev/shm
efivarfs efivarfs  128K   91K   33K  74% /sys/firmware/efi/efivars
tmpfs tmpfs 746M  9.6M  736M   2% /run
/dev/sdb1 ext4   57G   26G   28G  49% /run/initramfs/live
tmpfs tmpfs 1.9G  8.0K  1.9G   1% /tmp
vartmp tmpfs 1.9G 0  1.9G   0% /var/tmp
/dev/loop3 ext4  7.8G   21M  7.4G   1% /home
tmpfs tmpfs 373M  116K  373M   1% /run/user/1000
tmpfs tmpfs 373M   96K  373M   1% /run/user/1001

I expect /dev/mapper/live-rw to be bigger than 5.8G, I expect it to be 
16GB as specified with --overlay-size-mb 16384 parameter. What am I 
doing wrong when creating the bootable USB stick? Which options Do I 
have to set, that it becomes a stick with 'data persistence' as 
explained in 
https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/index.html#command-line-method


    "/'data persistence' support - so changes you make to the entire 
live environment will persist across boots/"


Thanks in advance for any help.

Regards,

Meikel

--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: remove a disk from raid1 array

[Roger Heflin]

You need to add this to the grub kernel boot line:
bootdegraded=true
otherwise the default behavior is to freak out and not work.

On Wed, Jul 3, 2024 at 5:17 AM François Patte
 wrote:
>
> Bonjour,
>
> I need to remove a disk from a raid1 array and restart the computer
> *without* that disk and without any other disk
>
> Up to now, if I stop the computer, unplug the disk and restart, the
> computer does not start complaining that it has not find all the disks.
>
> Do I have to remove the disk from the array (set it faulty and remove)
> with mdadm before stopping the computer? Or is there another way to
> proceed?
>
> Thank you.
>
> --
> François Patte
> UFR de mathématiques et informatique
> Laboratoire CNRS MAP5, UMR 8145
> Université Paris Descartes
> 45, rue des Saints Pères
> F-75270 Paris Cedex 06
> Tél. +33 (0)6 7892 5822
> http://www.math-info.univ-paris5.fr/~patte
> --
> ___
> 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, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot

[Mike Wright]

On 7/3/24 07:21, Tom Horsley wrote:


...sendmail is utterly cryptic,


I still have nightmares about the Bat book.

--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

install fedora 40 raid1+lvm

[François Patte]

Bonjour,

Where can I find some details on the installation of fedora 40, I would 
like to have raid1 arrays and lvm.


Thank you.

--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte
--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

[Frédéric]

> Are you using windows to create the usb stick?

No, I created them from F38 with either dd or mediawriter.

> Was the f36 image a lot smaller then all the newer versions?

I do not remember but I think they were all more than 2Mb.
I've now solved the issue by installing F36, then upgrading to F40. I
now run a brand new F40 on a brand new SSD :=)

It is still a pity that the live media do not boot as UEFI. This would
prevent people to trial Fedora.

Thanks
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

nmcli and system-connections

[Alex]

Hi,
I've just upgraded a fedora39 server to fedora40 and my network stopped
working because I was still using the legacy network-scripts ifcfg format.

I've gone through the migration using nmcli but not all connections were
migrated properly and no files were written to
/etc/NetworkManager/system-connections. The directory is empty.

Any idea why this may have happened? The connections are there:

# nmcli c
NAMEUUID  TYPE  DEVICE
br0 bc8c06e1-de8a-45cb-b011-ee517f316527  bridgebr0
eth125253a0c-a37f-4fbf-821b-167cb4a4c2d9  ethernet  eth1
Wired connection 1  d689f70c-1b64-370d-aa18-cf4bb8fb38c3  ethernet  eth0
lo  74c10aaf-3f2b-4e18-a751-d0bd601dbf7b  loopback  lo
virbr0  a8bd63ea-f45e-4230-aaff-882bfa1c16fd  bridgevirbr0
vnet0   03e4e6cc-c720-4f93-8189-ecde725292b4  tun   vnet0
Wired connection 2  3f23946f-954b-3760-bfc8-2df420e6d503  ethernet  --

However, I also have virtual interfaces on eth1:1 and others. What are the
next steps?

# nmcli c migrate
Connection 'lo' (74c10aaf-3f2b-4e18-a751-d0bd601dbf7b) successfully
migrated.
Connection 'Wired connection 1' (d689f70c-1b64-370d-aa18-cf4bb8fb38c3)
successfully migrated.
Connection 'Wired connection 2' (3f23946f-954b-3760-bfc8-2df420e6d503)
successfully migrated.
Connection 'br0' (bc8c06e1-de8a-45cb-b011-ee517f316527) successfully
migrated.
Connection 'virbr0' (a8bd63ea-f45e-4230-aaff-882bfa1c16fd) successfully
migrated.
Connection 'vnet0' (03e4e6cc-c720-4f93-8189-ecde725292b4) successfully
migrated.
Connection 'eth1' (25253a0c-a37f-4fbf-821b-167cb4a4c2d9) successfully
migrated.

I've also tried "nmcli con reload". I also had to manually bring up eth1
with ifconfig.
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot

[George N. White III]

On Wed, Jul 3, 2024 at 12:16 PM George N. White III 
wrote:

> On Wed, Jul 3, 2024 at 11:43 AM Tom Horsley  wrote:
>
>> On Wed, 3 Jul 2024 10:04:30 -0400
>> Tim Evans wrote:
>>
>> > Suggestions for further digging?  Thanks.
>>
>> Probably not really helpful, but sendmail is utterly cryptic, I started
>> using postfix years ago because it was easier to configure.
>>
>
> I did the same.   A web search for  suggests
> it is a Verizon thing.
>
> Found
https://www.verizon.com/content/dam/support/pdf/user_guide/Verizon-Internet-Gateway-(ASK-NCM1100)-User-Manual-v1.pdf
In "CONFIGURE the VERIZON INTERNET GATEWAY", it says you can use
192.168.1.1 for   !

-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot

[George N. White III]

On Wed, Jul 3, 2024 at 11:43 AM Tom Horsley  wrote:

> On Wed, 3 Jul 2024 10:04:30 -0400
> Tim Evans wrote:
>
> > Suggestions for further digging?  Thanks.
>
> Probably not really helpful, but sendmail is utterly cryptic, I started
> using postfix years ago because it was easier to configure.
>

I did the same.   A web search for  suggests
it is a Verizon thing.

-- 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Local, system e-mails only delivered on reboot

[Tom Horsley]

On Wed, 3 Jul 2024 10:04:30 -0400
Tim Evans wrote:

> Suggestions for further digging?  Thanks.

Probably not really helpful, but sendmail is utterly cryptic, I started
using postfix years ago because it was easier to configure.

Maybe run as root:

fgrep -R mynetworksettings /etc

to see if it can find the cryptic bit laying around somewhere?
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Local, system e-mails only delivered on reboot

[Tim Evans]

[I posted a similar question a couple of months back, but mistakenly 
thought I had resolved the issue]


One of my F40 systems fails to deliver local, system-generated e-mails 
(logfiles and such) UNTIL it gets rebooted.


sendmail-8.18.1-1.fc40.x86_64 is installed for local e-mail handling.

On reboot, SOME of the accumulated messages--along with failure warning 
messages that have been generated--get delivered to local mailbox 
(/var/spool/mail/username). Other messages remain in the queue.


Today, I noted at the end of a dnf update, the following:

Reload daemon failed: Transport endpoint is not connected
Failed to start jobs: Transport endpoint is not connected

No indication of which daemon being referred to, so it's not clear if 
this is referring to the sendmail daemon.


Journalctl reports (after rebooting):

Jul 03 09:45:04 kestrel (sendmail)[1524]: sendmail.service: Referenced 
but unset

 environment variable evaluates to an empty string: SENDMAIL_OPTARG
Jul 03 09:45:04 kestrel sendmail[1525]: starting daemon (8.18.1): 
SMTP+queueing@

01:00:00
Jul 03 09:45:04 kestrel systemd[1]: sendmail.service: Can't open PID 
file /run/sendmail.pid (yet?) after start: No such file or directory


And then, a batch of these, corresponding to the undelivered e-mails:

Jul 03 09:45:07 kestrel sendmail[1526]: 45T7V2ou003307: 
to=, delay=4+06:14:04, xdelay=00:00:00, 
mailer=esmtp, pri=9500566, relay=kestrel.mynetworksettings.com., 
dsn=4.4.1, stat=Deferred: Connection refused by 
kestrel.mynetworksettings.com.


Even so, SOME the queued messages were in fact delivered after the 
reboot completed. Others remain in the queue, for example:


# mailq
/var/spool/mqueue (9 requests)
-Q-ID- --Size-- -Q-Time- 
Sender/Recipient---

4627Lrpw008404 3884 Tue Jul  2 03:21 
 (Deferred: Connection refused by 
kestrel.mynetworksettings.co)

 

I do not know where the bogus domain name "mynetworksettings.com" comes 
from, as the system has a proper hostname.


My other F40 systems do not have this issue, as local e-mail is 
delivered properly.


Suggestions for further digging?  Thanks.
--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Hypothetical boot question

[Jonathan Billings]

> On Jul 2, 2024, at 19:31, Mike Wright  wrote:
> 
> On 7/2/24 07:44, Frank Bures wrote:
>> Hi,
>> I was wondering if it was possible to boot the existing F40 installation 
>> from a USB.  I tried to research this but everything I was able to find 
>> dealt with booting a live image of F40 from USB and/or installing a live 
>> image of F40 on a USB.
>> What I want is to create a USB stick with /boot and /boot/efi fs in such a 
>> way that it boots an existing F40 installation on a HD.
>> I am not talking about rescuing the system from a live Fedora USB.  I am 
>> talking about a fully automatic boot of an existing installed Fedora from a 
>> USB.
>> Is it possible and what would it involve?
> 
> I found this article; it is 8 years old and mostly covers MBR boot but there 
> is one efi boot example.
> 
> https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk
> 
> --
> 
> This one looks interesting.  Harddrives are hdX starting at 0.  Add a 
> menuentry to your usb grub.cfg
> 
> 
> menuentry "Boot from second disk" {
>   chainloader (hd1)+1
> }
> 
> but changed to this:
> 
> menuentry "Boot from first harddisk" {
>  chainloader (hd0)+1
> }
> 
> Give it a try and see what happens.

That won’t work for UEFI, you’d need to give a path to a UEFI executable on 
hdX. 

I believe you’d edit: /etc/grub.d/40_custom to add that to the final grub.cfg. 

-- 
Jonathan Billings
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

remove a disk from raid1 array

[François Patte]

Bonjour,

I need to remove a disk from a raid1 array and restart the computer 
*without* that disk and without any other disk


Up to now, if I stop the computer, unplug the disk and restart, the 
computer does not start complaining that it has not find all the disks.


Do I have to remove the disk from the array (set it faulty and remove) 
with mdadm before stopping the computer? Or is there another way to 
proceed?


Thank you.

--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte
--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

physicalfitt

[nike well]

I am nikewell a PR consultant at physicalfitt With over 6 years of experience 
in the PR and digital industry, I specialize in helping teams achieve their 
goals by streamlining processes and implementing effective strategies 
https://www.physicalfitt.com/
-- 
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue