Re: Still not working
Thanks. Unfortunately I just read your message now after a day of
building the x64 version of CentOS. :-(
I haven't gotten to the point to where I'm tackling the production
version with mod_python. After installing the OS, I added Postgres,
Python 2.5, pyscopg2, pylons, sqlalchemy, and mako. Everything seems
to be kosher, but now I'm having problem with either the Paste web
server or pyscopg2.
I have two actions in a single controller. Both of them just do a
simple query via pyscopg2 and pass the output to a template. One of
them works fine, while the other causes Paste to silently die to the
shell prompt when cur.execute(query) is executed. I get a HTTP 200
response, but no content and no error messages on the console. Paste
just dies. Postgres just reports LOG: unexpected EOF on client
connection in the server log. My code works elsewhere and the two
queries aren't all that different. I'm stumped...
Is there anyway that I can figure out why Paste is dying? Strace
hasn't been that helpful. Here's what I get. The SELECT statement is
printed to the screen immediately before it's executed:
SELECT * FROM tasks_get_open(%s) ['jamie']
[{WIFSIGNALED(s) WTERMSIG(s) == SIGSEGV}], 0, NULL) = 565
--- SIGCHLD (Child exited) @ 0 (0) ---
futex(0x6ce030, FUTEX_WAKE, 1) = 0
futex(0x6d10c0, FUTEX_WAKE, 1) = 0
futex(0x6d10c0, FUTEX_WAKE, 1) = 0
futex(0x6ce030, FUTEX_WAKE, 1) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {0x2a9564e480, [], SA_RESTORER,
0x3bb910c430}, 8) = 0
futex(0x6d10c0, FUTEX_WAKE, 1) = 0
futex(0x52f7c0, FUTEX_WAKE, 1) = 0
futex(0x5012a0, FUTEX_WAKE, 1) = 0
futex(0x5012a0, FUTEX_WAKE, 1) = 0
futex(0x5012a0, FUTEX_WAKE, 1) = 0
exit_group(-11) = ?
Process 564 detached
On Mar 20, 2:37 pm, Cliff Wells [EMAIL PROTECTED] wrote:
On Tue, 2007-03-20 at 10:50 -0700, Jamie wrote:
Thanks for the suggestions; unfortunately it's still not working.
There was nothing in /var/llog/messages, but I disabled selinux
anyhow. I'm still getting a file not found error.
I beginning to wonder if I have a deeper system issue though. The
motherboard in my dev box blew out last week so I put the HDD in an
available system. I don't know whether it's because the original had a
32-bit Intel chip and the new one has a 64-bit AMD, but some things
have been a bit flaky. Python, for example, was complaining about not
being able to find a module that's part of the base package. After
recompiling it things worked normally again. I might just wipe it and
reload. Keep you posted...
Did you do a fresh install on the AMD? If so, did you install the
x86_64 or i386 version? Most distros maintain a separate /usr/lib
and /usr/lib64 for compatibility and I've had issues with building
Python packages on these platforms. In my case I managed to work around
it by simply getting rid of the 32-bit /usr/lib and renaming
the /usr/lib64 to /usr/lib. The problem seems to be due to the fact
that certain Python modules get stuck in lib64 and some in lib and
Python gets confused. Switching to pure 64 bit in this way will mean
you can't run certain binary-only packages (Flash for one) but won't
hurt much else.
As an aside, unless you've got over 4GB of RAM, you'll find that 64bit
mode will make your machine considerably slower (and less compatible) so
I'd highly recommend just sticking with the i386 version unless you've
got lots of RAM.
Regards,
Cliff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~--~~~~--~~--~--~---
Re: Still not working
On Wed, 2007-03-21 at 21:50 +, Jamie wrote: Thanks. Unfortunately I just read your message now after a day of building the x64 version of CentOS. :-( I haven't gotten to the point to where I'm tackling the production version with mod_python. After installing the OS, I added Postgres, Python 2.5, pyscopg2, pylons, sqlalchemy, and mako. Everything seems to be kosher, but now I'm having problem with either the Paste web server or pyscopg2. See this: http://www.initd.org/tracker/psycopg/ticket/127 or if that site isn't working (it was having some issues as I write this): http://72.14.253.104/search?q=cache:gXyPuRIu2YEJ:www.initd.org/tracker/psycopg/ticket/127+psycopg2+x86_64+segfaulthl=enct=clnkcd=3gl=us http://72.14.253.104/search?q=cache:EX0Pb0DZZSoJ:lists.initd.org/pipermail/psycopg/2007-February/005326.html+psycopg2+x86_64+segfaulthl=enct=clnkcd=1gl=us It seems this is an issue wrt Python 2.5 and Psycopg2. You might try falling back to Python 2.4 and see if the problem persists. Regards, Cliff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Still not working
Thanks for the suggestions; unfortunately it's still not working. There was nothing in /var/llog/messages, but I disabled selinux anyhow. I'm still getting a file not found error. I beginning to wonder if I have a deeper system issue though. The motherboard in my dev box blew out last week so I put the HDD in an available system. I don't know whether it's because the original had a 32-bit Intel chip and the new one has a 64-bit AMD, but some things have been a bit flaky. Python, for example, was complaining about not being able to find a module that's part of the base package. After recompiling it things worked normally again. I might just wipe it and reload. Keep you posted... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Still not working
On Tue, 2007-03-20 at 10:50 -0700, Jamie wrote: Thanks for the suggestions; unfortunately it's still not working. There was nothing in /var/llog/messages, but I disabled selinux anyhow. I'm still getting a file not found error. I beginning to wonder if I have a deeper system issue though. The motherboard in my dev box blew out last week so I put the HDD in an available system. I don't know whether it's because the original had a 32-bit Intel chip and the new one has a 64-bit AMD, but some things have been a bit flaky. Python, for example, was complaining about not being able to find a module that's part of the base package. After recompiling it things worked normally again. I might just wipe it and reload. Keep you posted... Did you do a fresh install on the AMD? If so, did you install the x86_64 or i386 version? Most distros maintain a separate /usr/lib and /usr/lib64 for compatibility and I've had issues with building Python packages on these platforms. In my case I managed to work around it by simply getting rid of the 32-bit /usr/lib and renaming the /usr/lib64 to /usr/lib. The problem seems to be due to the fact that certain Python modules get stuck in lib64 and some in lib and Python gets confused. Switching to pure 64 bit in this way will mean you can't run certain binary-only packages (Flash for one) but won't hurt much else. As an aside, unless you've got over 4GB of RAM, you'll find that 64bit mode will make your machine considerably slower (and less compatible) so I'd highly recommend just sticking with the i386 version unless you've got lots of RAM. Regards, Cliff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
