1
<?xml version="1.0" encoding="latin1" ?>
2
<!DOCTYPE chapter SYSTEM "chapter.dtd">
7
<year>2003</year><year>2009</year>
8
<holder>Ericsson AB. All Rights Reserved.</holder>
11
The contents of this file are subject to the Erlang Public License,
12
Version 1.1, (the "License"); you may not use this file except in
13
compliance with the License. You should have received a copy of the
14
Erlang Public License along with this software. If not, it can be
15
retrieved online at http://www.erlang.org/.
17
Software distributed under the License is distributed on an "AS IS"
18
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
19
the License for the specific language governing rights and limitations
24
<title>Error Logging</title>
29
<file>error_logging.xml</file>
33
<title>Error Information From the Runtime System</title>
34
<p>Error information from the runtime system, that is, information
35
about a process terminating due to an uncaught error exception,
36
is by default written to terminal (tty):</p>
37
<code type="none"><![CDATA[
38
=ERROR REPORT==== 9-Dec-2003::13:25:02 ===
39
Error in process <0.27.0> with exit value: {{badmatch,[1,2,3]},[{m,f,1},{shell,eval_loop,2}]}]]></code>
40
<p>The error information is handled by the <em>error logger</em>, a
41
system process registered as <c>error_logger</c>. This process
42
receives all error messages from the Erlang runtime system and
43
also from the standard behaviours and different Erlang/OTP
45
<p>The exit reasons (such as <c>badarg</c> above) used by
46
the runtime system are described in
47
<seealso marker="doc/reference_manual:errors#exit_reasons">Errors and Error Handling</seealso>
48
in the Erlang Reference Manual.</p>
49
<p>The process <c>error_logger</c> and its user interface (with
50
the same name) are described in
51
<seealso marker="kernel:error_logger">error_logger(3)</seealso>.
52
It is possible to configure the system so that error information
53
is written to file instead/as well as tty. Also, it is possible
54
for user defined applications to send and format error
55
information using <c>error_logger</c>.</p>
59
<title>SASL Error Logging</title>
60
<p>The standard behaviors (<c>supervisor</c>, <c>gen_server</c>,
61
etc.) sends progress and error information to <c>error_logger</c>.
62
If the SASL application is started, this information is written
64
<seealso marker="sasl:error_logging">SASL Error Logging</seealso>
65
in the SASL User's Guide for further information.</p>
67
% <input>erl -boot start_sasl</input>
68
Erlang (BEAM) emulator version 5.4.13 [hipe] [threads:0] [kernel-poll]
71
=PROGRESS REPORT==== 31-Mar-2006::12:45:58 ===
72
supervisor: {local,sasl_safe_sup}
73
started: [{pid,<0.33.0>},
75
{mfa,{alarm_handler,start_link,[]}},
76
{restart_type,permanent},
80
=PROGRESS REPORT==== 31-Mar-2006::12:45:58 ===
81
supervisor: {local,sasl_safe_sup}
82
started: [{pid,<0.34.0>},
84
{mfa,{overload,start_link,[]}},
85
{restart_type,permanent},
89
=PROGRESS REPORT==== 31-Mar-2006::12:45:58 ===
90
supervisor: {local,sasl_sup}
91
started: [{pid,<0.32.0>},
95
[{local,sasl_safe_sup},sasl,safe]}},
96
{restart_type,permanent},
98
{child_type,supervisor}]
100
=PROGRESS REPORT==== 31-Mar-2006::12:45:58 ===
101
supervisor: {local,sasl_sup}
102
started: [{pid,<0.35.0>},
103
{name,release_handler},
104
{mfa,{release_handler,start_link,[]}},
105
{restart_type,permanent},
109
=PROGRESS REPORT==== 31-Mar-2006::12:45:58 ===
111
started_at: nonode@nohost
112
Eshell V5.4.13 (abort with ^G)