[LON-CAPA-admin] Cannot start loncapa . . .
todd.ruskell at gmail.com
Tue Aug 14 23:08:46 EDT 2012
I feel sheepish now.
On Tue, Aug 14, 2012 at 8:55 PM, Stuart Raeburn <raeburn at msu.edu> wrote:
> The first thing I would check is that your filesystem has free space, and
> is also not in read-only mode because of a disk/RAID issue. All those
> failed daemons suggest that the pid files could not be written (which would
> also explain why you see nothing helpful in the log files either).
> Stuart Raeburn
> LON-CAPA Academic Consortium
> Quoting Todd Ruskell <todd.ruskell at gmail.com>:
> Hi all,
>> I recently attempted to upgrade loncapa from 2.10.0 to 2.10.1 on an access
>> server. The update script appeared to work just fine. But now, when I
>> to start the loncapa services, this is what I get:
>> [root at lc1 loncapa-2.10.1]# /etc/init.d/loncontrol start
>> Opening firewall access on port 5663.
>> Starting LON-CAPA
>> Starting LON-CAPA client and daemon processes (please be patient)
>> lonmemcached failed
>> lonsql failed
>> lond failed
>> lonc failed
>> lonmaxima failed
>> lonr failed
>> [root at lc1 loncapa-2.10.1]#
>> And the logs don't seem to help much. I'm guessing that somewhere some
>> permissions may have run amok, but I'm pretty stymied. Any suggestions as
>> to where I should start to look?
> LON-CAPA-admin mailing list
> LON-CAPA-admin at mail.lon-capa.**org <LON-CAPA-admin at mail.lon-capa.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the LON-CAPA-admin