Thanks - it seems that "/tmp" (160M) is not big enough... ( "passenger upload buffer dir", etc. )
-----Original Message----- From: Carsten Munk [mailto:[email protected]] Sent: Wednesday, July 04, 2012 9:26 PM To: [email protected] Subject: Re: [mer-general] large files fail to be submitted to a "local OBS appliance" 2012/7/5 Steve Rae <[email protected]>: > Of the 131 MER packages that I am trying to rebuild, > > two of the packages fail when performing an "osc commit": > > Transmitting file data .Server returned an error: HTTP Error 500: Internal > Server Error > > > > I think that it is because of the file size: > > gcc-linaro-4.6-2011.12.tar.bz2 (69M) > > linux-2.6.37.tar.bz2 (71M) > > ((( the next largest file is > > binutils-2.22.tar.bz2 (20M) > > and it is successfully transmitted... ))) > >From what I recall, OBS utilizes /tmp or /srv/obs/upload as storage when files are being uploaded (on frontend and backup). Can you verify either of these have enough space? As an alternative, the way we typically full-rebuild Mer is by linkpac'ing to the MDS's packages as the MDS contains full sources as well, working around the need to upload or import src rpms. See https://wiki.merproject.org/wiki/Local_Mer for an example for this. Mer's systems are designed to let you full-rebuild in this manner as we consider it an essential part of vendor's ability to ensure their product work can continue if Mer itself is somehow offline or disappears. Or for device-specific Core rebuilds with proper optimization flags, etc.. Let us know if you have any problems, we're more than happy to help. /Carsten > > > I am building in a "local OBS appliance" with the > > > http://repo.pub.meego.com/releases/Mer-OBS/2.3.1mer1.03/builds/i586/packages/ > > applied - I suspect that there is a configuration somewhere which is > limiting the file size to ~20M... > > > > Any help would be appreciated. > > Thanks, Steve
