![]() ![]() So might be better to go with OMV image directly instead of trying to set it up in DietPi. In addition to those problems, noip2 (at least version 2.1. Because DietPi is an extremely small and lean version of Debian, were OMV install quite a large amount of packages (even if not needed or used). The removal of the noip2 Dynamic Update Client (DUC) from the repository is explained in Debian bug 653957.One of the problems was a security issue, described in Debian bug 601229. Thats why the init.d script and the systemd unit failed: They started noip2 just to see it immediately exits. when you start it, it creates another process that runs in background (so called forking) and the foreground process immediately returns (exits). Your RPi might have just received a different IP. Some research revealed the noip2 runs as a daemon, i.e. Login and post the output of ifconfig -a. It normally just means that dhcp didn't give it an address in time to show up on the motd. Next to this, OMV is exactly the opposite of DietPi. Just because it says there is no ip address on the message of the day (motd), doesn't mean it didn't get one. From my point of view, there are to many conflicts and dependencies. I did not continue at this point, even if OMV was running and I was able to login to website. Solution would be to switch web server preference to Nginx before.It will lead to some conflicts if you already have a different type of web server running ![]() Solution would be to disable watchdog service.I noticed watchdog service was not working correctly on my RPI due to missing kernel dependencies.The -I parameter can be used to override the device name in the configuration data file or to force the supplied name into the configuration data file while it is being created. solution would be to set STATIC IP instead of DHCP The client can be invoked with the -i IPaddress parameter which will force the setting of that address at.I guess it was due to issues with time sync and system time not set correctly on one of my restarts, DHCP was not working correctly and there was no IP address assigned leading to some services failing and no access possible to the system.If you use dhcp then 'dhclient devicename' should give you an address after a few seconds. Time sync will happen after OMV has been started only If it says DOWN then run 'ip link set devicename up' and run ip link again. Downside, there will be no time sync during reboot/restart.Looks like OMV has it’s own Time Sync process. Solution would be to disable the service. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |