Netgate Store

Author Topic: send() failed (40: Message too long)  (Read 7979 times)

0 Members and 1 Guest are viewing this topic.

Offline hardy_rafael17

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +2/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #15 on: June 12, 2016, 01:12:49 pm »
Hi.... Yes Im getting the exact same log... after upgrade...
system specs... below

Offline tosman61

  • Jr. Member
  • **
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #16 on: June 19, 2016, 05:48:47 am »
i need help please.


Offline Gertjan

  • Hero Member
  • *****
  • Posts: 2700
  • Karma: +219/-9
    • View Profile
Re: send() failed (40: Message too long)
« Reply #17 on: June 19, 2016, 05:56:58 pm »
@tosman61 : a dns with 0.0.0.0 doesn't shock you ?
The log also show up using a single WAN  ?
Your are using the captive portal on LAN ?
Are you syslogging to a syslog server (on LAN) ?

Offline quikmcw

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #18 on: November 15, 2016, 06:24:21 am »
I'm getting this error, a lot.  How can you view the messages that are too long ??

Offline Gertjan

  • Hero Member
  • *****
  • Posts: 2700
  • Karma: +219/-9
    • View Profile
Re: send() failed (40: Message too long)
« Reply #19 on: November 15, 2016, 12:41:21 pm »
I'm getting this error, a lot.  How can you view the messages that are too long ??
tcpdump ?

Offline krashneo

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #20 on: November 16, 2016, 04:07:10 pm »
Dear all,

I was looking for someting in nginx-error.log and I found this:

2016/11/16 19:16:53 [alert] 33631#100096: send() failed (40: Message too long)
2016/11/16 19:16:53 [error] 33631#100096: *1421957 upstream sent too big header while reading response header from upstream, client: 172.16.14.192, server: , request: "GET /index.php?zone=pucpcaldas&redirurl=http%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16.0.1%2Fhttp%3A%2F%2F172.16
2016/11/16 19:16:53 [alert] 33631#100096: send() failed (40: Message too long)


I think there is the problem, many redirects from the header...

I changed my form from:
<input name="redirurl" type="hidden" value="$PORTAL_REDIRURL$">

To:
<input name="redirurl" type="hidden" value="http://www.google.com">

to see the results... I will reply asap

Offline quikmcw

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #21 on: November 17, 2016, 09:24:04 am »
setup a syslogd to a server and the pfSense box is dumping the same error and not the full "too long" message
"nginx: 2016/11/17 08:36:08 [alert] 38209#100232: send() failed (40: Message too long)"

What happens for me is I get many of these messages then the system will not allow gui access and affects the openvpn sessions, but other traffic works as normal.

I'm running a SG-8860 box with the lastest version, no additional packages loaded, one internet connection, 4 subnets, 20 IPSecs and an average of 5 vpn's.

I need to know what these too log messages are to see what is causing the problem.

Offline quikmcw

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #22 on: November 17, 2016, 09:29:22 am »
just pulled this from the box:

            Crash report begins.  Anonymous machine information:

amd64
10.3-RELEASE-p9
FreeBSD 10.3-RELEASE-p9 #1 5fc1b19(RELENG_2_3_2): Tue Sep 27 12:25:49 CDT 2016     root@factory23-amd64-builder:/builder/factory-232/tmp/obj/builder/factory-232/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[17-Nov-2016 09:46:52 America/New_York] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /usr/local/www/diag_command.php on line 231
[17-Nov-2016 09:46:52 America/New_York] PHP Stack trace:
[17-Nov-2016 09:46:52 America/New_York] PHP   1. {main}() /usr/local/www/diag_command.php:0
[17-Nov-2016 09:46:52 America/New_York] PHP   2. exec() /usr/local/www/diag_command.php:231


Filename: /var/crash/minfree
2048

Offline JDvD

  • Jr. Member
  • **
  • Posts: 45
  • Karma: +1/-0
    • View Profile
    • Freelance: Tecnología Informática Redes Programación Creativo
Re: send() failed (40: Message too long)
« Reply #23 on: November 24, 2016, 10:12:18 am »
My pfsense is dumping the same error after upgrade 2.3.2-RELEASE (amd64).
2WAN - 1LAN - Proxy Transp - Captive Portal

Code: [Select]
nginx: 2016/11/24 11:58:30 [error] 18508#100108: send() failed (54: Connection reset by peer)
nginx: 2016/11/24 12:02:38 [alert] 74659#100142: send() failed (40: Message too long)

What happened?
USER ERROR: Replace user and press any key to continue ...

Offline nutel.pr

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #24 on: November 25, 2016, 12:55:23 pm »
Same problem in my pfsense, 2.3.2-RELEASE-p1 (amd64)
built on Tue Sep 27 12:13:07 CDT 2016
FreeBSD 10.3-RELEASE-p9


2016/11/25 15:13:07 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:13:38 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:13:40 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:14:12 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:14:27 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:14:41 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:15:36 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:15:49 [alert] 15518#100112: send() failed (40: Message too long)
2016/11/25 15:21:53 [alert] 15623#100082: send() failed (40: Message too long)
2016/11/25 15:23:19 [alert] 15623#100082: send() failed (40: Message too long)

Offline sisko212

  • Full Member
  • ***
  • Posts: 102
  • Karma: +2/-0
    • View Profile
    • A tribute to a real genius
Re: send() failed (40: Message too long)
« Reply #25 on: January 04, 2017, 06:18:01 am »
Same trouble with my pfsense after upgrade to 2.3.2 pi1, coming from pfsense 2.2.x
I didn't installed any Captive portal.
This issue looks related to the web interface, even if i can't be 100% sure.
I tried to remove all widgets from dashboard, switch from http to https, and taking a look from shell with "tail -f /var/log/nginx-error.log", an alert entry appears a couple times per minutes, instead once per second as before.

Offline Lampogriz

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #26 on: August 21, 2017, 06:22:50 am »
Same problem here, 2.3.4-RELEASE-p1 (amd64)

Offline stbird

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #27 on: September 08, 2017, 11:59:05 pm »
2.3.4-RELEASE-p1 (amd64)

captive portal

Any ideas for this problem?

Offline Lampogriz

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #28 on: January 15, 2018, 01:15:24 am »
Upgraded to 2.4.2 , still spams "send() failed (40: Message too long)" in log

Offline SouthPointHotel

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: send() failed (40: Message too long)
« Reply #29 on: January 29, 2018, 04:30:45 pm »
I am also getting these since upgrade.  Are there any logs that give more info?

Same here. help?