Can someone running Zope 2.7.0 post what is shown under the control panel? I've just managed to get it running but it is shown as an unreleased version:- The Control Panel provides access to system information and management functions such as database and product management. Zope Version (unreleased version, python 2.3.3, os2emx) Python Version 2.3.3 (#0, Dec 21 2003, 23:43:28) [EMX GCC 2.8.1] System Platform os2emx SOFTWARE_HOME /usr/local/python/Lib/python ZOPE_HOME /usr/local/python INSTANCE_HOME /zope CLIENT_HOME /zope/var Network Services ZServer.HTTPServer.zhttp_server (Port: 8080) ZServer.FTPServer.FTPServer (Port: 8021) Process Id 7808 (3) Running For 12 hours 19 min 3 sec It appears to have been installed in the wrong place, at least I wouldn't have expected it to get installed under /usr/local/python. Also, there is no Restart button next to the Shutdown button. Is this normal? -- John
John Poltorak wrote:
Can someone running Zope 2.7.0 post what is shown under the control panel?
I've just managed to get it running but it is shown as an unreleased version:-
The Control Panel provides access to system information and management functions such as database and product management.
Zope Version (unreleased version, python 2.3.3, os2emx)
Python Version 2.3.3 (#0, Dec 21 2003, 23:43:28) [EMX GCC 2.8.1]
System Platform os2emx
SOFTWARE_HOME /usr/local/python/Lib/python
ZOPE_HOME /usr/local/python
INSTANCE_HOME /zope
CLIENT_HOME /zope/var
Network Services ZServer.HTTPServer.zhttp_server (Port: 8080) ZServer.FTPServer.FTPServer (Port: 8021)
Process Id 7808 (3)
Running For 12 hours 19 min 3 sec
It appears to have been installed in the wrong place, at least I wouldn't have expected it to get installed under /usr/local/python.
Also, there is no Restart button next to the Shutdown button. Is this normal?
reed the install documentation in the source tree, about how to define the prefix of zope with 2.7 the normal configure make install steps have to be done so in order to define the installation location use: ./configure --prefix=/path/to/soft/home the "unreleased version" problem is a problem of the source version, as far as i know "version.txt" is missing
On Tue, Mar 16, 2004 at 11:32:17AM +0100, Bernd Dorn wrote:
John Poltorak wrote:
Can someone running Zope 2.7.0 post what is shown under the control panel?
I've just managed to get it running but it is shown as an unreleased version:-
The Control Panel provides access to system information and management functions such as database and product management.
Zope Version (unreleased version, python 2.3.3, os2emx)
reed the install documentation in the source tree, about how to define the prefix of zope
Yes, I have used prefix but builds both with and without it seem to get built the same way...
with 2.7 the normal configure make install steps have to be done
so in order to define the installation location use: ./configure --prefix=/path/to/soft/home
It doesn't work here. Can you show what you have in the Control Panel screen?
the "unreleased version" problem is a problem of the source version, as far as i know "version.txt" is missing
Is that in the distributed version of Zope 2.7.0 ? -- John
John Poltorak wrote:
On Tue, Mar 16, 2004 at 11:32:17AM +0100, Bernd Dorn wrote:
John Poltorak wrote:
Can someone running Zope 2.7.0 post what is shown under the control panel?
I've just managed to get it running but it is shown as an unreleased version:-
The Control Panel provides access to system information and management functions such as database and product management.
Zope Version (unreleased version, python 2.3.3, os2emx)
reed the install documentation in the source tree, about how to define the prefix of zope
Yes, I have used prefix but builds both with and without it seem to get built the same way...
with 2.7 the normal configure make install steps have to be done
so in order to define the installation location use: ./configure --prefix=/path/to/soft/home
It doesn't work here.
Can you show what you have in the Control Panel screen?
the "unreleased version" problem is a problem of the source version, as far as i know "version.txt" is missing
Is that in the distributed version of Zope 2.7.0 ?
my cp output:: The Control Panel provides access to system information and management functions such as database and product management. Zope Version (unreleased version, python 2.3.3, linux2) Python Version 2.3.3 (#1, Jan 29 2004, 07:54:24) [GCC 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)] System Platform linux2 SOFTWARE_HOME /opt/zope/270/lib/python ZOPE_HOME /opt/zope/270 INSTANCE_HOME /home/bd/zopes/first CLIENT_HOME /home/bd/zopes/first/var Network Services ZServer.HTTPServer.zhttp_server (Port: 8080) Process Id 7238 (32771) Running For 3 hours 11 min 37 sec :: dunno how to install without configure, sorry
Hi all I am looking for a Corporate Actions Feed (similar to the RSS News feed) for financial services which can be integrated with a Zope CMS. Does someone know about a proven / known product in the market for Corporate Actions feed? Any specs or information on the lines will be helpful! Regards Darshan.
The install procedure for Zope 2.7.0 when building from source does not seem to install the 'version.txt' file. I couldn't find any predefined install target to do it, so I just copied the file manually: cp /usr/local/src/zope/Zope-2.7.0/lib/python/version.txt /usr/local/Zope-2.7.0/lib/python/ (Of course, the front of those file paths depends on my particular configuration -- adjust accordingly). After restarting ZServer the correct Zope version number appears in the Control Panel. -- Fred Yankowski fred@ontosys.com tel: +1.630.879.1312 OntoSys, Inc PGP keyID: 7B449345 fax: +1.630.879.1370 www.ontosys.com 38W242 Deerpath Rd, Batavia, IL 60510-9461, USA
On Tue, Mar 16, 2004 at 08:43:43AM -0600, Fred Yankowski wrote:
The install procedure for Zope 2.7.0 when building from source does not seem to install the 'version.txt' file. I couldn't find any predefined install target to do it, so I just copied the file manually:
cp /usr/local/src/zope/Zope-2.7.0/lib/python/version.txt /usr/local/Zope-2.7.0/lib/python/
(Of course, the front of those file paths depends on my particular configuration -- adjust accordingly).
After restarting ZServer the correct Zope version number appears in the Control Panel.
Thanks, it shows the correct version now. A more important thing which is missing though, is a Restart button... Do you have one?
-- Fred Yankowski fred@ontosys.com tel: +1.630.879.1312 OntoSys, Inc PGP keyID: 7B449345 fax: +1.630.879.1370 www.ontosys.com 38W242 Deerpath Rd, Batavia, IL 60510-9461, USA
-- John
John Poltorak wrote:
Thanks, it shows the correct version now.
A more important thing which is missing though, is a Restart button... Do you have one?
You won't have one of those unless Zope is running as a daemon. Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Wed, Mar 17, 2004 at 09:23:47AM +0000, Chris Withers wrote:
John Poltorak wrote:
Thanks, it shows the correct version now.
A more important thing which is missing though, is a Restart button... Do you have one?
You won't have one of those unless Zope is running as a daemon.
Is this something new in v2.7.0 ? I'm not aware of a flag for selecting daemon mode. Is that something which goes in zope.conf? Can't see anything in the docs - although there are so many docs, that I'm probably looking in the wrong place...
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
One answer to the "so many docs" problem regarding Restart button: Google (get lucky) for: zope "restart button" daemon At 01:59 PM 3/17/2004 +0000, John Poltorak wrote:
A more important thing which is missing though, is a Restart button... Do you have one?
You won't have one of those unless Zope is running as a daemon.
Is this something new in v2.7.0 ?
I'm not aware of a flag for selecting daemon mode. Is that something which goes in zope.conf?
Can't see anything in the docs - although there are so many docs, that I'm probably looking in the wrong place...
On Tue, Mar 16, 2004 at 02:54:44PM +0000, John Poltorak wrote:
A more important thing which is missing though, is a Restart button... Do you have one?
Not when I started zope with bin/runzope. It appears when I start zope with bin/zopectl. As someone else said, the latter starts zope as a daemon process, which I think adds a new top-level process that handles the restart event. Zope 2.7.0 has some significant differences from the 2.6.x versions -- justifying the new second-level version number. This is most apparent to me in the top-level scripts and configuration files. The new setup is good, once you get used to it. The ability to use the zopectl and zeoctl scripts directly in /etc/init.d/ is handy (although I'm a little concerned about just where the processes now change EUID away from root -- it's not as obvious as before). -- Fred Yankowski fred@ontosys.com tel: +1.630.879.1312 OntoSys, Inc PGP keyID: 7B449345 fax: +1.630.879.1370 www.ontosys.com 38W242 Deerpath Rd, Batavia, IL 60510-9461, USA
On Wed, Mar 17, 2004 at 01:23:03PM -0600, Fred Yankowski wrote:
On Tue, Mar 16, 2004 at 02:54:44PM +0000, John Poltorak wrote:
A more important thing which is missing though, is a Restart button... Do you have one?
Not when I started zope with bin/runzope. It appears when I start zope with bin/zopectl.
Unfortunately or me zopectl doesn't work. I just tried it anf got:- Traceback (most recent call last): File "/opt/zope/lib/python/Zope/Startup/zopectl.py", line 207, in ? main() File "/opt/zope/lib/python/Zope/Startup/zopectl.py", line 188, in main c = ZopeCmd(options) File "/opt/zope/lib/python/zdaemon/zdctl.py", line 117, in __init__ self.get_status() File "/opt/zope/lib/python/zdaemon/zdctl.py", line 158, in get_status resp = self.send_action("status") File "/opt/zope/lib/python/zdaemon/zdctl.py", line 138, in send_action sock = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM) AttributeError: 'module' object has no attribute 'AF_UNIX' I haven't yet worked out what this means - it may well be an underlying problem with Python. I'm not running under Unix so don't expect anyone on this list to be able to suggest what might be wrong...
-- Fred Yankowski fred@ontosys.com tel: +1.630.879.1312 OntoSys, Inc PGP keyID: 7B449345 fax: +1.630.879.1370 www.ontosys.com 38W242 Deerpath Rd, Batavia, IL 60510-9461, USA
-- John
On Wed, Mar 17, 2004 at 07:29:54PM +0000, John Poltorak wrote:
I haven't yet worked out what this means - it may well be an underlying problem with Python. I'm not running under Unix so don't expect anyone on this list to be able to suggest what might be wrong...
I suspect that your problem is exactly that zopectl only runs on *nix systems. I no longer run Zope on Win32, so I'm no help there. I've heard that the latest zope versions come with installers that set up zope as a service, so that you can do 'net start zope' or something like that. There should be plenty of people on the list who can steer you the right way. <cue>those people</cue> -- Fred Yankowski fred@ontosys.com tel: +1.630.879.1312 OntoSys, Inc PGP keyID: 7B449345 fax: +1.630.879.1370 www.ontosys.com 38W242 Deerpath Rd, Batavia, IL 60510-9461, USA
On Wed, Mar 17, 2004 at 01:41:09PM -0600, Fred Yankowski wrote:
On Wed, Mar 17, 2004 at 07:29:54PM +0000, John Poltorak wrote:
I haven't yet worked out what this means - it may well be an underlying problem with Python. I'm not running under Unix so don't expect anyone on this list to be able to suggest what might be wrong...
I suspect that your problem is exactly that zopectl only runs on *nix systems. I no longer run Zope on Win32, so I'm no help there. I've heard that the latest zope versions come with installers that set up zope as a service, so that you can do 'net start zope' or something like that. There should be plenty of people on the list who can steer you the right way. <cue>those people</cue>
I don't use Windows either so I don't expect anyone on the list to know how to fix the problem in this case.
-- Fred Yankowski fred@ontosys.com tel: +1.630.879.1312 OntoSys, Inc PGP keyID: 7B449345 fax: +1.630.879.1370 www.ontosys.com 38W242 Deerpath Rd, Batavia, IL 60510-9461, USA
-- John
Fred Yankowski wrote:
I suspect that your problem is exactly that zopectl only runs on *nix systems. I no longer run Zope on Win32, so I'm no help there. I've heard that the latest zope versions come with installers that set up zope as a service, so that you can do 'net start zope' or something like that. There should be plenty of people on the list who can steer you the right way. <cue>those people</cue>
yes, there is a way to run zope as a service. Check out the $INSTANCE_HOME/bin/zopeservice.py script. It installs/uninstalls zope instances as a service. joseph
On Wed, 2004-03-17 at 14:23, Fred Yankowski wrote:
Zope 2.7.0 has some significant differences from the 2.6.x versions -- justifying the new second-level version number. This is most apparent to me in the top-level scripts and configuration files. The new setup is good, once you get used to it. The ability to use the zopectl and zeoctl scripts directly in /etc/init.d/ is handy (although I'm a little concerned about just where the processes now change EUID away from root -- it's not as obvious as before).
It's in lib/python/Zope/Startup/__init__.py, FWIW. - C
Chris McDonough wrote:
It's in lib/python/Zope/Startup/__init__.py, FWIW.
Is Toby Dickenson happy about the logging yet? (always a good sign of whether it's robust and secure ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Monday 22 March 2004 15:47, Chris Withers wrote:
Chris McDonough wrote:
It's in lib/python/Zope/Startup/__init__.py, FWIW.
Is Toby Dickenson happy about the logging yet? (always a good sign of whether it's robust and secure ;-)
I trust the security of syslog for Zope's event logging and squid for access logging, so Im happy that the relevant secure logging facilities are available somewhere for those who believe they need them. Zope's own logs are useful in development, but I wouldnt want to have to rely on them in a hostile production environment. -- Toby Dickenson
Toby Dickenson wrote:
Zope's own logs are useful in development, but I wouldnt want to have to rely on them in a hostile production environment.
How come? (links to past messages would be fine ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Tuesday 23 March 2004 08:44, Chris Withers wrote:
Toby Dickenson wrote:
Zope's own logs are useful in development, but I wouldnt want to have to rely on them in a hostile production environment.
How come?
Suppose your Zope server is compromised. Your event log and access log are critical for detecting the compromise, and then diagnosing the flaw that led to the compromise. Currently the Zope server process has privileges to rewrite all of its log files, so it is possible for anyone who has broken into a Zope server to remove all traces of their presence. Apache does this right. Its worker processes run under the 'httpd' uid, but its log files are accessible only by root. When the worker process is started it is given a pipe filedescriptor, and a seperate process running as root copies log entries out of the pipe and into the log file. A compromised worker process can generate fake log entries, but it cant remove old ones. -- Toby Dickenson
Toby Dickenson wrote:
Suppose your Zope server is compromised. Your event log and access log are critical for detecting the compromise, and then diagnosing the flaw that led to the compromise. Currently the Zope server process has privileges to rewrite all of its log files, so it is possible for anyone who has broken into a Zope server to remove all traces of their presence.
Apache does this right. Its worker processes run under the 'httpd' uid, but its log files are accessible only by root. When the worker process is started it is given a pipe filedescriptor, and a seperate process running as root copies log entries out of the pipe and into the log file. A compromised worker process can generate fake log entries, but it cant remove old ones.
Uh... or you could just write the logs to a pipe and have a non-privileged reader process write them to disk. Like, oh, daemontools. -- Jamie Heilman http://audible.transient.net/~jamie/
Chris Withers wrote:
Toby Dickenson wrote:
Zope's own logs are useful in development, but I wouldnt want to have to rely on them in a hostile production environment.
How come?
(links to past messages would be fine ;-)
Somewhere in that mess of code ZServer url decodes the entire first line of a request and then sends it to the logger, or maybe only part of it.... at any rate, enough that you basically can't trust anything in the access logs. Then there are the issues of granularity (common log format really sucks for that), compounded with the latency and multithreading issues that yield out of order entries, which Dieter can tell you about. Some of this is easy to fix, some of it isn't, but its all easy to ignore if you've got reliable logs from a good gateway server. -- Jamie Heilman http://audible.transient.net/~jamie/
participants (10)
-
Bernd Dorn -
Chris McDonough -
Chris Withers -
Darshan Preet Singh Manku -
Fred Yankowski -
Jamie Heilman -
John Poltorak -
Joseph Kocherhans -
Paul Howell -
Toby Dickenson