Provided by: ganeti_2.9.3-1_all bug


       ganeti-noded - Ganeti node daemon


       ganeti-noded  [-f]  [-d]  [-p  PORT]  [-b  ADDRESS] [-i INTERFACE] [--no-mlock] [--syslog]
       [--no-ssl] [-K SSL_KEY_FILE] [-C SSL_CERT_FILE]


       The ganeti-noded is the daemon which is responsible for the node functions in  the  Ganeti

       By  default,  in  order  to  be able to support features such as node powercycling even on
       systems with a very damaged root disk, ganeti-noded locks itself in RAM using mlockall(2).
       You can disable this feature by passing in the --no-mlock to the daemon.

       For  testing  purposes,  you  can give the -f option and the program won't detach from the
       running terminal.

       Debug-level message can be activated by giving the -d option.

       Logging to syslog, rather than its own log file, can be enabled by passing in the --syslog

       The ganeti-noded daemon listens to port 1811 TCP, on all interfaces, by default.  The port
       can be overridden by an entry in the  services  database  (usually  /etc/services)  or  by
       passing  the  -p  option.   The  -b  option  can be used to specify the address to bind to
       (defaults to; alternatively, the -i option can be used to specify  the  interface
       to bind do.

       Ganeti  noded  communication  is  protected  via SSL, with a key generated at cluster init
       time.  This can be disabled  with  the  --no-ssl  option,  or  a  different  SSL  key  and
       certificate can be specified using the -K and -C options.

       The  role  of the node daemon is to do almost all the actions that change the state of the
       node.  Things like creating  disks  for  instances,  activating  disks,  starting/stopping
       instance and so on are done via the node daemon.

       Also,  in  some  cases  the  startup/shutdown  of  the master daemon are done via the node
       daemon, and the cluster IP address is also added/removed to the master node via it.

       If the node daemon is stopped, the instances are not affected, but  the  master  won't  be
       able to talk to that node.

       Currently  the  master-node  RPC is done using a simple RPC protocol built using JSON over


       Report  bugs  to  project  website  (  or   contact   the
       developers using the Ganeti mailing list (


       Ganeti  overview  and specifications: ganeti(7) (general overview), ganeti-os-interface(7)
       (guest OS definitions), ganeti-extstorage-interface(7) (external storage providers).

       Ganeti  commands:  gnt-cluster(8)   (cluster-wide   commands),   gnt-job(8)   (job-related
       commands),  gnt-node(8) (node-related commands), gnt-instance(8) (instance commands), gnt-
       os(8) (guest OS commands), gnt-storage(8) (storage  commands),  gnt-group(8)  (node  group
       commands), gnt-backup(8) (instance import/export commands), gnt-debug(8) (debug commands).

       Ganeti  daemons:  ganeti-watcher(8) (automatic instance restarter), ganeti-cleaner(8) (job
       queue cleaner), ganeti-noded(8) (node daemon), ganeti-masterd(8) (master daemon),  ganeti-
       rapi(8) (remote API daemon).

       Ganeti htools: htools(1) (generic binary), hbal(1) (cluster balancer), hspace(1) (capacity
       calculation), hail(1) (IAllocator plugin), hscan(1) (data gatherer from remote  clusters),
       hinfo(1) (cluster information printer), mon-collector(7) (data collectors interface).


       Copyright  (C) 2006, 2007, 2008, 2009, 2010, 2011, 2012 Google Inc.  Permission is granted
       to copy, distribute and/or modify under the terms of the GNU  General  Public  License  as
       published  by  the  Free Software Foundation; either version 2 of the License, or (at your
       option) any later version.

       On Debian systems, the complete text of the GNU General Public License  can  be  found  in