The next line starts talking about something else entirely. Apache2 error log 
has no entries in it. That is the first place I checked. 
Thanks for the response Jason. 

-----Original Message-----
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jason 
Stephenson
Sent: Wednesday, June 14, 2017 3:14 PM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] Catalogue not loading as expected

Chazya,

Ok. There is no error message on that line, though that does have a 500 status.

Does the next line have more information? Is that from syslog or the
apache2 error.log? If that's from syslog or the access log, try looking in the 
error log for apache2.

Hope that helps,
Jason

On 06/14/2017 06:45 AM, Chazya Sinkamba wrote:
> Hi,
> Thank you for the response. I checked the error log, and the error 
> that came up after clicking on a link that was supposed to give me 
> titles authored by 'chazya'(an author I made up to test the system), 
> is as below;
> 
> ----------------------------------------------------------------------
> ------
> ------------------
> Jun 14 12:37:02 ubuntu-evergreen root: 10.5.1.84 - - 
> [14/Jun/2017:12:34:51
> +0200] "GET
> /eg/opac/results?blimit=10;qtype=author;bterm=Chazya;locg=1;fi%3Ahas_b
> rowse_
> entry=1526%2C8 HTTP/1.1" 500 798
> ----------------------------------------------------------------------
> ------
> -------------------
> 
> Tried going to google with it, no joy there. 
> 
> -----Original Message-----
> From: Open-ils-general
> [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf 
> Of Jason Stephenson
> Sent: Tuesday, June 13, 2017 4:33 PM
> To: open-ils-general@list.georgialibraries.org
> Subject: Re: [OPEN-ILS-GENERAL] Catalogue not loading as expected
> 
> Chazya,
> 
> I haven't seen something like that for a long time, so I don't know 
> off the top of my head what might cause it. It could be a number of things.
> 
> Since you got an internal server error, there should be log messages 
> from Apache, the web server, that will provide some clue as to what happened.
> 
> Depending on your configuration, you can look in 
> /var/log/apache2/error.log or /var/log/syslog for the messages from Apache.
> 
> Errors should be relatively obvious, but look for lines with a 500 in 
> a field by itself. That is the typical number for an internal server error.
> That line should indicate when the error happened, and what caused it.
> 
> If you can find that and share it, someone can probably tell you where 
> else to start looking.
> 
> Good luck,
> Jason
> 
> On 06/13/2017 08:15 AM, Chazya Sinkamba wrote:
>> Hi all,
>>
>> New to evergreen, just finished populating the data after initial 
>> installation. To confirm the data has been loaded, I searched for a 
>> title, and got the results as desired. Clicking on the title however 
>> resulted in the page loading for ages, and eventually giving me an 
>> internal server error. Has anyone else experienced this? Any idea 
>> what I did wrong?
>>
>> Thanks
>>
>>  
>>
>> Chazya Sinkamba
>>
> 

Reply via email to