[LON-CAPA-users] Unresponsive lon-capa

[D G Teed]

On Mon, Feb 7, 2011 at 6:15 PM, Stuart Raeburn <raeburn@msu.edu> wrote:

> If you install lynx (the RPM is included in the standard RHEL 4 distro).
>
> On RHEL4:
>
> up2date -i lynx
>
> then you can use:
>
> /usr/sbin/apachectl fullstatus
>
> from the command line in an ssh session on <yourserver> to retrieve the same
> information as a web browser will display with a request for:
>
> http://<yourserver>/server-status/
>
>> Also, when attempting access to Set Domain Configuration,
>> while at this time the apache service is responding
>> normally, I saw an error just now:
>>
>> Something somewhere went wrong... etc. - the report form.
>>
>> The error was:
>>
>> Internal info:
>>
>> ERROR:
>> Undefined subroutine &Apache::domainprefs::handler called.
>
> This error is specific to Apache 1.3 (only currently used for LON-CAPA with
> Redhat Enterprise 4).  The solution is to include the line:
>
> use Apache::domainprefs();
>
> in /etc/httpd/conf/startup.pl
>
> A revised version of the startup.pl file (for LON-CAPA 2.9) includes this
> change. So if you replace rev. 1.34 of startup.pl with rev 1.34.10.1, and
> reload httpd you will eliminate the ISE seen on RHEL4 when the DC displays
> the Domain Configuration page.
>
> All on one line:
>
> wget -O /etc/httpd/conf/startup.pl
> 'http://source.loncapa.org/cgi-bin/cvsweb.cgi/~checkout~/loncom/startup.pl?rev=1.34.10.1;content-type=text/plain'
>
> Then:
>
> /etc/init.d/httpd reload
>
> You may also want to replace domainprefs.pm included in 2.9.1 with an
> updated version, which includes three changes to suppress warnings displayed
> when starting Apache 1.3.
>
> All on one line (for LON-CAPA 2.9.1):
>
> wget -O /home/httpd/lib/perl/Apache/domainprefs.pm
> 'http://source.loncapa.org/cgi-bin/cvsweb.cgi/~checkout~/loncom/interface/domainprefs.pm?rev=1.102.2.16;content-type=text/plain'
>

OK, thanks for these tips.  I've updated the startup.pl to include
the additional 'use' line.  I'm not sure if the apachectl command
will respond when we get these unresponsive situations, but
I'll try the next time it comes to be an issue.

Regards,

--Donald Teed