
858 Appendix B Syslog messages
320818-A
css error: <reason> ERROR Problem encountered when parsing a style
sheet. The problem could be in the Nortel
SNAS 4050 css parser, or it could be a
problem on the processed page.
Failed to syslog traffic :<reason> -- disabling
traf log
ERROR Problem occurred when the Nortel
SNAS 4050 tried to send traffic logging syslog
messages. Traffic syslogging was disabled as
a result.
www_authenticate: bad credentials ERROR The browser sent a malformed
WWW-Authenticate: credentials header. Most
likely a broken client.
http error: <reason>, Request=”<method>
<host><path>”
ERROR A problem was encountered when parsing the
HTTP traffic. The problem indicates either a
non-standard client/server or that the Nortel
SNAS 4050 HTTP parser is out of sync
because of an earlier non-standard
transaction from the client or server on this
TCP stream.
http header warning cli: <reason>
(<header>)
ERROR The client sent a bad HTTP header.
http header warning srv: <reason>
(<header>)
ERROR The server sent a bad HTTP header.
failed to parse Set-Cookie <header> ERROR The Nortel SNAS 4050 got a malformed
Set-Cookie header from the backend web
server.
Bad IP:PORT data <line> in hc script ERROR Bad ip:port found in health check script.
Reconfigure the health script. (Normally, the
CLI captures this type of problem earlier.)
Bad regexp (<expr>) in health check ERROR Bad regular expression found in health check
script. Reconfigure the health script.
(Normally, the CLI captures this type of
problem earlier.)
Bad script op found <script op> ERROR Bad script operation found in health check
script. Reconfigure the health script.
(Normally, the CLI captures this type of
problem earlier.)
Connect failed: <reason> ERROR Connect to backend server failed with
<reason>
html error: <reason> ERROR Error encountered when parsing HTML.
Probably non-standard HTML.
Table 196 Traffic Processing messages — ERROR (Sheet 2 of 3)
Message Category Explanation/Action
Komentarze do niniejszej Instrukcji