This is a copy and paste of a support case opened from a github issue .
./securedrop-admin install fails and mon and app boxes become unreachable
SecureDrop v0.5.2
Tails (admin box) - 3.3After running ./securedrop-admin install, the app and mon boxes both reboot after some time.
Unfortunately, they both then hang waiting for Network Configuration.
The ansible script on the amdin box waits for the boxes to come back, but when they hang, the script eventually fails.
Also (I think because the ansible script failed), we do not have an app-source-ths or any other ths files and can no longer access the mon and app servers.
ā
We have repeated this twice (after having to wipe the drives completely from app and mon by removing them and putting them in a sled).
Is there any explanation for why the app and mon boxes would not be able to get a Network Configuration? We looked over the firewall configuration and it seems fineā¦
at that point I asked the user for details on hardware and they responded with
Is there a command I can run that will help to give you various hardware info quickly?
If I boot into the mon server as the root user and less /etc/network/interfaces I get the following:
auto lo
iface lo inet loopback
Is there a command I can run that will help to give you various hardware info quickly?
If I boot into the mon server as the root user and less /etc/network/interfaces I get the following:
auto lo
iface lo inet loopback
The primary network interface
auto em1
iface em1 inet static
addresss 10.20.3.2
netmask 255.255.255.0
network 10.20.3.0
boradcast 10.20.3.255
gateway 10.20.3.1
dns-* options are implementd by the resolveconf package, if installed
dns-nameservers 8.8.8.8
auto em1
iface em1 inet static
addresss 10.20.3.2
netmask 255.255.255.0
network 10.20.3.0
boradcast 10.20.3.255
gateway 10.20.3.1
dns-nameservers 8.8.8.8
Iāve taken a few more cracks at this from the firewall end of the configuration, running the install, reformatting the servers after each attempt, etc. and still running in to the same roadblock.
Scenario:
ā¢ I initiate the installer from the admin workstation.
ā¢ It proceeds up to the point where it triggers the servers to reboot.
ā¢ During the reboot process, both servers hang up atā¦
Waiting for network configurationā¦
Waiting up to 60 more seconds for network configuration
ā¢ After the timeout, both servers proceed to the log in screen.
ā¢ The installer on admin workstation then displays the following error:
RUNNING HANDLER [common : wait_for] **************************************************************************************************************************
fatal: [mon ā localhost]: FAILED! => {āchangedā: false, āelapsedā: 301, āfailedā: true, āmsgā: āTimeout when waiting for search string OpenSSH in 10.20.3.2:22ā}
fatal: [app ā localhost]: FAILED! => {āchangedā: false, āelapsedā: 301, āfailedā: true, āmsgā: āTimeout when waiting for search string OpenSSH in 10.20.2.2:22ā}Notes:
ā¢ Able to SSH from all three machines pre-install.
ā¢ In the troubleshooting process, Iāve enabled all SSH traffic across all three firewall interfaces between the app, mon and admin machines.
ā¢ App and mon are reformatted and Ubuntu reloaded after each attempt.
ā¢ The admin workstation is a MacBook Air with a Thunderbolt to Ethernet adapter and booting from a Tails SD card.Any thoughts are greatly appreciated.