Re: sendto: No buffer space available
I use a freebsd box as a gateway for my home network. It uses a dialup internet connection. When my ISP is having network problems, I will get the precise same issue. I have also had the modem crash, and also got the same problem. I could fix it by killing ppp and restarting it.That clears the tcp buffers for ppp. I suspect you possibly have a bad NIC or perhaps some other network issue that's intermittent. Taking down the interface might clear the buffers... NEOFAST.NET North East Oregon FAST Net mark(at)neofast.net - Original Message - From: Haesu [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 9:32 AM Subject: sendto: No buffer space available Hello, We have a FreeBSD box here that we use to route some GRE tunnels and ipv6 gif tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d. We have about 12 FreeBSD boxes with exact same configuration, the only difference is just the IP address of each interface. None of them fail but this one box... Everyday, this box stops all networking. I can still console in and stuff.. When I typed 'ping 127.0.0.1' at the console after networking locked up, it says: ping: sendto: No buffer space available --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 7/24/03 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendto: No buffer space available
I did ifconfig down/up on all interfaces, and that didn't help... The only way to clear it up seems like rebooting the whole box.. This one isn't related to any ppp, it has gre tunnels which are kernel based... This is bazzarre problem.. none of the other boxes exhibit this problem ever.. Thanks, -hc -- Sincerely, Haesu C. TowardEX Technologies, Inc. WWW: http://www.towardex.com E-mail: [EMAIL PROTECTED] Cell: (978) 394-2867 On Wed, Jul 30, 2003 at 10:02:02AM -0700, Mark Koskenmaki wrote: I use a freebsd box as a gateway for my home network. It uses a dialup internet connection. When my ISP is having network problems, I will get the precise same issue. I have also had the modem crash, and also got the same problem. I could fix it by killing ppp and restarting it.That clears the tcp buffers for ppp. I suspect you possibly have a bad NIC or perhaps some other network issue that's intermittent. Taking down the interface might clear the buffers... NEOFAST.NET North East Oregon FAST Net mark(at)neofast.net - Original Message - From: Haesu [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 9:32 AM Subject: sendto: No buffer space available Hello, We have a FreeBSD box here that we use to route some GRE tunnels and ipv6 gif tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d. We have about 12 FreeBSD boxes with exact same configuration, the only difference is just the IP address of each interface. None of them fail but this one box... Everyday, this box stops all networking. I can still console in and stuff.. When I typed 'ping 127.0.0.1' at the console after networking locked up, it says: ping: sendto: No buffer space available --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 7/24/03 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendto: No buffer space available
I had the same exact problem. I traced it to be a bug in some software
that opened a domain socket(2) but could not connect(2) and never closed
the descriptor returned.
something like:
sd = socket(AF_UNIX, SOCK_STREAM, 0);
...
if(connect(sd, (struct sockaddr *)saddr, sizeof(saddr)) 0) {
return -1;
}
where close(2) was skipped on sd if the connect failed.
over a period of time (12-18hrs), these unconnected sockets would fill
up the available buffer space, and exhibit the same symptoms you are
having. even running ifconfig would fail with No buffer space available.
from intro(2):
55 ENOBUFS No buffer space available. An operation on a socket or pipe
was not performed because the system lacked sufficient buffer space or
because a queue was full.
Fixing that bug fixed the problem. I doubt you have a hardware problem,
I would try narrowing down what software is causing the lockup. truss(1)
might help you out here.
Dave
On Wed, 2003-07-30 at 09:32, Haesu wrote:
Hello,
We have a FreeBSD box here that we use to route some GRE tunnels and ipv6 gif
tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d.
We have about 12 FreeBSD boxes with exact same configuration, the only
difference is just the IP address of each interface.
None of them fail but this one box...
Everyday, this box stops all networking. I can still console in and stuff.. When
I typed 'ping 127.0.0.1' at the console after networking locked up, it says:
ping: sendto: No buffer space available
The only solution seems to be rebooting it everyday... It happens every 12 hours
or so...
This is not related with mbuf, etc either, as netstat -m doesn't show any
issues.
The box has one IP address and IPv6 address in addition to 127.0.0.1 on lo0
interface. It also has a ds0 interface with 10.5.5.5/30 assigned to ds0.
This is exact same configuration on all other boxes, and none of them fail but
this one.
I've swapped out NICs with different vendors 3 times (tried, xl, dc, and now rl)
I've also swapped out the whole box, and also swapped out the whole hard drive
and did full reinstall. And problem still persists and it's definately not
hardware as I swapped everything out... (unless the 3 NIC vendors above are all
exhibiting same issue)
I tried to look on Google but nothing useful that corelates to this particular
issue..
Any help would be very appreciated :)
Thanks,
-hc
The box is running FreeBSD 4.8-STABLE
FreeBSD necsis 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 29 13:10:11 GMT 2003
[EMAIL PROTECTED]:/usr/src/sys/compile/router i386
Following is output of netstat -s AFTER the networking locks up with no buffer
space available error:
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendto: No buffer space available
Hmmm... i had truss running but the moment it died it was running gettimeoftheday() so
i am not sure :-/
I tried different ports on the switch.. It's a cisco switch btw, and other freebsd
boxes on that switch
are not exhibiting similar problem
I'll try putting this behind a hub or something other than cisco just for kicks but if
anyone has any further ideas/suggestions, i'd really appreciate it.
Thank you!
-hc
--
Sincerely,
Haesu C.
TowardEX Technologies, Inc.
WWW: http://www.towardex.com
E-mail: [EMAIL PROTECTED]
Cell: (978) 394-2867
On Wed, Jul 30, 2003 at 11:36:35AM -0700, Dave Byrne wrote:
I had the same exact problem. I traced it to be a bug in some software
that opened a domain socket(2) but could not connect(2) and never closed
the descriptor returned.
something like:
sd = socket(AF_UNIX, SOCK_STREAM, 0);
...
if(connect(sd, (struct sockaddr *)saddr, sizeof(saddr)) 0) {
return -1;
}
where close(2) was skipped on sd if the connect failed.
over a period of time (12-18hrs), these unconnected sockets would fill
up the available buffer space, and exhibit the same symptoms you are
having. even running ifconfig would fail with No buffer space available.
from intro(2):
55 ENOBUFS No buffer space available. An operation on a socket or pipe
was not performed because the system lacked sufficient buffer space or
because a queue was full.
Fixing that bug fixed the problem. I doubt you have a hardware problem,
I would try narrowing down what software is causing the lockup. truss(1)
might help you out here.
Dave
On Wed, 2003-07-30 at 09:32, Haesu wrote:
Hello,
We have a FreeBSD box here that we use to route some GRE tunnels and ipv6 gif
tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d.
We have about 12 FreeBSD boxes with exact same configuration, the only
difference is just the IP address of each interface.
None of them fail but this one box...
Everyday, this box stops all networking. I can still console in and stuff.. When
I typed 'ping 127.0.0.1' at the console after networking locked up, it says:
ping: sendto: No buffer space available
The only solution seems to be rebooting it everyday... It happens every 12 hours
or so...
This is not related with mbuf, etc either, as netstat -m doesn't show any
issues.
The box has one IP address and IPv6 address in addition to 127.0.0.1 on lo0
interface. It also has a ds0 interface with 10.5.5.5/30 assigned to ds0.
This is exact same configuration on all other boxes, and none of them fail but
this one.
I've swapped out NICs with different vendors 3 times (tried, xl, dc, and now rl)
I've also swapped out the whole box, and also swapped out the whole hard drive
and did full reinstall. And problem still persists and it's definately not
hardware as I swapped everything out... (unless the 3 NIC vendors above are all
exhibiting same issue)
I tried to look on Google but nothing useful that corelates to this particular
issue..
Any help would be very appreciated :)
Thanks,
-hc
The box is running FreeBSD 4.8-STABLE
FreeBSD necsis 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 29 13:10:11 GMT 2003
[EMAIL PROTECTED]:/usr/src/sys/compile/router i386
Following is output of netstat -s AFTER the networking locks up with no buffer
space available error:
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
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]
RE: sendto: No buffer space available
I think heading down the path of switchign out network
gear is a bad idea, this is definitely something in
the software.
I have had this error a few times when messing with
the TCP window sizes, net.inet.tcp.sendspace and
net.inet.tcp.recvspace. When I set them to something
over 128000 I would get the error. The solution was
set the number of mbufs to 128000. Doing so allowed
me to make the window sizes 256000 and eliminated
the error.
-good luck
-mtl
--
Michael Lapinski
Computer Scientist
GE Research
I think there is a world market for maybe five computers.
- IBM Chairman Thomas Watson, 1943
--Original Message-
-From: Haesu [mailto:[EMAIL PROTECTED]
-Sent: Wednesday, July 30, 2003 4:26 PM
-To: Dave Byrne; [EMAIL PROTECTED]; [EMAIL PROTECTED]
-Subject: Re: sendto: No buffer space available
-
-
-Hmmm... i had truss running but the moment it died it was
-running gettimeoftheday() so i am not sure :-/
-
-I tried different ports on the switch.. It's a cisco switch
-btw, and other freebsd boxes on that switch
-are not exhibiting similar problem
-
-I'll try putting this behind a hub or something other than
-cisco just for kicks but if anyone has any further
-ideas/suggestions, i'd really appreciate it.
-
-Thank you!
-
--hc
-
---
-Sincerely,
- Haesu C.
- TowardEX Technologies, Inc.
- WWW: http://www.towardex.com
- E-mail: [EMAIL PROTECTED]
- Cell: (978) 394-2867
-
-On Wed, Jul 30, 2003 at 11:36:35AM -0700, Dave Byrne wrote:
- I had the same exact problem. I traced it to be a bug in
-some software
- that opened a domain socket(2) but could not connect(2) and
-never closed
- the descriptor returned.
-
- something like:
-
- sd = socket(AF_UNIX, SOCK_STREAM, 0);
- ...
- if(connect(sd, (struct sockaddr *)saddr, sizeof(saddr)) 0) {
-return -1;
- }
-
- where close(2) was skipped on sd if the connect failed.
-
- over a period of time (12-18hrs), these unconnected sockets
-would fill
- up the available buffer space, and exhibit the same symptoms you are
- having. even running ifconfig would fail with No buffer
-space available.
-
- from intro(2):
- 55 ENOBUFS No buffer space available. An operation on a
-socket or pipe
- was not performed because the system lacked sufficient
-buffer space or
- because a queue was full.
-
- Fixing that bug fixed the problem. I doubt you have a
-hardware problem,
- I would try narrowing down what software is causing the
-lockup. truss(1)
- might help you out here.
-
-
-
- Dave
-
-
-
-
- On Wed, 2003-07-30 at 09:32, Haesu wrote:
- Hello,
-
- We have a FreeBSD box here that we use to route some GRE
-tunnels and ipv6 gif tunnels. We use zebra for dynamic
-routing running zebra, bgpd, ospfd, and ospf6d.
-
- We have about 12 FreeBSD boxes with exact same
-configuration, the only
- difference is just the IP address of each interface.
-
- None of them fail but this one box...
-
- Everyday, this box stops all networking. I can still
-console in and stuff.. When
- I typed 'ping 127.0.0.1' at the console after networking
-locked up, it says:
- ping: sendto: No buffer space available
-
- The only solution seems to be rebooting it everyday... It
-happens every 12 hours
- or so...
-
- This is not related with mbuf, etc either, as netstat -m
-doesn't show any
- issues.
-
- The box has one IP address and IPv6 address in addition
-to 127.0.0.1 on lo0
- interface. It also has a ds0 interface with 10.5.5.5/30
-assigned to ds0.
- This is exact same configuration on all other boxes, and
-none of them fail but
- this one.
-
- I've swapped out NICs with different vendors 3 times
-(tried, xl, dc, and now rl)
-
- I've also swapped out the whole box, and also swapped out
-the whole hard drive
- and did full reinstall. And problem still persists and
-it's definately not
- hardware as I swapped everything out... (unless the 3 NIC
-vendors above are all
- exhibiting same issue)
-
- I tried to look on Google but nothing useful that
-corelates to this particular
- issue..
-
- Any help would be very appreciated :)
-
- Thanks,
- -hc
-
- The box is running FreeBSD 4.8-STABLE
- FreeBSD necsis 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul
-29 13:10:11 GMT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/router i386
-
- Following is output of netstat -s AFTER the networking
-locks up with no buffer
- space available error:
-
-
- ___
- [EMAIL PROTECTED] mailing list
- http://lists.freebsd.org/mailman/listinfo/freebsd-isp
- To unsubscribe, send any mail to
-[EMAIL PROTECTED]
-
-___
-[EMAIL PROTECTED] mailing list
-http://lists.freebsd.org/mailman/listinfo/freebsd-isp
-To unsubscribe, send any mail to [EMAIL PROTECTED]
-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo
Re: sendto: No buffer space available
On Thu, 31 Jul 2003 06:25 am, Haesu wrote: Hmmm... i had truss running but the moment it died it was running gettimeoftheday() so i am not sure :-/ If it is software, the other thing to try might be sockstat if your not already aware of it (it lists all the sockets being used by which programs). JacobRhoden - http://rhoden.id.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
