SO Install adapters show up but do not initiate

[ItsJustMeK]

Hi,
I am installing a new SO eval/standalone for my home. Have been running it on a very old i3 box with some issues on latest version, just too slow.
New H/W with an i5, using the 2.4.11 ISO on a boot USB. The initial install to SSD works fine, after reboot and login, the installer recognizes the M/B NIC as well as the dual port NIC based upon Intel 82576 chip, but when I select them and put in static IP details the installer does not initialize them and I get network errors, unable to connect and the install fails. No logs with any details.

ifconfig does not show the adapters.

I thought maybe an issue with Oracle Linux 9 and the devices, so I tried an install of it with their latest ISO and it worked fine, initialized the NIC's and used them to download the files as the source of the install, so I am now a bit stumped.

I routed around in the OS logs to try and find something, but nothing there.
The PC is an older Dell Inspiron with i5 4660, 16 GB RAM, 2 TB SSD and the 2 port NIC is below:
https://www.amazon.com/dp/B01LXTF48X?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

Any ideas / suggestions would be greatly appreciated. I have not been able to find anything like this Googling around.

[ItsJustMeK]

So after this I configured the main adapter in Oracle Linux (OL) and then copied the config file below to try to fix this
/etc/NetworkManager/system-connections/enp2s0f0.nmconnection
I then re-ran the SO install from the boot USB. This time it recognized the NICs and initiated them properly. Only thing I can figure is the OL installer somehow initialized it and the new state was then properly recognizable by SO. The install went well then until the below errors:

Cleaning up temp files in /nsm/elastic-agent-workspace

[INFO ] Loading fresh modules for state activity
[INFO ] Fetching file from saltenv 'base', ** done ** 'elasticfleet/install_agent_grid.sls'
[INFO ] Executing command /bin/systemctl in directory '/root'
[INFO ] Running state [salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64] at time 02:13:34.363954
[INFO ] Executing state cmd.script for [salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64]
[INFO ] Fetching file from saltenv 'base', ** done ** 'elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64'
[INFO ] Executing command '/opt/so/__salt.tmp.ahbf5swv' in directory '/opt/so'
[ERROR ] Command '/opt/so/__salt.tmp.ahbf5swv' failed with return code: 1
[ERROR ] stdout:
Installation initiated, view install log for further details.
[ERROR ] retcode: 1
[ERROR ] {'pid': 301113, 'retcode': 1, 'stdout': '\nInstallation initiated, view install log for further details.', 'stderr': ''}
[INFO ] Completed state [salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64] at time 02:13:41.774709 (duration_in_ms=7410.755)
[WARNING ] State is set to retry, but a valid dict for retry configuration was not found. Using retry defaults
[INFO ] State result does not match retry until value, state will be re-run in 30 seconds
[INFO ] Running state [salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64] at time 02:14:11.788624
[INFO ] Executing state cmd.script for [salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64]
[INFO ] Executing command '/opt/so/__salt.tmp.7uty6u04' in directory '/opt/so'
[ERROR ] Command '/opt/so/__salt.tmp.7uty6u04' failed with return code: 1
[ERROR ] stdout:
Installation initiated, view install log for further details.
[ERROR ] retcode: 1
[ERROR ] {'pid': 302045, 'retcode': 1, 'stdout': '\nInstallation initiated, view install log for further details.', 'stderr': ''}
[INFO ] Completed state [salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64] at time 02:14:15.501027 (duration_in_ms=3712.402)
local:

      ID: run_installer
Function: cmd.script
    Name: salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64
  Result: False
 Comment: Attempt 1: Returned a result of "False", with the following comment: "Command 'salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64' run"
          Command 'salt://elasticfleet/files/so_agent-installers/so-elastic-agent_linux_amd64' run
 Started: 02:13:34.363954
Duration: 41123.157 ms
 Changes:
          ----------
          pid:
              302045
          retcode:
              1
          stderr:
          stdout:

              Installation initiated, view install log for further details.

Summary for local

Succeeded: 0 (changed=1)
Failed: 1

AND

              {"error":{"root_cause":[{"type":"process_cluster_event_timeout_exception","reason":"failed to process cluster event (put-lifecycle-so-common-logs) within 30s"}],"type":"process_cluster_event_timeout_exception","reason":"failed to process cluster event (put-lifecycle-so-common-logs) within 30s"},"status":503}
  Result: False
 Comment: One or more requisite failed: ssl.influxdb_crt
  Result: False
  Result: False
 Comment: One or more requisite failed: ssl.redis_crt
  Result: False
  Result: False
 Comment: One or more requisite failed: ssl.etc_elasticfleet_crt
  Result: False
  Result: False
 Comment: One or more requisite failed: ssl.etc_elasticfleet_logstash_crt
  Result: False
  Result: False
 Comment: One or more requisite failed: ssl.etc_elasticfleet_logstash_key
  Result: False
 Comment: One or more requisite failed: ssl.etc_elasticfleet_crt, ssl.etc_elasticfleet_key

[ERROR ] Command '/opt/so/__salt.tmp.ahbf5swv' failed with return code: 1
[ERROR ] stdout:
[ERROR ] retcode: 1
[ERROR ] {'pid': 301113, 'retcode': 1, 'stdout': '\nInstallation initiated, view install log for further details.', 'stderr': ''}
[ERROR ] Command '/opt/so/__salt.tmp.7uty6u04' failed with return code: 1
[ERROR ] stdout:
[ERROR ] retcode: 1
[ERROR ] {'pid': 302045, 'retcode': 1, 'stdout': '\nInstallation initiated, view install log for further details.', 'stderr': ''}
Result: False

so-status show all as OK, but the web interface shows the elastic_agent.fleet_server as red / down.

[cm-ops]

Are there any errors in dmesg?

[ItsJustMeK]

Unfortunately dmesg only goes back to yesterday. It is full of IPTables-dropped messages.

[ItsJustMeK]

So I am going to close this. Not getting anywhere. Over night I re-installed for the third time, and it seems to be the charm. No errors this time and it seems to be working properly after install finished.