Changes between Version 4 and Version 5 of OsgVpbBuildEnvLinux


Ignore:
Timestamp:
Aug 3, 2010, 9:31:39 PM (14 years ago)
Author:
Torben Dannhauer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • OsgVpbBuildEnvLinux

    v4 v5  
    44
    55Basically it is possible to render virtualPlanetBuilder Databases on MS Windows and Linux. Unfortunately MS Windows is not stable enough, maybe caused by NTFS and the heavy systemload (RAM, CPU, HDD).
    6 To render large databases, it is absolutely necessary to use VPB on linux. This HowTo is guide to setup a proper
     6To render large databases, it is absolutely necessary to use VPB on linux. This !HowTo is guide to setup a proper
    77
    88
    … …  
    160160
    161161To fulfill this requirements, let's assume this setup:
    162  * One node acts as server node and has the IP 192.168.0.55
    163  * Two nodes act as client nodes and have the IPs 192.168.0.54 and 192.168.0.56
     162 * One machine acts as server node and has the IP 192.168.0.55
     163 * Two machines act as client nodes and have the IPs 192.168.0.54 and 192.168.0.56
    164164 * sshfs is used as network filesystem
    165165 * the username on all nodes is fsd
    166  * The destination folder for the compiled database is {{/geodata}}
    167  * The local drive with geo source data is {{/localSourceData}}
     166 * The destination folder for the compiled database is /geodata
     167 * The local drive with geo source data is /localSourceData
    168168
    169169
    … …  
    178178}}}
    179179
    180 Because remote ssh commands do not invoke the environment settings of an interactive shell, ssh must be prepared to provide the required environment variables also for ssh non-interactive-shell:
    181 {{{
    182 #!sh
    183 vim /etc/ssh/sshd_config
    184 
    185 
     180Because remote ssh commands do not invoke the environment settings of an interactive shell, ssh must be prepared to provide the required environment variables also for ssh non-interactive-shell: '''vim /etc/ssh/sshd_config'''
     181{{{
     182#!sh
    186183PermitUserEnvironment yes
    187 
    188 vim /home/fsd/.ssh/environment
     184}}}
     185
     186'''vim /home/fsd/.ssh/environment'''
     187{{{
     188#!sh
    189189LD_LIBRARY_PATH=/home/fsd/OpenSceneGraph/lib/:/home/fsd/VirtualPlanetBuilder/lib/
    190190OSG_FILE_PATH=/home/fsd/sampledata/:/home/fsd/sampledata/Images
    … …  
    209209
    210210=== Preparation after boot of all clients ===
    211  * mount at the @@+++ server node @@  the destination harddrive into the appropriate folder:
     211 * mount at the '''server node'''  the destination harddrive into the appropriate folder:
    212212{{{
    213213#!sh
    214214mount /dev/sde1 /geodata
    215215}}}
    216  * mount on @@+++ all client nodes  @@ the destination directory of the server node over sshfs.
     216 * mount on '''all client nodes''' the destination directory of the server node over sshfs.
    217217Let's assume the server has the IP 192.168.0.56:
    218218{{{
    … …  
    226226
    227227To allow easy recalls of the database build command, create a script:
    228 {{vim /etc/geodata/compile_BRD_Sued.sh}}:
    229 {{{
     228'''vim /etc/geodata/compile_BRD_Sued.sh'''
     229{{{
     230#!sh
    230231#!/bin/sh
    231232
    … …  
    245246
    246247If everything is setup correctly, the processing step ist very easy. Open an new shell on the server node and call as standard user (NOT ROOT!):
    247 <code>
     248{{{
     249#!sh
    248250cd /geodata
    249251./compile_BRD_SUED.sh
    250 </code>
     252}}}
    251253
    252254While the database is creating, it is possible to watch the actual progress in another console. Because files are written and modified, the viewer application will give warnings or will terminate in few cases. This happens due to the creation progress and does not affect or modify the database, please ignore it.
    … …  
    262264
    263265To resume the crashed compile process, execute on the server node:
    264 <code>
     266{{{
     267#!sh
    265268cd /geodata
    266269vpbmaster --machines machinepool.txt --tasks build_master.tasks
    267 </code>
    268 
    269 Take care @@+++ NOT @@ to call the compile script again, in this case all compiled tasks will be resetted to status "pending"
     270}}}
     271
     272Take care '''NOT''' to call the compile script again, in this case all compiled tasks will be resetted to status "pending"
    270273
    271274See TerrainData for data sources.
    … …  
    274277
    275278If compiling fails at the beginning:
    276 * reboot
    277 * Please check if you use a 64 bit operating system
    278 * check your limits: {{limits -a}}
     279 * reboot
     280 * Please check if you use a 64 bit operating system
     281 * check your limits: {{limits -a}}
    279282
    280283If compiling fails after many hours or days:
    281 * Maybe your OS runs out of any ressource, so reboot and resume (read above)
    282 * Check your hardware if resuming do not help.
     284 * Maybe your OS runs out of any ressource, so reboot and resume (read above)
     285 * Check your hardware if resuming do not help.
    283286
    284287If only local threads are executed, but no remote ones:
    285 * Check your ssh setup, if you can login passwordless from the server node to the client nodes
    286 * Check your ssh setup, if your environmental variables on the client nodes are available if you login to a client node
     288 * Check your ssh setup, if you can login passwordless from the server node to the client nodes
     289 * Check your ssh setup, if your environmental variables on the client nodes are available if you login to a client node