Error Connection failed Service nginx

Hello,

I am applying to you because of an error I get and whose reason I can not understand.

My RPI is configured as a FTP server where 4 video cams continuously upload their snapshots (one every 3 seconds).

Every 3 hours a task of my computer uploads via FTP the backup of my documents directory.

During this backup I receive following email from OMV.

Zitat

Connection failed Service nginx
Date: Wed, 01 Feb 2017 20:20:05
Action: restart
Host: raspberrypi
Description: failed protocol test [HTTP] at INET[127.0.0.1:80] via TCP -- HTTP: Error receiving data -- Resource temporarily unavailable

Your faithful employee,
Monit

Alles anzeigen

followed a few seconds later from another email.

Zitat

Connection succeeded Service nginx

Date: Wed, 01 Feb 2017 20:20:42
Action: alert
Host: raspberrypi
Description: connection succeeded to INET[127.0.0.1:80] via TCP

Your faithful employee,
Monit

Alles anzeigen

What could be the reason and how could I solve it?

Tbanks,
Daniele

Zitat von ryecoaaron

The RPi is slow and you are overloading it.

Use a faster system.

Thanks for replying.
I understand. Isn't there a way to transfer the backup file without overloading the RPi?

Thanks,
daniele

Zitat von kochin

Last week I converted my PogoPlug E02 from Debian Wheezy to Jessie and installed OMV 3.0.64. Since then, I've been trying to track down this issue. At the end I came to the same conclusion as ryecoaaron. It's my PogoPlug E02 too slow to handle all the load.

The monit service periodically test HTTP and restarts nginx when the test fails. If the system is under heavy load, the test tends to fail when nginx doesn't respond fast enough. You may disable the HTTP test by commenting out this line in /etc/monit/conf.d/openmediavault-nginx.conf.

Code

if failed host 127.0.0.1 port 80 protocol http then restart

Then restart monit. Of course, that also remove the ability of nginx restarting automatically when it really fails. So, in stead, I propose changing the line to

Code

if failed host localhost port 80 protocol http timeout 20 seconds for 2 times within 3 cycles then restart

What that line does is to increase timeout from 5 sec (default) to 20 sec and restart nginx only when tests in 2 out of 3 cycles failed. Those numbers can be changed to see what work best. At least for my PogoPlug, that change stabilizes OMV 3.0.64 to be usable even though the CPU usage hits 100% often.

With all that said, my puny PogoPlug was quite usable with OMV 2.x without having to meddle with monit. OMV 3.0.x seems to put heavier load on the box.

Alles anzeigen

Thanks for advising.

I will try it.

I am wondering, isn't there a way to avoid overloading for instance reducing the priority of one ftp task?