Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/boincadm/prj/html/inc/boinc_db.inc on line 147
HTTP error 413, client intended to send too large body

HTTP error 413, client intended to send too large body

Message boards : Closed Issues : HTTP error 413, client intended to send too large body
Message board moderation

To post messages, you must log in.


Deprecated: Creation of dynamic property BoincUser::$prefs is deprecated in /var/boincadm/prj/html/inc/forum_db.inc on line 164

Deprecated: Creation of dynamic property BoincUser::$prefs is deprecated in /var/boincadm/prj/html/inc/forum_db.inc on line 164

Deprecated: Creation of dynamic property BoincUser::$prefs is deprecated in /var/boincadm/prj/html/inc/forum_db.inc on line 164
AuthorMessage
=Lupus=

Send message
Joined: 16 Feb 19

Deprecated: Creation of dynamic property BoincUser::$nposts is deprecated in /var/boincadm/prj/html/inc/forum.inc on line 613
Posts: 4
Credit: 218,715
RAC: 0
Message 3041 - Posted: 17 Feb 2019, 19:02:42 UTC

Getting Error 413 on reporting. Not your executable but a BOINC problem.

17.02.2019 19:50:06 | Tomáš Brada Experiment Grid | Sending scheduler request: Requested by project.
17.02.2019 19:50:06 | Tomáš Brada Experiment Grid | Reporting 968 completed tasks
17.02.2019 19:50:06 | Tomáš Brada Experiment Grid | Not requesting tasks: "no new tasks" requested via Manager
17.02.2019 19:50:08 | Tomáš Brada Experiment Grid | Scheduler request failed: Error 413


Retried manually, persists the retries.
ID: 3041 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Tomáš Brada
Project administrator
Volunteer developer
Avatar

Send message
Joined: 3 Feb 19

Deprecated: Creation of dynamic property BoincUser::$nposts is deprecated in /var/boincadm/prj/html/inc/forum.inc on line 613
Posts: 667
Credit: 432,784
RAC: 0
Message 3042 - Posted: 17 Feb 2019, 19:42:18 UTC - in response to Message 3041.  

Indeed:
Feb 17 20:36:29 saran nginx[22469]: ... client intended to send too large body: 1346049 bytes
ID: 3042 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Tomáš Brada
Project administrator
Volunteer developer
Avatar

Send message
Joined: 3 Feb 19
Posts: 667
Credit: 432,784
RAC: 0
Message 3046 - Posted: 17 Feb 2019, 20:32:13 UTC - in response to Message 3042.  

Please try again. I amended configuration of nginx.
ID: 3046 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
=Lupus=

Send message
Joined: 16 Feb 19
Posts: 4
Credit: 218,715
RAC: 0
Message 3047 - Posted: 17 Feb 2019, 23:03:35 UTC - in response to Message 3046.  

Worked.

Seems my client wanted to report the first 100 to 200 failures.
Which your webserver did not like.
And when i killed the already-closed workunits i generated an even bigger number…

1 Megabyte is way too much for a "normal" request but, well, it is BOINC.
All report-completes and everything else goes thru normal HTTP requests.
Which is easy because the needed protocols are on every OS but seems to need a Little bit tweaking when handling big requests or reportings.

Happy I could help you find that "error" in early-alpha phase instead of later on when hundreds of users are there...
ID: 3047 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
zombie67 [MM]
Avatar

Send message
Joined: 16 Feb 19

Deprecated: Creation of dynamic property BoincUser::$nposts is deprecated in /var/boincadm/prj/html/inc/forum.inc on line 613
Posts: 14
Credit: 1,519,846
RAC: 0
Message 3048 - Posted: 17 Feb 2019, 23:14:54 UTC

I had to add the following to my cc_config.xml, because it was trying to report too many tasks at once:

<cc_config> 
	<options> 
		<max_tasks_reported>50</max_tasks_reported>
	</options> 
</cc_config> 


It sounds like the server side has been fixed, and I can remove this limitation now?
Reno, Nevada
Team: SETI.USA
ID: 3048 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Tomáš Brada
Project administrator
Volunteer developer
Avatar

Send message
Joined: 3 Feb 19
Posts: 667
Credit: 432,784
RAC: 0
Message 3051 - Posted: 18 Feb 2019, 9:21:09 UTC

I increased the scheduler max upload size to 2 Gi. If you had not reported the error, everyone would have to add that tag to their config and be annoyed. Thanks. I also disabled request and response buffering in nginx for the scheduler, in case it was enabled by default.
Zombie, if you find that you need any other config tweak to make the project work on your end, post a note in the forum. It might get fixed if it is trivial.
ID: 3051 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
zombie67 [MM]
Avatar

Send message
Joined: 16 Feb 19
Posts: 14
Credit: 1,519,846
RAC: 0
Message 3057 - Posted: 18 Feb 2019, 15:53:18 UTC - in response to Message 3051.  

Thanks!
Reno, Nevada
Team: SETI.USA
ID: 3057 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Closed Issues : HTTP error 413, client intended to send too large body

©2024 Tomáš Brada