Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
02/02/12 16:12:59 (12 years ago)
- Author:
-
szwells
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
accepted
-
Property
Component
changed from
General
to
Deployment
-
Property
Remaining Time
changed from
to
0.5
-
Property
Milestone
changed from
Unscheduled
to
OMERO-Beta4.4
-
Property
Sprint
changed from
to
2012-02-14 (8)
-
|
initial
|
v3
|
|
| 1 | 1 | Occasionally the 10.0.2.15 VirtualBox NAT address isn't allocated at VM bootup. This means that you can have a VM without any working network which means that you cannot access the VM from insight or via SSH. |
| 2 | 2 | |
| 3 | | If you have launched the VM in headless mode then you cannot access the VM to fix this. If the VM is launched in console mode then you can log in and execute: |
| 4 | | |
| 5 | | {{{ |
| 6 | | $ dhclient -r |
| 7 | | $ dhclient eth0 |
| 8 | | }}} |
| 9 | | |
| 10 | | Therefore, when the VM is booted we should include a boot script that runs after everything else has been started which checks whether the VM has an IP address for the eth0 interface, if it does not then it should use the above commands to get a new IP address. |
| | 3 | Although this occurs as a result of a recurring VirtualBox bug, the most reliable way to fix the networking is to release force a new dhcp lease from the VirtualBox inbuilt DHCP server. A script is required to make this an easy & straightforward for the user. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.14187 sec.)
