Hello,
bric_soap media export is failing with "Apache::SizeLimit httpd process too big" in the log file.
My export looks something like this...
/usr/local/bricolage/bin/bric_soap media list_ids --with-related-media --username xxx --password xxx --server http://localhost/ --timeout 0 --continue-on-errors --search cover_date_start=2010-02-01T00:01:00Z --search cover_date_end=2010-02-01T23:59:00Z --timeout 0 | /usr/local/bricolage/bin/bric_soap media export -> media_2010_02_01.xml --username xxx --password xxx --server http://localhost/ --timeout 0 --continue-on-errors -
I also tried modifying /usr/local/bricolage/lib/Bric/SOAPMedia.pm file to skip reading and writing the actual image asset by commenting that logic out and writing a blank dataElement in it's place like this...
sub serialize_asset {
...
# read in file data
# my $fh = $media->get_file;
# my $data = join('',<$fh>);
# $writer->dataElement(data => MIME::Base64::encode_base64($data,''));
$writer->dataElement(data => '');
# close $fh;
...
}
We only do about 20 photos per day, so I cannot understand why a)it's taking over an hour to process and b)it eventually fails. This is the message when it fails:
TRANSPORT ERROR: 500 Server closed connection without sending any data back
Check the Apache error log for more information.
My pertinent bricolage.conf settings are:
CHECK_PROCESS_SIZE = Yes
MAX_PROCESS_SIZE = 64000
CHECK_FREQUENCY = 10
MIN_SHARE_SIZE = 0
MAX_UNSHARED_SIZE = 0
Any thoughts and help is greatly appreciated.
Thank you,
Mike
bric_soap media export is failing with "Apache::SizeLimit httpd process too big" in the log file.
My export looks something like this...
/usr/local/bricolage/bin/bric_soap media list_ids --with-related-media --username xxx --password xxx --server http://localhost/ --timeout 0 --continue-on-errors --search cover_date_start=2010-02-01T00:01:00Z --search cover_date_end=2010-02-01T23:59:00Z --timeout 0 | /usr/local/bricolage/bin/bric_soap media export -> media_2010_02_01.xml --username xxx --password xxx --server http://localhost/ --timeout 0 --continue-on-errors -
I also tried modifying /usr/local/bricolage/lib/Bric/SOAPMedia.pm file to skip reading and writing the actual image asset by commenting that logic out and writing a blank dataElement in it's place like this...
sub serialize_asset {
...
# read in file data
# my $fh = $media->get_file;
# my $data = join('',<$fh>);
# $writer->dataElement(data => MIME::Base64::encode_base64($data,''));
$writer->dataElement(data => '');
# close $fh;
...
}
We only do about 20 photos per day, so I cannot understand why a)it's taking over an hour to process and b)it eventually fails. This is the message when it fails:
TRANSPORT ERROR: 500 Server closed connection without sending any data back
Check the Apache error log for more information.
My pertinent bricolage.conf settings are:
CHECK_PROCESS_SIZE = Yes
MAX_PROCESS_SIZE = 64000
CHECK_FREQUENCY = 10
MIN_SHARE_SIZE = 0
MAX_UNSHARED_SIZE = 0
Any thoughts and help is greatly appreciated.
Thank you,
Mike