File: how_to_analyze_error_message.html

package info (click to toggle)
groonga 11.0.0-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 121,576 kB
  • sloc: ansic: 801,209; javascript: 62,121; ruby: 46,206; cpp: 33,790; xml: 24,951; yacc: 13,333; sh: 7,776; python: 3,266; makefile: 2,315; perl: 133
file content (184 lines) | stat: -rw-r--r-- 9,221 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184


<!DOCTYPE html>

<html lang="en">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>10.2. How to analyze error messages &#8212; Groonga v10.1.1-31-g1e46ba6 documentation</title>
    <link rel="stylesheet" href="../_static/groonga.css" type="text/css" />
    <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
    
    <script id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
    <script src="../_static/jquery.js"></script>
    <script src="../_static/underscore.js"></script>
    <script src="../_static/doctools.js"></script>
    <script src="../_static/language_data.js"></script>
    
    <link rel="shortcut icon" href="../_static/favicon.ico"/>
    <link rel="index" title="Index" href="../genindex.html" />
    <link rel="search" title="Search" href="../search.html" />
    <link rel="next" title="10.3. How to avoid mmap Cannot allocate memory error" href="mmap_cannot_allocate_memory.html" />
    <link rel="prev" title="10.1. 同じ検索キーワードなのに全文検索結果が異なる" href="different_results_with_the_same_keyword.html" /> 
  </head><body>
<div class="header">
  <h1 class="title">
    <a id="top-link" href="../index.html">
      <span class="project">groonga</span>
      <span class="separator">-</span>
      <span class="description">An open-source fulltext search engine and column store.</span>
    </a>
  </h1>

  <div class="other-language-links">
    <ul>
      <li><a href="../../../ja/html/troubleshooting/how_to_analyze_error_message.html">日本語</a></li>
    </ul>
  </div>
</div>
  

    <div class="related" role="navigation" aria-label="related navigation">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="../genindex.html" title="General Index"
             accesskey="I">index</a></li>
        <li class="right" >
          <a href="mmap_cannot_allocate_memory.html" title="10.3. How to avoid mmap Cannot allocate memory error"
             accesskey="N">next</a> |</li>
        <li class="right" >
          <a href="different_results_with_the_same_keyword.html" title="10.1. 同じ検索キーワードなのに全文検索結果が異なる"
             accesskey="P">previous</a> |</li>
        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v10.1.1-31-g1e46ba6 documentation</a> &#187;</li>
          <li class="nav-item nav-item-1"><a href="../troubleshooting.html" accesskey="U"><span class="section-number">10. </span>Troubleshooting</a> &#187;</li>
        <li class="nav-item nav-item-this"><a href=""><span class="section-number">10.2. </span>How to analyze error messages</a></li> 
      </ul>
    </div>  

    <div class="document">
      <div class="documentwrapper">
        <div class="bodywrapper">
          <div class="body" role="main">
            
  <div class="section" id="how-to-analyze-error-messages">
<h1><span class="section-number">10.2. </span>How to analyze error messages<a class="headerlink" href="#how-to-analyze-error-messages" title="Permalink to this headline">¶</a></h1>
<p>This section describes how to analyze Groonga error messages.</p>
<div class="section" id="how-to-analyze-socket-errors">
<h2><span class="section-number">10.2.1. </span>How to analyze socket errors<a class="headerlink" href="#how-to-analyze-socket-errors" title="Permalink to this headline">¶</a></h2>
<p>This subsection describes how to analyze socket errors with an example.</p>
<div class="section" id="example">
<h3><span class="section-number">10.2.1.1. </span>Example<a class="headerlink" href="#example" title="Permalink to this headline">¶</a></h3>
<p>The following is an example of an error message reported by Groonga, where xxxxx is an arbitrary number:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>socket error[xxxxx]: no buffer: accept
</pre></div>
</div>
</div>
<div class="section" id="how-to-analyze">
<h3><span class="section-number">10.2.1.2. </span>How to analyze<a class="headerlink" href="#how-to-analyze" title="Permalink to this headline">¶</a></h3>
<p>First, grep Groonga source files for “SOERR” that is the name of a macro for socket errors.</p>
<p>Then, extract SOERRs whose argument contains “accept” from the grep output and you will find the following SOERRs:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>lib/com.c:      SOERR(&quot;listen - start accept&quot;);
lib/com.c:      SOERR(&quot;listen - disable accept&quot;);
lib/com.c:        SOERR(&quot;accept&quot;);
</pre></div>
</div>
<p>It is clear that the above error message is associated with the last line because the error message contains only “accept”.</p>
<p>The source code around the line is as follows:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>grn_sock fd = accept(com-&gt;fd, NULL, NULL);
if (fd == -1) {
  if (errno == EMFILE) {
    grn_com_event_stop_accept(ctx, ev);
  } else {
    SOERR(&quot;accept&quot;);
  }
  return;
}
</pre></div>
</div>
<p>From the above source code, you can confirm that the error occurred due to accept.
Let’s dig into the cause.</p>
<p>The error message provides hints for investigation:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>[10055]: no buffer
</pre></div>
</div>
<p>10055 is a Windows socket error code and “no buffer” is a message by Groonga given in SOERR.</p>
<p>Windows socket error codes are listed in the following page:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>https://msdn.microsoft.com/ja-jp/library/windows/desktop/ms740668(v=vs.85).aspx
</pre></div>
</div>
<p>10055 is assigned to WSAENOBUFS and its description is as follows:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>No buffer space available.

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
</pre></div>
</div>
<p>From the above description, you can narrow down the causes.
The possible causes are the lack of memory and too many connections.
Finally, determine which one is appropriate for the situation when the error occurred.</p>
</div>
</div>
</div>


            <div class="clearer"></div>
          </div>
        </div>
      </div>
      <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
        <div class="sphinxsidebarwrapper">
  <h3><a href="../index.html">Table of Contents</a></h3>
  <ul>
<li><a class="reference internal" href="#">10.2. How to analyze error messages</a><ul>
<li><a class="reference internal" href="#how-to-analyze-socket-errors">10.2.1. How to analyze socket errors</a><ul>
<li><a class="reference internal" href="#example">10.2.1.1. Example</a></li>
<li><a class="reference internal" href="#how-to-analyze">10.2.1.2. How to analyze</a></li>
</ul>
</li>
</ul>
</li>
</ul>

  <h4>Previous topic</h4>
  <p class="topless"><a href="different_results_with_the_same_keyword.html"
                        title="previous chapter"><span class="section-number">10.1. </span>同じ検索キーワードなのに全文検索結果が異なる</a></p>
  <h4>Next topic</h4>
  <p class="topless"><a href="mmap_cannot_allocate_memory.html"
                        title="next chapter"><span class="section-number">10.3. </span>How to avoid mmap Cannot allocate memory error</a></p>
<div id="searchbox" style="display: none" role="search">
  <h3 id="searchlabel">Quick search</h3>
    <div class="searchformwrapper">
    <form class="search" action="../search.html" method="get">
      <input type="text" name="q" aria-labelledby="searchlabel" />
      <input type="submit" value="Go" />
    </form>
    </div>
</div>
<script>$('#searchbox').show(0);</script>
        </div>
      </div>
      <div class="clearer"></div>
    </div>
    <div class="related" role="navigation" aria-label="related navigation">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="../genindex.html" title="General Index"
             >index</a></li>
        <li class="right" >
          <a href="mmap_cannot_allocate_memory.html" title="10.3. How to avoid mmap Cannot allocate memory error"
             >next</a> |</li>
        <li class="right" >
          <a href="different_results_with_the_same_keyword.html" title="10.1. 同じ検索キーワードなのに全文検索結果が異なる"
             >previous</a> |</li>
        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v10.1.1-31-g1e46ba6 documentation</a> &#187;</li>
          <li class="nav-item nav-item-1"><a href="../troubleshooting.html" ><span class="section-number">10. </span>Troubleshooting</a> &#187;</li>
        <li class="nav-item nav-item-this"><a href=""><span class="section-number">10.2. </span>How to analyze error messages</a></li> 
      </ul>
    </div>
    <div class="footer" role="contentinfo">
        &#169; Copyright 2009-2021, Brazil, Inc.
    </div>
  </body>
</html>