LinuxMCE Forums
General => Users => Topic started by: daballiemo on July 16, 2011, 09:31:52 am
-
Hi all,
haven't done update for a while because the system was running ok. Now in a situation where I had to rebuild on of my MD ended in the situation where it keeps rebooting due to the nvidia script. As I know it was solved in an update I went ahead and updated the system (core & MD's. All went ok but the orbiter on the 7970, it was showing the "Loading, please wait" screen and alternativly "Loading....." and "Requesting" line beneath it - forever.
Went ahead and did:
- full regen and reload
- full regen/reload again followed by a core reboot & phone reboot
- deleted phone, rebooted core and ..... connect the phone to power again.
there the other fun starts, because somehow the phone is still known in Asterisk its registered. Deleted the extension in FreePBX and it keeps on working ???
LMCE however does not detect a new phone... So no orbiter.
tia
Han
-
We'll it went even further, after my actions Asterisk is running at 100% CPU and all of my SCCP extensions are in status "Registering" but they never do...
I have a feeling that I am heading towards a reinstall pfff
-
Stumbled upon this thread;
http://forum.linuxmce.org/index.php?topic=4885.0 (http://forum.linuxmce.org/index.php?topic=4885.0)
and checked my /etc/asterisk/sccp.conf which was indeed contain stuff on deleted phones, so I cleaned it out leaving nothing after the file comments but [devices] and [lines]
Rebooted the system and Asterisk is back to normal. So I'll start to add the SCCP phones again.
Han
-
Phones are added again but still my 7970 is showing the image Linux MCE Orbiter Loading please wait.... just after showing "Invalid phone IP 192.168.80.132" ???
I am out of options now, anybody any clue?
tia
Han
-
Don't know if this helps but I had a similar problem once and found that another device had the same IP as my 7970. In my case it was a panasonic web cam. I changed the ip on the webcam and the phone started working.
Randy
-
Possy helped me out a bit and during that it showed that also my weborbiter was not working anymore:
<What i see in syslog is:
Jul 16 18:01:50 dcerouter kernel: [ 425.802102] Proxy_Orbiter[23045]: segfault at 0 ip b6ff2591 sp b6408c9c error 4 in libc-2.8.90.so[b6f92000+158000]
Jul 16 18:01:52 dcerouter kernel: [ 427.331838] Proxy_Orbiter[23162]: segfault at 0 ip b715e591 sp b6574c9c error 4 in libc-2.8.90.so[b70fe000+158000]
Jul 16 18:02:03 dcerouter kernel: [ 438.474038] Proxy_Orbiter[23421]: segfault at 0 ip b7040591 sp b6456c9c error 4 in libc-2.8.90.so[b6fe0000+158000]
Jul 16 18:02:04 dcerouter kernel: [ 439.565751] Proxy_Orbiter[23481]: segfault at 0 ip b70bb591 sp b64d1c9c error 4 in libc-2.8.90.so[b705b000+158000]
Jul 16 18:02:17 dcerouter kernel: [ 452.227106] Proxy_Orbiter[23864]: segfault at 0 ip b6fa5591 sp b63bbc9c error 4 in libc-2.8.90.so[b6f45000+158000]
Jul 16 18:02:19 dcerouter kernel: [ 454.662555] Proxy_Orbiter[23901]: segfault at 0 ip b7057591 sp b646dc9c error 4 in libc-2.8.90.so[b6ff7000+158000]
Jul 16 18:02:29 dcerouter kernel: [ 464.579347] Proxy_Orbiter[24645]: segfault at 0 ip b700b591 sp b6421c9c error 4 in libc-2.8.90.so[b6fab000+158000]
Jul 16 18:02:32 dcerouter kernel: [ 467.575313] Proxy_Orbiter[24688]: segfault at 0 ip b6f91591 sp b63a7c9c error 4 in libc-2.8.90.so[b6f31000+158000]
Jul 16 18:02:42 dcerouter kernel: [ 477.014975] Proxy_Orbiter[25054]: segfault at 0 ip b6fe0591 sp b63f6c9c error 4 in libc-2.8.90.so[b6f80000+158000]
Jul 16 18:02:47 dcerouter kernel: [ 482.298064] Proxy_Orbiter[25234]: segfault at 0 ip b7001591 sp b6417c9c error 4 in libc-2.8.90.so[b6fa1000+158000]
I have already re-installed pluto-proxy-orbiter, removed it from the local repo and reinstalled it again, all having the same result.
dcerouter_1015593:~# dpkg -l|grep pluto-proxy
ii pluto-proxy-orbiter 2.0.0.44.11071324189 <insert up to 60 chars description>
dcerouter_1015593:~#
Anybody shed any light on this?
-
Problem solved;
After talking to Possy & Uplink on #linuxmce it showed that a directory was missing; /usr/pluto/orbiter/bits. Just did a simple mkdir bits and for one the weborbiter is up and running again.
thx to all
Han
-
Hello guys,
I have the same issue with my c7970.
Also I have dpkg -l|grep pluto-proxy
ii pluto-proxy-orbiter 2.0.0.44.11071324189 <insert up to 60 chars description>
I create /usr/pluto/orbiter/bits but c7970 didn't connect.
If I do a ls for /usr/pluto/orbiter/bits i get only one directory called "174". that is the weborbiter device, the ID for 7970 orbiter is "54".
I made a full regenerate for my c7970 orbiter but nothing happens.
What can I do now?
Thanks in advance.
Hernan
-
Hey now it works, what I did was:
create /usr/pluto/orbiter/bits
Reboot core
full regenerate 7970 orbiter
reload router.
Then orbiter at C7970 begins to work.
Thanks
Hernan
-
Don't know if this helps but I had a similar problem once and found that another device had the same IP as my 7970. In my case it was a panasonic web cam. I changed the ip on the webcam and the phone started working.
Randy
Randy,
you were right! It showed that somewhere in the whole proces all !! of my embedded phones had the mac address and ip address of the 7970. I cannot see why this would happen, probably my DB got screwed. I deleted all of the MD embedded phones. After that I added them again. Then hooked up my 7970, which was directly autodetected and added.
grtz
Han