Nginx Active: active (exited) status after upgrade to OMV 3.0

Hello there,

I used the omv-upgrade command in OMV 2.2.13 to upgrade to the latest version, since there was no version 3.0 made for RPi B, as I understood. I put a hold on php5-pam as required on the Raspberry Pi B model.

However, Nginx doesn't seem to start:

I get

service nginx status
● nginx.service - LSB: starts the nginx web server
   Loaded: loaded (/etc/init.d/nginx)
   Active: active (exited) since Fri 2016-11-11 20:43:54 CST; 1s ago
  Process: 1214 ExecStop=/etc/init.d/nginx stop (code=exited, status=0/SUCCESS)
  Process: 1177 ExecReload=/etc/init.d/nginx reload (code=exited, status=0/SUCCESS)
  Process: 1278 ExecStart=/etc/init.d/nginx start (code=exited, status=0/SUCCESS)

I am not sure what this means, but I tried to stop / start the service, to no avail. There's no port 80 open on doing a port scan, and no web GUI displayed.
On plugging in the TV, it still reports OMV 2.2.13 version.
Configuration: RPi B running off USB HDD, RTC installed. Software configuration, except for running off the HDD, is stock 2.2.13 OMV.

If that is any helpful, I don't see the omv-* utilities anymore, only omv-mkgraph is available.

How would I solve this issue?

Hm, ok, but strictly speaking, why does the active (exited) service means in this case?

And even if I re-flash to a OMV 2.x, how do I ensure that it stays in the 2.x branch when I perform the upgrades? Can omv-update still be used?