Jimbodude, that sounds just like my scenario. Just a little more info on it, my system was completely unresponsive and appeared to be in a swap of death. My hard drive light was stuck on and I could not log in to it from any where. After about 20 minutes of trying, I hard powered off the machine. That is when these problems started. This also happened on the same machine on the 7.10 series and is actually the reason why I switched to the beta. What I am going to suggest is that this folder get cleared early on in startup. Has anyone entered a ticket yet? If not, I will. If so, post it here.

OK, the networking problems are in several other threads. I just couldn't read them since my networking was down. 

I was just going to say that. Try deleting those files (I can't remember where but it ends with /pluto/lock) and rebooting. That fixed it for me.

That looks like a mounting error or a kernel error. To debug this I would look to see if /lib/modules/2.6.27-14-generic/ has been mounted properly. If so, then running depmod -a on the media director should generate that file. If it isn't mounted, then maybe test to see if that location is exported properly. I'm not going to be much help on the latter part as I am unsure how that section works.

OK, that's not the same problem I had then.   

One thing I found was that my systems would sometimes wait for quite a while doing something after a fresh rebuild. I would come back later and it was all fine and dandy.

fido, have you done apt-get update, apt-get dist-upgrade on the media director? Just curious if that has been done or if it fixed your problem.

I do believe your remote will be fixed by doing the following on your media director:
apt-get update
apt-get dist-upgrade

Can you log in at your moon ** login? I had mine recently stop working (no idea yet) and it appears that the network connection turned itself off. If you try and login at moon ** login and it just halts, then you have the same symptoms that I do.

OK, so I deleted everything in pluto's lock folder. Then I rebooted. Almost everything came back to normal. I had to go into the webadmin and turn off the firewall (don't know why) so that it would route packets again. Other than that, it seems to be working. Well, except that I'm having some trouble booting a media director but I think that is a different problem.

Thanks for the help!

DCERouter.log wasn't even getting created, I launched it manually and it started.
I had something looping forever and I think it was LaunchManager (at work right now).

First thing when I get home is to kill all the lock files and reboot. Maybe it is just that simple. Here's hoping!   

My system crashed over the weekend and I rebooted it. Now a bunch of things are not working when it boots up. I had this happen before on the older version (7 series) and that is when I switched over to the 8.10 alpha. I am completely up to date on everything.

If I run "/usr/pluto/bin/Start_DCERouter.sh" then it starts manually, but I am sure that is not the only thing broken as any client on the network now has no Internet access. DNS works, but packets do not route through the core machine.

I just reinstalled a ton of packages (basically pluto-*) and rebooted a few times. I don't even know what logs to look at. Oh and my UUID for one of my drives got changed so it wouldn't auto-mount. I updated the database and it started working, but only after I created /mnt/device.

Basically I had a craptacular weekend. Any help as to where to start looking? I really don't feel like wiping the system out and starting over again. I will, but I'd rather understand what is going on than just blindly wipe my disk.

Thanks, I'll test this once I get my core to start working again. I forgot that I had manually run that on a previous run. Is there any was of doing that automagically? A script that will trigger that, or something? Not a big deal, but if there is a shortcut I'll take it.

I ran apt-get dist-upgrade on my system and it crashed later (unrelated I think) so the first reboot in a while and nothing is working quite right. None of my extra disks are getting auto-mounted and the log shows:

1 Tue Aug 18 22:27:03 PDT 2009 23331 CALLED TO MOUNT DEVICE 67
2 Tue Aug 18 22:27:03 PDT 2009 23331 Cannot find hal object with volume.uuid =

I look and it looks like the UUID for the partition is different than what the LinuxMCE has for it. Also, it will not route any network traffic now. I had to unplug all my systems from behind my core and plug them in front of the core to get access to the Internets. I guess I'm just having a bad week.

After all the wonderful work Thom did, my remote was working perfectly. I rebuilt my media director over the weekend (just clicked the button that said rebuild) and the buttons are no longer all working. Forward, rewind, etc. work but not Power, Play, nor Pause. I haven't been able to test all the buttons yet, but I could not get those important ones to work.

Any help in trying to diagnose this?

Most modern power supplies can automatically switch between different voltages (110-240). This unit appears to have an external power supply. So, worst case, you can replace the supply with one that works in your region. Almost everything I have works in all the countries I travel to. Even my Philip's 42 LCD works in 110-240 volt ranges.

Very nice! Might I suggest gathering up all of the videos (Thom's various feature demos, howtos, etc.) and placing them on the videos page? They don't even have to be hosted by linuxmce but could all be YouTube.