It is true. I install OMV 3.x multiple times per day most days. There are harmless errors that people worry too much about. Commercial NASes just hide the errors. Whenever you install a php or nginx update, nginx and/or php5-fpm need to be restarted. This generates communication errors until the service is restarted. This is almost impossible to avoid but harmless.
I'm sorry but I would have to disagree on that. I realize I'm using extras-testing, but I think having SSL is a major requirement for access from the outside. So I tried this 1 plugin over a new clean OMV3, and immediately fall into that same hole:
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
git git-man liberror-perl
Suggested packages:
git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk
gitweb git-arch git-cvs git-mediawiki git-svn
Recommended packages:
patch
The following NEW packages will be installed:
git git-man liberror-perl openmediavault-letsencrypt
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 4563 kB of archives.
After this operation, 23.6 MB of additional disk space will be used.
Get:1 http://ftp.surfnet.nl/os/Linux/distr/debian/ jessie/main liberror-perl all 0.17-1.1 [22.4 kB]
Get:2 https://dl.bintray.com/openmed…velopers/erasmus-testing/ jessie/main openmediavault-letsencrypt all 2.3 [11.2 kB]
Get:3 http://ftp.surfnet.nl/os/Linux/distr/debian/ jessie/main git-man all 1:2.1.4-2.1+deb8u2 [1267 kB]
Get:4 http://ftp.surfnet.nl/os/Linux/distr/debian/ jessie/main git amd64 1:2.1.4-2.1+deb8u2 [3262 kB]
Fetched 4563 kB in 0s (9033 kB/s)
Selecting previously unselected package liberror-perl.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 32733 files and directories currently installed.)
Preparing to unpack .../liberror-perl_0.17-1.1_all.deb ...
Unpacking liberror-perl (0.17-1.1) ...
Selecting previously unselected package git-man.
Preparing to unpack .../git-man_1%3a2.1.4-2.1+deb8u2_all.deb ...
Unpacking git-man (1:2.1.4-2.1+deb8u2) ...
Selecting previously unselected package git.
Preparing to unpack .../git_1%3a2.1.4-2.1+deb8u2_amd64.deb ...
Unpacking git (1:2.1.4-2.1+deb8u2) ...
Selecting previously unselected package openmediavault-letsencrypt.
Preparing to unpack .../openmediavault-letsencrypt_2.3_all.deb ...
Unpacking openmediavault-letsencrypt (2.3) ...
Processing triggers for man-db (2.7.0.2-5) ...
>>> *************** Error ***************
Failed to read from socket: Connection reset by peer
<<< *************************************
>>> *************** Error ***************
Failed to connect to socket: Connection refused
<<< *************************************
>>> *************** Error ***************
Failed to connect to socket: Connection refused
<<< *************************************
Either way, I now have a weird Error dialog window I can't close, and the entire web-gui is locked up because of that. It says [Error] Communication error. So, I can have all the patience in the world, but when this keeps happening with the install of just the first crucial plugin I would like to use, it has nothing to do with patience. When I look in syslog, this might be of interest;
Jul 23 14:58:21 sugar monit[815]: 'omv-engined' restart on user request
Jul 23 14:58:21 sugar monit[815]: Monit daemon with PID 815 awakened
Jul 23 14:58:21 sugar monit[815]: Awakened by User defined signal 1
Jul 23 14:58:21 sugar monit[815]: 'omv-engined' trying to restart
Jul 23 14:58:21 sugar monit[815]: 'omv-engined' stop: /bin/systemctl
Jul 23 14:58:21 sugar monit[815]: 'omv-engined' start: /bin/systemctl
Jul 23 14:58:21 sugar systemd[1]: openmediavault-engined.service: Supervising process 6433 which is not our child. We'll most likely not notice when it exits.
Jul 23 14:58:21 sugar monit[815]: 'omv-engined' restart action done
Jul 23 14:58:22 sugar systemd[1]: openmediavault-engined.service: main process exited, code=exited, status=255/n/a
Jul 23 14:58:22 sugar systemd[1]: Unit openmediavault-engined.service entered failed state.
Jul 23 14:58:27 sugar monit[815]: 'omv-engined' restart on user request
Jul 23 14:58:27 sugar monit[815]: Monit daemon with PID 815 awakened
Jul 23 14:58:27 sugar monit[815]: Awakened by User defined signal 1
Jul 23 14:58:27 sugar monit[815]: 'omv-engined' trying to restart
Jul 23 14:58:27 sugar monit[815]: 'omv-engined' start: /bin/systemctl
Jul 23 14:58:27 sugar systemd[1]: openmediavault-engined.service: Supervising process 6815 which is not our child. We'll most likely not notice when it exits.
Jul 23 14:58:27 sugar systemd[1]: openmediavault-engined.service: main process exited, code=exited, status=255/n/a
Jul 23 14:58:27 sugar systemd[1]: Unit openmediavault-engined.service entered failed state.
Jul 23 14:58:57 sugar monit[815]: 'omv-engined' failed to start (exit status 0) -- no output
Jul 23 14:58:57 sugar monit[815]: 'omv-engined' restart action done
Jul 23 14:59:27 sugar monit[815]: 'omv-engined' process is not running
Jul 23 14:59:27 sugar monit[815]: 'omv-engined' trying to restart
Jul 23 14:59:27 sugar monit[815]: 'omv-engined' start: /bin/systemctl
Jul 23 14:59:27 sugar systemd[1]: openmediavault-engined.service: Supervising process 6853 which is not our child. We'll most likely not notice when it exits.
Jul 23 14:59:28 sugar systemd[1]: openmediavault-engined.service: main process exited, code=exited, status=255/n/a
Jul 23 14:59:28 sugar systemd[1]: Unit openmediavault-engined.service entered failed state.
Jul 23 14:59:58 sugar monit[815]: 'omv-engined' failed to start (exit status 0) -- no output
Jul 23 15:00:01 sugar CRON[6860]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
Jul 23 15:00:01 sugar rrdcached[862]: Received FLUSHALL
Jul 23 15:00:28 sugar monit[815]: 'omv-engined' process is not running
Jul 23 15:00:28 sugar monit[815]: 'omv-engined' trying to restart
Jul 23 15:00:28 sugar monit[815]: 'omv-engined' start: /bin/systemctl
Jul 23 15:00:28 sugar systemd[1]: openmediavault-engined.service: Supervising process 6925 which is not our child. We'll most likely not notice when it exits.
Jul 23 15:00:28 sugar systemd[1]: openmediavault-engined.service: main process exited, code=exited, status=255/n/a
Jul 23 15:00:28 sugar systemd[1]: Unit openmediavault-engined.service entered failed state.
Jul 23 15:00:58 sugar monit[815]: 'omv-engined' failed to start (exit status 0) -- no output
I tried searching on some of these and its possible solutions, but it's not easily solved, not even for me. And this is my job.
After a reboot, I get this again (under the [Show details] button):
Error #0:exception 'OMV\Rpc\Exception' with message 'Failed to connect to socket: Connection refused' in /usr/share/php/openmediavault/rpc/rpc.inc:138Stack trace:#0 /usr/share/php/openmediavault/rpc/proxy/json.inc(95): OMV\Rpc\Rpc::call('Services', 'getStatus', Array, Array, 3)#1 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()#2 {main}