Media Directors hanging

[DeathMagnetic]

I've just finished setting up 9 media directors and every one of them hangs after the line:

restarting openbsd secure shell server sshd
...done

I've tried opening a shell and trying startx but I'm told I'm not allowed (probably because I'm logged in as sambahelper). Have I missed something? I'm sure one of the media directors was working when it was on it's own, now nothing boots except the server.

EDIT: The webadmin page says they're all amd64 architecture but they're i386. The thing is, the media director that was working was set as amd64 the whole time and worked fine. When I changed it to i386 and rebuit the image it failed. I also can't seem to delete any of the media directors from the system.

[mathieu]

Hi,

I have the same issue (hangs after the line: restarting openbsd secure shell server sshd ...done)
Same hardware in the past produced working MD. Only difference is I disabled the onboard nic and replaced it with a pci intel nic.

br mathieu

[Kezza]

I've had similar problems (On initial boot not after setting them up) and ended up creating new generic PC as MD in web admin, entering the MAC address and then booting up the MD which seems to work fine.

Have you seen this? http://svn.linuxmce.org/trac.cgi/ticket/702#comment:2

[Crawtech]

Hi Guys

I have had the same problem and i found if a waited 10 min it would go
But i have found if i unplug my Nas from the system it starts strait away   
Do you Guys have a NAS on your system at all

 

[DeathMagnetic]

I left all 9 at this line overnight and now that I'm back they're all running perfectly. So basically I was missing patience.

[Crawtech]

typhoon
Do you have a NAS on your system at all

[DeathMagnetic]

No.

[mathieu]

Hi,

my MD is still hanging on the "Restarting OpenBSD secure Shell Server..."

As mentioned above I tried to let it sit for a couple of houres with no result.
Removing the MD in webadmin and then creating it again in the webadmin  with mac adress (like stated by Kezza in this thread) also didn't work for me.

I guess this is my 5th try now. I'm realy clueless now. The strange thing is that yesterday out of the blue I had succes with creating this MD. It was the first md setup on a fresh core with the Diskless_CreateTBZ just finished.( Unfortunaly I screwed that one up and had to delete it in the webmin. )

Is there a command to launch the House-setup by hand?
Is there someone who can bring some light here 

br herman

[lmwashere]

I am having a similar problem, but mine has only made it to the  "Restarting OpenBSD secure Shell Server..." once. It usually hangs at the line about pxelinux.0

Go figure.

I suspect that mine has something to do with the fact that it keeps trying to install the 177 or 173 nvidia drivers, despite me having the 195 installed on the hybrid.

I do not have a nas, but there is a windows xp machine on the network outside of the media network. (not on 192.168.80.*, on 192.168.1.*). LMCE asked me if I wanted to use it and I told it never to use it. There doesn't seem to be any further issue with it.

[mathieu]

trying to match the conditions that lead to the succesfull md install, I restored an Image (clonezilla is my friend ) of a fresh core with the Diskless_CreateTBZ script activated.
Besides this I used other utp cabling and GB switch  to eliminate network issues.
On the internal network are no other devices.
No peripherals are connected to the MD during the setup proces.

Unfortunaly the result is the same.

The only thing (I can see ) that may have varied compared with the succesfull install is the timing of reloading the router after the  message "...finished installing software...in order to use...reload the router" is displayed on any orbiter.


I certainly want to dive a little deeper to see what is causing the problem. Where can I start looking?

thanks in advance

[mihajzm]

You should examine log's of the MD . On core it's in location /usr/pluto/diskless/ (md number) /var/log/pluto

[mathieu]

Ok, I went through the logs (there are not many)and copied/paste all suspicious stuff here: http://pastebin.com/hKqFjKGP

 

cannot access /lib/modules/*/misc/

is in all off the following logs

#
kernmod.pluto-app-server.postinst.postinst.Thu\,\ 17\ Jun\ 2010\ 22\:18\:11\ +0000.log
#
kernmod.pluto-boot-scripts.postinst.postinst.Thu\,\ 17\ Jun\ 2010\ 22\:18\:58\ +0000.log
#
kernmod.pluto-createdevice.postinst.postinst.Thu\,\ 17\ Jun\ 2010\ 22\:18\:58\ +0000.log
#
kernmod.pluto-dcecommon.postinst.postinst.Thu\,\ 17\ Jun\ 2010\ 22\:18\:28\ +0000.log
#
kernmod.pluto-disk-monitor.postinst.postinst.Thu\,\ 17\ Jun\ 2010\ 22\:18\:29\ +0000.log
#
kernmod.pluto-disc-drive-functions.postinst.postinst.Thu\,\ 17\ Jun\ 2010\ 22\:19\:05\ +0000.log
#
kernmod.pluto-libserial.postinst.postinst.Thu\,\ 17\ Jun\ 2010\ 22\:18\:29\ +0000.log
#
kernmod.pluto-mythtv-player.postinst.postinst.Thu, 17 Jun 2010 22:20:13 +0000.log
#
kernmod.pluto-nvidia-video-drivers.postinst.postinst.Fri, 18 Jun 2010 09:29:30 +0200.log
#
kernmod.pluto-orbiter.postinst.postinst.Thu, 17 Jun 2010 22:18:58 +0000.log
#
kernmod.pluto-pluto-main-db.postinst.postinst.Thu, 17 Jun 2010 22:18:28 +0000.log
#
kernmod.pluto-pluto-media-db.postinst.postinst.Thu, 17 Jun 2010 22:19:05 +0000.log
#
kernmod.pluto-plutoutils.postinst.postinst.Thu, 17 Jun 2010 22:18:27 +0000.log
#
kernmod.pluto-raid-tools.postinst.postinst.Thu, 17 Jun 2010 22:18:29 +0000.log
#
kernmod.pluto-sdl-helpers.postinst.postinst.Thu, 17 Jun 2010 22:18:30 +0000.log
#
kernmod.pluto-serializeclass.postinst.postinst.Thu, 17 Jun 2010 22:18:27 +0000.log
#
kernmod.pluto-simplephone.postinst.postinst.Thu, 17 Jun 2010 22:18:30 +0000.log
#
kernmod.pluto-storage-devices.postinst.postinst.Thu, 17 Jun 2010 22:18:29 +0000.log
#
kernmod.pluto-xine-player.postinst.postinst.Thu, 17 Jun 2010 22:18:28 +0000.log
#

In mount-wrapper.log are some entries with exit status 1, don't know if these effect the above?
Will further investigate the content of /lib/modules/* to see if misc/ is there.
 

[DeathMagnetic]

I had a problem with the MDs constantly restarting instead of booting MCE, turns out it was the architecture being set to amd64 instead of i386. They set up fine, just wouldn't boot into the AV Wizard. Try checking that. But like I say the only thing I could do was wait.

pxelinux.0 is usually the last line you see before the AV Wizard starts, but it can take a moment if there are several of them on the network.

[lmwashere]

That is amusing. I bet the problem is that I am an idiot.

Come to think of it the screen went to sleep after that. I bet it went to the avwizard on a different video output. I will use the key combo to switch it to DVI when I get home.


Normally it beeps when it starts the avwizard though, perhaps not this time. I will post back if that was my issue.

[DeathMagnetic]

I've never noticed the beep for the AV Wizard, usually just find the screen has nothing on it. With so many MDs trying to use the AV Wizard even switching display adapters was taking a moment.