Plugins » Discovery

Foreman-proxy server fails to start on discovery image 3.1.2. Output from discovery-debug is below. When I start foreman-proxy manually after a while, it start without issue.
Problem is probably caused by the fact that server has many NICs and DHCP takes longer and network is not prepared on time, but this is only a guess.

Started Configures LLDP for enp4s0f2.
Generating SSH2 RSA host key: [  OK  ]
Generating SSH2 ECDSA host key: [  OK  ]
Generating SSH2 ED25519 host key: [  OK  ]
Started OpenSSH Server Key Generation.
Started OpenSSH server daemon.
Starting OpenSSH server daemon...
Started /etc/rc.d/rc.local Compatibility.
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
.......................................................................................................................+++
writing new private key to '/etc/foreman-proxy/key.pem'
-----
end of string encountered while processing type of subject name element #0
problems making Certificate Request
foreman-proxy.service: control process exited, code=exited status=1
Failed to start Foreman Proxy.
Unit foreman-proxy.service entered failed state.
foreman-proxy.service failed.
Reached target Multi-User System.
Starting Multi-User System.
Started Stop Read-Ahead Data Collection 10s After Completed Startup.
Starting Stop Read-Ahead Data Collection 10s After Completed Startup.
Starting Update UTMP about System Runlevel Changes...
Started Update UTMP about System Runlevel Changes.
Startup finished in 2.706s (kernel) + 4.509s (initrd) + 38.231s (userspace) = 45.448s.
Kernel opts: BOOT_IMAGE=boot/fdi-image/vmlinuz0 initrd=boot/fdi-image/initrd0.img rootflags=loop root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.
Entering screen_countdown
DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 13 (xid=0x4b569a6f)
DHCPREQUEST on eno1 to 255.255.255.255 port 67 (xid=0x4b569a6f)
DHCPOFFER from 172.27.19.131
DHCPACK from 172.27.19.131 (xid=0x4b569a6f)
<info>    address 172.27.19.184
<info>    plen 25 (255.255.255.128)
<info>    gateway 172.27.19.254
<info>    server identifier 172.27.19.131
<info>    lease time 43119
<info>    nameserver '172.27.19.131'
<info>    domain name 'mgmt.cloud.tl'
<info>  (eno1): DHCPv4 state changed unknown -> bound
bound to 172.27.19.184 -- renewal in 19150 seconds.
<info>  (eno1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
<info>  (eno1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
<info>  (eno1): device state change: secondaries -> activated (reason 'none') [90 100 0]
<info>  NetworkManager state is now CONNECTED_LOCAL
<info>  NetworkManager state is now CONNECTED_GLOBAL
<info>  Policy set 'primary' (eno1) as default for IPv4 routing and DNS.
<info>  (eno1): Activation: successful, device activated.
<info>  startup complete
[system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
dbus[883]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Starting Network Manager Script Dispatcher Service...
dbus[883]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'