plone-users — General mailinglist for users of Plone

Re: [Plone-Users] ZRS and plone.app.theming

[Nathan V. G. <van...@gm...>]

The whole point of ZRS is to be able to have data replicated. If things are
edited in the database on master, they should be replicated to the
secondary read-only zeo.

Are you certain it's replicating correctly?

On Mon, Jul 13, 2015 at 2:27 PM, Mike Metcalfe <mi...@we...> wrote:

> Hi Nathanm
>
> On 13 July 2015 at 12:59, Nathan Van Gheem <van...@gm...> wrote:
>
>> You are still using a primary zeo server right? Assuming you're talking
>> about doing changes TTW. Why not just change the skin on the primary and
>> it'll get replicated out.
>>
>
> I'm not sure what you mean by a primary zeo. I have 2 zeo clusters, a
> master that replicates to a specific port and a slave that replicates from
> that port (with all clients in readonly mode). When I make style changes in
> the master TTW I don't get that replicated to the slave. However,
> activating/deactivating the skin on the master does affect the slave.
>



-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp

Re: [Plone-Users] ZRS and plone.app.theming

[Mike M. <mi...@we...>]

Hi Nathanm

On 13 July 2015 at 12:59, Nathan Van Gheem <van...@gm...> wrote:

> You are still using a primary zeo server right? Assuming you're talking
> about doing changes TTW. Why not just change the skin on the primary and
> it'll get replicated out.
>

I'm not sure what you mean by a primary zeo. I have 2 zeo clusters, a
master that replicates to a specific port and a slave that replicates from
that port (with all clients in readonly mode). When I make style changes in
the master TTW I don't get that replicated to the slave. However,
activating/deactivating the skin on the master does affect the slave.

Re: [Plone-Users] ZRS and plone.app.theming

[T. K. N. <ng...@pl...>]

I think for a lot of theme changes (e.g. images, CSS files) you could serve them from a remote absolute URL you can specify in the advanced settings. That way you could make changes to those resources and they should appear on both your sites.

	Kim

> On Jul 13, 2015, at 6:59 AM, Nathan Van Gheem <van...@gm...> wrote:
> 
> You are still using a primary zeo server right? Assuming you're talking about doing changes TTW. Why not just change the skin on the primary and it'll get replicated out.
> 
> On Mon, Jul 13, 2015 at 12:24 PM, Mike Metcalfe <mi...@we... <mailto:mi...@we...>> wrote:
> Hi,
> 
> I have ZRS installed and it replicates content changes perfectly. If I change the code on the master, I simply upgrade the code on the replica and restart it. However if I want to change the skin,  I cannot upload it into the replica instance because it is in read-only mode. So to roll out a skin change I must drop the replica, switch off replicate-from and read-only, upload the new skin zip file, drop the instance, switch on replication and read-only and restart it.
> 
> Does anyone know an alternative to this lengthy procedure?
> 
> Thanks,
> 
> -- 
> Mike Metcalfe
> 
> 082 903 8268
> mi...@we... <mailto:mi...@we...>
> www.webtide.co.za <http://www.webtide.co.za/>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/ <https://www.gigenetcloud.com/>
> _______________________________________________
> Plone-Users mailing list
> Plo...@li... <mailto:Plo...@li...>
> https://lists.sourceforge.net/lists/listinfo/plone-users <https://lists.sourceforge.net/lists/listinfo/plone-users>
> 
> 
> 
> 
> -- 
> Nathan Van Gheem
> Solutions Architect
> Wildcard Corp
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/_______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users

Re: [Plone-Users] ZRS and plone.app.theming

[Nathan V. G. <van...@gm...>]

You are still using a primary zeo server right? Assuming you're talking
about doing changes TTW. Why not just change the skin on the primary and
it'll get replicated out.

On Mon, Jul 13, 2015 at 12:24 PM, Mike Metcalfe <mi...@we...> wrote:

> Hi,
>
> I have ZRS installed and it replicates content changes perfectly. If I
> change the code on the master, I simply upgrade the code on the replica and
> restart it. However if I want to change the skin,  I cannot upload it into
> the replica instance because it is in read-only mode. So to roll out a skin
> change I must drop the replica, switch off replicate-from and read-only,
> upload the new skin zip file, drop the instance, switch on replication and
> read-only and restart it.
>
> Does anyone know an alternative to this lengthy procedure?
>
> Thanks,
>
> --
> Mike Metcalfe
>
> 082 903 8268
> mi...@we...
> www.webtide.co.za
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users
>
>


-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp

[Plone-Users] ZRS and plone.app.theming

[Mike M. <mi...@we...>]

Hi,

I have ZRS installed and it replicates content changes perfectly. If I
change the code on the master, I simply upgrade the code on the replica and
restart it. However if I want to change the skin,  I cannot upload it into
the replica instance because it is in read-only mode. So to roll out a skin
change I must drop the replica, switch off replicate-from and read-only,
upload the new skin zip file, drop the instance, switch on replication and
read-only and restart it.

Does anyone know an alternative to this lengthy procedure?

Thanks,

-- 
Mike Metcalfe

082 903 8268
mi...@we...
www.webtide.co.za

[Plone-Users] Server Version disclosure

[eras m. <er...@gm...>]

Hi All,

I have to disable server version disclosure.

Apache is in the front-end of plone.Added the following in apache configuration

ServerTokens Prod
ServerSignature Off

When acessing the site by using
wget -S https://www.mydomain.com --no-check-certificate

I still get
Server: Zope/(Zope 2.10.9-final, python 2.4.6, linux2) ZServer/1.1 Plone/3.3.1

I don't want this server information to be displayed.
Anything more to be done? Please help.

[Plone-Users] Remember, lists will be getting shut down eventually, use community.plone.org!

[Nathan V. G. <na...@va...>]

Hi Community,

Just a reminder that, some day, these lists will no longer be supported.

Please sign up at https://community.plone.org/ and configure your mail
settings!

-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[dieter <di...@ha...>]

Eggert Ehmke <egg...@be...> writes:
> ...
> Thanks for the hint. Where could I adjust the timeout?

It used to be defined in the "zoperunner" section of the
Zope configuration file ("etc/zope.conf"), documented in
"Zope2.Startup:zopeschema.xml" -- apparently, it has been dropped in
the meantime. In addition, the runner (at least "zdrun.py")
no longer supervises a successful startup of the Zope process - thus,
there should no longer be a need for the option.

In addition, the daemon runner is supposed to use the same
logging configuration as the Zope process itself. However, this
seems not to work. Not sure, there is a way to work around this bug
(and get the daemon logs) -- apart from changing sources.


> It seem to be a systematic problem, now I can see it on three different 
> installations of Plone 4.3.6. I am not sure about 4.3.5, but it definitely did 
> not show up before. The databases are not particular large.

Apparently, you found "SIGTERM" signal log messages in your
logfile. This means that someone/something has sent those signals
to the Zope process. Key to the understanding of your problem
is to find out who/what did this.

Potential candidates:

  *  some supervising/monitoring software (you should know whether you let
     your Zope/Plone processes be supervised)

  *  the daemon process (usually "zdaemon.zdrun").
     Apparently, it no longer sends
     "SIGTERM" signals to the Zope process for startup problems.

     Getting its logging working may give hints whether it is
     responsible

  *  the Zope process itself.

     Usually, it does not do this - however, extensions might
     do it.
     
     As your Zope runs well in "foreground" mode; this is not likely.

  *  the operating system
     
     However, it should write a log message (usually somewhere
     below "/var/log") when it does.

     As your Zope runs well in "foreground" mode, this is not likely.

As your Zope runs well in "foreground" mode (which does not
use a daemon process) but not in "daemon" mode (which uses a
daemon process), indications are strong that something with
the daemon process does not work as it should be.

The most likely cause would be permission problems for the communication
sockets between "zopectl" and "zdrun". However, you have rules out this
cause.


If nothing else helps, you may need to debug the startup process.

The difficult part is the debugging of the daemonized "zdrun"
as "daemonization" has dropped the connection to the terminal
necessary for the debugger interaction. The trick to get
around this difficulty is to force "zopectl" to use "zdrun"
but do not pass to it the request to "daemonize".
You may be able to do this by setting the "daemon" attribute
to "false" in the "zoperunner" section of your "etc/zope.conf" file.

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Eggert E. <egg...@be...>]

Am Samstag, 20. Juni 2015, 08:22:55 schrieb dieter:
> Eggert Ehmke <egg...@be...> writes:
> > Am Donnerstag, 18. Juni 2015, 08:06:11 schrieb Steve McMahon:
> >> On Wed, Jun 17, 2015 at 2:46 PM, Eggert Ehmke <egg...@be...>
> >> 
> >> wrote:
> >> > Yes, what's more: when started via
> >> > bin/instance fg
> >> > it runs fine, no restarts.
> >> 
> >> A nearly sure sign that your problem is with permissions and ownerships.
> >> When running in "fg" there is no need to write our a pid file. Check your
> >> ownership and permissions in ./var. The daemon process must be able to
> >> write out its pid and log files.
> > 
> > All directories in var have
> > drwxrws--- 4 plone_daemon plone_group
> > All files have
> > -rw-r--r-- 1 plone_daemon plone_group
> > 
> > Beside of thus, the pid file is written, even when running in fg. Also the
> > log file instance log is written, but gives no clue other then what
> > stated in the first post.
> 
> Nevertheless, your observations indicate some problem with the
> "zdaemon <-> zope" communication.
> 
> When I remember right, the "zdaemon" sends a "SIGTERM" to the controlled
> "zope" process when it does not receive a startup answer within some
> time limit and then tries to start the "zope" process again.
> I had to increase this timeout in a case where opening a large
> number of large ZODB storages took too much time - as the "zope" process
> did not complete its startup sufficiently fast.
> 
> When I remember right, "zdaemon" allows to specify a logfile of its
> own. You may try this to get information about "zdaemon"s observations
> about the "zope" process.

Hello Dieter,

Thanks for the hint. Where could I adjust the timeout?

It seem to be a systematic problem, now I can see it on three different 
installations of Plone 4.3.6. I am not sure about 4.3.5, but it definitely did 
not show up before. The databases are not particular large.

Eggert


> 
> 
> --
> Dieter
> 
> 
> 
> ----------------------------------------------------------------------------
> -- _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[dieter <di...@ha...>]

Eggert Ehmke <egg...@be...> writes:

> Am Donnerstag, 18. Juni 2015, 08:06:11 schrieb Steve McMahon:
>> On Wed, Jun 17, 2015 at 2:46 PM, Eggert Ehmke <egg...@be...>
>> 
>> wrote:
>> > Yes, what's more: when started via
>> > bin/instance fg
>> > it runs fine, no restarts.
>> 
>> A nearly sure sign that your problem is with permissions and ownerships.
>> When running in "fg" there is no need to write our a pid file. Check your
>> ownership and permissions in ./var. The daemon process must be able to
>> write out its pid and log files.
>
> All directories in var have
> drwxrws--- 4 plone_daemon plone_group
> All files have
> -rw-r--r-- 1 plone_daemon plone_group
>
> Beside of thus, the pid file is written, even when running in fg. Also the log 
> file instance log is written, but gives no clue other then what stated in the 
> first post.

Nevertheless, your observations indicate some problem with the
"zdaemon <-> zope" communication.

When I remember right, the "zdaemon" sends a "SIGTERM" to the controlled
"zope" process when it does not receive a startup answer within some
time limit and then tries to start the "zope" process again.
I had to increase this timeout in a case where opening a large
number of large ZODB storages took too much time - as the "zope" process
did not complete its startup sufficiently fast.

When I remember right, "zdaemon" allows to specify a logfile of its
own. You may try this to get information about "zdaemon"s observations
about the "zope" process.


--
Dieter

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Eggert E. <egg...@be...>]

Am Donnerstag, 18. Juni 2015, 08:06:11 schrieb Steve McMahon:
> On Wed, Jun 17, 2015 at 2:46 PM, Eggert Ehmke <egg...@be...>
> 
> wrote:
> > Yes, what's more: when started via
> > bin/instance fg
> > it runs fine, no restarts.
> 
> A nearly sure sign that your problem is with permissions and ownerships.
> When running in "fg" there is no need to write our a pid file. Check your
> ownership and permissions in ./var. The daemon process must be able to
> write out its pid and log files.

All directories in var have
drwxrws--- 4 plone_daemon plone_group
All files have
-rw-r--r-- 1 plone_daemon plone_group

Beside of thus, the pid file is written, even when running in fg. Also the log 
file instance log is written, but gives no clue other then what stated in the 
first post.

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Steve M. <st...@dc...>]

On Wed, Jun 17, 2015 at 2:46 PM, Eggert Ehmke <egg...@be...>
wrote:

> Yes, what's more: when started via
> bin/instance fg
> it runs fine, no restarts.


A nearly sure sign that your problem is with permissions and ownerships.
When running in "fg" there is no need to write our a pid file. Check your
ownership and permissions in ./var. The daemon process must be able to
write out its pid and log files.

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[espen <es...@me...>]

17. juni 2015 kl. 23:47 skrev eehmke [via Plone] <ml-...@n2...>:

> Yes, what's more: when started via 
> bin/instance fg 
> it runs fine, no restarts. 

I can not see any reason why the below has anything to do with this, but just in case it has:

JS (and CSS) files are also in debug mode, so a JS typo in one JS file will not affetct the others that are usually merged ( in /portal_javascript )
Some files in subfolder in themes are not avalable in  ‘normal mode’ (if not declared properly), but in debug mode they are. (yes, this is almost a bug)

(even more far fetched):
If you run in debug mode, the CSS files will be the same for anon and logged in users (because they are  served one by one, not merged.
This means that if you acces a CSS file as ‘admin’, the file might be avalable to anon users after this
(maybe even more important if a JS file or CSS is made as a browser view ( plonetruegallery, collective.prettyphoto and some other add-ons do this (mine for example)

Espen


> 
> Eggert 
> 
> Am Mittwoch, 17. Juni 2015, 12:37:24 schrieb espen: 
> > probably a stupid suggestion, but: 
> > 
> > Is there any chance that there is a ‘bad add on’ installed ? 
> > Does it start in debug mode OK ? 
> > 
> > Espen 
> > 
> > 17. juni 2015 kl. 16:53 skrev eehmke [via Plone] <ml- 
> [hidden email]>:
> 
> > > Ok now my 4.3.6 Plone instances seem to run. I observed a different 
> > > problem on two servers (different machines): 
> > > 
> > > every 3 or4 minutes the instances are restarted. In the instance.log this 
> > > can be found: 
> > > 
> > > 2015-06-17T16:28:11 INFO Zope Ready to handle requests 
> > > ------ 
> > > 2015-06-17T16:30:00 INFO SignalHandler Caught signal SIGTERM 
> > > ------ 
> > > 2015-06-17T16:30:00 INFO Z2 Shutting down fast 
> > > ------ 
> > > 2015-06-17T16:30:00 INFO ZServer closing HTTP to new connections 
> > > ------ 
> > > 2015-06-17T16:30:00 INFO ZServer closing WebDAV to new connections 
> > > ... 
> > > 
> > > I can't get what causes the SIGTERMs. How can I debug this? 
> > > 
> > > Am Montag, 15. Juni 2015, 16:17:04 schrieb Steve McMahon: 
> > > > Just wanted to add that I've found Jens method rock solid and we're 
> > > > using 
> > > > it in the Plone 5 Unified Installer. 
> > > > 
> > > > setutools annoyances, unfortunately, remain with builds created via the 
> > > > 4.3.x installer. 
> > > > 
> > > > On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <[hidden email]> 
> > > > 
> > > > wrote: 
> > > > > for me it works out fine (universally it seem) as described here: 
> > > > > https://community.plone.org/t/not-using-bootstrap-py-as-default/620
> > > > > 
> > > > > Jens 
> > > > > 
> > > > > On 2015-06-15 13:54, Eggert Ehmke wrote: 
> > > > > > Hello, 
> > > > > > 
> > > > > > I changed my buildout to draw Plone 4.3.6. Now my buildout fails: 
> > > > > > 
> > > > > > $ sudo -u plone_buildout bin/buildout 
> > > > > > 
> > > > > > Traceback (most recent call last): 
> > > > > >   File "bin/buildout", line 17, in <module> 
> > > > > >   
> > > > > >     import zc.buildout.buildout 
> > > > > >   
> > > > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1- 
> > > > > > 
> > > > > > py2.7.egg/zc/buildout/buildout.py", line 40, in <module> 
> > > > > > 
> > > > > >     import zc.buildout.download 
> > > > > >   
> > > > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1- 
> > > > > > 
> > > > > > py2.7.egg/zc/buildout/download.py", line 20, in <module> 
> > > > > > 
> > > > > >     from zc.buildout.easy_install import realpath 
> > > > > >   
> > > > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1- 
> > > > > > 
> > > > > > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module> 
> > > > > > 
> > > > > >     import setuptools.archive_util 
> > > > > >   
> > > > > >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, 
> > > > > >   in 
> > > > > > 
> > > > > > <module> 
> > > > > > 
> > > > > >   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, 
> > > > > >   in 
> > > > > > 
> > > > > > <module> 
> > > > > > 
> > > > > >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in 
> > > > > 
> > > > > <module> 
> > > > > 
> > > > > > AttributeError: 'module' object has no attribute 'packaging' 
> > > > > > 
> > > > > > I already tried to upgrade my setuptools: 
> > > > > > 
> > > > > > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools 
> > > > > > Searching for setuptools 
> > > > > > Reading https://pypi.python.org/simple/setuptools/
> > > > > > Best match: setuptools 17.1.1 
> > > > > > Processing setuptools-17.1.1-py2.7.egg 
> > > > > > setuptools 17.1.1 is already the active version in easy-install.pth 
> > > > > > Installing easy_install script to /usr/local/Plone/Python-2.7/bin 
> > > > > > Installing easy_install-2.7 script to 
> > > > > > /usr/local/Plone/Python-2.7/bin 
> > > > > > 
> > > > > > Using /usr/local/Plone/Python-2.7/lib/python2.7/site- 
> > > > > > packages/setuptools-17.1.1-py2.7.egg 
> > > > > > Processing dependencies for setuptools 
> > > > > > Finished processing dependencies for setuptools 
> > > > > > 
> > > > > > This seems to work but does not make a difference. Any ideas? 
> > > > > > 
> > > > > > Regards 
> > > > > > Eggert 
> > > > > 
> > > > > ---------------------------------------------------------------------- 
> > > > > ---- 
> > > > > ---- 
> > > 
> > > -------------------------------------------------------------------------- 
> > > ---- _______________________________________________ 
> > > Plone-Users mailing list 
> > > [hidden email] 
> > > https://lists.sourceforge.net/lists/listinfo/plone-users
> > > 
> > > 
> > > If you reply to this email, your message will be added to the discussion 
> > > below: 
> > > http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4
> > > -3-6-tp7573985p7574006.html To start a new topic under General Questions, 
> > > email [hidden email] To unsubscribe from Plone, 
> > > click here. 
> > > NAML 
> > 
> > -- 
> > View this message in context: 
> > http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4-3
> > -6-tp7573985p7574009.html Sent from the General Questions mailing list 
> > archive at Nabble.com.
> 
> 
> 
> ------------------------------------------------------------------------------ 
> _______________________________________________ 
> Plone-Users mailing list 
> [hidden email] 
> https://lists.sourceforge.net/lists/listinfo/plone-users
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4-3-6-tp7573985p7574010.html
> To start a new topic under General Questions, email ml-...@n2... 
> To unsubscribe from Plone, click here.
> NAML





--
View this message in context: http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4-3-6-tp7573985p7574011.html
Sent from the General Questions mailing list archive at Nabble.com.

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Eggert E. <egg...@be...>]

Yes, what's more: when started via 
bin/instance fg
it runs fine, no restarts.

Eggert

Am Mittwoch, 17. Juni 2015, 12:37:24 schrieb espen:
> probably a stupid suggestion, but:
> 
> Is there any chance that there is a ‘bad add on’ installed ?
> Does it start in debug mode OK ?
> 
> Espen
> 
> 17. juni 2015 kl. 16:53 skrev eehmke [via Plone] <ml-
nod...@n2...>:
> > Ok now my 4.3.6 Plone instances seem to run. I observed a different
> > problem on two servers (different machines):
> > 
> > every 3 or4 minutes the instances are restarted. In the instance.log this
> > can be found:
> > 
> > 2015-06-17T16:28:11 INFO Zope Ready to handle requests
> > ------
> > 2015-06-17T16:30:00 INFO SignalHandler Caught signal SIGTERM
> > ------
> > 2015-06-17T16:30:00 INFO Z2 Shutting down fast
> > ------
> > 2015-06-17T16:30:00 INFO ZServer closing HTTP to new connections
> > ------
> > 2015-06-17T16:30:00 INFO ZServer closing WebDAV to new connections
> > ...
> > 
> > I can't get what causes the SIGTERMs. How can I debug this?
> > 
> > Am Montag, 15. Juni 2015, 16:17:04 schrieb Steve McMahon:
> > > Just wanted to add that I've found Jens method rock solid and we're
> > > using
> > > it in the Plone 5 Unified Installer.
> > > 
> > > setutools annoyances, unfortunately, remain with builds created via the
> > > 4.3.x installer.
> > > 
> > > On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <[hidden email]>
> > > 
> > > wrote:
> > > > for me it works out fine (universally it seem) as described here:
> > > > https://community.plone.org/t/not-using-bootstrap-py-as-default/620
> > > > 
> > > > Jens
> > > > 
> > > > On 2015-06-15 13:54, Eggert Ehmke wrote:
> > > > > Hello,
> > > > > 
> > > > > I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
> > > > > 
> > > > > $ sudo -u plone_buildout bin/buildout
> > > > > 
> > > > > Traceback (most recent call last):
> > > > >   File "bin/buildout", line 17, in <module>
> > > > >   
> > > > >     import zc.buildout.buildout
> > > > >   
> > > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > > > 
> > > > > py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
> > > > > 
> > > > >     import zc.buildout.download
> > > > >   
> > > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > > > 
> > > > > py2.7.egg/zc/buildout/download.py", line 20, in <module>
> > > > > 
> > > > >     from zc.buildout.easy_install import realpath
> > > > >   
> > > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > > > 
> > > > > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
> > > > > 
> > > > >     import setuptools.archive_util
> > > > >   
> > > > >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11,
> > > > >   in
> > > > > 
> > > > > <module>
> > > > > 
> > > > >   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8,
> > > > >   in
> > > > > 
> > > > > <module>
> > > > > 
> > > > >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in
> > > > 
> > > > <module>
> > > > 
> > > > > AttributeError: 'module' object has no attribute 'packaging'
> > > > > 
> > > > > I already tried to upgrade my setuptools:
> > > > > 
> > > > > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
> > > > > Searching for setuptools
> > > > > Reading https://pypi.python.org/simple/setuptools/
> > > > > Best match: setuptools 17.1.1
> > > > > Processing setuptools-17.1.1-py2.7.egg
> > > > > setuptools 17.1.1 is already the active version in easy-install.pth
> > > > > Installing easy_install script to /usr/local/Plone/Python-2.7/bin
> > > > > Installing easy_install-2.7 script to
> > > > > /usr/local/Plone/Python-2.7/bin
> > > > > 
> > > > > Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
> > > > > packages/setuptools-17.1.1-py2.7.egg
> > > > > Processing dependencies for setuptools
> > > > > Finished processing dependencies for setuptools
> > > > > 
> > > > > This seems to work but does not make a difference. Any ideas?
> > > > > 
> > > > > Regards
> > > > > Eggert
> > > > 
> > > > ----------------------------------------------------------------------
> > > > ----
> > > > ----
> > 
> > --------------------------------------------------------------------------
> > ---- _______________________________________________
> > Plone-Users mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/plone-users
> > 
> > 
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4
> > -3-6-tp7573985p7574006.html To start a new topic under General Questions,
> > email ml-...@n2... To unsubscribe from Plone,
> > click here.
> > NAML
> 
> --
> View this message in context:
> http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4-3
> -6-tp7573985p7574009.html Sent from the General Questions mailing list
> archive at Nabble.com.

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[espen <es...@me...>]

probably a stupid suggestion, but:

Is there any chance that there is a ‘bad add on’ installed ?
Does it start in debug mode OK ?

Espen

17. juni 2015 kl. 16:53 skrev eehmke [via Plone] <ml-...@n2...>:

> Ok now my 4.3.6 Plone instances seem to run. I observed a different problem on 
> two servers (different machines): 
> 
> every 3 or4 minutes the instances are restarted. In the instance.log this can 
> be found: 
> 
> 2015-06-17T16:28:11 INFO Zope Ready to handle requests 
> ------ 
> 2015-06-17T16:30:00 INFO SignalHandler Caught signal SIGTERM 
> ------ 
> 2015-06-17T16:30:00 INFO Z2 Shutting down fast 
> ------ 
> 2015-06-17T16:30:00 INFO ZServer closing HTTP to new connections 
> ------ 
> 2015-06-17T16:30:00 INFO ZServer closing WebDAV to new connections 
> ... 
> 
> I can't get what causes the SIGTERMs. How can I debug this? 
> 
> Am Montag, 15. Juni 2015, 16:17:04 schrieb Steve McMahon:
> 
> > Just wanted to add that I've found Jens method rock solid and we're using 
> > it in the Plone 5 Unified Installer. 
> > 
> > setutools annoyances, unfortunately, remain with builds created via the 
> > 4.3.x installer. 
> > 
> > On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <[hidden email]> 
> > 
> > wrote: 
> > > for me it works out fine (universally it seem) as described here: 
> > > https://community.plone.org/t/not-using-bootstrap-py-as-default/620
> > > 
> > > Jens 
> > > 
> > > On 2015-06-15 13:54, Eggert Ehmke wrote: 
> > > > Hello, 
> > > > 
> > > > I changed my buildout to draw Plone 4.3.6. Now my buildout fails: 
> > > > 
> > > > $ sudo -u plone_buildout bin/buildout 
> > > > 
> > > > Traceback (most recent call last): 
> > > >   File "bin/buildout", line 17, in <module> 
> > > >   
> > > >     import zc.buildout.buildout 
> > > >   
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1- 
> > > > 
> > > > py2.7.egg/zc/buildout/buildout.py", line 40, in <module> 
> > > > 
> > > >     import zc.buildout.download 
> > > >   
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1- 
> > > > 
> > > > py2.7.egg/zc/buildout/download.py", line 20, in <module> 
> > > > 
> > > >     from zc.buildout.easy_install import realpath 
> > > >   
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1- 
> > > > 
> > > > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module> 
> > > > 
> > > >     import setuptools.archive_util 
> > > >   
> > > >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, in 
> > > > 
> > > > <module> 
> > > > 
> > > >   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, in 
> > > > 
> > > > <module> 
> > > > 
> > > >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in 
> > > 
> > > <module> 
> > > 
> > > > AttributeError: 'module' object has no attribute 'packaging' 
> > > > 
> > > > I already tried to upgrade my setuptools: 
> > > > 
> > > > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools 
> > > > Searching for setuptools 
> > > > Reading https://pypi.python.org/simple/setuptools/
> > > > Best match: setuptools 17.1.1 
> > > > Processing setuptools-17.1.1-py2.7.egg 
> > > > setuptools 17.1.1 is already the active version in easy-install.pth 
> > > > Installing easy_install script to /usr/local/Plone/Python-2.7/bin 
> > > > Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin 
> > > > 
> > > > Using /usr/local/Plone/Python-2.7/lib/python2.7/site- 
> > > > packages/setuptools-17.1.1-py2.7.egg 
> > > > Processing dependencies for setuptools 
> > > > Finished processing dependencies for setuptools 
> > > > 
> > > > This seems to work but does not make a difference. Any ideas? 
> > > > 
> > > > Regards 
> > > > Eggert 
> > > 
> > > -------------------------------------------------------------------------- 
> > > ---- 
> > > 
> > > 
> > > 
> > > -- 
> > > Klein & Partner KG, member of BlueDynamics Alliance 
> > > 
> > > 
> > > 
> > > -------------------------------------------------------------------------- 
> > > ---- _______________________________________________ 
> > > Plone-Users mailing list 
> > > [hidden email] 
> > > https://lists.sourceforge.net/lists/listinfo/plone-users
> 
> 
> 
> ------------------------------------------------------------------------------ 
> _______________________________________________ 
> Plone-Users mailing list 
> [hidden email] 
> https://lists.sourceforge.net/lists/listinfo/plone-users
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4-3-6-tp7573985p7574006.html
> To start a new topic under General Questions, email ml-...@n2... 
> To unsubscribe from Plone, click here.
> NAML





--
View this message in context: http://plone.293351.n2.nabble.com/Problems-whem-upgrading-from-4-3-5-to-4-3-6-tp7573985p7574009.html
Sent from the General Questions mailing list archive at Nabble.com.

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Steve M. <st...@dc...>]

One thing that will cause Plone processes under control of something like
supervisor to cycle up and down is an an inability to write out pid and or
log files. Check your permissions and ownership. Make sure the daemon can
write out it's log and pid files.

On Wed, Jun 17, 2015 at 7:52 AM, Eggert Ehmke <egg...@be...>
wrote:

> Ok now my 4.3.6 Plone instances seem to run. I observed a different
> problem on
> two servers (different machines):
>
> every 3 or4 minutes the instances are restarted. In the instance.log this
> can
> be found:
>
> 2015-06-17T16:28:11 INFO Zope Ready to handle requests
> ------
> 2015-06-17T16:30:00 INFO SignalHandler Caught signal SIGTERM
> ------
> 2015-06-17T16:30:00 INFO Z2 Shutting down fast
> ------
> 2015-06-17T16:30:00 INFO ZServer closing HTTP to new connections
> ------
> 2015-06-17T16:30:00 INFO ZServer closing WebDAV to new connections
> ...
>
> I can't get what causes the SIGTERMs. How can I debug this?
>
> Am Montag, 15. Juni 2015, 16:17:04 schrieb Steve McMahon:
> > Just wanted to add that I've found Jens method rock solid and we're using
> > it in the Plone 5 Unified Installer.
> >
> > setutools annoyances, unfortunately, remain with builds created via the
> > 4.3.x installer.
> >
> > On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <je...@bl...>
> >
> > wrote:
> > > for me it works out fine (universally it seem) as described here:
> > > https://community.plone.org/t/not-using-bootstrap-py-as-default/620
> > >
> > > Jens
> > >
> > > On 2015-06-15 13:54, Eggert Ehmke wrote:
> > > > Hello,
> > > >
> > > > I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
> > > >
> > > > $ sudo -u plone_buildout bin/buildout
> > > >
> > > > Traceback (most recent call last):
> > > >   File "bin/buildout", line 17, in <module>
> > > >
> > > >     import zc.buildout.buildout
> > > >
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > >
> > > > py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
> > > >
> > > >     import zc.buildout.download
> > > >
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > >
> > > > py2.7.egg/zc/buildout/download.py", line 20, in <module>
> > > >
> > > >     from zc.buildout.easy_install import realpath
> > > >
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > >
> > > > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
> > > >
> > > >     import setuptools.archive_util
> > > >
> > > >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11,
> in
> > > >
> > > > <module>
> > > >
> > > >   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8,
> in
> > > >
> > > > <module>
> > > >
> > > >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in
> > >
> > > <module>
> > >
> > > > AttributeError: 'module' object has no attribute 'packaging'
> > > >
> > > > I already tried to upgrade my setuptools:
> > > >
> > > > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
> > > > Searching for setuptools
> > > > Reading https://pypi.python.org/simple/setuptools/
> > > > Best match: setuptools 17.1.1
> > > > Processing setuptools-17.1.1-py2.7.egg
> > > > setuptools 17.1.1 is already the active version in easy-install.pth
> > > > Installing easy_install script to /usr/local/Plone/Python-2.7/bin
> > > > Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin
> > > >
> > > > Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
> > > > packages/setuptools-17.1.1-py2.7.egg
> > > > Processing dependencies for setuptools
> > > > Finished processing dependencies for setuptools
> > > >
> > > > This seems to work but does not make a difference. Any ideas?
> > > >
> > > > Regards
> > > > Eggert
> > >
> > >
> --------------------------------------------------------------------------
> > > ----
> > >
> > >
> > >
> > > --
> > > Klein & Partner KG, member of BlueDynamics Alliance
> > >
> > >
> > >
> > >
> --------------------------------------------------------------------------
> > > ---- _______________________________________________
> > > Plone-Users mailing list
> > > Plo...@li...
> > > https://lists.sourceforge.net/lists/listinfo/plone-users
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users
>

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Steve M. <st...@dc...>]

Any chance you're running with any resource limits in place? From the OS or
some process monitor like supervisor?

On Wed, Jun 17, 2015 at 7:52 AM, Eggert Ehmke <egg...@be...>
wrote:

> Ok now my 4.3.6 Plone instances seem to run. I observed a different
> problem on
> two servers (different machines):
>
> every 3 or4 minutes the instances are restarted. In the instance.log this
> can
> be found:
>
> 2015-06-17T16:28:11 INFO Zope Ready to handle requests
> ------
> 2015-06-17T16:30:00 INFO SignalHandler Caught signal SIGTERM
> ------
> 2015-06-17T16:30:00 INFO Z2 Shutting down fast
> ------
> 2015-06-17T16:30:00 INFO ZServer closing HTTP to new connections
> ------
> 2015-06-17T16:30:00 INFO ZServer closing WebDAV to new connections
> ...
>
> I can't get what causes the SIGTERMs. How can I debug this?
>
> Am Montag, 15. Juni 2015, 16:17:04 schrieb Steve McMahon:
> > Just wanted to add that I've found Jens method rock solid and we're using
> > it in the Plone 5 Unified Installer.
> >
> > setutools annoyances, unfortunately, remain with builds created via the
> > 4.3.x installer.
> >
> > On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <je...@bl...>
> >
> > wrote:
> > > for me it works out fine (universally it seem) as described here:
> > > https://community.plone.org/t/not-using-bootstrap-py-as-default/620
> > >
> > > Jens
> > >
> > > On 2015-06-15 13:54, Eggert Ehmke wrote:
> > > > Hello,
> > > >
> > > > I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
> > > >
> > > > $ sudo -u plone_buildout bin/buildout
> > > >
> > > > Traceback (most recent call last):
> > > >   File "bin/buildout", line 17, in <module>
> > > >
> > > >     import zc.buildout.buildout
> > > >
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > >
> > > > py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
> > > >
> > > >     import zc.buildout.download
> > > >
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > >
> > > > py2.7.egg/zc/buildout/download.py", line 20, in <module>
> > > >
> > > >     from zc.buildout.easy_install import realpath
> > > >
> > > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > >
> > > > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
> > > >
> > > >     import setuptools.archive_util
> > > >
> > > >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11,
> in
> > > >
> > > > <module>
> > > >
> > > >   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8,
> in
> > > >
> > > > <module>
> > > >
> > > >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in
> > >
> > > <module>
> > >
> > > > AttributeError: 'module' object has no attribute 'packaging'
> > > >
> > > > I already tried to upgrade my setuptools:
> > > >
> > > > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
> > > > Searching for setuptools
> > > > Reading https://pypi.python.org/simple/setuptools/
> > > > Best match: setuptools 17.1.1
> > > > Processing setuptools-17.1.1-py2.7.egg
> > > > setuptools 17.1.1 is already the active version in easy-install.pth
> > > > Installing easy_install script to /usr/local/Plone/Python-2.7/bin
> > > > Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin
> > > >
> > > > Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
> > > > packages/setuptools-17.1.1-py2.7.egg
> > > > Processing dependencies for setuptools
> > > > Finished processing dependencies for setuptools
> > > >
> > > > This seems to work but does not make a difference. Any ideas?
> > > >
> > > > Regards
> > > > Eggert
> > >
> > >
> --------------------------------------------------------------------------
> > > ----
> > >
> > >
> > >
> > > --
> > > Klein & Partner KG, member of BlueDynamics Alliance
> > >
> > >
> > >
> > >
> --------------------------------------------------------------------------
> > > ---- _______________________________________________
> > > Plone-Users mailing list
> > > Plo...@li...
> > > https://lists.sourceforge.net/lists/listinfo/plone-users
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users
>

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Eggert E. <egg...@be...>]

Ok now my 4.3.6 Plone instances seem to run. I observed a different problem on 
two servers (different machines):

every 3 or4 minutes the instances are restarted. In the instance.log this can 
be found:

2015-06-17T16:28:11 INFO Zope Ready to handle requests
------
2015-06-17T16:30:00 INFO SignalHandler Caught signal SIGTERM
------
2015-06-17T16:30:00 INFO Z2 Shutting down fast
------
2015-06-17T16:30:00 INFO ZServer closing HTTP to new connections
------
2015-06-17T16:30:00 INFO ZServer closing WebDAV to new connections
...

I can't get what causes the SIGTERMs. How can I debug this?

Am Montag, 15. Juni 2015, 16:17:04 schrieb Steve McMahon:
> Just wanted to add that I've found Jens method rock solid and we're using
> it in the Plone 5 Unified Installer.
> 
> setutools annoyances, unfortunately, remain with builds created via the
> 4.3.x installer.
> 
> On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <je...@bl...>
> 
> wrote:
> > for me it works out fine (universally it seem) as described here:
> > https://community.plone.org/t/not-using-bootstrap-py-as-default/620
> > 
> > Jens
> > 
> > On 2015-06-15 13:54, Eggert Ehmke wrote:
> > > Hello,
> > > 
> > > I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
> > > 
> > > $ sudo -u plone_buildout bin/buildout
> > > 
> > > Traceback (most recent call last):
> > >   File "bin/buildout", line 17, in <module>
> > >   
> > >     import zc.buildout.buildout
> > >   
> > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > 
> > > py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
> > > 
> > >     import zc.buildout.download
> > >   
> > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > 
> > > py2.7.egg/zc/buildout/download.py", line 20, in <module>
> > > 
> > >     from zc.buildout.easy_install import realpath
> > >   
> > >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > > 
> > > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
> > > 
> > >     import setuptools.archive_util
> > >   
> > >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, in
> > > 
> > > <module>
> > > 
> > >   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, in
> > > 
> > > <module>
> > > 
> > >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in
> > 
> > <module>
> > 
> > > AttributeError: 'module' object has no attribute 'packaging'
> > > 
> > > I already tried to upgrade my setuptools:
> > > 
> > > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
> > > Searching for setuptools
> > > Reading https://pypi.python.org/simple/setuptools/
> > > Best match: setuptools 17.1.1
> > > Processing setuptools-17.1.1-py2.7.egg
> > > setuptools 17.1.1 is already the active version in easy-install.pth
> > > Installing easy_install script to /usr/local/Plone/Python-2.7/bin
> > > Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin
> > > 
> > > Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
> > > packages/setuptools-17.1.1-py2.7.egg
> > > Processing dependencies for setuptools
> > > Finished processing dependencies for setuptools
> > > 
> > > This seems to work but does not make a difference. Any ideas?
> > > 
> > > Regards
> > > Eggert
> > 
> > --------------------------------------------------------------------------
> > ----
> > 
> > 
> > 
> > --
> > Klein & Partner KG, member of BlueDynamics Alliance
> > 
> > 
> > 
> > --------------------------------------------------------------------------
> > ---- _______________________________________________
> > Plone-Users mailing list
> > Plo...@li...
> > https://lists.sourceforge.net/lists/listinfo/plone-users

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Yuri <yu...@al...>]

So, what is the easier and clean way to deal with a 4.3 buildout and I 
want to upgrade from 4.3.5 to 4.3.6?

Il 16/06/2015 01:17, Steve McMahon ha scritto:
> Just wanted to add that I've found Jens method rock solid and we're 
> using it in the Plone 5 Unified Installer.
>
> setutools annoyances, unfortunately, remain with builds created via 
> the 4.3.x installer.
>
> On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <je...@bl... 
> <mailto:je...@bl...>> wrote:
>
>     for me it works out fine (universally it seem) as described here:
>     https://community.plone.org/t/not-using-bootstrap-py-as-default/620
>
>     Jens
>
>     On 2015-06-15 13:54, Eggert Ehmke wrote:
>     > Hello,
>     >
>     > I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
>     >
>     > $ sudo -u plone_buildout bin/buildout
>     > Traceback (most recent call last):
>     >   File "bin/buildout", line 17, in <module>
>     >     import zc.buildout.buildout
>     >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
>     > py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
>     >     import zc.buildout.download
>     >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
>     > py2.7.egg/zc/buildout/download.py", line 20, in <module>
>     >     from zc.buildout.easy_install import realpath
>     >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
>     > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
>     >     import setuptools.archive_util
>     >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line
>     11, in
>     > <module>
>     >   File "build/bdist.linux-i686/egg/setuptools/extension.py",
>     line 8, in
>     > <module>
>     >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21,
>     in <module>
>     > AttributeError: 'module' object has no attribute 'packaging'
>     >
>     > I already tried to upgrade my setuptools:
>     >
>     > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
>     > Searching for setuptools
>     > Reading https://pypi.python.org/simple/setuptools/
>     > Best match: setuptools 17.1.1
>     > Processing setuptools-17.1.1-py2.7.egg
>     > setuptools 17.1.1 is already the active version in easy-install.pth
>     > Installing easy_install script to /usr/local/Plone/Python-2.7/bin
>     > Installing easy_install-2.7 script to
>     /usr/local/Plone/Python-2.7/bin
>     >
>     > Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
>     > packages/setuptools-17.1.1-py2.7.egg
>     > Processing dependencies for setuptools
>     > Finished processing dependencies for setuptools
>     >
>     > This seems to work but does not make a difference. Any ideas?
>     >
>     > Regards
>     > Eggert
>     >
>     >
>     >
>     ------------------------------------------------------------------------------
>     >
>
>
>     --
>     Klein & Partner KG, member of BlueDynamics Alliance
>
>
>     ------------------------------------------------------------------------------
>     _______________________________________________
>     Plone-Users mailing list
>     Plo...@li...
>     <mailto:Plo...@li...>
>     https://lists.sourceforge.net/lists/listinfo/plone-users
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users

Re: [Plone-Users] Managing access to references?

[dieter <di...@ha...>]

Christoph Pingel <pin...@gm...> writes:

> Hello,
>
> I have a site running Plone 4.16 with a custom contenttype. I need certain functionality to be available for anonymous users, which I can steer with adapted workflows.
> However, I ran into a problem with references. 
>
> Traceback (innermost last):
> ...
> Module Products.PloneHotfix20130618.catalog, line 56, in getObject
> Module OFS.Traversable, line 316, in restrictedTraverse
> Module OFS.Traversable, line 251, in unrestrictedTraverse
> __traceback_info__: ([], '933200cf2aca426ca4098213a4eb85c7')
> Unauthorized: You are not allowed to access '933200cf2aca426ca4098213a4eb85c7' in this context
> ...
> I appreciate any hints to a solution.

I would approach this problem via debugging, e.g. by means of
"Products.PDBDebugMode".

First, I would find out which type of object this is, by which
"object permission" is is protected and what to do to get this
permission granted to "Anonymous".

The object permission of an object "obj" is "obj.__roles__".
However, due to access magic, "obj.__roles__" is usually immediately
resolved to the roles the permission is granted to. The get
the permission itself, some access path must be used which avoids
the access magic - often "obj.__class__.__roles__". The result
is an object defined on "C" level. Use "dir" on it to find out about
its attributes. Some of those attributes give the permission name.

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Steve M. <st...@dc...>]

Just wanted to add that I've found Jens method rock solid and we're using
it in the Plone 5 Unified Installer.

setutools annoyances, unfortunately, remain with builds created via the
4.3.x installer.

On Mon, Jun 15, 2015 at 1:39 PM, Jens W. Klein <je...@bl...>
wrote:

> for me it works out fine (universally it seem) as described here:
> https://community.plone.org/t/not-using-bootstrap-py-as-default/620
>
> Jens
>
> On 2015-06-15 13:54, Eggert Ehmke wrote:
> > Hello,
> >
> > I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
> >
> > $ sudo -u plone_buildout bin/buildout
> > Traceback (most recent call last):
> >   File "bin/buildout", line 17, in <module>
> >     import zc.buildout.buildout
> >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
> >     import zc.buildout.download
> >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > py2.7.egg/zc/buildout/download.py", line 20, in <module>
> >     from zc.buildout.easy_install import realpath
> >   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> > py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
> >     import setuptools.archive_util
> >   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, in
> > <module>
> >   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, in
> > <module>
> >   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in
> <module>
> > AttributeError: 'module' object has no attribute 'packaging'
> >
> > I already tried to upgrade my setuptools:
> >
> > $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
> > Searching for setuptools
> > Reading https://pypi.python.org/simple/setuptools/
> > Best match: setuptools 17.1.1
> > Processing setuptools-17.1.1-py2.7.egg
> > setuptools 17.1.1 is already the active version in easy-install.pth
> > Installing easy_install script to /usr/local/Plone/Python-2.7/bin
> > Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin
> >
> > Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
> > packages/setuptools-17.1.1-py2.7.egg
> > Processing dependencies for setuptools
> > Finished processing dependencies for setuptools
> >
> > This seems to work but does not make a difference. Any ideas?
> >
> > Regards
> > Eggert
> >
> >
> >
> ------------------------------------------------------------------------------
> >
>
>
> --
> Klein & Partner KG, member of BlueDynamics Alliance
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users
>

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Jens W. K. <je...@bl...>]

for me it works out fine (universally it seem) as described here:
https://community.plone.org/t/not-using-bootstrap-py-as-default/620

Jens

On 2015-06-15 13:54, Eggert Ehmke wrote:
> Hello,
> 
> I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
> 
> $ sudo -u plone_buildout bin/buildout 
> Traceback (most recent call last):
>   File "bin/buildout", line 17, in <module>
>     import zc.buildout.buildout
>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
>     import zc.buildout.download
>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> py2.7.egg/zc/buildout/download.py", line 20, in <module>
>     from zc.buildout.easy_install import realpath
>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
>     import setuptools.archive_util
>   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, in 
> <module>
>   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, in 
> <module>
>   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in <module>
> AttributeError: 'module' object has no attribute 'packaging'
> 
> I already tried to upgrade my setuptools:
> 
> $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
> Searching for setuptools
> Reading https://pypi.python.org/simple/setuptools/
> Best match: setuptools 17.1.1
> Processing setuptools-17.1.1-py2.7.egg
> setuptools 17.1.1 is already the active version in easy-install.pth
> Installing easy_install script to /usr/local/Plone/Python-2.7/bin
> Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin
> 
> Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
> packages/setuptools-17.1.1-py2.7.egg
> Processing dependencies for setuptools
> Finished processing dependencies for setuptools
> 
> This seems to work but does not make a difference. Any ideas?
> 
> Regards
> Eggert
> 
> 
> ------------------------------------------------------------------------------
> 


-- 
Klein & Partner KG, member of BlueDynamics Alliance

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Nathan V. G. <na...@va...>]

oh, the bootstrap.py command might require:

- bin/python bootstrap.py --setuptools-version=7.0 -v 2.2.5

and this is using latest bootstrap.py from
https://bootstrap.pypa.io/bootstrap-buildout.py

On Mon, Jun 15, 2015 at 8:50 AM, Nathan Van Gheem <na...@va...>
wrote:

> setuptools version issues are a pain..
>
> Sometimes, even though it tries downloading a new version, buildout won't
> pick of the new version because of the way it overrides paths.
>
> Some things to try in combination:
>
> - upgrade buildout
> - upgrade bootstrap(https://bootstrap.pypa.io/bootstrap-buildout.py) with
> version that includes the --setuptools-version option
> - upgrade setuptools
>
> A somewhat old problem proof "recipe" that we have in our ansible setup
> and should work for you goes something like this:
>
> - install virtualenv
> - bin/pip uninstall setuptools -y
> - bin/pip install setuptools==7.0
> - bin/python bootstrap.py --setuptools-version=7.0
>
> On Mon, Jun 15, 2015 at 6:54 AM, Eggert Ehmke <egg...@be...>
> wrote:
>
>> Hello,
>>
>> I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
>>
>> $ sudo -u plone_buildout bin/buildout
>> Traceback (most recent call last):
>>   File "bin/buildout", line 17, in <module>
>>     import zc.buildout.buildout
>>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
>> py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
>>     import zc.buildout.download
>>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
>> py2.7.egg/zc/buildout/download.py", line 20, in <module>
>>     from zc.buildout.easy_install import realpath
>>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
>> py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
>>     import setuptools.archive_util
>>   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, in
>> <module>
>>   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, in
>> <module>
>>   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in
>> <module>
>> AttributeError: 'module' object has no attribute 'packaging'
>>
>> I already tried to upgrade my setuptools:
>>
>> $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
>> Searching for setuptools
>> Reading https://pypi.python.org/simple/setuptools/
>> Best match: setuptools 17.1.1
>> Processing setuptools-17.1.1-py2.7.egg
>> setuptools 17.1.1 is already the active version in easy-install.pth
>> Installing easy_install script to /usr/local/Plone/Python-2.7/bin
>> Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin
>>
>> Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
>> packages/setuptools-17.1.1-py2.7.egg
>> Processing dependencies for setuptools
>> Finished processing dependencies for setuptools
>>
>> This seems to work but does not make a difference. Any ideas?
>>
>> Regards
>> Eggert
>>
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Plone-Users mailing list
>> Plo...@li...
>> https://lists.sourceforge.net/lists/listinfo/plone-users
>>
>
>
>
> --
> Nathan Van Gheem
> Solutions Architect
> Wildcard Corp
>



-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp

Re: [Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Nathan V. G. <na...@va...>]

setuptools version issues are a pain..

Sometimes, even though it tries downloading a new version, buildout won't
pick of the new version because of the way it overrides paths.

Some things to try in combination:

- upgrade buildout
- upgrade bootstrap(https://bootstrap.pypa.io/bootstrap-buildout.py) with
version that includes the --setuptools-version option
- upgrade setuptools

A somewhat old problem proof "recipe" that we have in our ansible setup and
should work for you goes something like this:

- install virtualenv
- bin/pip uninstall setuptools -y
- bin/pip install setuptools==7.0
- bin/python bootstrap.py --setuptools-version=7.0

On Mon, Jun 15, 2015 at 6:54 AM, Eggert Ehmke <egg...@be...>
wrote:

> Hello,
>
> I changed my buildout to draw Plone 4.3.6. Now my buildout fails:
>
> $ sudo -u plone_buildout bin/buildout
> Traceback (most recent call last):
>   File "bin/buildout", line 17, in <module>
>     import zc.buildout.buildout
>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
>     import zc.buildout.download
>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> py2.7.egg/zc/buildout/download.py", line 20, in <module>
>     from zc.buildout.easy_install import realpath
>   File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
> py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
>     import setuptools.archive_util
>   File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, in
> <module>
>   File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, in
> <module>
>   File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in
> <module>
> AttributeError: 'module' object has no attribute 'packaging'
>
> I already tried to upgrade my setuptools:
>
> $ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
> Searching for setuptools
> Reading https://pypi.python.org/simple/setuptools/
> Best match: setuptools 17.1.1
> Processing setuptools-17.1.1-py2.7.egg
> setuptools 17.1.1 is already the active version in easy-install.pth
> Installing easy_install script to /usr/local/Plone/Python-2.7/bin
> Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin
>
> Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
> packages/setuptools-17.1.1-py2.7.egg
> Processing dependencies for setuptools
> Finished processing dependencies for setuptools
>
> This seems to work but does not make a difference. Any ideas?
>
> Regards
> Eggert
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users
>



-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp

[Plone-Users] Problems whem upgrading from 4.3.5 to 4.3.6

[Eggert E. <egg...@be...>]

Hello,

I changed my buildout to draw Plone 4.3.6. Now my buildout fails:

$ sudo -u plone_buildout bin/buildout 
Traceback (most recent call last):
  File "bin/buildout", line 17, in <module>
    import zc.buildout.buildout
  File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
py2.7.egg/zc/buildout/buildout.py", line 40, in <module>
    import zc.buildout.download
  File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
py2.7.egg/zc/buildout/download.py", line 20, in <module>
    from zc.buildout.easy_install import realpath
  File "/usr/local/Plone/buildout-cache/eggs/zc.buildout-1.7.1-
py2.7.egg/zc/buildout/easy_install.py", line 29, in <module>
    import setuptools.archive_util
  File "build/bdist.linux-i686/egg/setuptools/__init__.py", line 11, in 
<module>
  File "build/bdist.linux-i686/egg/setuptools/extension.py", line 8, in 
<module>
  File "build/bdist.linux-i686/egg/setuptools/dist.py", line 21, in <module>
AttributeError: 'module' object has no attribute 'packaging'

I already tried to upgrade my setuptools:

$ sudo ../Python-2.7/bin/easy_install --upgrade setuptools
Searching for setuptools
Reading https://pypi.python.org/simple/setuptools/
Best match: setuptools 17.1.1
Processing setuptools-17.1.1-py2.7.egg
setuptools 17.1.1 is already the active version in easy-install.pth
Installing easy_install script to /usr/local/Plone/Python-2.7/bin
Installing easy_install-2.7 script to /usr/local/Plone/Python-2.7/bin

Using /usr/local/Plone/Python-2.7/lib/python2.7/site-
packages/setuptools-17.1.1-py2.7.egg
Processing dependencies for setuptools
Finished processing dependencies for setuptools

This seems to work but does not make a difference. Any ideas?

Regards
Eggert