I get an error message after configuring my EPIA M10000 as a media director. It went through all of the installing fine, did the av setup screen. But now when it starts up I get a progress bar and when that finishes:Orbiter cannot register with the router. Please try again later.I do not even know where to begin troubleshooting this.

/sbin/ifconfig | pg - this will list your network interfaces. if you went with the defaults, eth0 should be DHCP and obtain an IP Address from your router, eth1 should be in the range of 192.168.80.xxx and should be static.

Try to ping the following addresses from the command line of the core:

1) 127.0.0.12) the ip listed by eth03) the ip listed by eth14) www.google.com

If these all come back ok, then try and post your logs here and we'll see what we can sort.

If any of the above fail, let us know and we'll see if we can work it out!

I just installed it for the first time with .42. I could ping all those just fine. Heres some logs. I didnt know which ones you needed. In DCERouter.log that was repeated over and over and over. I noticed in the syslog that it could not start the log for the Media Director due to permissions.??

Yes I've just gone through a dozen installs of v42 on MiniITX each time tried something different but I get the above too. I also notice that flickr.pl keeps spawning more and more eating around 200mb of memory each which gets to a point of a load avg of 20 and no longer responds.

I tried an install of v39 which gets updates nd that fails too. That was my last fullly working version.

To add I was using it fine on v39 as a media director but v42 wont work. now I notcied that there is an ALSA warning about needing to try dxs_support=5 I have no idea if that was there before though. I'm going to give it a closer look as could it have broken between versions?

Perhaps the orbitor is having trouble because the media director is not working?

I did have one instance of the avwizard locking up on the sound bit. I've tried no sound at all but not no luck. I may next try disabling the sound card completely and see what it does.

This is one of the issues that made me give up with Pluto for the time being. I found that DCERouter often died on my core; restarting it solved the problem of the orbiter not being able to connect.

I'm currently running MiniMyth as a front end, which has increased the WAF no end.

Hi,

maybe this info is too late for you, but anyway. In current Pluto release I also see that DCERouter is unresponsive from time to time and even on reloads it is stucked frequently. Manually killing it's own process helps for a bit.

Pluto guys say that they fixed the problem, but it will be in next release (0.43)...