Is there any way of getting Zope's startup msgs into a log? They don't appear in Z2.log. -- John
John Poltorak wrote at 2004-3-6 20:42 +0000:
Is there any way of getting Zope's startup msgs into a log?
They go there, provided Zope lives long enough to do it. Zope does not put them directly into this log file for two reasons: * when starting up, it does not know where (and how) to log for this, it must have read its configuration file * Zope allows to switch the process user after ports have been opened. When the log file is opened too early, they are owned by the wrong owner.
They don't appear in Z2.log.
"Z2.log" is (by default) the so called "access log file". Each request (!) gets a line there on termination. Problems are logged in the so called "event log file". -- Dieter
On Sun, Mar 07, 2004 at 07:59:29PM +0100, Dieter Maurer wrote:
John Poltorak wrote at 2004-3-6 20:42 +0000:
Is there any way of getting Zope's startup msgs into a log?
They go there, provided Zope lives long enough to do it.
Zope does not put them directly into this log file for two reasons:
* when starting up, it does not know where (and how) to log for this, it must have read its configuration file
I am not aware of any configuration file for 2.6.4..
Problems are logged in the so called "event log file".
Is this something which would be used by default? I can't see one anywhere?
-- Dieter
-- John
John Poltorak wrote:
I am not aware of any configuration file for 2.6.4..
upgrade to 2.7 ;-)
Problems are logged in the so called "event log file".
Is this something which would be used by default? I can't see one anywhere?
Set the EVENT_LOG_FILE variable and remove the -D from after z2.py in your start script... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Mon, Mar 08, 2004 at 11:41:07AM +0000, Chris Withers wrote:
John Poltorak wrote:
I am not aware of any configuration file for 2.6.4..
upgrade to 2.7 ;-)
Easier said than done... I'm running Zope on OS/2 because someone ported 2.6.0 a while ago. This 'porting' actually amounted to knowing that eight lines needed to be removed from z2.py. The same lines needed to be removed from 2.6.4, but 2.7.0 sounds like a whole new ball game.
Problems are logged in the so called "event log file".
Is this something which would be used by default? I can't see one anywhere?
Set the EVENT_LOG_FILE variable and remove the -D from after z2.py in your start script...
Thanks, I'll give that a try.
cheers,
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
John Poltorak wrote:
I'm running Zope on OS/2 because someone ported 2.6.0 a while ago. This 'porting' actually amounted to knowing that eight lines needed to be removed from z2.py. The same lines needed to be removed from 2.6.4, but 2.7.0 sounds like a whole new ball game.
What eight lines were they? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Tue, Mar 09, 2004 at 09:38:04AM +0000, Chris Withers wrote:
John Poltorak wrote:
I'm running Zope on OS/2 because someone ported 2.6.0 a while ago. This 'porting' actually amounted to knowing that eight lines needed to be removed from z2.py. The same lines needed to be removed from 2.6.4, but 2.7.0 sounds like a whole new ball game.
What eight lines were they?
See attached diff. It due to the OS/2 port of Python not being able to handle sticky bits.
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
John Poltorak wrote:
I'm running Zope on OS/2 because someone ported 2.6.0 a while ago. This 'porting' actually amounted to knowing that eight lines needed to be removed from z2.py. The same lines needed to be removed from 2.6.4, but 2.7.0 sounds like a whole new ball game.
What eight lines were they?
See attached diff.
It due to the OS/2 port of Python not being able to handle sticky bits.
Ah, right. What happens if you try 2.7.0? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Wed, Mar 10, 2004 at 02:11:06PM +0000, Chris Withers wrote:
John Poltorak wrote:
I'm running Zope on OS/2 because someone ported 2.6.0 a while ago. This 'porting' actually amounted to knowing that eight lines needed to be removed from z2.py. The same lines needed to be removed from 2.6.4, but 2.7.0 sounds like a whole new ball game.
What eight lines were they?
See attached diff.
It due to the OS/2 port of Python not being able to handle sticky bits.
Ah, right. What happens if you try 2.7.0?
Configure _appears_ to work OK, but something fails right at the end. Haven't figured out what just yet. This is what happens as it fails:- running build running build_scripts creating U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/mkzeoinstance.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/mkzopeinstance.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/check_catalog.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying utilities/load_site.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/requestprofiler.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/zpasswd.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/testrunner.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/copyzopeskel.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/compilezpy.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/decompilezpy.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts ECHO is on. Zope built. Next, do "\make install\" \(or "\make instance\" to run a Zope instance directly from the build directory\). ECHO is on. "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" \ build --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-temp" running build running build_py running build_ext running build running build_py running build running build_scripts "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" install \ --home="/opt/Zope-2.7" --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-temp" invalid command name '' make: *** [install] Error 1 Maybe it's a shell problem, I don't know... The invalid command name has me puzzled.
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
John Poltorak wrote:
Configure _appears_ to work OK, but something fails right at the end. Haven't figured out what just yet.
This is what happens as it fails:-
running build running build_scripts creating U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/mkzeoinstance.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/mkzopeinstance.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/check_catalog.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying utilities/load_site.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/requestprofiler.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/zpasswd.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/testrunner.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/copyzopeskel.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/compilezpy.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts copying and adjusting utilities/decompilezpy.py -> U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts ECHO is on. Zope built. Next, do "\make install\" \(or "\make instance\" to run a Zope instance directly from the build directory\). ECHO is on. "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" \ build --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-temp" running build running build_py running build_ext running build running build_py running build running build_scripts "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" install \ --home="/opt/Zope-2.7" --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-temp" invalid command name '' make: *** [install] Error 1
Maybe it's a shell problem, I don't know... The invalid command name has me puzzled.
Is it possible that there is a command which consists of only a make variable $(COMMAND) and that variable is empty in this case? Troy
On Wed, Mar 10, 2004 at 08:35:17AM -0600, Troy Farrell wrote:
John Poltorak wrote:
Configure _appears_ to work OK, but something fails right at the end. Haven't figured out what just yet.
This is what happens as it fails:-
ECHO is on. "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" \ build --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-temp" running build running build_py running build_ext running build running build_py running build running build_scripts "U:\USR\BIN\PYTHON.EXE" "U:/unixos2/workdir/Zope-2.7.0/setup.py" install \ --home="/opt/Zope-2.7" --build-base="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3" --build-lib="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-lib" --build-scripts="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-scripts" --build-temp="U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3/build-temp" invalid command name '' make: *** [install] Error 1
Maybe it's a shell problem, I don't know... The invalid command name has me puzzled.
Is it possible that there is a command which consists of only a make variable $(COMMAND) and that variable is empty in this case?
Maybe you can see something untoward in this Makefile that gets created:- # Zope2 build and install Makefile. # We do as much as possible in Python in order to avoid needing to # learn autoconf or some other awful thing. ;-) NAME=Zope MAJOR_VERSION=2.7 MINOR_VERSION=0 RELEASE_TAG=b3 PACKAGE_NAME=${NAME}-${MAJOR_VERSION}.${MINOR_VERSION}-${RELEASE_TAG} PYTHON="U:\USR\BIN\PYTHON.EXE" TMPDIR=/tmp PREFIX=/opt/Zope-2.7 BASE_DIR=U:/unixos2/workdir/Zope-2.7.0 BUILD_BASE=U:/unixos2/workdir/Zope-2.7.0/build-base/python-2.3 DISTUTILS_OPTS= INSTALL_FLAGS= TESTOPTS=-v BUILD_FLAGS=--build-base="${BUILD_BASE}" \ --build-lib="${BUILD_BASE}/build-lib" \ --build-scripts="${BUILD_BASE}/build-scripts"\ --build-temp="${BUILD_BASE}/build-temp" RM=rm -f RMRF=rm -rf FIND=find XARGS=xargs CD=cd LN=ln -sfn CP=cp TAR=tar MKDIR=mkdir -p .PHONY : clean install uninstall instance untestinst testinst build unbuild .PHONY : default # default: The default step (invoked when make is called without a target) default: build @echo @echo Zope built. Next, do \'make install\' \(or \'make instance\' @echo to run a Zope instance directly from the build directory\). @echo # build: Do whatever 'setup.py build' implies build: ${PYTHON} "${BASE_DIR}/setup.py" \ ${DISTUTILS_OPTS} build ${BUILD_FLAGS} # unbuild: Remove the build directory (undo the make build step) unbuild: ${RMRF} ${BUILD_BASE} # install: Install a software home. # # Note: Unless ${PREFIX}/bin already has a 'python', symlink the # "canonical" Python for this Zope into it. install: build ${PYTHON} "${BASE_DIR}/setup.py" ${DISTUTILS_OPTS} install \ --home="${PREFIX}" ${BUILD_FLAGS} ${INSTALL_FLAGS} [ -f ${PREFIX}/bin/python ] || ${LN} ${PYTHON} ${PREFIX}/bin/python @echo @echo Zope binaries installed successfully. @echo Now run \'${PREFIX}/bin/mkzopeinstance.py\'
Troy
-- John
John Poltorak wrote:
NAME=Zope MAJOR_VERSION=2.7 MINOR_VERSION=0 RELEASE_TAG=b3
Looks like you only have Beta 3, have you tried the final source release?
PYTHON="U:\USR\BIN\PYTHON.EXE"
Oh boy, that's gotta be OS/2 specific ;-)
RM=rm -f RMRF=rm -rf FIND=find XARGS=xargs CD=cd LN=ln -sfn CP=cp TAR=tar MKDIR=mkdir -p
Do all of the above utilities exist and work?
# build: Do whatever 'setup.py build' implies build: ${PYTHON} "${BASE_DIR}/setup.py" \ ${DISTUTILS_OPTS} build ${BUILD_FLAGS}
I'd guessing ${PYTHON} is causing issues here. Does U:\USR\BIN\PYTHON.EXE work at a command prompt? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Thu, Mar 11, 2004 at 11:19:20AM +0000, Chris Withers wrote:
John Poltorak wrote:
NAME=Zope MAJOR_VERSION=2.7 MINOR_VERSION=0 RELEASE_TAG=b3
Looks like you only have Beta 3, have you tried the final source release?
AFAIK I am using:- http://zope.org/Products/Zope/2.7.0/Zope-2.7.0.tgz Where, in the archive, is the realease tag information held?
PYTHON="U:\USR\BIN\PYTHON.EXE"
Oh boy, that's gotta be OS/2 specific ;-)
That's what comes up in my makefile when I build using '--with-python=/usr/bin/python' It _appears_ to work... AFAICT it's 'make install' which has failed. How do I tell whether make has actually worked correctly?
RM=rm -f RMRF=rm -rf FIND=find XARGS=xargs CD=cd LN=ln -sfn CP=cp TAR=tar MKDIR=mkdir -p
Do all of the above utilities exist and work?
I don't currently have FIND or XARGS. I'll grab them and see if it makes a difference.
# build: Do whatever 'setup.py build' implies build: ${PYTHON} "${BASE_DIR}/setup.py" \ ${DISTUTILS_OPTS} build ${BUILD_FLAGS}
I'd guessing ${PYTHON} is causing issues here. Does U:\USR\BIN\PYTHON.EXE work at a command prompt?
Well it produces a
command prompt. I'm using v2.3.3 and it seems to run Zope 2.6.4 without any problems.
cheers,
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
John Poltorak wrote:
On Thu, Mar 11, 2004 at 11:19:20AM +0000, Chris Withers wrote:
John Poltorak wrote:
NAME=Zope MAJOR_VERSION=2.7 MINOR_VERSION=0 RELEASE_TAG=b3
Looks like you only have Beta 3, have you tried the final source release?
AFAIK I am using:-
http://zope.org/Products/Zope/2.7.0/Zope-2.7.0.tgz
Where, in the archive, is the realease tag information held?
If you're sure, then I'd paste the above in the collector as someone obviously left an incorrect version tag lying around.
AFAICT it's 'make install' which has failed.
How do I tell whether make has actually worked correctly?
You don't get any errors when you do a make install ;-)
Do all of the above utilities exist and work?
I don't currently have FIND or XARGS. I'll grab them and see if it makes a difference.
Cool. Do let us know :-)
I'd guessing ${PYTHON} is causing issues here. Does U:\USR\BIN\PYTHON.EXE work at a command prompt?
Well it produces a command prompt.
A command prompt or a Python prompt?
I'm using v2.3.3 and it seems to run Zope 2.6.4 without any problems.
...although not officially recommended ;-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
John Poltorak wrote at 2004-3-7 19:42 +0000:
...
Zope does not put them directly into this log file for two reasons:
* when starting up, it does not know where (and how) to log for this, it must have read its configuration file
I am not aware of any configuration file for 2.6.4..
You see how essential it is to state the Zope version when you report problems. Zope 2.6 does not have a configuration file; this start with Zope 2.7.
Problems are logged in the so called "event log file".
Is this something which would be used by default? I can't see one anywhere?
It is used by default -- from Zope 2.7 on. For Zope 2.6, read "doc/LOGGING.txt". -- Dieter
participants (4)
-
Chris Withers -
Dieter Maurer -
John Poltorak -
Troy Farrell