Page 2 of 2

Re: virtual appliance - help

PostPosted: Mon Jun 04, 2012 6:15 am
by jmoore
Hi Adrian,

where are you trying to log in with root/omero? Web or Insight? Via the CLI? Can you show us a screenshot?

Thanks,
~Josh

Re: virtual appliance - help

PostPosted: Thu Jun 14, 2012 9:55 am
by jumpfunky
Hi,

same issue to Adrian:
eth0 has correct ip:
Image

I'am able to connect via ssh from host:
ssh omero@localhost -p 2222


But when I try to connect with INSIGHT (root / omero):
Image

Any suggestions?

Edit: Even the Webclient ( http://localhost:4080/webclient ) doesnt response!

Re: virtual appliance - help

PostPosted: Sat Jun 16, 2012 12:24 pm
by abradd
Hi all,

Sorry for the slow reply I did not realise that anyone had responded!

I tried to connect through both the web client and insight with no luck (u: root p: omero). I even changed the password (of root) and added a new user and could not get access. I have tried on Windows 7, Mac OS X 10.7 and Ubuntu 10.04 with no success. I am able to shell from into the VM though (tried on Mac).

jumpfunky appears to be having the same issue. His screenshots replicate the login failure I had.

On a positive note, I have since managed to get server running on a desktop I have which is running Ubuntu 10.04 Desktop.

Edit:
I just checked and I am able to login via the CLI (u: root, p:omero). Also found aother forum post that appeared to be having the same problems (http://www.openmicroscopy.org/community ... f=5&t=1094). It appears those issues were on an older VM, I am using the 4.3.4 VM. Not sure whether they resolved their issues.

Re: virtual appliance - help

PostPosted: Sun Jun 17, 2012 6:08 pm
by jumpfunky
This version works for me:
http://cvs.openmicroscopy.org.uk/snapsh ... irtualbox/

But i have to remove the udev-rule:
rm /etc/udev/rules.d/70-persistent-net.rules

Re: virtual appliance - help

PostPosted: Tue Jun 26, 2012 1:30 pm
by ckm
What's the issue that requires removing the udev rules?

Re: virtual appliance - help

PostPosted: Tue Jun 26, 2012 2:51 pm
by rleigh
If the virtualbox MAC address for eth0 changes, then udev will notice and rename the interface to eth1, then ethn+1 for each change of MAC address at boot. This tends to break the networking configuration, since you then have to manually update the configuration to use the new device name.