LinuxMCE Forums
Archive => Archive => Pluto Main General Issues => Topic started by: archived on November 26, 2005, 12:49:26 am
-
Obviously, I'm new here. I'm trying to find a package to begin managing a couple things at home. The first 2 targets will be security (exiting Caddx NX-8E with the NX-540 automation card) and thermostats (I plan to buy HAI Omnistats soon). Someone suggested Pluto home.
I downloaded the image yesterday. My main system runs Windows, and I can't change it right now, so I'm trying to install just the core on a spare laptop. I realize this is pretty minimal, but I'm hoping it will be enough to get me started and then I can decide on an upgrade path later.
The install appears to go ok, but when it's done I am not able to get to the admin screen via a web browser. It times out. I then try rebooting. When it comes up, I get a flashing red message DCERouter status: "not responding on socket. Probably dead". When I look at the log I see an error message saying "Cannot initialize plug-in for device: 13". I tried some searches, but I can't determine what is device 13, what's wrong with it, or if that's even the cause of the problem.
Can anyone help?
-
I had the same message whan first insatalling build .32, after checking the MD5 sum was good I burnt a new CD at a slower speed (24x) and was able to complete a good install from this CD.
HTH
Russell
-
Thanks Russel. I'll try burning a new CD.
-
Well, the new CD helped. The error 13 is gone. However, I still can't get to the admin web page. When I try pinging anything on my network it says "Network is unreachable".
-
Perhaps I should give up on Pluto and work on Misterhouse instead. :(
-
piper_chuck
PostPosted: 29 Nov 2005 11:53 Post subject:
Well, the new CD helped. The error 13 is gone. However, I still can't get to the admin web page. When I try pinging anything on my network it says "Network is unreachable".
Hi,
how many nic cards are you having?
sounds like a network problem ...
please provide more info about your installation, hybrid or core?
if the network is unreachable we cannot enter with remote assistance to help you
-
Perhaps I should give up on Pluto and work on Misterhouse instead. :(
Hi,
don't give up, it'll pay you off at the end. BTW, you don't need to choose between MH and Pluto - you can use them both - search forums for 'misterhouse'...
I'm going through similar story....
Regards,
Rob.
-
Rob, thanks for the support. I guess I'll work on the 2 things in parallel. Fortunately, I can run MH on a Windows machine that I know is working right.
Dan, the laptop I'm installing on has a small hard drive so I went minimal and only installed the core. I also said no to DHCP because I need to keep DHCP in my router right now. The laptop only has one NIC. I agree it sounds like a network problem.
When it comes up I get an IP address in the 24.25.5. range, does that sound right? I can ping that address from other computers at home, but when I ping from the laptop it fails. I don't see the laptop in the router's list of DCHP clients.
I've considered installing a standard Linux distribution just to see if that would work.
Update after typing the above. The address the laptop is coming up with is that of the roadrunner DNS. This doesn't seem right.
-
I did a bit of research and found some tips saying it's almost certainly a routing problem.
"If you get 'Network is unreachable' messages when you try to access the network, then the routing information specified in /etc/pcmcia/network.opts is incorrect. This exact message is an absolutely foolproof indication of a routing error. On the other hand, mis-configured cards will usually fail silently."
I'll check into it tonight.
-
Still no luck. Well, no GOOD luck! :( I tried a bunch of different things. I can't get Linux to talk to the network. I tried enabling DHCP in /etc/pcmcia/network.opts. Didn't work. Tried coding a static IP address, didn't work. No matter what I change, it's just not willing to talk to anyone else.
The odd thing is the network card seems to work just fine during install. Can someone confirm that things are downloaded during install? Once the install is finished it seems Linux gets dumb and forgets how to talk to the network.
Anyway, I'm trying one last install. Once it's finished I'll try enabling DHCP one more time. The installs are easy, it's not like I've been able to customize anything yet. It takes clock time, but I can do other things, such as working on my Misterhouse configuration, while it's running.
-
I also just noticed that during install it's got an address from DHCP in the router. Ping from one of my other machines to this address works. It's obvious that the card works, and that Linux has the necessary drivers, but something is messed up when the install is finished.
-
Anyone have any ideas? I've reinstalled and set dhcp to yes in the /etc/pcmcia/network.opts file. Still not working.
-
Guess not. Oh well. I'm off to get a full distribution of Linux and see if that works. Maybe I'll give Pluto another try sometime later. Meanwhile, if anyone's got an idea on what was wrong with the Pluto distribution, send me a PM.
-
Sorry for not answering before. I only now found some time to go through my stack of assigned topics.
If you can ping the DHCP-assigned address from your network (i.e. you get replies back) then networking is working on that laptop.
You sound like the DHCP server on your network gives the 24.25.5.x IP to the laptop so it has to be correct, right? It should give network unreachable since you can ping it. You don't say what your network configuration is. You have a DHCP server that assigns... 24.25.5.x (i.e. routable) IP addresses? Parameters go like this: Gateway, Netmask (I can compute the network address from this in my head), DNS, IP range the DHCP server assigns to your network.
Also see what "ip route" and "ip addr" say and post that here (if you're still with us that is...)
-
Hi, the router is configured to give back 192.168.1.1xx addresses. When I brought up the Pluto machine, it did not appear in the router's DHCP list, although I recall seeing it there at some point during the install. The address Pluto seems to have gotten hung up on is the DNS address. The reason I can ping this address from other machines on my network is not because networking is working on the Pluto machine, but because the DNS is running, at my ISP.
Anyway, at this point I've tried another Linux distribution, Fedora. Came up first try, got a 192.168.1.1nn address, and all networking is fine. This helps me know that there's not a problem in my network, laptop, or with Linux support for this machine. It must be something in the Linux configuration for Pluto. Note, I'm just trying to isolate the problem, not trying to place blame. :D
I can't give you ip route or addr info since Pluto's not longer there. From memory, ip addr showed no address for the eth0 interface. I'd still like to get Pluto running, at some point in the future I'd like to start building a media center. However, I need a fix for the networking problem before I can go any further.
-
Weird. Pluto should have taken an address from the DHCP server and if it could not do that at install time, it would have asked you to input that data manually, so there's no real way the Pluto system would have decided on its own to use your provider's DNS IP address.
-
Obviously there's something going wrong during install. I've done several installs, same thing happened every time.
-
Try this:
At install time, disconnect the network cable until it passed the DHCP autodiscovery phase and then plug it back in. Then, input the network parameters by hand. I can find some time to discover what goes wrong with DHCP if this works.
-
Fortunately, I haven't actually done anything with the linux that I installed, so I guess I can wipe it out. If get some time tonight, I can try installing Pluto again. This will be about the 6th install. :cry: Any idea how far into the install it does the DHCP access?
-
To be safe, just disconnect the machine's network until you reach that step and it asks you about IP address. This step is in stage 1, after you booted the CD, before the partitioning.
-
Got it.
-
CD portion of the install is finished. It's going through the stuff that happens after the CD is ejected. I manually set the address to 192.168.1.110 at the suggested time and then plugged in the cable. The install seems to be going well and I'm able to ping the address from other machines on this network. Still waiting for the install to finish.
-
AAAAAAARRRRRRRRRRRRGGGGGGGGGGGGG :x :x :x :x :x
Here's what happened.
Install finished fine. I rebooted when asked and everything appeared to be going ok. I could still ping from other machines. Sometime during the boot, ping no longer worked. When the boot finally completed, the IP address reported on the DCERouter status screen is: 24.25.5.150. I know for a FACT that I entered this as the DNS address during install. There's a bug somewhere in the code that's confusing the real IP address with that of the DNS. During install I chose core, no DHCP server.
Meanwhile, MH is working great on my Windows machine!
-
Oh boy. This is going to be hard to track down... since it actually works for everybody else (including us).
Under these circumstanced, I have to ask:
How willing are you to help solve this problem?
How good are you with MySQL, vim/nano/a console text editor, Linux? (MySQL knowledge isn't really needed if I go into the system).
Because, if you're not fed up yet, and Pluto is still on that machine, I can guide you to manually set the networking back and enable remote assistance so I can get into the machine and understand what's going on.
-
I'll do what I can to help. Pluto is still on the system. While I'm far from a Linux expert, if you tell me the files and changes I can make them. I've never done anything with MySQL.
-
The file you have to change is /etc/network/interfaces . It's contents at this point should be self-explanatory, but in any event, it should look something like this:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 1.1.1.2
netmask 255.255.255.0
gateway 1.1.1.1
The 1.1.1.1 and 1.1.1.2 IPs are samples here.
After you saved this file, run this
/etc/init.d/networking restart
Also check that in your /etc/resolv.conf file you have the correct nameserver:nameserver 1.1.1.3
This should get your network online (until you reboot, since the actual settings are in the datbase).
To allow me access into the system you have to enable Remote Assistance. There are two ways to do this:
1. from the Pluto Admin website, go to Wizard -> Security -> Outside access, tick the "Allow Pluto tech support temporary access using this password" checkbox, write the password twice and click Update
2. from the console, run /usr/pluto/bin/RA.sh and follow the instructions
After you enabled this, send me your installation number and the password you wrote in there to this address: radu.c _at_ plutohome.com
Tell me if the system is going to be online all the time, or just in a certain hour interval so I can sync.
-
Here's what I found (and fixed):
Interfaces:
auto lo
iface lo inet loopback
auto 24.25.5.150
iface 24.25.5.150 inet static
address 24.25.5.150
netmask 24.25.5.150
gateway 24.25.5.150
Resolver file was correct. And I finally have a Pluto admin screen on another system!!! YAY!!!
-
Fixed in SVN, revision 6366.