I have a couple of zones. On one zone, I have lighttpd. On another, I got a customer using Apache. This is on a 2009.06 release.
Every once in a while, maybe every other day, the server becomes unstable. HTTP requests no longer get a response. Sometimes, it works after a while w/o a problem. But sometimes, a restart of the server is necessary. I am using crossbow for these zones, with virtual links. I was doing a dtrace for all open* calls and I saw something like this: Could it be that there is something wrong with the /dev/urandom device in OpenSolaris? It is very peculiar and I can't figure it out. I find it strange that this same type of behavior happens in two different zones running two different applications. Do you guys have any pointers? Next time this happens, what can I do to capture more data? The customer wants to move away from OpenSolaris and go back to Solaris because of this. Thanks! 2 62318 open:entry postgres pg_stat_tmp/pgstat.tmp 2 62318 open:entry postgres pg_stat_tmp/pgstat.tmp 2 62720 open64:entry httpd /dev/urandom 2 62318 open:entry httpd /etc/crypto/pkcs11.conf dtrace: error on enabled probe ID 2 (ID 62318: syscall::open:entry): invalid address (0xfd4abc63) in action #2 at DIF offset 28 2 62318 open:entry httpd /usr/lib/security/pkcs11_softtoken.so 2 62318 open:entry httpd /usr/lib/libsoftcrypto.so.1 2 62318 open:entry httpd /usr/lib/libsoftcrypto/libsoftcrypto_hwcap1.so.1 -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
