1832906 Members
2696 Online
110048 Solutions
New Discussion

Re: Socket error

 
sethu_1
New Member

Socket error

Hi,

I am also facing a similar kind of problem "BAD FILE NUMBER".
This is all about connection between 2 different OS.
I am the server (OS is HPUX-11), client is LINUX.

After writing a large chunk of data continuously,
It gives the "bad file number", means socket fd is no longer valid!
Neither me , nor the the other end initiated connection close!
then, how can it suddenly say that fd is invalid?

when the other end is also HPUX(a simple telnet, where
it displays the messages it is getting,)this error never occurs!.

Is there anything to do with the socket buffers becoming full?
but even in that case, it will return the number of bytes written.
It will never close the connection?

Is there any specific reason for a socket tobecome invalid??

please help me!!!
2 REPLIES 2
Michael Tully
Honored Contributor

Re: Socket error

At a guess, how big are the files your writing?
If they are over 2Gb, is the filesystem being written to have largefiles support ?

# fstyp -v /dev/myvg/rlvolx
and look for the f_flag: 16 This has largefiles support. If it is zero it is not.
Anyone for a Mutiny ?
Michael Tully
Honored Contributor

Re: Socket error

You could also look at patch number PHNE_27777. I read a post on a similar problem where this patch solved it.
Anyone for a Mutiny ?