Great, I didn´t know about how to hable SIG35 (first time using gdb
I saw several logs like these
[2017/2/15 3:13:3] WARNING: write signal 35: Bad file descriptor
[2017/2/15 3:13:4] WARNING: write signal 35: Bad file descriptor
[2017/2/15 3:13:5] WARNING: write signal 35: Bad file descriptor
[2017/2/15 3:13:6] WARNING: write signal 35: Bad file descriptor
[2017/2/15 3:13:7] WARNING: write signal 35: Bad file descriptor
[2017/2/15 3:13:8] WARNING: write signal 35: Bad file descriptor
[2017/2/15 3:13:9] WARNING: write signal 35: Bad file descriptor
And finally:
[2017/2/15 3:13:30] DEBUG: Sending Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,Map-Reply->
flags:P=1,E=0,S=0,Map-Reply-> flags:P=1,E=0,S=0,ecord-count: 1, nonce:
9473ea437bfbf19e
*Program received signal SIGSEGV, Segmentation fault.*
0x0003e8a4 in get_interface_with_address (address=address@entry=0xbefff7a4)
at iface_list.c:354
354 glist_for_each_entry(iface_it,interface_list){
(gdb)
(gdb)
(gdb)
(gdb)
(gdb)
(gdb) bt
#0 0x0003e8a4 in get_interface_with_address (address=address@entry=0xbefff7a4)
at iface_list.c:354
#1 0x00021660 in tun_control_dp_get_output_ctrl_sock (data=0x68cb0,
udp_conn=udp_conn@entry=0xbefff7a4) at
control/control-data-plane/tun/cdp_tun.c:411
#2 0x00021784 in tun_control_dp_send_msg (ctrl=<optimized out>,
buff=0xb6e01a90, udp_conn=0xbefff7a4) at
control/control-data-plane/tun/cdp_tun.c:191
#3 0x0001ddf0 in tr_recv_map_request (uc=0xbefff7a4, buf=<optimized out>,
xtr=0xb6de8150) at control/lisp_xtr.c:467
#4 xtr_recv_msg (dev=0xb6de8150, msg=<optimized out>, uc=0xbefff7a4) at
control/lisp_xtr.c:2127
#5 0x00021228 in tun_control_dp_recv_msg (sl=<optimized out>) at
control/control-data-plane/tun/cdp_tun.c:171
#6 0x0003a40c in sock_process_fd (lst=0xb6de8070, fdset=0xb6de8080) at
lib/sockets.c:245
#7 sockmstr_process_all (m=0xb6de8070) at lib/sockets.c:271
#8 0x000123ec in main (argc=<optimized out>, argv=<optimized out>) at
oor.c:503
I will keep gdb console open, in case you need something else.
El mié., 15 feb. 2017 a las 3:09, Florin Coras (<fcoras.li...@gmail.com>)
escribió:
Hi,
Did you try: handle SIG35 noprint nostop?
Florin
On Feb 14, 2017, at 10:00 PM, José Miguel Guzmán <jmguz...@whitestack.com>
wrote:
I have been trying to run it under gdb, but I am not sure if I am doing it
correctly
When running in gdb, it fails immediately (not the same when running w/o
gdb)
With gdb:
*# rm /var/run/oor.pid; gdb --directory /root/oor-1.1.1/oor /usr/sbin/oor*
[2017/2/15 2:58:55] WARNING: No Proxy-ETR defined. Packets to non-LISP
destinations will be forwarded natively (no LISP encapsulation). This may
prevent mobility in some scenarios.
Program received signal SIG35, Real-time event 35.
0xb6fd41a4 in __clone () from /lib/ld-musl-armhf.so.1
(gdb) bt full
#0 0xb6fd41a4 in __clone () from /lib/ld-musl-armhf.so.1
No symbol table info available.
#1 0xb6fd4ec8 in ?? () from /lib/ld-musl-armhf.so.1
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I am not sure if this is what you need.
El mié., 15 feb. 2017 a las 2:37, Lori Jakab (<lorand.ja...@gmail.com>)
escribió:
On Wed, Feb 15, 2017 at 4:47 AM, José Miguel Guzmán <jmguz...@whitestack.com
> wrote:
Hi
I think I understand the configuration of OOR much better now, but I
realized that OOR is crashing (about every 30m)
[...]
What kind of information would be useful to collect, to be able to
troubleshoot?
Is it possible to start OOR under gdb on OpenWrt? In that case, when the
segmentation fault occurs you can get a backtrace, which would show the
call graph causing the crash.
-Lori
--
*José Miguel Guzmán*Senior Network Consultant
Latin America & Caribbean
+1 (650) 248-2490 <+16502482490>
+56 (9) 9064-2780 <+56990642780>
jmguz...@whitestack.com
jmguzmanc
_______________________________________________
Users mailing list
Users@openoverlayrouter.org
http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
--
*José Miguel Guzmán*Senior Network Consultant
Latin America & Caribbean
+1 (650) 248-2490 <+16502482490>
+56 (9) 9064-2780 <+56990642780>
jmguz...@whitestack.com
jmguzmanc
_______________________________________________
Users mailing list
Users@openoverlayrouter.org
http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
