add -a option to journalctl
On Mon, Feb 10, 2020 at 6:19 PM Nuno Ferreira wrote:
> Hi Daniel,
>
> I noticed that you already moved the ERR log to DBG in the pipe limit
> module. Did you have the opportunity to look at the other 2 errors?
> Glad if I can help, but I will need some directions espe
Hi Daniel,
I noticed that you already moved the ERR log to DBG in the pipe limit
module. Did you have the opportunity to look at the other 2 errors?
Glad if I can help, but I will need some directions especially about
the place where the "[466B blob data]" is getting printed.
Thanks,
Nuno
On Wed
Hi,
http_reply_parse is not present in the configs. I've explicitly set it as
"no" and the result is the same. If I set it as "yes", topos complains like
this:
Jan 22 15:00:10 proxy1 kamailio[29316]: ERROR: topos [topos_mod.c:282]:
tps_prepare_msg(): cannot parse cseq header
Thank you,
Nuno
On
Hello,
do you have http_reply_parse=yes ?
The error is from topos catching the http reply being sent out and
trying to handle it.
Cheers,
Daniel
On 22.01.20 12:34, Nuno Ferreira wrote:
> Hi,
>
> I'm using kamailio 5.2.4 (topos enabled) and HTTP 1.1
> Here's ngrep output:
>
> T 127.0.0.1:32
Hi,
I'm using kamailio 5.2.4 (topos enabled) and HTTP 1.1
Here's ngrep output:
T 127.0.0.1:32322 -> 127.0.0.1:8000 [AP]
POST /RPC HTTP/1.1.
User-Agent: curl/7.29.0.
Host: 127.0.0.1:8000.
Accept: */*.
Content-Type: application/json.
Content-Length: 75.
.
{"id": 1, "jsonrpc": "2.0", "method": "
Hello,
what version of kamailio are you using and what http version is curl
using? Can you paste here the http request taken with ngrep from the
network?
Cheers,
Daniel
On 21.01.20 19:00, Nuno Ferreira wrote:
> Hi Daniel,
>
> There's no other traffic than the HTTP requests.
> This comment in src
Hi Daniel,
There's no other traffic than the HTTP requests.
This comment in src/core/parser/parse_fline.c 99 - 113, caugh my attention:
} else if (http_reply_parse != 0 &&
(*tmp=='H' || *tmp=='h') &&
/* 'HTTP/1.' */
strncasecmp( tmp+1, HTTP_VERSION+1, HTTP_VERSION_LEN-1)==0 &&
/* [0|1] */
((*(tm
Hello,
as I said, watch the traffic on port 8000 with ngrep or some other
network sniffer to see what data comes there. You can also start
kamailio with debug=3 in config, more debug logs should be printed to
syslog to get the context of what is processed at that time.
Cheers,
Daniel
On 21.01.20
Hi Daniel,
Thanks for your feedback.
I have a dedicated listen directive for JSONRPC
listen = 127.0.0.1:8000
and then an event_route for it:
event_route[xhttp:request] {
if ($Rp != 8000) {
xhttp_reply("403", "Forbidden", "text/html",
"Forbidden");
exit;
}
if ($hu =~ "^
Hello,
can you want the traffic on port 8000 and see if there is no
"unexpected" traffic there? There should be no error message for parsing
the first line of an HTTP request.
The error message related the missing pipe can be made debug.
Cheers,
Daniel
On 21.01.20 15:34, Nuno Ferreira wrote:
>
10 matches
Mail list logo
