Hi, I am running the dbt2 test kit for postgres-8.0.1.The driver and client are running on Sun Solaris 10 and the database is running on Red Hat 9.I am running the test kit for 100 warehouses with tpw(terminal per warehouse) value of 80. I did truss on driver and found that after executing some transactions an error comes related to EPROTONOSUP. The particular point where error comes looks like this- so_socket(PF_INET, SOCK_STREAM, -4, "", SOV_DEFAULT) Err#120 EPROTONOSUP . Above this error the normal behaviour was: so_socket(PF_INET, SOCK_STREAM, IPPROTO_TCP, "", SOV_DEFAULT) = 255 I found that this error comes when the protocol is not supported by the addres family. Could you please help me out on this about how to solve this one as how after executing for some time the protocol is not supported at all. Thanks & Regards uma ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony
So, what does this have to do with openssh? umashankar uniyal wrote:> Hi, > I am running the dbt2 test kit for postgres-8.0.1.The > driver and client are running on Sun Solaris 10 and > the database is running on Red Hat 9.I am running the > test kit for 100 warehouses with tpw(terminal per > warehouse) value of 80. > > I did truss on driver and found that after executing > some transactions an error comes related to > EPROTONOSUP. The particular point where error comes > looks like this- > > so_socket(PF_INET, SOCK_STREAM, -4, "", SOV_DEFAULT) > Err#120 EPROTONOSUP . > > Above this error the normal behaviour was: > so_socket(PF_INET, SOCK_STREAM, IPPROTO_TCP, "", > SOV_DEFAULT) = 255 > > I found that this error comes when the protocol is not > supported by the addres family. > Could you please help me out on this about how to > solve this one as how after executing for some time > the protocol is not supported at all. > > Thanks & Regards > uma
Possibly Parallel Threads
- libvirtd remote access
- Odd Samba 4 ("4.2.0pre1-GIT-b505111"; actually only using client) behaviour #2 - "accept: Software caused connection abort".
- Group permissions issue migrating from 2.2.8a to 3.0.23a
- OpenSSH 3.9p1 X11 forwarding
- Calling LAPACK functions directly from R