Hello everyone, I just got the new DA for Sybase 11.9.2 and installed it without any errors (I even imported the module into python successfully). Now when I try to run ./start, I hear some activity from the hard drive but the prompt returns and nothing is started. Anytime I delete the file sy_occ.so from the product directory, Zope starts just fine. This is what I have: SuSE Linux 6.2 Python 1.5.2 Zope 2.01 Sybase DAv2 Any help will be greatly appreciated.
Nothing at all is sent to the console when you use ./start? This is odd. Are you using the source release of Zope or was it a binary install? Gerard Rowe wrote:
Hello everyone, I just got the new DA for Sybase 11.9.2 and installed it without any errors (I even imported the module into python successfully).
Now when I try to run ./start, I hear some activity from the hard drive but the prompt returns and nothing is started. Anytime I delete the file sy_occ.so from the product directory, Zope starts just fine.
This is what I have:
SuSE Linux 6.2 Python 1.5.2 Zope 2.01 Sybase DAv2
Any help will be greatly appreciated.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
Nothing is sent back to the console, I just get back the command prompt. Yes I am using the source release and that compiled and ran without a problem. Like I said, the funny thing is whenever I delete the sy_occ.so from the SybaseDAv2 products directory Zope starts up just fine. I don't know if it's because I run Zope as a diiferent user than Sybase ( don't know much about Zope and Sybase but trying to learn). On Mon, 29 Nov 1999, Chris McDonough wrote:
Nothing at all is sent to the console when you use ./start? This is odd.
Are you using the source release of Zope or was it a binary install?
Gerard Rowe wrote:
Hello everyone, I just got the new DA for Sybase 11.9.2 and installed it without any errors (I even imported the module into python successfully).
Now when I try to run ./start, I hear some activity from the hard drive but the prompt returns and nothing is started. Anytime I delete the file sy_occ.so from the product directory, Zope starts just fine.
This is what I have:
SuSE Linux 6.2 Python 1.5.2 Zope 2.01 Sybase DAv2
Any help will be greatly appreciated.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
Try to start Zope without the start batch file by issuing the command: python z2.py -D when in the top-level Zope directory... See what kinds of messages you get back... Gerard Rowe wrote:
Nothing is sent back to the console, I just get back the command prompt.
Yes I am using the source release and that compiled and ran without a problem. Like I said, the funny thing is whenever I delete the sy_occ.so from the SybaseDAv2 products directory Zope starts up just fine.
I don't know if it's because I run Zope as a diiferent user than Sybase ( don't know much about Zope and Sybase but trying to learn).
On Mon, 29 Nov 1999, Chris McDonough wrote:
Nothing at all is sent to the console when you use ./start? This is odd.
Are you using the source release of Zope or was it a binary install?
Gerard Rowe wrote:
Hello everyone, I just got the new DA for Sybase 11.9.2 and installed it without any errors (I even imported the module into python successfully).
Now when I try to run ./start, I hear some activity from the hard drive but the prompt returns and nothing is started. Anytime I delete the file sy_occ.so from the product directory, Zope starts just fine.
This is what I have:
SuSE Linux 6.2 Python 1.5.2 Zope 2.01 Sybase DAv2
Any help will be greatly appreciated.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
Still not working, I just get back the command prompt with no messages whatsoever. On Mon, 29 Nov 1999, Chris McDonough wrote:
Try to start Zope without the start batch file by issuing the command:
python z2.py -D
when in the top-level Zope directory...
See what kinds of messages you get back...
Gerard Rowe wrote:
Nothing is sent back to the console, I just get back the command prompt.
Yes I am using the source release and that compiled and ran without a problem. Like I said, the funny thing is whenever I delete the sy_occ.so from the SybaseDAv2 products directory Zope starts up just fine.
I don't know if it's because I run Zope as a diiferent user than Sybase ( don't know much about Zope and Sybase but trying to learn).
On Mon, 29 Nov 1999, Chris McDonough wrote:
Nothing at all is sent to the console when you use ./start? This is odd.
Are you using the source release of Zope or was it a binary install?
Gerard Rowe wrote:
Hello everyone, I just got the new DA for Sybase 11.9.2 and installed it without any errors (I even imported the module into python successfully).
Now when I try to run ./start, I hear some activity from the hard drive but the prompt returns and nothing is started. Anytime I delete the file sy_occ.so from the product directory, Zope starts just fine.
This is what I have:
SuSE Linux 6.2 Python 1.5.2 Zope 2.01 Sybase DAv2
Any help will be greatly appreciated.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
Well, lets start from the very beginning then... type "python", hit enter, do you get an interpreter shell? Gerard Rowe wrote:
Still not working, I just get back the command prompt with no messages whatsoever.
On Mon, 29 Nov 1999, Chris McDonough wrote:
Try to start Zope without the start batch file by issuing the command:
python z2.py -D
when in the top-level Zope directory...
See what kinds of messages you get back...
Gerard Rowe wrote:
Nothing is sent back to the console, I just get back the command prompt.
<snip> -- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors. What next? On Mon, 29 Nov 1999, Chris McDonough wrote:
Well, lets start from the very beginning then... type "python", hit enter, do you get an interpreter shell?
Gerard Rowe wrote:
Still not working, I just get back the command prompt with no messages whatsoever.
On Mon, 29 Nov 1999, Chris McDonough wrote:
Try to start Zope without the start batch file by issuing the command:
python z2.py -D
when in the top-level Zope directory...
See what kinds of messages you get back...
Gerard Rowe wrote:
Nothing is sent back to the console, I just get back the command prompt.
<snip> -- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Hmmm... Assuming your copy of z2.py hasn't been altered from the distributed module, calling the command "python z2.py -D" from the command line should always return *something*. Try this from the python shell: import os, sys, getopt, string Any errors? Gerard Rowe wrote:
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors.
What next?
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
I am able to import all the listed modules sucessfully. On Mon, 29 Nov 1999, Chris McDonough wrote:
Hmmm...
Assuming your copy of z2.py hasn't been altered from the distributed module, calling the command "python z2.py -D" from the command line should always return *something*.
Try this from the python shell:
import os, sys, getopt, string
Any errors?
Gerard Rowe wrote:
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors.
What next?
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
Gerard Rowe wrote:
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors.
Check the zope user's environment. Usually done by actually logging in at the console, or doing an 'su -' to become root (or su - <zopeuser> if zope is not run by root). Does zope start as root and switch user? It _may_ be an issue of it being set in your terminal (as root), but when zope switches, the zopeuser doesn't have the path set up (in the darkness a gunshot is heard ;-) If you are getting the core file, you can run strings on it to see all sorts of stuff, among which is the environment. You could also run: $ strace ./start to see what system calls are being made. If you want, I could look at the core file if you send it my way (off-list of course). Are you getting one? (Guess I should have asked earlier...) Since your ld.so.conf is configured properly, did you run ldconfig? Just a few more things to try ... Bill -- "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." -- Carl Sagan
I run Zope under my regular login and Sybase under the user 'sybase'. With respect to Zope, I have the SYBASE environment variable set and I have the LD_LIBRARY_PATH variable set (I even added and exported them in the start script). Everything seems to be in order on the Zope side of things. My main concern is that of the Sybase setup. I'm new to Sybase so I don't know if everything is set up correcty but the server is running and I can connect to it using 'isql -Usa -P<password> -Ssybase' and issue queries. I am at a complete loss as to what is going wrong Bye the way, I tried strace but have no idea what to look for. The only thing that I can make sense of is that the 'open' system call is used a number of times and returns the "No such file or directory" message. On Mon, 29 Nov 1999, Bill Anderson wrote:
Gerard Rowe wrote:
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors.
Check the zope user's environment. Usually done by actually logging in at the console, or doing an 'su -' to become root (or su - <zopeuser> if zope is not run by root). Does zope start as root and switch user? It _may_ be an issue of it being set in your terminal (as root), but when zope switches, the zopeuser doesn't have the path set up (in the darkness a gunshot is heard ;-)
If you are getting the core file, you can run strings on it to see all sorts of stuff, among which is the environment. You could also run: $ strace ./start to see what system calls are being made. If you want, I could look at the core file if you send it my way (off-list of course).
Are you getting one? (Guess I should have asked earlier...)
Since your ld.so.conf is configured properly, did you run ldconfig?
Just a few more things to try ...
Bill
-- "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." -- Carl Sagan
The environment seems ok and I'm not getting a core dump file. Not quite sure if my system disabled the generation of core files. What's that command again? On Mon, 29 Nov 1999, Bill Anderson wrote:
Gerard Rowe wrote:
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors.
Check the zope user's environment. Usually done by actually logging in at the console, or doing an 'su -' to become root (or su - <zopeuser> if zope is not run by root). Does zope start as root and switch user? It _may_ be an issue of it being set in your terminal (as root), but when zope switches, the zopeuser doesn't have the path set up (in the darkness a gunshot is heard ;-)
If you are getting the core file, you can run strings on it to see all sorts of stuff, among which is the environment. You could also run: $ strace ./start to see what system calls are being made. If you want, I could look at the core file if you send it my way (off-list of course).
Are you getting one? (Guess I should have asked earlier...)
Since your ld.so.conf is configured properly, did you run ldconfig?
Just a few more things to try ...
Bill
-- "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." -- Carl Sagan
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Gerard Rowe wrote:
The environment seems ok and I'm not getting a core dump file.
Not quite sure if my system disabled the generation of core files. What's that command again?
quick check : # ulimit -c if that is 0 then #ulimit -c 100000 btw, did you try a *trace? -- CIMPOESU Teodor, Web Programmer @ DIGICOM S.A. Bucharest, Romania @ Internet, site development @ teo@digiro.net , +(401)-330.47.28 official home page ~ http://www.digiro.net/ Internet web page ~ http://internet.digiro.net/
Gerard Rowe wrote:
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors.
What next?
Try a ltrace (if you have it ) or strace like: (in ~Zope) # ltrace -f -S -o python.trace ./bin/python z2.py or # strace -ff -o python.trace ./bin/python z2.py but be aware that (least w/ ltrace) you will get megs of info :-) If you know what to look for (like _init() calls in .so) use -e flag for ltrace. gl. -- CIMPOESU Teodor, Web Programmer @ DIGICOM S.A. Bucharest, Romania @ Internet, site development @ teo@digiro.net , +(401)-330.47.28 official home page ~ http://www.digiro.net/ Internet web page ~ http://internet.digiro.net/
Teodor Cimpoesu wrote:
Gerard Rowe wrote:
Yes I do get a shell and I'm even able to import the sy_occ.so module without any errors.
What next?
Try a ltrace (if you have it ) or strace like: (in ~Zope) # ltrace -f -S -o python.trace ./bin/python z2.py or # strace -ff -o python.trace ./bin/python z2.py
but be aware that (least w/ ltrace) you will get megs of info :-) If you know what to look for (like _init() calls in .so) use -e flag for ltrace. gl.
I would add that for strace (which should do it), you may want to redirect output to a file, and look at it in your favourite editor. You would want to look for opens and writes. Another idea is to add to s2.py a function printing out the environment. perhaps it should do this when in debug mode anyway? Bill -- "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." -- Carl Sagan
participants (4)
-
Bill Anderson -
Chris McDonough -
Gerard Rowe -
Teodor Cimpoesu