Hi;
I'm reading the Plone book. It states that for Zope 2.7 (I have 2.78)
ZEO is built in by default but must be instantiated thus:
cd /opt/Zope-2/7/bin
./mkzeoinstance /var/zeo
or some such code. So I tried this:
cd /usr/local/zope/278/bin
./mkzeoinstance.py ../../instance2/var/zeo
where 27
- Original Message -
From: "beno" <[EMAIL PROTECTED]>
To:
Sent: Saturday, September 02, 2006 9:24 AM
Subject: [Zope] ZEO Problem
Hi;
I'm reading the Plone book. It states that for Zope 2.7 (I have 2.78) ZEO
is built in by default but must be instantiated thu
02, 2006 9:24 AM
Subject: [Zope] ZEO Problem
Hi;
I'm reading the Plone book. It states that for Zope 2.7 (I have 2.78)
ZEO is built in by default but must be instantiated thus:
cd /opt/Zope-2/7/bin
./mkzeoinstance /var/zeo
or some such code. So I tried this:
cd /usr/local/zope/278/b
- Original Message -
From: "beno" <[EMAIL PROTECTED]>
To:
Sent: Saturday, September 02, 2006 10:27 AM
Subject: Re: [Zope] ZEO Problem
I got this working by changing the following in zope.conf:
server localhost:7080
to
server 202.71.106.119:
Apparently,
Jonathan wrote:
I got this working by changing the following in zope.conf:
server localhost:7080
to
server 202.71.106.119:
Apparently, it needs its own port?
TIA,
beno
You need to make sure that the entry in your zeo client config file
(zope.conf)
eg
server 194.123.123.123:8100
--On 2. September 2006 12:15:47 -0400 beno <[EMAIL PROTECTED]> wrote:
address 8100
and that your zeo server is running on the ip address specified in the
entry in zope.conf
That's logical. Why does zeo need its own port?
Because every kind of network service needs its own port.
-aj
HI,
we have quite a Problem with out Zope/Zeo system. We run at the moment
Zope cluster with 10 application servers and a zeo server with
Filestorage. Our Data.fs is 3.5 Gig at the moment (after Pack).
I runs most of the time without problem. But sometimes things screw up
2006-08-07T14:29:19 INF
Gerhard Schmidt wrote at 2006-8-7 15:54 +0200:
> ...
>2006-08-07T14:29:19 INFO ZEO.StorageServer (97002/10.152.64.23:52518)
>Transaction
>+blocked waiting for storage. Clients waiting: 1.
> ...
>2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Blocked
>transaction restarted.
On Mon, Aug 07, 2006 at 09:09:56PM +0200, Dieter Maurer wrote:
> Gerhard Schmidt wrote at 2006-8-7 15:54 +0200:
> > ...
> >2006-08-07T14:29:19 INFO ZEO.StorageServer (97002/10.152.64.23:52518)
> >Transaction
> >+blocked waiting for storage. Clients waiting: 1.
> > ...
> >2006-08-07T14:29:50 INFO ZE
Gerhard Schmidt wrote at 2006-8-8 08:06 +0200:
> ... long time commit locks ...
>To understand this can you tell me when a transaction is started and when
>its closed. Does the Zeo server wait until all data is recieved bevor the
>transaction is started or does the transaktion start when the data
10 matches
Mail list logo
