Hi,
First, greate news and thanks for EFA v5 beta ...
I don't know where to this topic (no EFA v5 Bugs), so I put it here ...
I successfully install EFA v5 on top of Rocky Linux 9.
After initial configuration I type "OK"
and get this errors:
[eFa] - Starting MariaDB and Configuring
/usr/bin/mysqladmin: connect to server at 'localhost.localdomain' failed
error: 'Host '127.0.0.1' is not allowed to connect to this MariaDB server'
ERROR 1067 (42000) at line 58: Invalid default value for 'lastsent'
and
[eFa] - Setting IP settings
cp: cannot stat '/etc/sysconfig/network-scripts/ifcfg-ens33': No such file or directory
[eFa] - Error initializing system! Please try again...
In Rocky Linux 9 all network profiles are stored in "/etc/NetworkManager/system-connections/" and not in "/etc/sysconfig/network-scripts/"
How to go around this ...
HowTo test EFAv5
- shawniverson
- Posts: 3650
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: HowTo test EFAv5
Thank you for testing. I will be working on fixing these and releasing a new version to test.
Re: HowTo test EFAv5
I just tried EFAv5 and came across the same issue... I'll look out for the fix and try again..
Re: HowTo test EFAv5
Installed Centos Stream9 server.
All network connection definitions on my Centos stream 9 server (no GUI) have to be administered through NetworkManager (nmcli). The connection definitions are in the /etc/NetworkManager/system-connections directory.
The efa-Configure scripts and Menus (4 - IP settings) are trying to access and modify /etc/sysconfig/network-scripts/ifcfg-ens192, which do not exist on the server, producing a lot of errors and changing/creating wrong files.
Looking at the github, it is obvious you are still using sysconfig/network-scripts interface configuration definitions, now abandoned for NetworkManager.
The Centos Stream 8 installation I have in production is still using ifcfg network-scripts.
Do you want us to switch back from NM to ifcfg, or the changes in scripts toward NetworkManager are in the timeline?
All network connection definitions on my Centos stream 9 server (no GUI) have to be administered through NetworkManager (nmcli). The connection definitions are in the /etc/NetworkManager/system-connections directory.
The efa-Configure scripts and Menus (4 - IP settings) are trying to access and modify /etc/sysconfig/network-scripts/ifcfg-ens192, which do not exist on the server, producing a lot of errors and changing/creating wrong files.
Looking at the github, it is obvious you are still using sysconfig/network-scripts interface configuration definitions, now abandoned for NetworkManager.
The Centos Stream 8 installation I have in production is still using ifcfg network-scripts.
Do you want us to switch back from NM to ifcfg, or the changes in scripts toward NetworkManager are in the timeline?
- shawniverson
- Posts: 3650
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: HowTo test EFAv5
I am working on switching over to NetworkManager.
Re: HowTo test EFAv5
Today installed on Rocky Linux 9 server. Sofar no problem detected.
I will copy step by step my individual settings from my eFav4 production box.
Should I test something specific?
I will copy step by step my individual settings from my eFav4 production box.
Should I test something specific?
Re: HowTo test EFAv5
After reboot I found this message at Cli:
I will now transfer my setting from production EFav4 box and test further...
Need to install additionally
due to recipient verification via AD ldap server.
Code: Select all
systemd-sysv-generator[595]: SysV service '/etc/rc.d/init.d/adcc' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Need to install additionally
Code: Select all
postfix-ldap