Hi Zope Users! After the upgrade of my box from redhat 8 to redhat 9 my zope 2.6.1 doesn't work any more. I didn't installed zope rpms, so all zope binaries are as beftore. The box is a smp i686 with 2.4.20-8smp kernel and glibc 2.3.2-11.9. When I connect to http://mybox:8080/ I got sometimes the 'zope welcome screen', but mostly not. Trying to access sth else the server does not answer as well - the browser is waiting infinitely for the server response. There is no error message in the logs or somewhere else. Starting the server as user zope by call ./start & I can see followed processes: [zope@mybox zope_dev]# ps auxf USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND zope 1305 0.0 0.2 4532 1392 pts/2 S 12:36 0:00 | \_ -bash zope 1343 0.1 0.6 4364 3380 pts/2 S 12:36 0:00 | \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py zope 1346 1.0 2.9 49632 15168 pts/2 S 12:36 0:05 | \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py The output is the same as for working server under rh8, but a browser gets no response making (as root) strace onto pid 1346 gives this: ... gettimeofday({1055327969, 572131}, NULL) = 0 fcntl64(16, F_SETFD, FD_CLOEXEC) = 0 select(17, [9 13 14 15 16], [], [], {30, 0}) = 1 (in [16], left {30, 0}) recv(16, "GET /manage HTTP/1.1\r\nAccept: im"..., 4096, 0) = 353 gettimeofday({1055327969, 574106}, NULL) = 0 futex(0x8bd83d4, FUTEX_WAKE, 1, {1, 1}) = 1 futex(0x8bd83c8, FUTEX_WAKE, 1, {0, 1}) = 1 futex(0x8bd667c, FUTEX_WAKE, 1, {1, 17}) = 1 futex(0x8bd6670, FUTEX_WAKE, 1, {0, 17}) = 1 futex(0x8bd8240, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x8bd8240, FUTEX_WAKE, 1, NULL) = 0 select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) Originally the server was started by root by calling zope8580 script (quite the same as 'start' script, but with extra -u zope parameter). The process list is looking this way: [root@mybox zope_dev]# ps auxf USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 18550 0.0 0.1 3752 708 pts/1 S 16:11 0:00 initlog -c /opt/zope_dev/zope8580 8580 root 18551 0.2 0.6 4368 3380 pts/1 S 16:11 0:00 \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py -u zope -P 8500 -D zope 18557 1.5 2.9 49680 14896 pts/1 S 16:11 0:04 \_ [python] ^^^^^^^^^^^^ making strace onto 18557 pid I get [root@mybox zope_dev]# strace -p 18557 trace: ptrace(PTRACE_SYSCALL, ...): Operation not permitted detach: ptrace(PTRACE_DETACH, ...): Operation not permitted I've downloaded from ZopeSite and installed once more the linux binaries for 2.6.1 - the same result. I've downloaded 2.6.1 sources, compiled and installed - no success as well. Always no response from server without any error message. I ran out of ideas what could it be and how to fix it. I'm wondering if its the only case of strange behavior rh9+zope2.6.1 Any help or suggestions would be appreciated Grzegorz
Check the mailing list archives of the last weeks. This issues has been discussed and solved before. -aj --On Mittwoch, 11. Juni 2003 15:50 Uhr +0200 Grzegorz Jasko <jasko@industriebrandpartners.de> wrote:
Hi Zope Users!
After the upgrade of my box from redhat 8 to redhat 9 my zope 2.6.1 doesn't work any more. I didn't installed zope rpms, so all zope binaries are as beftore. The box is a smp i686 with 2.4.20-8smp kernel and glibc 2.3.2-11.9. When I connect to http://mybox:8080/ I got sometimes the 'zope welcome screen', but mostly not. Trying to access sth else the server does not answer as well - the browser is waiting infinitely for the server response. There is no error message in the logs or somewhere else.
Starting the server as user zope by call ./start & I can see followed processes: [zope@mybox zope_dev]# ps auxf USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND zope 1305 0.0 0.2 4532 1392 pts/2 S 12:36 0:00 | \_ -bash zope 1343 0.1 0.6 4364 3380 pts/2 S 12:36 0:00 | \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py zope 1346 1.0 2.9 49632 15168 pts/2 S 12:36 0:05 | \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py
The output is the same as for working server under rh8, but a browser gets no response
making (as root) strace onto pid 1346 gives this: ... gettimeofday({1055327969, 572131}, NULL) = 0 fcntl64(16, F_SETFD, FD_CLOEXEC) = 0 select(17, [9 13 14 15 16], [], [], {30, 0}) = 1 (in [16], left {30, 0}) recv(16, "GET /manage HTTP/1.1\r\nAccept: im"..., 4096, 0) = 353 gettimeofday({1055327969, 574106}, NULL) = 0 futex(0x8bd83d4, FUTEX_WAKE, 1, {1, 1}) = 1 futex(0x8bd83c8, FUTEX_WAKE, 1, {0, 1}) = 1 futex(0x8bd667c, FUTEX_WAKE, 1, {1, 17}) = 1 futex(0x8bd6670, FUTEX_WAKE, 1, {0, 17}) = 1 futex(0x8bd8240, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x8bd8240, FUTEX_WAKE, 1, NULL) = 0 select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout)
Originally the server was started by root by calling zope8580 script (quite the same as 'start' script, but with extra -u zope parameter). The process list is looking this way: [root@mybox zope_dev]# ps auxf USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 18550 0.0 0.1 3752 708 pts/1 S 16:11 0:00 initlog -c /opt/zope_dev/zope8580 8580 root 18551 0.2 0.6 4368 3380 pts/1 S 16:11 0:00 \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py -u zope -P 8500 -D zope 18557 1.5 2.9 49680 14896 pts/1 S 16:11 0:04 \_ [python] ^^^^^^^^^^^^
making strace onto 18557 pid I get [root@mybox zope_dev]# strace -p 18557 trace: ptrace(PTRACE_SYSCALL, ...): Operation not permitted detach: ptrace(PTRACE_DETACH, ...): Operation not permitted
I've downloaded from ZopeSite and installed once more the linux binaries for 2.6.1 - the same result. I've downloaded 2.6.1 sources, compiled and installed - no success as well. Always no response from server without any error message. I ran out of ideas what could it be and how to fix it. I'm wondering if its the only case of strange behavior rh9+zope2.6.1
Any help or suggestions would be appreciated
Grzegorz
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
RH9 appears to be causing this problem for a lot of people... see list archives for discussion and a fix. http://zope.nipltd.com/public/lists/zope-archive.nsf/ HTH, Dylan On Wed, 2003-06-11 at 06:50, Grzegorz Jasko wrote:
Hi Zope Users!
After the upgrade of my box from redhat 8 to redhat 9 my zope 2.6.1 doesn't work any more. I didn't installed zope rpms, so all zope binaries are as beftore. The box is a smp i686 with 2.4.20-8smp kernel and glibc 2.3.2-11.9. When I connect to http://mybox:8080/ I got sometimes the 'zope welcome screen', but mostly not. Trying to access sth else the server does not answer as well - the browser is waiting infinitely for the server response. There is no error message in the logs or somewhere else.
Starting the server as user zope by call ./start & I can see followed processes: [zope@mybox zope_dev]# ps auxf USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND zope 1305 0.0 0.2 4532 1392 pts/2 S 12:36 0:00 | \_ -bash zope 1343 0.1 0.6 4364 3380 pts/2 S 12:36 0:00 | \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py zope 1346 1.0 2.9 49632 15168 pts/2 S 12:36 0:05 | \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py
The output is the same as for working server under rh8, but a browser gets no response
making (as root) strace onto pid 1346 gives this: ... gettimeofday({1055327969, 572131}, NULL) = 0 fcntl64(16, F_SETFD, FD_CLOEXEC) = 0 select(17, [9 13 14 15 16], [], [], {30, 0}) = 1 (in [16], left {30, 0}) recv(16, "GET /manage HTTP/1.1\r\nAccept: im"..., 4096, 0) = 353 gettimeofday({1055327969, 574106}, NULL) = 0 futex(0x8bd83d4, FUTEX_WAKE, 1, {1, 1}) = 1 futex(0x8bd83c8, FUTEX_WAKE, 1, {0, 1}) = 1 futex(0x8bd667c, FUTEX_WAKE, 1, {1, 17}) = 1 futex(0x8bd6670, FUTEX_WAKE, 1, {0, 17}) = 1 futex(0x8bd8240, FUTEX_WAIT, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x8bd8240, FUTEX_WAKE, 1, NULL) = 0 select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout) select(17, [9 13 14 15 16], [], [], {30, 0}) = 0 (Timeout)
Originally the server was started by root by calling zope8580 script (quite the same as 'start' script, but with extra -u zope parameter). The process list is looking this way: [root@mybox zope_dev]# ps auxf USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 18550 0.0 0.1 3752 708 pts/1 S 16:11 0:00 initlog -c /opt/zope_dev/zope8580 8580 root 18551 0.2 0.6 4368 3380 pts/1 S 16:11 0:00 \_ /opt/zope_dev/bin/python /opt/zope_dev/z2.py -u zope -P 8500 -D zope 18557 1.5 2.9 49680 14896 pts/1 S 16:11 0:04 \_ [python] ^^^^^^^^^^^^
making strace onto 18557 pid I get [root@mybox zope_dev]# strace -p 18557 trace: ptrace(PTRACE_SYSCALL, ...): Operation not permitted detach: ptrace(PTRACE_DETACH, ...): Operation not permitted
I've downloaded from ZopeSite and installed once more the linux binaries for 2.6.1 - the same result. I've downloaded 2.6.1 sources, compiled and installed - no success as well. Always no response from server without any error message. I ran out of ideas what could it be and how to fix it. I'm wondering if its the only case of strange behavior rh9+zope2.6.1
Any help or suggestions would be appreciated
Grzegorz
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
participants (3)
-
Andreas Jung -
Dylan Reinhardt -
Grzegorz Jasko