Haluk Durmus wrote:
Thanks,
I had the same problem on my Debian after a distribution upgrade from Woody with kernel 2.4.18 to Sarge and kernel 2.6.8. I traced the jsvc call with strace -f. So I got the following messages:
[pid 11313] capset(0x19980330, 0, {CAP_SETGID|CAP_SETUID|CAP_NET_BIND_SERVICE, CAP_SETGID|CAP_SETUID|CAP_NET_BIND_SERVICE, CAP_SETGID|CAP_SETUID|CAP_NET_BIND_SERVICE}) = -1 EPERM (Operation not permitted)
[pid 11313] write(2, "jsvc.exec error: ", 17) = 17
[pid 11313] write(2, "syscall failed in set_caps", 26) = 26
It seems that some things regarding security and/or cryptography have changed in the kernels. What helped me out of my situation was:
modprobe capability
This solved my problem with the Error set_caps.
Nice to hear.
But now I have an other one!
jsvc didn't bind to port 80
Error in catalino.out log:
Jan 3, 2005 2:24:34 PM org.apache.coyote.http11.Http11Protocol start SEVERE: Error starting endpoint java.net.BindException: Permission denied:80
Please verify that no http server (apache, squid etc.) is running --> only one process may use a port.
Wolfgang
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
