On Tue, Sep 11, 2007 at 09:52:36PM +0200, Manuel Bouyer wrote:
> On Tue, Sep 11, 2007 at 09:43:15PM +0200, Manuel Bouyer wrote:
> > On Tue, Sep 11, 2007 at 03:20:29PM -0400, Thor Lancelot Simon wrote:
> > > On Tue, Sep 11, 2007 at 08:45:11PM +0200, Manuel Bouyer wrote:
> > > > 
> > > > Can you investigate what is trying to load signal.py on your system ?
> > > 
> > > Well, it's clearly a dependency of some Python module.  Can you see if
> > > you've got it on your system anywhere?  Maybe it's my Python installation
> > > that's broken, and so it should be found in some other part of the Python
> > > search path...
> > 
> > Well, I have no signal.py/signal.pyc on my systems. find didn't return
> > anything in /usr/pkg, and locate didn't return anything relevant either.
> 
> And a
> find /usr/pkg -type f |xargs fgrep -l signal.py
> 
> didn't return anything either. I can't explain why xm is looking for a
> signal.py on your system.

It might be error-handling code and not the actual source of the problem.
Scrolling up the ktrace output a bit I find:

   165      1 python2.4 CALL  connect(3,0x839d428,0x1b)
   165      1 python2.4 NAMI  "/var/run/xend/xmlrpc.sock"
   165      1 python2.4 RET   connect -1 errno 2 No such file or directory

This looks more serious.  ps shows:

root     102  0.0  1.2 6672  3252 ?     I     1:37PM 0:00.00 /usr/pk    0  102 1  5172  10  0 6672  3252 wait     I    ?     0:00.00 /usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start 
root     103  0.0  2.6 7072  6792 ?     Ia    1:37PM 0:03.95 /usr/pk    0  103 102     0   2  0 7072  6792 netcon   Ia   ?     0:03.95 /usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start

And indeed there is no /var/run/xend/xmlrpc.sock, though there is in fact
a /var/run/xend.

-- 
  Thor Lancelot Simon	                                     tls@rek.tjls.com

  "The inconsistency is startling, though admittedly, if consistency is to
   be abandoned or transcended, there is no problem."	      - Noam Chomsky