Re: [CentOS] Unable to get dummy interfaces to persist across reboots in CentOS 8
No. Network Manager is always disabled on our builds since at least Cent5 days. The network stack has always been able to be managed properly without relying on Network Manager. Is that now an absolute requirement? It never has been prior. On Mon, Oct 26, 2020 at 6:26 PM Strahil Nikolov via CentOS wrote: > > Have you tried to use NetworkManager ? > After all ,anything network related should be done by it. > > [root@system ~]# nmcli connection add con-name dummy0 ifname dummy0 type dummy > Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully added. > > [root@system ~]# reboot > Shared connection to glustera closed. > > > [root@system ~]# uptime > 03:23:44 up 0 min, 1 user, load average: 1,57, 0,48, 0,17 > [root@glustera ~]# nmcli connection show > NAMEUUID TYPE DEVICE > dummy0 9fdd74fa-c143-4991-9bac-0e542704ac89 dummy dummy0 > > > [root@system ~]# ip a s dummy0 > 3: dummy0: mtu 1500 qdisc noqueue state UNKNOWN > group default qlen 1000 >link/ether ce:c9:83:97:10:ee brd ff:ff:ff:ff:ff:ff >inet6 fe80::599:a978:9457:df10/64 scope link noprefixroute > valid_lft forever preferred_lft forever > > P.S.: This is the first time I hear about dummy interfaces. What are those > used for ? > > Best Regards, > Strahil Nikolov > > > > > > > > > > В вторник, 27 октомври 2020 г., 02:42:06 Гринуич+2, Frank Even > написа: > > > > > > Anyone have any ideas? It's rather annoying that I can't get these to > persist across reboots without using some kind of helper script. > > On Fri, Oct 16, 2020 at 6:37 AM Frank Even > wrote: > > > > Hello all, hoping someone can help me out here. > > > > I cannot get dummy interfaces on a new Cent8 build to persist across > > reboots. > > > > On Cent7 - this is the process I use: > > > > Create Dummies: > > # cat /etc/modules-load.d/dummy.conf > > dummy > > # cat /etc/modprobe.d/dummyopts.conf > > options dummy numdummies=4 > > # ip link add dummy0 type dummy > > ## - repeating a/ ascending dummyN adapters for as many needed > > # service network start > > # dracut -f > > > > Now this was different than even how 6 handled it, forget how I > > finally dug that up (possible I even asked here). I've applied this > > same configuration to a Cent8 box I'm trying to stand up and it all > > appears to work fine, but unlike the Cent7 boxes, when the Cent8 box > > comes back up, all the dummy adapters are missing. I've been > > searching all over trying to find some documentation on this to no > > avail. I'm hoping someone has some suggestions here to help out. > > > > Thanks, > > Frank > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Unable to get dummy interfaces to persist across reboots in CentOS 8
As far as what dummy interfaces are used for, they're basically loopbacks that allow for some better network management/flexibility (by separating it from the actual system loopback). On Mon, Oct 26, 2020 at 6:26 PM Strahil Nikolov via CentOS wrote: > > Have you tried to use NetworkManager ? > After all ,anything network related should be done by it. > > [root@system ~]# nmcli connection add con-name dummy0 ifname dummy0 type dummy > Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully added. > > [root@system ~]# reboot > Shared connection to glustera closed. > > > [root@system ~]# uptime > 03:23:44 up 0 min, 1 user, load average: 1,57, 0,48, 0,17 > [root@glustera ~]# nmcli connection show > NAMEUUID TYPE DEVICE > dummy0 9fdd74fa-c143-4991-9bac-0e542704ac89 dummy dummy0 > > > [root@system ~]# ip a s dummy0 > 3: dummy0: mtu 1500 qdisc noqueue state UNKNOWN > group default qlen 1000 >link/ether ce:c9:83:97:10:ee brd ff:ff:ff:ff:ff:ff >inet6 fe80::599:a978:9457:df10/64 scope link noprefixroute > valid_lft forever preferred_lft forever > > P.S.: This is the first time I hear about dummy interfaces. What are those > used for ? > > Best Regards, > Strahil Nikolov > > > > > > > > > > В вторник, 27 октомври 2020 г., 02:42:06 Гринуич+2, Frank Even > написа: > > > > > > Anyone have any ideas? It's rather annoying that I can't get these to > persist across reboots without using some kind of helper script. > > On Fri, Oct 16, 2020 at 6:37 AM Frank Even > wrote: > > > > Hello all, hoping someone can help me out here. > > > > I cannot get dummy interfaces on a new Cent8 build to persist across > > reboots. > > > > On Cent7 - this is the process I use: > > > > Create Dummies: > > # cat /etc/modules-load.d/dummy.conf > > dummy > > # cat /etc/modprobe.d/dummyopts.conf > > options dummy numdummies=4 > > # ip link add dummy0 type dummy > > ## - repeating a/ ascending dummyN adapters for as many needed > > # service network start > > # dracut -f > > > > Now this was different than even how 6 handled it, forget how I > > finally dug that up (possible I even asked here). I've applied this > > same configuration to a Cent8 box I'm trying to stand up and it all > > appears to work fine, but unlike the Cent7 boxes, when the Cent8 box > > comes back up, all the dummy adapters are missing. I've been > > searching all over trying to find some documentation on this to no > > avail. I'm hoping someone has some suggestions here to help out. > > > > Thanks, > > Frank > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Unable to get dummy interfaces to persist across reboots in CentOS 8
> No. Network Manager is always disabled on our builds since at least > Cent5 days. The network stack has always been able to be managed > properly without relying on Network Manager. Is that now an absolute > requirement? It never has been prior. IIRC the old style network scripts will go away with the next RHEL release. I'm afraid NetworkManager will be the way to go in future. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] System not logging
One of my boxes has stopped logging some of the things it's supposed to. I use rsyslog which used to send named and dhcpd entries to separate log files. Both named and dhcpd are working. I have shut down the DHCPD server and run it in debug mode and the output is produced as expected. I have shut down rsyslog and run that in debug mode and it looks like everything is running, but it's not receiving messages to log. I tried journalctl | grep -Ei 'dhcpd'|tail and I see the log entries for the service starting up, but no entries for DHCP transactoins happening. My rsyslog also receives network messages from my firewall and they are logging as expected. This suggests to me that the problem is that the log entries are either not being generated, or are not being allowed to get to rsyslog. Anyone go any ideas? I've tried the usual first step, and briefly disabled selinux but that made no difference Gary ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Unable to get dummy interfaces to persist across reboots in CentOS 8
Requirement is a very strong word , but you should consider using it and here is a short demo why: - By default, RHEL uses NetworkManager to configure and manage network connections, and the /usr/sbin/ifup and /usr/sbin/ifdown scripts use NetworkManager to process ifcfg files in the /etc/sysconfig/network-scripts/ directory. [root@system ~]# ls -l /usr/sbin/ifup lrwxrwxrwx. 1 root root 22 21 окт 21,29 /usr/sbin/ifup -> /etc/alternatives/ifup [root@system ~]# alternatives --list | grep ifup ifup auto /usr/libexec/nm-ifup [root@system ~]# rpm -qf /usr/libexec/nm-ifup NetworkManager-1.22.8-5.el8_2.x86_64 - the old networks-scripts have been deprecated and are not the defaults anymore It's about time to switch to NM, but you got some 5-8 years till next EL release. Best Regards, Strahil Nikolov В сряда, 28 октомври 2020 г., 12:47:12 Гринуич+2, Frank Even написа: No. Network Manager is always disabled on our builds since at least Cent5 days. The network stack has always been able to be managed properly without relying on Network Manager. Is that now an absolute requirement? It never has been prior. On Mon, Oct 26, 2020 at 6:26 PM Strahil Nikolov via CentOS wrote: > > Have you tried to use NetworkManager ? > After all ,anything network related should be done by it. > > [root@system ~]# nmcli connection add con-name dummy0 ifname dummy0 type dummy > Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully added. > > [root@system ~]# reboot > Shared connection to glustera closed. > > > [root@system ~]# uptime > 03:23:44 up 0 min, 1 user, load average: 1,57, 0,48, 0,17 > [root@glustera ~]# nmcli connection show > NAME UUID TYPE DEVICE > dummy0 9fdd74fa-c143-4991-9bac-0e542704ac89 dummy dummy0 > > > [root@system ~]# ip a s dummy0 > 3: dummy0: mtu 1500 qdisc noqueue state UNKNOWN > group default qlen 1000 > link/ether ce:c9:83:97:10:ee brd ff:ff:ff:ff:ff:ff > inet6 fe80::599:a978:9457:df10/64 scope link noprefixroute > valid_lft forever preferred_lft forever > > P.S.: This is the first time I hear about dummy interfaces. What are those > used for ? > > Best Regards, > Strahil Nikolov > > > > > > > > > > В вторник, 27 октомври 2020 г., 02:42:06 Гринуич+2, Frank Even > написа: > > > > > > Anyone have any ideas? It's rather annoying that I can't get these to > persist across reboots without using some kind of helper script. > > On Fri, Oct 16, 2020 at 6:37 AM Frank Even > wrote: > > > > Hello all, hoping someone can help me out here. > > > > I cannot get dummy interfaces on a new Cent8 build to persist across > > reboots. > > > > On Cent7 - this is the process I use: > > > > Create Dummies: > > # cat /etc/modules-load.d/dummy.conf > > dummy > > # cat /etc/modprobe.d/dummyopts.conf > > options dummy numdummies=4 > > # ip link add dummy0 type dummy > > ## - repeating a/ ascending dummyN adapters for as many needed > > # service network start > > # dracut -f > > > > Now this was different than even how 6 handled it, forget how I > > finally dug that up (possible I even asked here). I've applied this > > same configuration to a Cent8 box I'm trying to stand up and it all > > appears to work fine, but unlike the Cent7 boxes, when the Cent8 box > > comes back up, all the dummy adapters are missing. I've been > > searching all over trying to find some documentation on this to no > > avail. I'm hoping someone has some suggestions here to help out. > > > > Thanks, > > Frank > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Run as root on reboot
Folks Is there a way to reboot and have a script run without intervention. During initial setup, I'd like to avoid the manual actions of logging on as root and executing a command, but instead have that command run without intervention. The output of the command would still show up on the terminal that initiated the reboot. Security is not a concern here. And I don't want to invoke high-powered functions like "jumpstart". David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Run as root on reboot
On Wed, 28 Oct 2020 16:34:32 -0700 david wrote: > Is there a way to reboot and have a script run without > intervention. rc.local -- Can we uninstall 2020 and install it again? This one has a virus. MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Run as root on reboot
At 04:47 PM 10/28/2020, Frank Cox wrote: On Wed, 28 Oct 2020 16:34:32 -0700 david wrote: > Is there a way to reboot and have a script run without > intervention. rc.local -- Alas, I think rc.local has become irrelevant with systemd, which is most Linux distros is the way forward. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Run as root on reboot
On Oct 28, 2020, at 19:58, david wrote: > > Alas, I think rc.local has become irrelevant with systemd, which is most > Linux distros is the way forward. I suggest running: systemctl cat rc-local.service The trick is to make the /etc/rc.d/rc.local file executable. However, honestly, what you are asking for should be to create your own systemd service to launch on boot. Systemd service units are trivial to write. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Run as root on reboot
On Wed, Oct 28, 2020 at 04:56:53PM -0700, david wrote: > Alas, I think rc.local has become irrelevant with systemd, which is most > Linux distros is the way forward. vi /etc/rc.local -> add what you need to run on boot chmod 700 /etc/rc.d/rc.local systemctl enable rc-local.service It's still supported, but disabled by default by both the unit being disabled and the file being non-executable. This works on 7, no idea about 8. They probably broke it there. John -- I thought I was in better shape. -- Don Pellmann, age 100, who set five world records at the San Diego Senior Games, but fell short in the pole vault, dislodging the bar three times, New York Times, 22 September 2015 signature.asc Description: PGP signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Run as root on reboot
--On Wednesday, October 28, 2020 5:34 PM -0700 david wrote: During initial setup, I'd like to avoid the manual actions of logging on as root and executing a command, but instead have that command run without intervention. "During initial setup" is vague. Lots of stuff happens during startup. With systemd, you can control what triggers your script to run. Does it need the filesystems up? Does it need networking? This will be a part of your systemd unit file. The output of the command would still show up on the terminal that initiated the reboot. This one might be hard. Is there a way to know where a reboot command came from? Does the kernel or systemd save this somewhere? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Run as root on reboot
At 07:10 PM 10/28/2020, Kenneth Porter wrote: --On Wednesday, October 28, 2020 5:34 PM -0700 david wrote: During initial setup, I'd like to avoid the manual actions of logging on as root and executing a command, but instead have that command run without intervention. "During initial setup" is vague. Lots of stuff happens during startup. With systemd, you can control what triggers your script to run. Does it need the filesystems up? Does it need networking? This will be a part of your systemd unit file. The output of the command would still show up on the terminal that initiated the reboot. This one might be hard. Is there a way to know where a reboot command came from? Does the kernel or systemd save this somewhere? By "initial setup", I meant during the initial install of the operating system, starting from "net-install". Maybe one user is defined. The reboot command is issued from a script that was initiated by hand. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Run as root on reboot
On Wed, Oct 28, 2020 at 8:53 PM david wrote: > > By "initial setup", I meant during the initial install of the > operating system, starting from "net-install". Maybe one user is > defined. The reboot command is issued from a script that was > initiated by hand. > so you want this script run /before/ the manually issued reboot ? why not just run the script and have IT initiate the reboot when its done ? -- -john r pierce recycling used bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
