Author Topic: initialize_LMdevice connect failure  (Read 3632 times)

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5501
  • DOES work for LinuxMCE.
    • View Profile
Re: initialize_LMdevice connect failure
« Reply #15 on: October 17, 2008, 05:59:02 am »
okay, sorry bro... let me re-read everything in this thread thus far, and stir it around in my brain a bit.

-Thom

bblboy54

  • Guest
Re: initialize_LMdevice connect failure
« Reply #16 on: October 17, 2008, 06:03:09 am »
okay, sorry bro... let me re-read everything in this thread thus far, and stir it around in my brain a bit.

Thanks :)
I really am trying to help the best that I can.....  I could just reload but I saw a couple other posts about this same issue and I'd really like to help find a solution and give back to the community -- I just don't have coding experience :(

bblboy54

  • Guest
Re: initialize_LMdevice connect failure
« Reply #17 on: October 17, 2008, 10:15:17 am »
I found something that might be of some use....

/var/crash/_usr_pluto_bin_discovery.py.0.crash

Code: [Select]
ProblemType: Crash
Date: Wed Oct 15 16:38:26 2008
ExecutablePath: /usr/pluto/bin/discovery.py
InterpreterPath: /usr/bin/python2.5
ProcCmdline: /usr/bin/python /usr/pluto/bin/discovery.py
ProcCwd: /usr/pluto/bin
ProcEnviron:
 SHELL=/bin/sh
 PATH=/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/bin:/sbin:/bin:/usr/bin/X11
ProcMaps:
 08048000-0813f000 r-xp 00000000 08:01 114262653  /usr/bin/python2.5
 0813f000-08164000 rw-p 000f6000 08:01 114262653  /usr/bin/python2.5
 08164000-0825f000 rw-p 08164000 00:00 0          [heap]
 b7833000-b7874000 rw-p b7833000 00:00 0
 b7874000-b787e000 r-xp 00000000 08:01 142147780  /lib/libgcc_s.so.1
 b787e000-b787f000 rw-p 0000a000 08:01 142147780  /lib/libgcc_s.so.1
*snip* Left out the long list of loaded files... if they'd be helpful, I can post them
Code: [Select]
b7fd7000-b7fd9000 rw-p 00019000 08:01 142148034  /lib/ld-2.6.1.so
 bfa1d000-bfa48000 rw-p bfa1d000 00:00 0          [stack]
 ffffe000-fffff000 r-xp 00000000 00:00 0          [vdso]
ProcStatus:
 Name:  discovery.py
 State: R (running)
 SleepAVG:      0%
 Tgid:  15205
 Pid:   15205
 PPid:  15202
 TracerPid:     0
 Uid:   0       0       0       0
 Gid:   0       0       0       0
 FDSize:        32
 Groups:       
 VmPeak:           10120 kB
 VmSize:           10120 kB
 VmLck:        0 kB
 VmHWM:     6488 kB
 VmRSS:     6488 kB
 VmData:            3028 kB
 VmStk:      172 kB
 VmExe:      988 kB
 VmLib:     5492 kB
 VmPTE:       16 kB
 Threads:       1
 SigQ:  1/30079
 SigPnd:        0000000000000000
 ShdPnd:        0000000000000000
 SigBlk:        0000000000000000
 SigIgn:        0000000001001000
 SigCgt:        0000000180000002
 CapInh:        0000000000000000
 CapPrm:        00000000fffffeff
 CapEff:        00000000fffffeff
 Cpus_allowed:  0f
 Mems_allowed:  1
PythonArgs: ['/usr/pluto/bin/discovery.py']
Traceback:
 Traceback (most recent call last):
   File "/usr/pluto/bin/discovery.py", line 11, in <module>
     UDPSock.bind(addr)
   File "<string>", line 1, in bind
 error: (98, 'Address already in use')

This error occured on the last time the core was attempting to start.  I am also seeing the following in /var/log/messages multiple times:

Oct 15 16:40:50 dcerouter kernel: [ 2723.696000] RPC: failed to contact local rpcbind server (errno 5).

I'm not sure if those are related because I think the rpcbind has to do with NFS and I think discovery.py is complaining about bind/named....  I could be way off base as well but I thought I'd post this in case it jogged someone's mind.  I'm going to keep looking around to see if I can figure out anything else.


seth

  • Guru
  • ****
  • Posts: 485
  • A day w/o LinuxMCE is like a day w/o sunshine!
    • View Profile
Re: initialize_LMdevice connect failure
« Reply #18 on: October 17, 2008, 02:45:29 pm »
 ;)
Hey,

As you have changed the default internal network to a different ip range, and bind is incorporated into the system to provide services to the internal network provided by LMCE, it is possible that the bind configuration file needs to be updated to the modified internal IP. There are several places that are hardcoded with 192.168.80.x network address, it could be as simple as changing that file.

I am not sure where it is, and I am away from my system, so I can not look. Some places of interest:

a.) mysql server config = /etc/mysql/my.cnf (this could be in etc, but pluto does utilize its own directory structure for some things)
b.) For mysql mythtv, and pluto db information, there probably has to be a GRANT ALL bit run on the new internal network ip.
c.) NFS shares in /etc/exports are probably still set to 192.168.80.0/255.255.255.0
d.) Samba config files are also probably still referencing the 192.168.80.x network
e.) Apparently bind is also hard set in /etc/named.conf
f.) There can also be a future mythtv issue, check the /etc/mythtv/mysql.txt files (they could be many places, use 'find'
g.) There is probably some changes needing made also to the dhcp server settings as well

I understand this is circumventing the "recommended" settings. And I would never try it myself, but rather than scream "Infidel" at everything, which I know doesn't always happen, perhaps someone who knows the system better than myself can chime in, as to all the places the internal network is configured to the system.

Regards, and Best Wishes,  ;D

Seth
".....Because Once you've LinuxMCE'd....."
System stats located at my user page:

http://wiki.linuxmce.org/index.php/User:Seth

los93sol

  • Guru
  • ****
  • Posts: 396
    • View Profile
Re: initialize_LMdevice connect failure
« Reply #19 on: October 17, 2008, 02:54:22 pm »
I am interested to find out what binds us to the .80.x networks as well.  I wouldn't have been so hesitant to start playing if it weren't for that requirement, but I came up with my own solution that works quite well for me.  I simply picked up a cheap router, loaded dd-wrt firmware to it and setup a VLAN for LMCE to run on where it is seperate the rest of my network.  This lets me cut holes across so the two networks can talk when I want them to, but not interfere with my existing IP schema

bblboy54

  • Guest
Re: initialize_LMdevice connect failure
« Reply #20 on: October 17, 2008, 10:42:36 pm »
a.) mysql server config = /etc/mysql/my.cnf (this could be in etc, but pluto does utilize its own directory structure for some things)
b.) For mysql mythtv, and pluto db information, there probably has to be a GRANT ALL bit run on the new internal network ip.
c.) NFS shares in /etc/exports are probably still set to 192.168.80.0/255.255.255.0
d.) Samba config files are also probably still referencing the 192.168.80.x network
e.) Apparently bind is also hard set in /etc/named.conf
f.) There can also be a future mythtv issue, check the /etc/mythtv/mysql.txt files (they could be many places, use 'find'
g.) There is probably some changes needing made also to the dhcp server settings as well

All of the places you listed above actually do have the correct 192.168.5.xxx addresses so it seems that the configuration utility set everything up properly.  I didn't check the databases themselves, however, as I'm really not sure of the best way to do that.  Also, for reference, the mythbackend process is still running fine.  I can access mythweb and see that it is actually recording the shows that I have scheduled.....  it has the screen shots of the shows as well.  If mysql was really broken, I wouldn't think that myth would be able to function as well.

bblboy54

  • Guest
Re: initialize_LMdevice connect failure
« Reply #21 on: October 17, 2008, 11:59:26 pm »
It looks like DCERouter is encountering a segmentation fault.

Code: [Select]
root@dcerouter:/usr/pluto/bin# ./DCERouter
Copyright (C) 2004 Pluto, Inc., a Florida Corporation
www.plutohome.com
Phone: +1 (877) 758-8648
This program is distributed according to the terms of the Pluto Public License, available at:
http://plutohome.com/index.php?section=public_license
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the Pluto Public License for more details.
---------------

05 10/17/08 17:52:30.002 Loaded plug-in device: 3 master device: 10 -- ./File_Grids_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.003 Loaded plug-in device: 4 master device: 27 -- ./General_Info_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.004 Loaded plug-in device: 5 master device: 31 -- ./Climate_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.004 Loaded plug-in device: 6 master device: 9 -- ./Datagrid_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.005 Loaded plug-in device: 7 master device: 39 -- ./Infrared_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.005 Loaded plug-in device: 8 master device: 32 -- ./Lighting_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.006 Loaded plug-in device: 9 master device: 12 -- ./Orbiter_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.007 Loaded plug-in device: 10 master device: 2 -- ./Media_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.009 Loaded plug-in device: 11 master device: 34 -- ./Telecom_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.009 Loaded plug-in device: 12 master device: 52 -- ./Event_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.010 Loaded plug-in device: 13 master device: 33 -- ./Security_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.010 Loaded plug-in device: 14 master device: 1809 -- ./Plug_And_Play_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.011 Loaded plug-in device: 23 master device: 6 -- ./Xine_Plugin.so <0xb6bfc6c0>
05 10/17/08 17:52:30.012 Loaded plug-in device: 32 master device: 36 -- ./MythTV_PlugIn.so <0xb6bfc6c0>
05 10/17/08 17:52:30.103 Plugin 3 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.188 Plugin 4 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.271 Plugin 5 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.355 Plugin 6 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.439 Plugin 7 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.525 Plugin 8 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.644 Plugin 9 activated <0xb6bfc6c0>
01 10/17/08 17:52:30.740 Device_EntertainArea refers to a NULL device 1 17 <0xb6bfc6c0>
05 10/17/08 17:52:30.756 Plugin 10 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.841 Phone device 21 with extension 200 <0xb6bfc6c0>
01 10/17/08 17:52:30.845 Telecom_Plugin::GetConfig - no pbx device <0xb6bfc6c0>
05 10/17/08 17:52:30.845 Plugin 11 activated <0xb6bfc6c0>
05 10/17/08 17:52:30.934 Plugin 12 activated <0xb6bfc6c0>
05 10/17/08 17:52:31.022 Plugin 13 activated <0xb6bfc6c0>
05 10/17/08 17:52:31.105 Plugin 14 activated <0xb6bfc6c0>
05 10/17/08 17:52:31.187 Plugin 23 activated <0xb6bfc6c0>
05 10/17/08 17:52:31.279 Plugin 32 activated <0xb6bfc6c0>
08 10/17/08 17:52:31.292 Received Message from 11 (Telecom Plug-in / Crawl Space) to 0 (unknown / ), type 1 id 922 Command:Send Asterisk Status, retry retry, parameters: <0xa7eebb90>
05 10/17/08 17:52:31.326 MythTV_PlugIn::SetPaths: won't create tv_shows for device 0. We are probably out of sync! <0xb6bfc6c0>
05 10/17/08 17:52:31.326 MythTV_PlugIn::SetPaths: won't create tv_shows for device 0. We are probably out of sync! <0xb6bfc6c0>
05 10/17/08 17:52:31.326 MythTV_PlugIn::SetPaths: won't create tv_shows for device 0. We are probably out of sync! <0xb6bfc6c0>
Segmentation fault (core dumped)
root@dcerouter:/usr/pluto/bin#

I can provide the coredump if it would help anyone

bblboy54

  • Guest
Re: initialize_LMdevice connect failure
« Reply #22 on: October 18, 2008, 12:02:25 am »
Since it appears that the segfault is happening directly after it has a problem with the mythtv plugin is it possible to disable that plugin on startup for troubleshooting purposes?  Basically if I can tell it not to load the myth plugin and everthing works then we know that it has something to do with that plugin specifically.

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5501
  • DOES work for LinuxMCE.
    • View Profile
Re: initialize_LMdevice connect failure
« Reply #23 on: October 18, 2008, 01:16:02 am »
yes, it's the mythtv plugin. wow, how'd you do that? It honestly doesn't know where it is.

okay, in the web admin > advanced > configuration > devices

expand the DCERouter on the left, the MythTV Plugin is under there. Select the MytHtv PlugIn.

in the main area, there is a checkbox to disable the device. click it. save.. reload router.

boy, how did that happen? hmmm

-Thom

bblboy54

  • First post!
  • Posts: 1
    • View Profile
Re: initialize_LMdevice connect failure
« Reply #24 on: October 18, 2008, 02:43:18 am »
Upon a reboot I found this in dmesg:

Code: newbielink:javascript:void(0); [nonactive]
[   53.100000] ------------[ cut here ]------------
[   53.100000] kernel BUG at /build/buildd/linux-source-2.6.22-2.6.22/fs/nfsd/nfs4recover.c:400!
[   53.100000] invalid opcode: 0000 [#1]
[   53.100000] SMP
[   53.100000] Modules linked in: nfsd exportfs lockd sunrpc xt_TCPMSS ipt_MASQUERADE ipt_TTL iptable_mangle xt_tcpudp xt_mark xt_state iptable_nat iptable_filter ip_tables x_tables ppdev autofs4 cpufreq_ondemand cpufreq_powersave cpufreq_stats cpufreq_conservative freq_table cpufreq_userspace video sbs dock container ac button battery nf_nat_irc nf_nat_ftp nf_nat nf_conntrack_irc nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack nfnetlink lp wm8775 xpad hci_usb bluetooth cx25840 af_packet tuner ipv6 snd_usb_audio snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_usb_lib snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq ivtv snd_timer snd_seq_device i2c_algo_bit cx2341x tveeprom snd videodev v4l2_common v4l1_compat soundcore parport_pc parport pcspkr serio_raw psmouse i2c_amd8111 k8temp amd_rng i2c_amd756 i2c_core shpchp pci_hotplug evdev ext3 jbd mbcache sg sd_mod usbhid hid ide_cd cdrom ata_generic libata 3w_9xxx scsi_mod floppy ohci_hcd e100 mii tg3 usbcore amd74xx ide_core raid10 raid456 xor raid1 raid0 multipath linear md_mod thermal processor fan fuse apparmor commoncap
[   53.100000] CPU:    3
[   53.100000] EIP:    0060:[<f95567e0>]    Not tainted VLI
[   53.100000] EFLAGS: 00010202   (2.6.22-14-generic #1)
[   53.100000] EIP is at nfsd4_init_recdir+0x80/0x90 [nfsd]
[   53.100000] eax: 0000005c   ebx: f9565060   ecx: 00000046   edx: 00000001
[   53.100000] esi: 00000008   edi: 00000801   ebp: 00000002   esp: f5117ed8
[   53.100000] ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
[   53.100000] Process rpc.nfsd (pid: 7317, ti=f5116000 task=f5092f90 task.ti=f5116000)
[   53.100000] Stack: f955996c f9565060 00000000 00000000 00000000 f9550f98 00000000 00000000
[   53.100000]        00000000 00000000 f95395b8 f5117f26 f5117f26 00000002 f7806004 f953a19e
[   53.100000]        f6ef6180 00000000 00008001 00386314 000280d0 00000010 c16f00c0 f7132c80
[   53.100000] Call Trace:
[   53.100000]  [<f9550f98>] nfs4_state_start+0xf8/0x1c0 [nfsd]
[   53.100000]  [<f95395b8>] nfsd_svc+0x48/0x150 [nfsd]
[   53.100000]  [<f953a19e>] write_threads+0x6e/0xc0 [nfsd]
[   53.100000]  [<c01fed0e>] copy_from_user+0x2e/0x70
[   53.100000]  [<c019d418>] simple_transaction_get+0x98/0xb0
[   53.100000]  [<f953a130>] write_threads+0x0/0xc0 [nfsd]
[   53.100000]  [<f9539e35>] nfsctl_transaction_write+0x55/0x80 [nfsd]
[   53.100000]  [<c0180c4e>] vfs_write+0xbe/0x170
[   53.100000]  [<f9539de0>] nfsctl_transaction_write+0x0/0x80 [nfsd]
[   53.100000]  [<c0181361>] sys_write+0x41/0x70
[   53.100000]  [<c01041d2>] sysenter_past_esp+0x6b/0xa9
[   53.100000]  =======================
[   53.100000] Code: ee 56 f9 01 00 00 00 8b 54 24 08 8b 44 24 0c e8 47 ff ff ff 83 c4 10 5b c3 89 5c 24 04 c7 04 24 e4 99 55 f9 e8 52 24 bd c6 eb dc <0f> 0b eb fe 8d b6 00 00 00 00 8d bf 00 00 00 00 55 31 ed 57 89
[   53.100000] EIP: [<f95567e0>] nfsd4_init_recdir+0x80/0x90 [nfsd] SS:ESP 0068:f5117ed8

The same thing still is happening tho.  I checked the disabled box and save, did a quick reload, and then rebooted the core to be sure and I'm still getting the seg fault after MythTV_PlugIn.  If the DCERouter process isn't running, is it possible that configuration changes from the web admin aren't really changed?

seth

  • Guru
  • ****
  • Posts: 485
  • A day w/o LinuxMCE is like a day w/o sunshine!
    • View Profile
Re: initialize_LMdevice connect failure
« Reply #25 on: October 19, 2008, 10:57:19 pm »
Just out of curiosity, you don't have another mythbackend running soewhere do you?

".....Because Once you've LinuxMCE'd....."
System stats located at my user page:

http://wiki.linuxmce.org/index.php/User:Seth