flumotion-worker(1)

1flumotion-worker(1)                Flumotion               flumotion-worker(1)
2
3
4

NAME

6       flumotion-worker - streaming media server worker
7
8

SYNOPSIS

10       flumotion-worker  [ - ] [ --debug debug configuration ] [ -L logdir ] [
11       -R rundir ] [ -H host ] [ -P port ] [ -T protocol ] [ -n name ] [ -D  ]
12       [  --daemonize-to=  directory  ] [ -F ports | --random-feederports ] -u
13       username -p password
14
15

DESCRIPTION

17       flumotion-worker is the part of flumotion that  actually  performs  all
18       the real work of encoding, streaming, etc. In a flumotion system, there
19       will be a single manager, and could be several workers running on  dif‐
20       ferent systems (this is useful to distribute the load of, for instance,
21       video encoding). You need to have a minimum of one worker for flumotion
22       to function correctly.
23
24       You should start flumotion-manager first, then connect flumotion-worker
25       to the running manager.
26
27

OPTIONS

29       -h, --help
30              Show a brief help message, then exit.
31
32       --version
33              Show the version number.
34
35       -v, --verbose
36              Be verbose in console output. This is equivalent to setting  the
37              debug level to 3, and will override any debug specifiers.
38
39       -dDEBUG, --debug=DEBUG
40              Set  the  debug configuration to the specified debug string. See
41              the Debugging section for details of this.
42
43       -L LOGDIR, --logdir=LOGDIR
44              Specify the directory for logging output from the worker.
45
46       -R RUNDIR, --rundir=RUNDIR
47              Specify the directory for runtime files created by the worker.
48
49       -HHOST, --host=HOST
50              Specify the hostname on which the manager is running.
51
52       -PPORT, --port=PORT
53              Specify the port on which the manager in running  (usually  7531
54              for SSL, or 8642 otherwise)
55
56       -TTRANSPORT, --transport=TRANSPORT
57              Set  the  transport  protocol  to  use,  either  'tcp' or 'ssl'.
58              Default is 'ssl'.
59
60       -nNAME, --name=NAME
61              Set the name for this worker to use in the manager.
62
63       -D, --daemonize
64              Run in the background as a daemon.
65
66       -u, --username
67              Specify the username to use to connect to the manager.
68
69       -p, --password
70              Specify the password to use to connect to the manager.
71
72       -FPORTS, --feederports=PORT_FROM-PORT_TO
73              Specify the range of feeder ports to use in the  format  'lower-
74              upper'. These are the ports used for inter-worker communication.
75              If you have multiple workers on separate  systems  (perhaps  one
76              doing  encoding,  behind  a  firewall,  and  a  second doing the
77              streaming outside the firewall), they must be able  to  communi‐
78              cate  using  this port range, so you'll have to open these ports
79              in your firewall. It is recommended that you have a range of  20
80              ports.
81
82       --random-feederports
83              Use random available feeder ports.
84
85

DEBUGGING

87       In  the unlikely event of something in flumotion not working, you might
88       want to debug it. The flumotion tools ( flumotion-worker  ,  flumotion-
89       admin , and flumotion-manager ) all allow you to turn on debugging out‐
90       put in two different ways.
91
92       Firstly, you can use an environment variable, FLU_DEBUG. Secondly,  you
93       can  launch  the  program  with a -d or --debug switch. Either approach
94       allows you to specify a debug configuration string with  the  following
95       syntax:
96
97              name1:n1,name2:n2,name3:n3
98
99       In this syntax, the 'name' variables can be replaced with the name of a
100       particular module within flumotion (such as 'admin', 'twisted',  etc.).
101       You can also use '*' to specify all modules. The 'n' variables are num‐
102       bers from 1 to 5, larger numbers corresponding to more  verbose  output
103       (ERROR,  WARN, INFO, DEBUG, and LOG). At level 4, full debugging infor‐
104       mation is emitted.
105
106       You can also use an abbreviated form where you  just  supply  a  single
107       number,  thisuses  that  debug level for all modules. Thus the simplest
108       way to enable full debug output for all modules is to use '-d 4' on the
109       command line.
110
111       A  more  complex  example  would be '-d *:3,admin:4' to set the logging
112       level for the admin module to DEBUG, and for all other modules to INFO.
113
114

EXAMPLES

116       Simple example, starting flumotion-worker connecting to a manager using
117       TCP,  default host and port, and with the username 'user' and the pass‐
118       word 'test'
119
120              flumotion-worker  -v  -T  tcp  -u   user   -p   test   --feeder‐
121              ports=8060-8080
122
123

BUGS

125       Hopefully   none.   If  you  find  any  bugs,  please  report  them  at
126       https://core.fluendo.com/trac/cgi-bin/trac.cgi
127
128