I know nothing about catalyst, but had some issue with guest as well, suddenly
they turned out no responding anymore.
The reason was metalog (inside guest) not processing the log messages it got
through /dev/log. I didn't investigate why metalog did not process the log
data anymore...
Since then I switched over to syslog-ng and network-logging where the issue
does not show up (could it be that kernel log client of metalog did block the
master metalog process?)
Bruno
On Tuesday 22 May 2007 22:05, Roderick A. Anderson wrote:
> This is going to be very vague but please bear with me.
>
> We just rebooted into a new kernel 2.6.20-1.2312.fc5.vs2.2.0.1smp and
> now the Catalyst test servers (http) will not automagically restart
> correctly when they detects changes in the .pm files. I see the message
> it has noticed the changed file but then just sits there until I Ctrl-C
> and start the server again.
>
> This was working with the 2.6.18-1.2255.fc5.vs2.0.2.2.0.rc9.1smp kernel.
>
> Anyone familiar with Catalyst and/or have an idea where to look for what
> is causing this? I'm thinking capabilities but with the change in both
> the base kernel and the Linux-vserver I could use a clue as to where to
> look.
>
> It is mostly an irritation to have to manually restart the Catalyst test
> server but I forgotten when I made a change to the application code and
> wondered why my changes didn't take affect. :-(
>
>
> Thanks,
> Rod
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Tue May 22 22:13:26 2007