Hello,
I'm not familiar with coding, however attached is the man for the writev on the
system. Help this can provide some additional information.
Thanks,
Kevin
Date: Wed, 18 Aug 2010 19:50:24 +0200
From: mico...@gmail.com
To: kevin....@hotmail.com; sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Kamailio 3.0 cann't access the RTPProxy
On 8/17/10 7:14 PM, KevinJin wrote:
Hello Daniel,
What does the nathelper error messages mean?
==========
hmm, invalid argurment ... try with this line:
LM_ERR("can't send command to a RTP proxy (%s/%d) [sock %d (%d), vcnt %d]\n",
strerror(errno), errno, rtpp_socks[node->idx],
node->idx, vcnt);
maybe will give some hints about which value is invalid.
Here's the log after the change:
4(14415) ERROR: nathelper [nathelper.c:2457]: can't send command to a RTP proxy
(Invalid argument/22) [sock 7 (0), vcnt 18]
can you check the manual page for writev on your system to see what are
possible reasons for 'Invalid argument' error (error code 22)? The values in
between [...] are just some debug values I wanted to see, not error codes or so.
Cheers,
Daniel
4(14415) ERROR: nathelper [nathelper.c:2492]: proxy <udp:210.13.x.y:7722> does
not respond, disable it
4(14415) ERROR: nathelper [nathelper.c:3144]: no available proxies
Thanks,
Kevin
From: kevin....@hotmail.com
To: mico...@gmail.com
Subject: RE: [SR-Users] Kamailio 3.0 cann't access the RTPProxy
Date: Tue, 17 Aug 2010 18:51:02 +0800
Hi Daniel,
Attached are the two kamailio logs,
unix_socket_log --- run rtp proxy wth -s unix:/tmp/rtpproxy.sock
udp_rtpproxy_log --- run rtp proxy with -s udp:*:7722
Please help to check what's wrong with it.
Thanks,
Kevin
Date: Tue, 17 Aug 2010 11:29:46 +0200
From: mico...@gmail.com
To: kevin....@hotmail.com
CC: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Kamailio 3.0 cann't access the RTPProxy
Hello,
please send full log at startup, your snippets include just few lines per
process, being mixed from different processes.
Cheers,
Daniel
On 8/14/10 3:54 AM, KevinJin wrote:
Hello,
Date: Thu, 12 Aug 2010 22:16:18 +0200
From: mico...@gmail.com
To: kevin....@hotmail.com
CC: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Kamailio 3.0 cann't access the RTPProxy
Hello,
On 8/12/10 8:34 PM, KevinJin wrote:
Hello,
Date: Thu, 12 Aug 2010 18:46:19 +0200
From: mico...@gmail.com
To: kevin....@hotmail.com
CC: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Kamailio 3.0 cann't access the RTPProxy
Hello,
On 8/12/10 4:47 PM, KevinJin wrote:
Hi Daniel,
What does the log below means? Does it mean nathelper has issue to send the
request to RTP proxy first or nathelper doesn't receive a response after
sending a request to the rtp proxy?
0(27429) ERROR: nathelper [nathelper.c:2457]: can't send command to a RTP proxy
this error is printed when write to socket fails. Do you have any firewall
running on the system? Is the user under which kamailio runs allowed to write
to sockets?
There's no firewall on the system, and I run the kamailio as root,
root 26310 1 0 02:24:19 ? 0:00
/usr/local/kamailio-3.0.2/sbin/kamailio -f /usr/local/kamailio-3.0.2/etc/kamail
You can edit module_k/nathelper/nathelper.c and replace the line 2457 with:
LM_ERR("can't send command to a RTP proxy (%s/%d)\n", strerror(errno), errno);
Recompile and reinstall. Hopefully will get more hints about what happens.
Here is the error message after the change:
2(26312) ERROR: nathelper [nathelper.c:2457]: can't send command to a RTP
proxy(Invalid argument/22)
2(26312) ERROR: nathelper [nathelper.c:2492]: proxy <udp:210.13.124.15:7722>
does not respond, disable it
2(26312) ERROR: nathelper [nathelper.c:3144]: no available proxies
what could be the cause?
hmm, invalid argurment ... try with this line:
LM_ERR("can't send command to a RTP proxy (%s/%d) [sock %d (%d), vcnt %d]\n",
strerror(errno), errno, rtpp_socks[node->idx],
node->idx, vcnt);
maybe will give some hints about which value is invalid.
Here's the log after the change:
4(14415) ERROR: nathelper [nathelper.c:2457]: can't send command to a RTP proxy
(Invalid argument/22) [sock 7 (0), vcnt 18]
4(14415) ERROR: nathelper [nathelper.c:2492]: proxy <udp:210.13.x.y:7722> does
not respond, disable it
4(14415) ERROR: nathelper [nathelper.c:3144]: no available proxies
Can you try as well with an unix file socket:
modparam("nathelper", "rtpproxy_sock", "unix:/tmp/rtpproxy.sock")
then start rtpproxy with -s unix:/tmp/rtpproxy.sock
4(17530) INFO: nathelper [nathelper.c:2369]: rtp proxy
<unix:/tmp/rtpproxy.sock> found, support for it re-enabled
3(17529) ERROR: nathelper [nathelper.c:2429]: can't send command to a RTP proxy
3(17529) ERROR: nathelper [nathelper.c:2492]: proxy <unix:/tmp/rtpproxy.sock>
does not respond, disable it
3(17529) ERROR: nathelper [nathelper.c:3144]: no available proxies
Thanks,
Kevin
I have no solaris (sparc) to try myself...
Cheers,
Daniel
Test env:
UA1 (Behind NAT) --------> Kamailio & RTPproxy (Public IP) --------->UA2
(Public IP)
Thanks,
Kevin
Cheers,
Daniel
0(27429) ERROR: nathelper [nathelper.c:2492]: proxy <udp:210.13.124.15:7722>
does not respond, disable it
There's no problem for the resource(CPU, mem etc.) on the server, the load is
very low.
Thanks in advance!
----------
0(27429) DEBUG: nathelper [nhelpr_funcs.c:148]: type <application/sdp> found
valid
0(27429) ERROR: nathelper [nathelper.c:3144]: no available proxies
0(27429) ERROR: nathelper [nathelper.c:2627]: no available proxies
0(27429) DEBUG: nathelper [nhelpr_funcs.c:148]: type <application/sdp> found
valid
0(27429) INFO: nathelper [nathelper.c:2369]: rtp proxy
<udp:210.13.124.15:7722> found, support for it re-enabled
0(27429) DEBUG: nathelper [nathelper.c:3196]: proxy reply: 42040 210.13.124.14
0(27429) DEBUG: nathelper [nhelpr_funcs.c:148]: type <application/sdp> found
valid
0(27429) ERROR: nathelper [nathelper.c:2457]: can't send command to a RTP proxy
0(27429) ERROR: nathelper [nathelper.c:2492]: proxy <udp:210.13.124.15:7722>
does not respond, disable it
0(27429) ERROR: nathelper [nathelper.c:3144]: no available proxies
0(27429) ERROR: nathelper [nathelper.c:2627]: no available proxies
Thanks,
Kevin
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com/
--
Daniel-Constantin Mierla
http://www.asipto.com/
--
Daniel-Constantin Mierla
http://www.asipto.com/
--
Daniel-Constantin Mierla
http://www.asipto.com/
man writev
Reformatting page. Please Wait... done
System Calls write(2)
NAME
write, pwrite, writev - write on a file
SYNOPSIS
#include <unistd.h>
ssize_t write(int fildes, const void *buf, size_t nbyte);
ssize_t pwrite(int fildes, const void *buf, size_t nbyte,
off_t offset);
#include <sys/uio.h>
ssize_t writev(int fildes, const struct iovec *iov, int iovcnt);
DESCRIPTION
The write() function attempts to write nbyte bytes from the
buffer pointed to by buf to the file associated with the
open file descriptor, fildes.
If nbyte is 0, write() will return 0 and have no other
results if the file is a regular file; otherwise, the
results are unspecified.
On a regular file or other file capable of seeking, the
actual writing of data proceeds from the position in the
file indicated by the file offset associated with fildes.
Before successful return from write(), the file offset is
incremented by the number of bytes actually written. On a
regular file, if this incremented file offset is greater
than the length of the file, the length of the file will be
set to this file offset.
If the O_SYNC bit has been set, write I/O operations on the
file descriptor complete as defined by synchronized I/O file
integrity completion.
If fildes refers to a socket, write() is equivalent to
send(3SOCKET) with no flags set.
On a file not capable of seeking, writing always takes place
starting at the current position. The value of a file
offset associated with such a device is undefined.
SunOS 5.10 Last change: 14 Aug 2007 1
System Calls write(2)
If the O_APPEND flag of the file status flags is set, the
file offset will be set to the end of the file prior to each
write and no intervening file modification operation will
occur between changing the file offset and the write opera-
tion.
For regular files, no data transfer will occur past the
offset maximum established in the open file description with
fildes.
A write() to a regular file is blocked if mandatory
file/record locking is set (see chmod(2)), and there is a
record lock owned by another process on the segment of the
file to be written:
o If O_NDELAY or O_NONBLOCK is set, write() returns
-1 and sets errno to EAGAIN.
o If O_NDELAY and O_NONBLOCK are clear, write()
sleeps until all blocking locks are removed or the
write() is terminated by a signal.
If a write() requests that more bytes be written than there
is room for-for example, if the write would exceed the pro-
cess file size limit (see getrlimit(2) and ulimit(2)), the
system file size limit, or the free space on the device-only
as many bytes as there is room for will be written. For
example, suppose there is space for 20 bytes more in a file
before reaching a limit. A write() of 512-bytes returns 20.
The next write() of a non-zero number of bytes gives a
failure return (except as noted for pipes and FIFO below).
If write() is interrupted by a signal before it writes any
data, it will return -1 with errno set to EINTR.
If write() is interrupted by a signal after it successfully
writes some data, it will return the number of bytes writ-
ten.
If write() exceeds the process file size limit, the applica-
tion generates a SIGXFSZ signal, whose default behavior is
to dump core.
After a write() to a regular file has successfully returned:
SunOS 5.10 Last change: 14 Aug 2007 2
System Calls write(2)
o Any successful read(2) from each byte position in
the file that was modified by that write will
return the data specified by the write() for that
position until such byte positions are again modi-
fied.
o Any subsequent successful write() to the same byte
position in the file will overwrite that file data.
Write requests to a pipe or FIFO are handled the same as a
regular file with the following exceptions:
o There is no file offset associated with a pipe,
hence each write request appends to the end of the
pipe.
o Write requests of {PIPE_BUF} bytes or less are
guaranteed not to be interleaved with data from
other processes doing writes on the same pipe.
Writes of greater than {PIPE_BUF} bytes may have
data interleaved, on arbitrary boundaries, with
writes by other processes, whether or not the
O_NONBLOCK or O_NDELAY flags are set.
o If O_NONBLOCK and O_NDELAY are clear, a write
request may cause the process to block, but on nor-
mal completion it returns nbyte.
o If O_NONBLOCK and O_NDELAY are set, write() does
not block the process. If a write() request for
PIPE_BUF or fewer bytes succeeds completely
write() returns nbyte. Otherwise, if O_NONBLOCK is
set, it returns -1 and sets errno to EAGAIN or if
O_NDELAY is set, it returns 0. A write() request
for greater than {PIPE_BUF} bytes transfers what
it can and returns the number of bytes written or
it transfers no data and, if O_NONBLOCK is set,
returns -1 with errno set to EAGAIN or if O_NDELAY
is set, it returns 0. Finally, if a request is
greater than PIPE_BUF bytes and all data previously
written to the pipe has been read, write()
transfers at least PIPE_BUF bytes.
When attempting to write to a file descriptor (other than a
pipe, a FIFO, a socket, or a STREAM) that supports nonblock-
ing writes and cannot accept the data immediately:
o If O_NONBLOCK and O_NDELAY are clear, write()
blocks until the data can be accepted.
SunOS 5.10 Last change: 14 Aug 2007 3
System Calls write(2)
o If O_NONBLOCK or O_NDELAY is set, write() does not
block the process. If some data can be written
without blocking the process, write() writes what
it can and returns the number of bytes written.
Otherwise, if O_NONBLOCK is set, it returns -1 and
sets errno to EAGAIN or if O_NDELAY is set, it
returns 0.
Upon successful completion, where nbyte is greater than 0,
write() will mark for update the st_ctime and st_mtime
fields of the file, and if the file is a regular file, the
S_ISUID and S_ISGID bits of the file mode may be cleared.
For STREAMS files (see intro(2) and streamio(7I)), the
operation of write() is determined by the values of the
minimum and maximum nbyte range ("packet size") accepted by
the STREAM. These values are contained in the topmost STREAM
module, and can not be set or tested from user level. If
nbyte falls within the packet size range, nbyte bytes are
written. If nbyte does not fall within the range and the
minimum packet size value is zero, write() breaks the
buffer into maximum packet size segments prior to sending
the data downstream (the last segment may be smaller than
the maximum packet size). If nbyte does not fall within the
range and the minimum value is non-zero, write() fails and
sets errno to ERANGE. Writing a zero-length buffer (nbyte is
zero) to a STREAMS device sends a zero length message with
zero returned. However, writing a zero-length buffer to a
pipe or FIFO sends no message and zero is returned. The
user program may issue the I_SWROPT ioctl(2) to enable
zero-length messages to be sent across the pipe or FIFO (see
streamio(7I)).
When writing to a STREAM, data messages are created with a
priority band of zero. When writing to a socket or to a
STREAM that is not a pipe or a FIFO:
o If O_NDELAY and O_NONBLOCK are not set, and the
STREAM cannot accept data (the STREAM write queue
is full due to internal flow control conditions),
write() blocks until data can be accepted.
o If O_NDELAY or O_NONBLOCK is set and the STREAM
cannot accept data, write() returns -1 and sets
errno to EAGAIN.
o If O_NDELAY or O_NONBLOCK is set and part of the
buffer has already been written when a condition
occurs in which the STREAM cannot accept additional
SunOS 5.10 Last change: 14 Aug 2007 4
System Calls write(2)
data, write() terminates and returns the number of
bytes written.
The write() and writev() functions will fail if the STREAM
head had processed an asynchronous error before the call.
In this case, the value of errno does not reflect the result
of write() or writev() but reflects the prior error.
pwrite()
The pwrite() function performs the same action as write(),
except that it writes into a given position without changing
the file pointer. The first three arguments to pwrite() are
the same as write() with the addition of a fourth argument
offset for the desired position inside the file.
writev()
The writev() function performs the same action as write(),
but gathers the output data from the iovcnt buffers speci-
fied by the members of the iov array: iov[0], iov[1], ...,
iov[iovcnt-1]. The iovcnt buffer is valid if greater than 0
and less than or equal to {IOV_MAX}. See intro(2) for a
definition of {IOV_MAX}.
The iovec structure contains the following members:
caddr_t iov_base;
int iov_len;
Each iovec entry specifies the base address and length of an
area in memory from which data should be written. The wri-
tev() function always writes all data from an area before
proceeding to the next.
If fildes refers to a regular file and all of the iov_len
members in the array pointed to by iov are 0, writev() will
return 0 and have no other effect. For other file types,
the behavior is unspecified.
If the sum of the iov_len values is greater than SSIZE_MAX,
the operation fails and no data is transferred.
RETURN VALUES
Upon successful completion, write() returns the number of
bytes actually written to the file associated with fildes.
This number is never greater than nbyte. Otherwise, -1 is
returned, the file-pointer remains unchanged, and errno is
SunOS 5.10 Last change: 14 Aug 2007 5
System Calls write(2)
set to indicate the error.
Upon successful completion, writev() returns the number of
bytes actually written. Otherwise, it returns -1, the
file-pointer remains unchanged, and errno is set to indicate
an error.
ERRORS
The write(), pwrite(), and writev() functions will fail if:
EAGAIN Mandatory file/record locking is set, O_NDELAY or
O_NONBLOCK is set, and there is a blocking record
lock; an attempt is made to write to a STREAM
that can not accept data with the O_NDELAY or
O_NONBLOCK flag set; or a write to a pipe or FIFO
of PIPE_BUF bytes or less is requested and less
than nbytes of free space is available.
EBADF The fildes argument is not a valid file descrip-
tor open for writing.
EDEADLK The write was going to go to sleep and cause a
deadlock situation to occur.
EDQUOT The user's quota of disk blocks on the file sys-
tem containing the file has been exhausted.
EFBIG An attempt is made to write a file that exceeds
the process's file size limit or the maximum file
size (see getrlimit(2) and ulimit(2)).
EFBIG The file is a regular file, nbyte is greater than
0, and the starting position is greater than or
equal to the offset maximum established in the
file description associated with fildes.
EINTR A signal was caught during the write operation
and no data was transferred.
EIO The process is in the background and is attempt-
ing to write to its controlling terminal whose
TOSTOP flag is set, or the process is neither
ignoring nor blocking SIGTTOU signals and the
process group of the process is orphaned.
SunOS 5.10 Last change: 14 Aug 2007 6
System Calls write(2)
ENOLCK Enforced record locking was enabled and
{LOCK_MAX} regions are already locked in the
system, or the system record lock table was full
and the write could not go to sleep until the
blocking record lock was removed.
ENOLINK The fildes argument is on a remote machine and
the link to that machine is no longer active.
ENOSPC During a write to an ordinary file, there is no
free space left on the device.
ENOSR An attempt is made to write to a STREAMS with
insufficient STREAMS memory resources available
in the system.
ENXIO A hangup occurred on the STREAM being written to.
EPIPE An attempt is made to write to a pipe or a FIFO
that is not open for reading by any process, or
that has only one end open (or to a file descrip-
tor created by socket(3SOCKET), using type
SOCK_STREAM that is no longer connected to a peer
endpoint). A SIGPIPE signal will also be sent to
the thread. The process dies unless special pro-
visions were taken to catch or ignore the signal.
ERANGE The transfer request size was outside the range
supported by the STREAMS file associated with
fildes.
The write() and pwrite() functions will fail if:
EFAULT The buf argument points to an illegal address.
EINVAL The nbyte argument overflowed an ssize_t.
The pwrite() function fails and the file pointer remains
unchanged if:
SunOS 5.10 Last change: 14 Aug 2007 7
System Calls write(2)
ESPIPE The fildes argument is associated with a pipe or
FIFO.
The write() and writev() functions may fail if:
EINVAL The STREAM or multiplexer referenced by fildes is
linked (directly or indirectly) downstream from a
multiplexer.
ENXIO A request was made of a non-existent device, or
the request was outside the capabilities of the
device.
ENXIO A hangup occurred on the STREAM being written to.
A write to a STREAMS file may fail if an error message has
been received at the STREAM head. In this case, errno is
set to the value included in the error message.
The writev() function may fail if:
EINVAL The iovcnt argument was less than or equal to 0 or
greater than {IOV_MAX}; one of the iov_len values
in the iov array was negative; or the sum of the
iov_len values in the iov array overflowed an
ssize_t.
USAGE
The pwrite() function has a transitional interface for 64-
bit file offsets. See lf64(5).
ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
SunOS 5.10 Last change: 14 Aug 2007 8
System Calls write(2)
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Interface Stability | Committed |
|_____________________________|_____________________________|
| MT-Level | write() is Async-Signal-Safe|
|_____________________________|_____________________________|
| Standard | See standards(5). |
|_____________________________|_____________________________|
SEE ALSO
intro(2), chmod(2), creat(2), dup(2), fcntl(2),
getrlimit(2), ioctl(2), lseek(2), open(2), pipe(2),
ulimit(2), send(3SOCKET), socket(3SOCKET), attributes(5),
lf64(5), standards(5), streamio(7I)
SunOS 5.10 Last change: 14 Aug 2007 9_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
