deutsche Version

  Description
  Screenshots
  •   Version 0.1
  •   Version 0.3
  •   Version 0.5
  •   Version 0.7
  •   Version 0.8
  •   Version 0.9
  •   Version 1.0
  •   MOSIXLOAD
  •   MOSIXMEM
  •   MOSIXHISTORY
  •   main-window


  •   Download
      Known Bugs
      FAQ
      HowTo
  • Install
  • main-window
  • configuration-win
  • migrator-win
  • remote-procs
  • execution-win
  • MOSIXVIEW-client  
  • MOSIXCOLLECTOR
  • MOSIXLOAD
  • MOSIXMEM
  • MOSIXHISTORY

  •   Mailingliste
      Mirrors
      Thanks

       HowTo
       openMosix
       diskless-clients

       HowTo
       openMosix +
       MOSIXVIEW
       with SSH

      openMosix HOWTO

      www.openmosix.org

       SourceForge Logo

      thanks to freshmeat.net
    MOSIXVIEW
    Clustermanagment

    MOSIXVIEW Clustermanagment
    FAQ:

  • I cannot compile MOSIXVIEW on my system?

  • At first QT >= 2.3.x is required.
    The QTDIR -environent variable has to be set to your QT-installation directories like it is well described in the INSTALL- file.
    In versions < 0.6 you can do a "make clean" and delete the two files:
    /mosixview/Makefile
    /mosixview/config.cache
    and try to compile again because i alway left the binary- and object-files in older versions.
    If you have any other problems post them to the MOSIXVIEW-mailinglist (or directly to me).

  • Can I use MOSIXVIEW with SSH?

  • Yes, until version 0.7 there is a built-in SSH-support. You have to be able to ssh to each node in your cluster without password (just like the same with using RSH this is required)

  • I started MOSIXVIEW but only the splash-screen appears. What is wrong?

  • Do not fork MOSIXVIEW in the background with & (e.g. mosixview &). It will not work properly. Maybe you cannot rsh/ssh (depends on what you want to use) as user root without password to each node?
    Try "rsh hostname" as root. You should not been promped for a password but soon get a login shell.
    (If you use SSH try "ssh hostname" as root.)
    You have to be root on the cluster because that is the only way the administrative commands executed by MOSIXVIEW requires root-privileges.

    MOSIXVIEW uses "rsh" as the default!
    If you only have "ssh" installed on your cluster
    edit (or create) the file /root/.mosixview and put "1111" in it. This is the main-configuration
    file for MOSIXVIEW and the last "1" stands for "use ssh instead of rsh".
    This will cause MOSIXVIEW to use "ssh" even for the first start.

  • The MOSIXVIEW-client is not working for me!

  • The MOSIXVIEW-client is executed per rsh (or ssh which you can configer whith a checkbox) on the remote host. It has to be installed in /usr/bin/ on each node.
    If you use RSH try:
    "xhost +hostname"
    "rsh hostname /usr/bin/mosixview_client -display your_local_host_name:0.0"
    or if you use SSH try:
    "xhost +hostname"
    "ssh hostname /usr/bin/mosixview_client -display your_local_host_name:0.0"
    If this works it will work in MOSIXVIEW too.
  • MOSIXVIEW crashes with "segmantation fault"!

  • Maybe you still use an old version of MOSIXVIEW which has bugs in the mosix.map-parser.
    (the versions > 0.4 are stable)
    It can happen if you edit your /etc/mosix.map file and changing the whole cluster-configuration during using MOSIXVIEW.
    A /etc/mosix.map with comments behind the hostnamen/ip is a problem too, e.g.

    1 mynode 1      # my first mosix-node

    change to

    1 mynode 1

    ! Known bug !
    MOSIXVIEW 0.9 crashes with seg-faults if the third byte of your ip-adresses
    in the /etc/mosix.map is one-digit wide only e.g. 192.168."3".22
    As a workaround one could change the ip-adresses to e.g. 192.168.33.22
    or insert the hostnames in the /etc/mosix.map e.g.
    1 host1 1
    2 host2 1
    ...
    The bug is fixed in the version 1.0

  • Why are the buttons in the MOSIXVIEW-configuration dialog not preselected?
    (automigration on/off, blocking on/off......)

  • I want them to be preselected too. The problem is to get the information of node. You have to login to each cluster-node because these information are not cluster-wide (to my mind). The status of each node is stored in the /proc/mosix/admin directory of each node. There may be a way if you use MFS/DFSA but i do not want MOSIXVIEW depend on it and login to each clusternode at startup is to much performance overhead (in my opinion).
    Everybody who knows a good way to get these information easy is invited to mail me.