HI David, Thank you. I'll look into the Apache settings as well. That reminds me of a similar issue I had with a PHP application and the problem was PHP execution time settings.
Also, I located an error message in the log. Looks like I'm getting a permission denied error for exports.pl. *[cgid:error] [pid 554389:tid 554389] (13)Permission denied: [client 172.56.200.129:42349 <http://172.56.200.129:42349>] AH01257: stderr from /usr/share/koha/intranet/cgi-bin/tools/export.pl <http://export.pl>: unable to connect to cgi daemon after multiple tries, referer: http://Ipaddress:8081/cgi-bin/koha/tools/inventory.pl <http://Ipaddress:8081/cgi-bin/koha/tools/inventory.pl>* When I checked the permission for the file, they are the same as other files in the "... /cgi-bin/tools" directory. The file inventory.pl permissions are the same as export.pl. The inventory page works on the front end. -Evan On Fri, Jul 19, 2024 at 3:50 PM David Nind <da...@davidnind.com> wrote: > Hi Evan. > > It's a long time since I've dealt with Apache server errors and the 503 > error you are getting, but here are some things to look at: > > - As you have tried with plenty of server memory, it's not likely to be > that. It may be something to do with how Apache is configured - including > settings like the Timeout, KeepAlive, MaxKeepAliveRequests, > KeepAliveTimeout settings. > > - I would look at the Apache server logs to see if there is something more > in there about the cause of the issue. > > - If your server is behind a firewall, proxy servers, or caches (something > I don't know much about) then that may be contributing as well. > > It may also be a Koha bug, but 63,000 items is not that large, and I > couldn't find a bug about performance issues when exporting the catalog. > > For running the misc/export_records.pl script from the command line, then > outputting to the terminal instead of saving to the file, this may be a > file permission error (well, that's what my searching says). > > In my local development environment testing, it was saving the file to > where I ran the command line from. So maybe changing the path of the file > to somewhere where the user you are running the command with has permission > may work. > > I'm not a system admin, so hopefully more experienced Koha system > administrators can share what they would try to troubleshoot the issues you > are having. > > David Nind > New Zealand > _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
