[Zope] Zope refusing to serve our large files (180M+)
Hi all, Sure someone's probably come across something similar, but I couldn't find anything in the archives: our zope is refusing to allow download of files greater than around 170M through the http server. We have a number of db dumpfiles we want people to be able to access. We are running Zope 2.7.0 with an Apache front (reverse-proxy, as our zope is on a non-standard port) on a linux2.4 kernel (mosix) with bags of memory; the apache end is fine - the zope installation is local and I am using the port number with all the same problems. 1) I can download a 170M file but not a 180M file through the http server. With the larger file request we get a 500 error in the trace log. The download box pops up but nothing is actually downloaded. 2) I can reach both through the ftp server but transfer rate is ridiculous (1.7Kb/sec) for a University lan. 3) Even if I could find out why ftp transfer is so slow and sort it, I seem unable to grant a non-manager read access to a LocalFS object: the properties don't stick when I change them, and Zope creates the link to the local directory with user Zope, group Zope, permissions 660, hence although managers can reach the files, nothing is reachable for an 'anonymous' user (I created a special user for ftp and gave only access to the specific directories, before you voice concerns!) I don't know all the ins and outs of Zope and there's probably something obvious I haven't done, but any help greatly appreciated, it's been driving me mad. I guess another option is to use our apache front for secure ftp access, but I wanted everything tidy, and besides I don't have root privileges on the server. Thanks in advance, Chris ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope refusing to serve our large files (180M+)
Hi, thanks for the reply. 1) I can download a 170M file but not a 180M file through the http server. With the larger file request we get a 500 error in the trace log. The download box pops up but nothing is actually downloaded. If there's a 500 error in the trace or access log, there should be something in your error_log too. Traceback please? None. Zippo. Squat. I've turned on 'ALL' logging in zope.conf for all logs. All I get is a simple entry in the Z2.log thus: 128.214.209.35 - cwilton [08/Dec/2005:18:38:46 +0300] GET /dali/downloads/180M.tar HTTP/1.1 500 272 Opera/8.5 (X11; Linux i686; U; en-GB) And an equally unhelpful entry in the trace log: -- 2005-12-08T18:45:23 B 1131651340 2005-12-08T18:45:23 GET /dali/downloads/180M.tar -- 2005-12-08T18:45:23 I 1131651340 2005-12-08T18:45:23 0 -- 2005-12-08T18:45:24 A 1131651340 2005-12-08T18:45:24 500 272 -- 2005-12-08T18:45:24 E 1131651340 2005-12-08T18:45:24 -- Nothing at all in our error log (stderr and stdout for zope process redirected to logfile) or the event log. Thanks for the advice on ftp; I might look at newer Zopes, but we'd rather not have to use zope's ftp (for reasons including those you pointed out), as our content should be reachable through the http server; I'd rather tackle that problem. LocalFS doesn't support properties at all AFAIK. Bummer. Anyhow, see above about wanting to avoid ftp... and Zope creates the link to the local directory with user Zope, group Zope, permissions 660 ... You're talking about Zope permissions and filesystem permissions in the same sentence ... Sorry, that was a bit muddled, what I meant was when I list dir contents using ftp, I see my LocalFS object listed there with 'owner' Zope, 'group' Zope, and mods 660 as far as ftp is concerned. The security settings in zope are the ones that I seem unable to change for a LocalFS object. Well, they're clickable, but the changes don't seem to stick. Again, bummer, but again, I was hoping it'd be unnecessary... Any obvious config settings I might be missing? Thanks, Chris ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope refusing to serve ... i am an idiot
Whoops. Sorry. Error log tells me it's a 'no space left on device' error: 2005-12-08T19:33:30 ERROR(200) SiteError http://ekhidna.biocenter.helsinki.fi/dali/downloads/180M.tar/index_html Traceback (most recent call last): File /data/backup/Zope-2.7.0/lib/python/ZPublisher/Publish.py, line 100, in publish request, bind=1) File /data/backup/Zope-2.7.0/lib/python/ZPublisher/mapply.py, line 88, in mapply if debug is not None: return debug(object,args,context) File /data/backup/Zope-2.7.0/lib/python/ZPublisher/Publish.py, line 40, in call_object result=apply(object,args) # Type scr to step into published object. File /data/backup/Zope-2.7.0/lib/python/OFS/Image.py, line 384, in index_html RESPONSE.write(data.data) File /data/backup/Zope-2.7.0/lib/python/ZServer/HTTPResponse.py, line 190, in write t.write(data) IOError: [Errno 28] No space left on device I assume this means there's a max cache size set somewhere. There's plenty of room left on our fs (hundreds of GB) so Zope isn't being allowed to use it at the moment. I'm asuming this is a Zope rather than local filesystem issue, but maybe I'm wrong; if it is a Zope issue, how I can increase standard cache size? We're not using a cache manager, yet... Thanks for your patience, Chris ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope refusing to serve ... i am an idiot
I assume this means there's a max cache size set somewhere. There's plenty of room left on our fs (hundreds of GB) so Zope isn't being allowed to use it at the moment. I'm asuming this is a Zope rather than local filesystem issue, but maybe I'm wrong; if it is a Zope issue, how I can increase standard cache size? We're not using a cache manager, yet... None of the above ;-) It's most likely that your temp directory is mounted on a small partition. Trying setting the envar TMPDIR to point at a directory on a large partition before starting Zope. That is, you're not running into a cache size problem, you're running into that Zope is creating a large temp file on a partition without enough space to hold it. Heh, it worked a treat! Blinkered as I was, I never thought to check the system temp dir; df-ing our filesystem tells me that today there is only 174M free on the root partition, where default /tmp is. That magical figure explains why I was able to download a 170M file but not a 180M file. Sorted. Big big thanks, Chris ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
