[Zope] ZEO start.py fails to start ZSS on Debian...

[sean.upton@uniontrib.com]

Well, it now works on my with the source release, so my ZSS is built off the
source release, and my ZEO Clients are all Debian deb-packaged Zope
installs.  Seems like a fair compromise; I will debug it though, and send a
not of my findings to the Debian package maintainer for Zope; hopefully a
fix can be found.

Does anyone know why it might work on Intel deb, but not on SPARC deb?
Debian uses an auto-build system to build source for multiple platforms even
though a given package maintainer may only build the packages on one.  I
wonder why this would cause what look to be identical installs (for the most
part, same Zope, same python, same libc6) to act differently?

Hopefully the answer is to debug start.py with the debugger, find out where
my setup causes the except: pass, and attempt to figure out why this is
happening.

Thanks,
Sean

-----Original Message-----
From: Tres Seaver [mailto:tseaver@palladion.com]
Sent: Wednesday, May 30, 2001 5:20 AM
To: sean.upton@uniontrib.com
Cc: zope@zope.org
Subject: Re: [Zope] ZEO start.py fails to start ZSS on Debian...


sean.upton@uniontrib.com wrote:


> I am running Debian testing (SPARC) with the 2.3.2-2 Zope deb, trying to
> install ZEO, and am hung up on the storage server install becuase, even in
> the simplest of cases, I cannot get lib/python/ZEO/start.py to do
> anything... I get the same issue with ZEO 1.0b1 and 1.0b3.  There are a
> bunch of
> 	try: ...
> 	except: pass
> statements in the start.py code, and I'm sure I'm getting hit with one of
> them; it's too bad there are not more debugging messages in there...  
> 
> Since there are no tracebacks, below is the best I have (a shell
transcript)
> 
> Under Debian, Zope is installed at /usr/lib/zope as a program root (and
thus
> ZEO, unpacked here, with ZEO1.0b3/ZEO copied to lib/python, so that there
is
> a lib/python/ZEO).  /var/lib/zope is the instance home and contains a var
> (/var/lib/zope/var) directory with Data.fs, log, and pid files.
> 
> Any help/thoughts would be appreciated...


I would probably try to find the errant spot using PDB, e.g.,
I would drop the following line into the 'main()' function:

     import pdb; pdb.set_trace()

Then, when you run the start script using '-D', the debugger will stop
at that point, and you can single step, print variables, etc., using
the "standard Python debugger",

  http://www.python.org/doc/1.5.2p2/lib/module-pdb.html


If that doesn't help, or if you've found a bug, then I would ask
for further help on the zodb-dev@zope.org list.

Tres.
--
===============================================================
Tres Seaver                                tseaver@digicool.com
Digital Creations     "Zope Dealers"       http://www.zope.org