User Pass
Home Sign Up Contact Log In
Page:
 
Anarcho
offline
Link
 
nginx/0.6.29

Does anyone else ever get that message?

Every time I try to update my AI with more than 1 or 2 outputs, I get this message and it erases all my changes.

I don't know if this belongs here, but it's really annoying.
 
Arawn
offline
Link
 
your trying to process too many lines, cut it in half and then update, and then do the rest.
 
Anarcho
offline
Link
 
Originally posted by Xander1
your trying to process too many lines, cut it in half and then update, and then do the rest.


Yeah, that is pretty inconvenient. Especially considering it takes about 5 minutes for the thing to save/reload anyway.

Seriously though, this server can't handle large AI updates? That's pretty ridiculous if you ask me.
 
r8
offline
Link
 
Originally posted by Anarcho
Originally posted by Xander1

your trying to process too many lines, cut it in half and then update, and then do the rest.


Yeah, that is pretty inconvenient. Especially considering it takes about 5 minutes for the thing to save/reload anyway.

Seriously though, this server can't handle large AI updates? That's pretty ridiculous if you ask me.


How large is your AI? There's actually a physical limit to how large of a request you can make with anything dealing with servers and such, I think it's something like 65,065 bytes, but someone with some programming knowledge would have to confirm that. So, if you have a ridiculously large AI, you might be hitting that limit.
 
r8
offline
Link
 
Bump to put back ahead of Moved threads.
 
azfredbird
offline
Link
 
I am having the same problem with my D al in Tallinn.
 
California
knows how to party
offline
Link
 
Think of it like.. your e-cock is too big for GLB's e-vaj.
 
Black Peter
offline
Link
 
Could also be you need to update the browser cache allocation. Think I heard that somewhere before in DC forum and the person with the issue increased the cache size and didn't have any issues after that. No idea if that would solve it though since it could well be server-side. Worth a look I suppose.

Edit:
Or not since this is what that error code means:

Error Message:
413 – Request Entity Too Large
Translation:
The Web server has determined that the data being sent by the browser is simply too large (that is, too many bytes). This occurs when file size limits are exceeded. For example, when uploading a very large file (using a technique such as HTTP PUT), a 413 error may be returned when the Web server sees that the file size is too large.

Solution:
This error is typically due to configuration or programming errors on the Web server end. It may be possible to shrink the request entity (such as uploading a smaller file). Otherwise, the Web server will need to be reconfigured to accommodate the larger entity. You should inform Webmasters of the offending sites about the trouble.

Guess your AI is just too damn big.
Edited by Toriq on May 26, 2009 19:16:05
 
Black Peter
offline
Link
 
Originally posted by r8

How large is your AI? There's actually a physical limit to how large of a request you can make with anything dealing with servers and such, I think it's something like 65,065 bytes, but someone with some programming knowledge would have to confirm that. So, if you have a ridiculously large AI, you might be hitting that limit.


It's a configuration option in IIs, AFAIK. It can be increased or decreased. But, don't really know what the effect on the GLB servers would be if it were to be increased.

----------
The fix is simply to up the size of the UploadReadAheadSize metabase property.

cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 204800

The metabase setting is represented in bytes, not KB as the technet article would suggest. You can change this setting up to 4GB although you probably wouldn't want to do so unless you had a compelling business need. Of course a site that required authentication would be an effective way of limiting the chances of DoS, so if you do need to up this limit, you should consider requiring client authentication to connect.
( http://blogs.msdn.com/jiruss/archive/2007/04/13/http-413-request-entity-too-large-can-t-upload-large-files-using-iis6.aspx )
Edited by Toriq on May 26, 2009 19:20:46
Edited by Toriq on May 26, 2009 19:20:19
 
TokenFlexican
offline
Link
 
That's what she said!
 
Anarcho
offline
Link
 
It'd be great to know what the actual limit is (and subsequently how much size each input/output consists of) so that these things can be avoided.

I have 65 inputs with approximately 15 outputs per.

I suppose it could use a little trimming, but I do use all of the plays in the playbook. It's just a matter of which plays get used for which team.
 
Zoblefu
offline
Link
 
As a web developer, I know you can actually adjust the setting to be different. Perhaps bort just needs to increase it.
 
California
knows how to party
offline
Link
 
Originally posted by Zoblefu
As a web developer, I know you can actually adjust the setting to be different. Perhaps bort just needs to increase it.


You assume that Bort wants to permanently fix something
 
Bort
Admin
offline
Link
 
Yeah, it sounds like you're hitting a technical limit of data somewhere. It could either be your browser or our web server saying "no."

Seems like I have seen larger AI's than you're describing, but maybe not. 15 outputs for 65 inputs is 975 outputs. That's a damn big form for any browser/server to process.

I do not know off the top of my head what nginx or apache's default values are for POST limits. Probably 64k? It could also be something I could update within the Perl code, with the POST_MAX variable, but it sounds like you're getting an error directly from the load balancer software, not from Perl.
 
PRIME EVIL
offline
Link
 
I like your old avatar better Bort
 
Page:
 


You are not logged in. Please log in if you want to post a reply.