RE: socket: no buffer space available

2003-12-16 Thread Jason Taylor
> On Mon, 2003-12-15 at 16:15, Andrew Thomson wrote:
> > I've got a perl script doing some p5-sybase stuff for me.. However after
> > a while, it fails with the following error message:
> >
> > .."socket: No buffer space available"...
> >
> > I've seen other reports from other uses getting this problem however no
> > clear responses on a fix.

I had a similar problem on a (5.1-RELEASE) box with a:

bge0:  mem
0xfcd2
-0xfcd2,0xfcd3-0xfcd3 irq 5 at device 0.0 on pci2

As well as the no buffer space problem, there were watchguard timeout
measures.

This may not be your problem, but its worth ruling out.

The fix was a kernel src patch for the bge driver.

Jason




RHYBUDD:  Mae'r wybodaeth sydd yn y neges E-Bost yma yn gyfrinachol ac mae'n bosib y 
bydd yn gyfreithiol freintiedig.  Os nad y sawl a fydd yn darllen y neges yma yw'r 
sawl y bwriadwyd yr e-bost ar ei gyfer, fe'ch hysbysir drwy hyn y gwaherddir 
defnyddio'r neges, ei rhannu, ei dosbarthu neu ei hatgynhyrchu gennych chi eich hun 
neu ar eich anogaeth.  Os cawsoch y neges yma trwy amryfusedd, a fyddech cystal รข rhoi 
gwybod i ni ar unwaith a dychwelyd y neges wreiddiol.  Nid yw'r wybodaeth sydd yn y 
neges yma o reidrwydd yn cynrychioli polisi a threfn weithredu'r Cyngor.  Os cewch gan 
y Cyngor hwn ddeunydd heb i chi ofyn amdano neu ddeunydd tramgwyddus rhowch wybod i ni 
ar unwaith.
Diolch

CAUTION:  The information in this E-Mail message is confidential and may be legally 
privileged.  If the reader of this message is not the intended recipient you are 
hereby notified that any use, dissemination, distribution or reproduction of this 
message by you or at your instigation is prohibited.  If you have received this 
message in error  please notify us immediately and return the original message to us.  
The information in this message does not necessarily represent Council policy or 
procedure.  In the instance  of receiving unsolicited or offensive mail from this 
Council please notify us immediately.
Where information of a sensitive or highly confidential nature is to be communicated, 
you will be informed that this information will be sent to you in writing and not by 
E-Mail, unless secure arrangements are made.
Thank you.


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re[2]: socket: no buffer space available

2003-12-15 Thread hugle
AT> Just for the record, I fixed this problem by recompiling my kernel with
AT> MAXUSERS 512
actualy you don't need to recompile kernel.
you can achieve that by doing:
echo kern.maxusers=0 >> /boot/loader.conf

It is better to use 0, since them freeBSD can dynamicaly change you
need (as i heard)
AT> :)

AT> ajt.

AT> On Mon, 2003-12-15 at 16:15, Andrew Thomson wrote:
>> I've got a perl script doing some p5-sybase stuff for me.. However after
>> a while, it fails with the following error message:
>> 
>> .."socket: No buffer space available"...
>> 
>> I've seen other reports from other uses getting this problem however no
>> clear responses on a fix.
>> 
>> This script used to work find on my 5.0-RELEASE box now I'm trying it on
>> a 5.1-RELEASE box. I admit the new box is a lower spec - less cpu and
>> less memory - so that may affect some of the default sysctl values???
>> 
>> I've tried tweaking a couple of sysctl entries however nothing has
>> gotten me over this hurdle.
>> 
>> Below are some relevant(??) sysctls.
>> 
>> kern.ipc.maxsockbuf: 1048576
>> kern.ipc.sockbuf_waste_factor: 8
>> kern.ipc.nmbufs: 17920
>> kern.ipc.nsfbufs: 2496
>> kern.ipc.mbuf_wait: 64
>> kern.ipc.mbuf_hiwm: 512
>> kern.ipc.mbuf_lowm: 128
>> 
>> kern.ipc.numopensockets: 94
>> kern.ipc.maxsockets: 4008
>> 
>> Any suggested tweaks appreciated.
>> 
>> Regards,
>> 
>> ajt.
>> 
>> 
>> ___
>> [EMAIL PROTECTED] mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "[EMAIL PROTECTED]"
>> 


AT> ___
AT> [EMAIL PROTECTED] mailing list
AT> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
AT> To unsubscribe, send any mail to
AT> "[EMAIL PROTECTED]"



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: socket: no buffer space available

2003-12-15 Thread Andrew Thomson
Just for the record, I fixed this problem by recompiling my kernel with
MAXUSERS 512

:)

ajt.

On Mon, 2003-12-15 at 16:15, Andrew Thomson wrote:
> I've got a perl script doing some p5-sybase stuff for me.. However after
> a while, it fails with the following error message:
> 
> .."socket: No buffer space available"...
> 
> I've seen other reports from other uses getting this problem however no
> clear responses on a fix.
> 
> This script used to work find on my 5.0-RELEASE box now I'm trying it on
> a 5.1-RELEASE box. I admit the new box is a lower spec - less cpu and
> less memory - so that may affect some of the default sysctl values???
> 
> I've tried tweaking a couple of sysctl entries however nothing has
> gotten me over this hurdle.
> 
> Below are some relevant(??) sysctls.
> 
> kern.ipc.maxsockbuf: 1048576
> kern.ipc.sockbuf_waste_factor: 8
> kern.ipc.nmbufs: 17920
> kern.ipc.nsfbufs: 2496
> kern.ipc.mbuf_wait: 64
> kern.ipc.mbuf_hiwm: 512
> kern.ipc.mbuf_lowm: 128
> 
> kern.ipc.numopensockets: 94
> kern.ipc.maxsockets: 4008
> 
> Any suggested tweaks appreciated.
> 
> Regards,
> 
> ajt.
> 
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


socket: no buffer space available

2003-12-14 Thread Andrew Thomson
I've got a perl script doing some p5-sybase stuff for me.. However after
a while, it fails with the following error message:

.."socket: No buffer space available"...

I've seen other reports from other uses getting this problem however no
clear responses on a fix.

This script used to work find on my 5.0-RELEASE box now I'm trying it on
a 5.1-RELEASE box. I admit the new box is a lower spec - less cpu and
less memory - so that may affect some of the default sysctl values???

I've tried tweaking a couple of sysctl entries however nothing has
gotten me over this hurdle.

Below are some relevant(??) sysctls.

kern.ipc.maxsockbuf: 1048576
kern.ipc.sockbuf_waste_factor: 8
kern.ipc.nmbufs: 17920
kern.ipc.nsfbufs: 2496
kern.ipc.mbuf_wait: 64
kern.ipc.mbuf_hiwm: 512
kern.ipc.mbuf_lowm: 128

kern.ipc.numopensockets: 94
kern.ipc.maxsockets: 4008

Any suggested tweaks appreciated.

Regards,

ajt.


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"