Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
W
White Rabbit Switch - Software
Manage
Activity
Members
Labels
Plan
Issues
91
Issue boards
Milestones
Wiki
Code
Merge requests
4
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Projects
White Rabbit Switch - Software
Commits
641b76db
Commit
641b76db
authored
9 years ago
by
Adam Wujek
Browse files
Options
Downloads
Patches
Plain Diff
doc/wrs-user-manual: add information about monit
Signed-off-by:
Adam Wujek
<
adam.wujek@cern.ch
>
parent
2246e285
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/wrs-developer-manual.in
+41
-0
41 additions, 0 deletions
doc/wrs-developer-manual.in
doc/wrs-user-manual.in
+1
-1
1 addition, 1 deletion
doc/wrs-user-manual.in
with
42 additions
and
1 deletion
doc/wrs-developer-manual.in
+
41
−
0
View file @
641b76db
...
...
@@ -1814,6 +1814,47 @@ gentle restarts before.
Date set from file @t
{
/update/saved
_
date
}
is never correct, but is based on
best effort principle.
@c ==========================================================================
@node Supervision of running processes
@section Supervision of running processes
During normal operation @t
{
monit
}
supervises several processes running on a wrs
switch. Check is done every 10 seconds. As for now supervised processes are:
@t
{
wrsw
_
rtud
}
,
@t
{
wrsw
_
hal
}
,
@t
{
ppsi
}
,
@t
{
lighttpd
}
,
@t
{
dropbear
}
,
@t
{
snmpd
}
.
In case any of the supervised processes does not run anymore (because of a crash,
exit etc.), @t
{
monit
}
restarts missing process. If 5 restarts of a process
occur during 10 cycles (10*10 seconds), the entire switch is restarted.
Since @t
{
monit
}
is started from the inittab, even if @t
{
monit
}
crashes for some
reason it will be re-spawned by the @t
{
init
}
.
@c ==========================================================================
@node Disabling monit
@subsection Disabling monit
In some cases, especially during development it is convenient to disable
@t
{
monit
}
to avoid annoying re-spawns of the processes and restarts of the entire
switch.
@t
{
monit
}
can be disabled with command:
@example
/etc/init.d/monit.sh stop
@end example
which will send STOP signal to @t
{
monit
}
or by adding @t
{
CONFIG
_
MONIT
_
DISABLE=y
}
to dot-config.
To re-enable @t
{
monit
}
first make sure there is no @t
{
CONFIG
_
MONIT
_
DISABLE=y
}
in dot-config, then execute command:
@example
/etc/init.d/monit.sh start
@end example
NOTE: Even when @t
{
monit
}
is disabled there is a process @t
{
/usr/bin/monit
}
in
a process list, but its state is "stopped" (T).
@c ==========================================================================
@node SDB and Hardware Information
@section SDB and Hardware Information
...
...
This diff is collapsed.
Click to expand it.
doc/wrs-user-manual.in
+
1
−
1
View file @
641b76db
...
...
@@ -554,7 +554,7 @@ value is changed by the web interface, proper action is taken.
@item CONFIG
_
MONIT
_
DISABLE
Disable monitoring of running processes by monit. Monit by default
re
spawns processes that have died. This option is useful mostly during
re
-
spawns processes that have died. This option is useful mostly during
development.
@end table
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment