Need extra help installing your Ooma Hub or Telo system? Let us know.
#55247 by abukta
Mon May 10, 2010 8:04 pm
I am getting on setup.ooma.com. I am trying to figure out my second handset keeps "searching..." instead of registering. I can't get the 2nd telo handset registered even though I have followed all the instruction. The 1st handset is working OK.

Does this "invalid pointer" exception have anything to do with this?

*** glibc detected *** ooma_cgi.cgi: munmap_chunk(): invalid pointer: 0xbee3ecc1 *** ======= Backtrace: ========= /lib/libc.so.6[0x4011a30c] ooma_cgi.cgi(templateFreeMem+0x264)[0x14f8c] ooma_cgi.cgi[0xf608] ooma_cgi.cgi[0xa7a4] ooma_cgi.cgi[0xa4d8] /lib/libc.so.6(__libc_start_main+0x118)[0x400bf364] ======= Memory map: ======== 00008000-0002f000 r-xp 00000000 fe:04 213 /home/httpd/cgi-bin/ooma_cgi.cgi 00037000-00038000 rwxp 00027000 fe:04 213 /home/httpd/cgi-bin/ooma_cgi.cgi 00038000-0005d000 rwxp 00000000 00:00 0 [heap] 40000000-4001e000 r-xp 00000000 fe:04 294 /lib/ld-2.10.1.so 4001e000-40022000 rwxp 00000000 00:00 0 40022000-40023000 rwxs 00000000 00:08 0 /SYSV34040226 (deleted) 40023000-40024000 rwxp 00000000 00:00 0 40025000-40026000 r-xp 0001d000 fe:04 294 /lib/ld-2.10.1.so 40026000-40027000 rwxp 0001e000 fe:04 294 /lib/ld-2.10.1.so 40027000-4002a000 r-xp 00000000 fe:04 383 /lib/libini.so 4002a000-40031000 ---p 00003000 fe:04 383 /lib/libini.so 40031000-40032000 rwxp 00002000 fe:04 383 /lib/libini.so 40032000-40033000 rwxp 00000000 00:00 0 40033000-40038000 r-xp 00000000 fe:04 298 /lib/libooma_util.so 40038000-4003f000 ---p 00005000 fe:04 298 /lib/libooma_util.so 4003f000-40040000 rwxp 00004000 fe:04 298 /lib/libooma_util.so 40040000-40042000 rwxp 00000000 00:00 0 40042000-40058000 r-xp 00000000 fe:04 379 /lib/libdict.so 40058000-4005f000 ---p 00016000 fe:04 379 /lib/libdict.so 4005f000-40060000 rwxp 00015000 fe:04 379 /lib/libdict.so 40060000-40063000 r-xp 00000000 fe:04 477 /lib/libopm.so 40063000-4006a000 ---p 00003000 fe:04 477 /lib/libopm.so 4006a000-4006b000 rwxp 00002000 fe:04 477 /lib/libopm.so 4006b000-4006c000 r-xp 00000000 fe:04 466 /lib/libmsg.so 4006c000-40074000 ---p 00001000 fe:04 466 /lib/libmsg.so 40074000-40075000 rwxp 00001000 fe:04 466 /lib/libmsg.so 40075000-40078000 r-xp 00000000 fe:04 481 /lib/libflate.so.1 40078000-4007f000 ---p 00003000 fe:04 481 /lib/libflate.so.1 4007f000-40080000 rwxp 00002000 fe:04 481 /lib/libflate.so.1 40080000-40089000 r-xp 00000000 fe:04 473 /lib/libshark-cgi.so.1 40089000-40091000 ---p 00009000 fe:04 473 /lib/libshark-cgi.so.1 40091000-40092000 rwxp 00009000 fe:04 473 /lib/libshark-cgi.so.1 40092000-40096000 rwxp 00000000 00:00 0 40096000-400a1000 r-xp 00000000 fe:04 470 /lib/libgcc_s.so.1 400a1000-400a9000 ---p 0000b000 fe:04 470 /lib/libgcc_s.so.1 400a9000-400aa000 rwxp 0000b000 fe:04 470 /lib/libgcc_s.so.1 400aa000-401e5000 r-xp 00000000 fe:04 282 /lib/libc-2.10.1.so 401e5000-401ec000 ---p 0013b000 fe:04 282 /lib/libc-2.10.1.so 401ec000-401ee000 r-xp 0013a000 fe:04 282 /lib/libc-2.10.1.so 401ee000-401ef000 rwxp 0013c000 fe:04 282 /lib/libc-2.10.1.so 401ef000-401f2000 rwxp 00000000 00:00 0 bee2a000-bee3f000 rw-p 00000000 00:00 0 [stack]
#55249 by southsound
Mon May 10, 2010 8:25 pm
I believe this may be the forewarning of a dire situation for mankind. It looks like there may be a tear in the time/space/voip continuum and unless someone of superior intellect is able to step in we are all doomed. I would dig a 3' wide hole about 6' deep and line it with tin foil - then deposit the offending device. Cover with about 2' of crushed rock and then flood with a mixture of water and unflavored gelatin. After curing, cover the hole with dirt and forget it ever happened. :shock:

Nah, that probably won't be necessary. Did you hold down the little antenna button for a few seconds to initiate the pairing process? I might try rebooting the Telo before giving up - the page of code is probably a browser-specific problem that has little to do with the pairing problem.

Here is another thread with the same glibc problem: http://www.ooma.com/forums/viewtopic.php?f=8&t=7576&p=53231&hilit=glibc#p53231
#55250 by abukta
Mon May 10, 2010 8:36 pm
Thanks southsound, I had a feeling it was red herring... but thought I ask. So I was able to clear, both, the error above and also the getting my 2nd handset work.

1) to get rid of the glibc junk ... I did a factory reset on telo.
2) to get my 2nd unit going, I had to do a factory reset on the handset itself.

I did not know about the second one so sent a note to support@oomacare.com and within 10min I had my answer thanks to Valentine (!!!). I have been having very good luck with their email support, it's been excellent for me.

Thanks Valentine, Luis, Emma and Elmer!
#55251 by southsound
Mon May 10, 2010 8:48 pm
I know you have been around a while since it says you joined in December of 2008 - but just in case no one has offered,

Welcome to ooma and to the forums! We're glad you're here!

Not to mention you accepted my attempt at levity and never missed a step! I'm glad things are working for you now and that customer support came through! :P
#55254 by abukta
Mon May 10, 2010 9:38 pm
Thanks for the welcoming words. I have been using for awhile with no problems (since 2008) so I am one of those happy customers (with lifetime premium subscr) and had no reason to really post anything :) . Hey, I hope you don't mind, now that I have my 2 handset working I have updated my signature... I hope yours isn't copy protected. Cheers.
#55255 by southsound
Mon May 10, 2010 9:44 pm
abukta wrote:Thanks for the welcoming words. I have been using for awhile with no problems (since 2008) so I am one of those happy customers (with lifetime premium subscr) and had no reason to really post anything :) . Hey, I hope you don't mind, now that I have my 2 handset working I have updated my signature... I hope yours isn't copy protected. Cheers.

Quite alright! And since your tenure predates mine, I think I'd have a hard time fighting for a copyright anyways.

Who is online

Users browsing this forum: No registered users and 11 guests