Re: segfault at 968 Error

2016-12-02 Thread VigneshDhanraj G
after loading libc symbols, gdb output as follows.

#0  0x7f90001cd790 in __pthread_initialize_minimal_internal () at
nptl-init.c:296
296 nptl-init.c: No such file or directory.
(gdb) bt
#0  0x7f90001cd790 in __pthread_initialize_minimal_internal () at
nptl-init.c:296
#1  0x7f90001cd209 in _init () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2  0x7f8c2000 in ?? ()
#3  0x7f9001289f09 in ?? () from /lib64/ld-linux-x86-64.so.2
#4  0x7f900128a0ce in ?? () from /lib64/ld-linux-x86-64.so.2
#5  0x7f900128e333 in ?? () from /lib64/ld-linux-x86-64.so.2
#6  0x7f9001289ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
#7  0x7f900128db1a in ?? () from /lib64/ld-linux-x86-64.so.2
#8  0x7f9000907760 in do_dlopen (ptr=0x7fffe9600e60) at dl-libc.c:86
#9  0x7f9001289ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
#10 0x7f90009077ff in dlerror_run (operate=0x7f90001cd762
<__pthread_initialize_minimal_internal+34>, args=0x1) at dl-libc.c:47
#11 0x7f90009078f7 in *__GI___libc_dlopen_mode (name=,
mode=) at dl-libc.c:160
#12 0x7f90008e0e94 in *__GI___nss_lookup_function (ni=0x24fce80,
fct_name=0x7f90009437c6 "gethostbyaddr_r") at nsswitch.c:434
#13 0x7f90008e16ab in *__GI___nss_next2 (ni=0x7fffe9600f88,
fct_name=0x7f90009437c6 "gethostbyaddr_r", fct2_name=0x0,
fctp=0x7fffe9600f80,
status=1, all_values=21518080) at nsswitch.c:271
#14 0x7f90008e7666 in __gethostbyaddr_r (addr=0x7fffe9601764, len=4,
type=, resbuf=0x7fffe9601610, buffer=,
buflen=, result=0x7fffe9601640, h_errnop=0x7fffe960164c)
at ../nss/getXXbyYY_r.c:274
#15 0x7f90008ece1d in *__GI_getnameinfo (sa=0x7fffe9601760,
addrlen=, host=0x69ac20 "UNKNOWN", hostlen=100,
serv=0x69aca0 "", servlen=100, flags=) at
getnameinfo.c:223

Is this is known issue??


On Fri, Dec 2, 2016 at 1:02 PM, VigneshDhanraj G  wrote:

> Thanks, same file consistently it is crashing.
>
> On Fri, Dec 2, 2016 at 12:44 PM,  wrote:
>
>> does it crash reproducable at the same file or is it randomly?
>>
>> Am 2. Dezember 2016 07:50:20 MEZ, schrieb VigneshDhanraj G <
>> vigneshdhanra...@gmail.com>:
>>
>>> Any update on this issue.
>>>
>>> On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G <
>>> vigneshdhanra...@gmail.com> wrote:
>>>
 Hi Team,

 While Running rsync rsync://username@ip:873 , I am getting following
 error.

 rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by
 peer (104)
 rsync error: error in rsync protocol data stream (code 12) at io.c(276)
 [Receiver=3.1.1]

 In Remote pc , i can see segmentation fault, dmesg gives following
 error. My remote PC using debian wheezy.

 rsync[9022]: segfault at 968 ip 7f90001cd790 sp 7fffe96008a0
 error 4 in libpthread-2.13.so[7f90001c8000+17000]

 gdb output: bt

 (gdb) bt
 #0  0x7fa75e8ab790 in __pthread_initialize_minimal_internal ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
 #1  0x7fa75e8ab209 in _init () from /lib/x86_64-linux-gnu/libpthre
 ad.so.0
 #2  0x7fa75e6a in ?? ()
 #3  0x7fa75f967f09 in ?? () from /lib64/ld-linux-x86-64.so.2
 #4  0x7fa75f9680ce in ?? () from /lib64/ld-linux-x86-64.so.2
 #5  0x7fa75f96c333 in ?? () from /lib64/ld-linux-x86-64.so.2
 #6  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
 #7  0x7fa75f96bb1a in ?? () from /lib64/ld-linux-x86-64.so.2
 #8  0x7fa75efe5760 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
 #9  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
 #10 0x7fa75efe57ff in ?? () from /lib/x86_64-linux-gnu/libc.so.6
 #11 0x7fa75efe58f7 in __libc_dlopen_mode () from
 /lib/x86_64-linux-gnu/libc.so.6
 #12 0x7fa75efbee94 in __nss_lookup_function () from
 /lib/x86_64-linux-gnu/libc.so.6
 #13 0x7fa75efbf6ab in __nss_next2 () from
 /lib/x86_64-linux-gnu/libc.so.6
 #14 0x7fa75efc5666 in gethostbyaddr_r () from
 /lib/x86_64-linux-gnu/libc.so.6
 #15 0x7fa75efcae1d in getnameinfo () from
 /lib/x86_64-linux-gnu/libc.so.6
 #16 0x00441002 in lookup_name ()
 #17 0x00440e3b in client_name ()
 #18 0x0044d566 in start_daemon ()
 #19 0x0043eb74 in start_accept_loop ()
 #20 0x0044da7e in daemon_main ()
 #21 0x00425751 in main ()

 strace output which shows segmentation fault.
 7241  read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0
 \0\3\0>\0\1\0\0\0\3008\0\0\0\0\0\0"..., 832) = 832
 7241  fstat(5, {st_mode=S_IFREG|0644, st_size=80712, ...}) = 0
 7241  mmap(NULL, 2185864, PROT_READ|PROT_EXEC,
 MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 0x7fd406a88000
 7241  mprotect(0x7fd406a9b000, 2093056, PROT_NONE) = 0
 7241  mmap(0x7fd406c9a000, 8192, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x12000) = 0x7fd406c9a000
 7241  

Re: segfault at 968 Error

2016-12-01 Thread VigneshDhanraj G
Thanks, same file consistently it is crashing.

On Fri, Dec 2, 2016 at 12:44 PM,  wrote:

> does it crash reproducable at the same file or is it randomly?
>
> Am 2. Dezember 2016 07:50:20 MEZ, schrieb VigneshDhanraj G <
> vigneshdhanra...@gmail.com>:
>
>> Any update on this issue.
>>
>> On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G <
>> vigneshdhanra...@gmail.com> wrote:
>>
>>> Hi Team,
>>>
>>> While Running rsync rsync://username@ip:873 , I am getting following
>>> error.
>>>
>>> rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by
>>> peer (104)
>>> rsync error: error in rsync protocol data stream (code 12) at io.c(276)
>>> [Receiver=3.1.1]
>>>
>>> In Remote pc , i can see segmentation fault, dmesg gives following
>>> error. My remote PC using debian wheezy.
>>>
>>> rsync[9022]: segfault at 968 ip 7f90001cd790 sp 7fffe96008a0
>>> error 4 in libpthread-2.13.so[7f90001c8000+17000]
>>>
>>> gdb output: bt
>>>
>>> (gdb) bt
>>> #0  0x7fa75e8ab790 in __pthread_initialize_minimal_internal () from
>>> /lib/x86_64-linux-gnu/libpthread.so.0
>>> #1  0x7fa75e8ab209 in _init () from /lib/x86_64-linux-gnu/libpthre
>>> ad.so.0
>>> #2  0x7fa75e6a in ?? ()
>>> #3  0x7fa75f967f09 in ?? () from /lib64/ld-linux-x86-64.so.2
>>> #4  0x7fa75f9680ce in ?? () from /lib64/ld-linux-x86-64.so.2
>>> #5  0x7fa75f96c333 in ?? () from /lib64/ld-linux-x86-64.so.2
>>> #6  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
>>> #7  0x7fa75f96bb1a in ?? () from /lib64/ld-linux-x86-64.so.2
>>> #8  0x7fa75efe5760 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
>>> #9  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
>>> #10 0x7fa75efe57ff in ?? () from /lib/x86_64-linux-gnu/libc.so.6
>>> #11 0x7fa75efe58f7 in __libc_dlopen_mode () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> #12 0x7fa75efbee94 in __nss_lookup_function () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> #13 0x7fa75efbf6ab in __nss_next2 () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> #14 0x7fa75efc5666 in gethostbyaddr_r () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> #15 0x7fa75efcae1d in getnameinfo () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> #16 0x00441002 in lookup_name ()
>>> #17 0x00440e3b in client_name ()
>>> #18 0x0044d566 in start_daemon ()
>>> #19 0x0043eb74 in start_accept_loop ()
>>> #20 0x0044da7e in daemon_main ()
>>> #21 0x00425751 in main ()
>>>
>>> strace output which shows segmentation fault.
>>> 7241  read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0
>>> \0\3\0>\0\1\0\0\0\3008\0\0\0\0\0\0"..., 832) = 832
>>> 7241  fstat(5, {st_mode=S_IFREG|0644, st_size=80712, ...}) = 0
>>> 7241  mmap(NULL, 2185864, PROT_READ|PROT_EXEC,
>>> MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 0x7fd406a88000
>>> 7241  mprotect(0x7fd406a9b000, 2093056, PROT_NONE) = 0
>>> 7241  mmap(0x7fd406c9a000, 8192, PROT_READ|PROT_WRITE,
>>> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x12000) = 0x7fd406c9a000
>>> 7241  mmap(0x7fd406c9c000, 6792, PROT_READ|PROT_WRITE,
>>> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fd406c9c000
>>> 7241  close(5)  = 0
>>> 7241  mprotect(0x7fd406c9a000, 4096, PROT_READ) = 0
>>> 7241  mprotect(0x7fd406ea2000, 4096, PROT_READ) = 0
>>> 7241  set_tid_address(0x7fd4080809d0)   = 7241
>>> 7241  --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>>> 6080  <... select resumed> )= ? ERESTARTNOHAND (To be
>>> restarted)
>>> 6080  --- SIGCHLD (Child exited) @ 0 (0) ---
>>> 6080  wait4(-1, NULL, WNOHANG, NULL)= 7241
>>> 6080  wait4(-1, NULL, WNOHANG, NULL)= -1 ECHILD (No child processes)
>>> 6080  rt_sigreturn(0x)  = -1 EINTR (Interrupted system
>>> call)
>>> 6080  select(5, [4], NULL, NULL, NULL 
>>>
>>> so, i have upgraded rsync to latest in my remote pc, but problem not get
>>> solved.
>>> Please help me to solve this.
>>>
>>> Regards,
>>> Vigneshdhanraj G
>>>
>>
>> --
>> Please use reply-all for most replies to avoid omitting the mailing list.
>> To unsubscribe or change options: 
>> https://lists.samba.org/mailman/listinfo/rsync
>> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>>
>>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.
>
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: segfault at 968 Error

2016-12-01 Thread devzero
does it crash reproducable at the same file or is it randomly?

Am 2. Dezember 2016 07:50:20 MEZ, schrieb VigneshDhanraj G 
:
>Any update on this issue.
>
>On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G <
>vigneshdhanra...@gmail.com> wrote:
>
>> Hi Team,
>>
>> While Running rsync rsync://username@ip:873 , I am getting following
>> error.
>>
>> rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset
>by
>> peer (104)
>> rsync error: error in rsync protocol data stream (code 12) at
>io.c(276)
>> [Receiver=3.1.1]
>>
>> In Remote pc , i can see segmentation fault, dmesg gives following
>error.
>> My remote PC using debian wheezy.
>>
>> rsync[9022]: segfault at 968 ip 7f90001cd790 sp 7fffe96008a0
>error
>> 4 in libpthread-2.13.so[7f90001c8000+17000]
>>
>> gdb output: bt
>>
>> (gdb) bt
>> #0  0x7fa75e8ab790 in __pthread_initialize_minimal_internal ()
>from
>> /lib/x86_64-linux-gnu/libpthread.so.0
>> #1  0x7fa75e8ab209 in _init () from /lib/x86_64-linux-gnu/
>> libpthread.so.0
>> #2  0x7fa75e6a in ?? ()
>> #3  0x7fa75f967f09 in ?? () from /lib64/ld-linux-x86-64.so.2
>> #4  0x7fa75f9680ce in ?? () from /lib64/ld-linux-x86-64.so.2
>> #5  0x7fa75f96c333 in ?? () from /lib64/ld-linux-x86-64.so.2
>> #6  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
>> #7  0x7fa75f96bb1a in ?? () from /lib64/ld-linux-x86-64.so.2
>> #8  0x7fa75efe5760 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
>> #9  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
>> #10 0x7fa75efe57ff in ?? () from /lib/x86_64-linux-gnu/libc.so.6
>> #11 0x7fa75efe58f7 in __libc_dlopen_mode () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #12 0x7fa75efbee94 in __nss_lookup_function () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #13 0x7fa75efbf6ab in __nss_next2 () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #14 0x7fa75efc5666 in gethostbyaddr_r () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #15 0x7fa75efcae1d in getnameinfo () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #16 0x00441002 in lookup_name ()
>> #17 0x00440e3b in client_name ()
>> #18 0x0044d566 in start_daemon ()
>> #19 0x0043eb74 in start_accept_loop ()
>> #20 0x0044da7e in daemon_main ()
>> #21 0x00425751 in main ()
>>
>> strace output which shows segmentation fault.
>> 7241  read(5,
>"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3008\0\0\0\0\0\0"...,
>> 832) = 832
>> 7241  fstat(5, {st_mode=S_IFREG|0644, st_size=80712, ...}) = 0
>> 7241  mmap(NULL, 2185864, PROT_READ|PROT_EXEC,
>MAP_PRIVATE|MAP_DENYWRITE,
>> 5, 0) = 0x7fd406a88000
>> 7241  mprotect(0x7fd406a9b000, 2093056, PROT_NONE) = 0
>> 7241  mmap(0x7fd406c9a000, 8192, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x12000) = 0x7fd406c9a000
>> 7241  mmap(0x7fd406c9c000, 6792, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fd406c9c000
>> 7241  close(5)  = 0
>> 7241  mprotect(0x7fd406c9a000, 4096, PROT_READ) = 0
>> 7241  mprotect(0x7fd406ea2000, 4096, PROT_READ) = 0
>> 7241  set_tid_address(0x7fd4080809d0)   = 7241
>> 7241  --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>> 6080  <... select resumed> )= ? ERESTARTNOHAND (To be
>> restarted)
>> 6080  --- SIGCHLD (Child exited) @ 0 (0) ---
>> 6080  wait4(-1, NULL, WNOHANG, NULL)= 7241
>> 6080  wait4(-1, NULL, WNOHANG, NULL)= -1 ECHILD (No child
>processes)
>> 6080  rt_sigreturn(0x)  = -1 EINTR (Interrupted
>system
>> call)
>> 6080  select(5, [4], NULL, NULL, NULL 
>>
>> so, i have upgraded rsync to latest in my remote pc, but problem not
>get
>> solved.
>> Please help me to solve this.
>>
>> Regards,
>> Vigneshdhanraj G
>>
>
>
>
>
>-- 
>Please use reply-all for most replies to avoid omitting the mailing
>list.
>To unsubscribe or change options:
>https://lists.samba.org/mailman/listinfo/rsync
>Before posting, read:
>http://www.catb.org/~esr/faqs/smart-questions.html

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: segfault at 968 Error

2016-12-01 Thread VigneshDhanraj G
Any update on this issue.

On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G <
vigneshdhanra...@gmail.com> wrote:

> Hi Team,
>
> While Running rsync rsync://username@ip:873 , I am getting following
> error.
>
> rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by
> peer (104)
> rsync error: error in rsync protocol data stream (code 12) at io.c(276)
> [Receiver=3.1.1]
>
> In Remote pc , i can see segmentation fault, dmesg gives following error.
> My remote PC using debian wheezy.
>
> rsync[9022]: segfault at 968 ip 7f90001cd790 sp 7fffe96008a0 error
> 4 in libpthread-2.13.so[7f90001c8000+17000]
>
> gdb output: bt
>
> (gdb) bt
> #0  0x7fa75e8ab790 in __pthread_initialize_minimal_internal () from
> /lib/x86_64-linux-gnu/libpthread.so.0
> #1  0x7fa75e8ab209 in _init () from /lib/x86_64-linux-gnu/
> libpthread.so.0
> #2  0x7fa75e6a in ?? ()
> #3  0x7fa75f967f09 in ?? () from /lib64/ld-linux-x86-64.so.2
> #4  0x7fa75f9680ce in ?? () from /lib64/ld-linux-x86-64.so.2
> #5  0x7fa75f96c333 in ?? () from /lib64/ld-linux-x86-64.so.2
> #6  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
> #7  0x7fa75f96bb1a in ?? () from /lib64/ld-linux-x86-64.so.2
> #8  0x7fa75efe5760 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #9  0x7fa75f967ba6 in ?? () from /lib64/ld-linux-x86-64.so.2
> #10 0x7fa75efe57ff in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #11 0x7fa75efe58f7 in __libc_dlopen_mode () from
> /lib/x86_64-linux-gnu/libc.so.6
> #12 0x7fa75efbee94 in __nss_lookup_function () from
> /lib/x86_64-linux-gnu/libc.so.6
> #13 0x7fa75efbf6ab in __nss_next2 () from
> /lib/x86_64-linux-gnu/libc.so.6
> #14 0x7fa75efc5666 in gethostbyaddr_r () from
> /lib/x86_64-linux-gnu/libc.so.6
> #15 0x7fa75efcae1d in getnameinfo () from
> /lib/x86_64-linux-gnu/libc.so.6
> #16 0x00441002 in lookup_name ()
> #17 0x00440e3b in client_name ()
> #18 0x0044d566 in start_daemon ()
> #19 0x0043eb74 in start_accept_loop ()
> #20 0x0044da7e in daemon_main ()
> #21 0x00425751 in main ()
>
> strace output which shows segmentation fault.
> 7241  read(5, 
> "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3008\0\0\0\0\0\0"...,
> 832) = 832
> 7241  fstat(5, {st_mode=S_IFREG|0644, st_size=80712, ...}) = 0
> 7241  mmap(NULL, 2185864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE,
> 5, 0) = 0x7fd406a88000
> 7241  mprotect(0x7fd406a9b000, 2093056, PROT_NONE) = 0
> 7241  mmap(0x7fd406c9a000, 8192, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x12000) = 0x7fd406c9a000
> 7241  mmap(0x7fd406c9c000, 6792, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fd406c9c000
> 7241  close(5)  = 0
> 7241  mprotect(0x7fd406c9a000, 4096, PROT_READ) = 0
> 7241  mprotect(0x7fd406ea2000, 4096, PROT_READ) = 0
> 7241  set_tid_address(0x7fd4080809d0)   = 7241
> 7241  --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> 6080  <... select resumed> )= ? ERESTARTNOHAND (To be
> restarted)
> 6080  --- SIGCHLD (Child exited) @ 0 (0) ---
> 6080  wait4(-1, NULL, WNOHANG, NULL)= 7241
> 6080  wait4(-1, NULL, WNOHANG, NULL)= -1 ECHILD (No child processes)
> 6080  rt_sigreturn(0x)  = -1 EINTR (Interrupted system
> call)
> 6080  select(5, [4], NULL, NULL, NULL 
>
> so, i have upgraded rsync to latest in my remote pc, but problem not get
> solved.
> Please help me to solve this.
>
> Regards,
> Vigneshdhanraj G
>
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html