Hi all,
having some new juicy PI4 and as follow-up to this post, I'm trying to figure out why my two PI4 (one 2GB and one 4GB) using the PI4 specific build 2019-07-17 boots and opens port 21, 22 and others - but not port 80 - so the OMV WEB UI isn't accessible.
I offline tweaked /etc/ssh/sshd_config to enable root+password access at first boot and the investigation begun.
1. nginx fails to start, it seems an IPv6 issue:
```
root@raspberrypi:/# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /etc/nginx/nginx.conf test failed
```
```
root@raspberrypi:/# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-08-29 17:01:45 UTC; 26s ago
Docs: man:nginx(8)
Process: 2739 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
Aug 29 17:01:45 raspberrypi systemd[1]: Starting A high performance web server and a reverse proxy server...
Aug 29 17:01:45 raspberrypi nginx[2739]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Aug 29 17:01:45 raspberrypi nginx[2739]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 29 17:01:45 raspberrypi systemd[1]: nginx.service: Control process exited, code=exited status=1
Aug 29 17:01:45 raspberrypi systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Aug 29 17:01:45 raspberrypi systemd[1]: nginx.service: Unit entered failed state.
Aug 29 17:01:45 raspberrypi systemd[1]: nginx.service: Failed with result 'exit-code'.
```
2. The log reports also other errors, like this:
```
root@raspberrypi:/# systemctl status watchdog.service
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-08-29 16:42:35 UTC; 22min ago
Process: 1181 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] 
[ "${watchdog_module}" = "none" ] /sbin/modprobe $watchdog_mod
Aug 29 16:42:35 raspberrypi systemd[1]: Starting watchdog daemon...
Aug 29 16:42:35 raspberrypi sh[1181]: modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/mo
Aug 29 16:42:35 raspberrypi sh[1181]: modprobe: FATAL: Module softdog not found in directory /lib/modules/4.19.50-v7l+
Aug 29 16:42:35 raspberrypi systemd[1]: watchdog.service: Control process exited, code=exited status=1
Aug 29 16:42:35 raspberrypi systemd[1]: Failed to start watchdog daemon.
Aug 29 16:42:35 raspberrypi systemd[1]: watchdog.service: Unit entered failed state.
Aug 29 16:42:35 raspberrypi systemd[1]: watchdog.service: Triggering OnFailure= dependencies.
Aug 29 16:42:35 raspberrypi systemd[1]: watchdog.service: Failed with result 'exit-code'.
```
Am I the only one out of 2265 downloads who doesn't boot OMV on a PI4 with 2GB or 4GB RAM? 
Someone already solved this?
Thanks,
Piero