Documentation

Proxedo Network Security Suite 2 Log Messages Guide

Chapter 4. Authentication Server log messages

Hide Sidebar Previous | Up | Next

Previous Up Next
 Home 

Copyright: © 2021 Balasys IT Security
Send your comments to support@balasys.hu

  • Contents
  • Search
loading table of contents...
  • Preface
    • 1. Single-line log message for connections
  • 1. Application-level Gateway log messages
    • 1.1.
      • 1.1.1. Http accounting
      • 1.1.2. Request administratively prohibited
      • 1.1.3. Instance definition not found in policy
      • 1.1.4. Deinitialization requested for instance
      • 1.1.5. Cleaning up instance
      • 1.1.6. Server connection failure
      • 1.1.7. Server connection established
      • 1.1.8. Server connection failure, no destination
      • 1.1.9. All destinations are down, clearing cache and trying again
      • 1.1.10. Destination is down, skipping
      • 1.1.11. Destination is down, keeping state
      • 1.1.12. Side stacking failed, socketPair failed
      • 1.1.13. Side-stacking proxy instance
      • 1.1.14. Side-stacking failed
      • 1.1.15. Client foreign port below 1024
      • 1.1.16. Server foreign port below 1024 in passive mode
      • 1.1.17. Server foreign port is not good in active mode
      • 1.1.18. Unknown side when calling bounceCheck
      • 1.1.19. Outbound connection not permitted
      • 1.1.20. Error resolving hostname
      • 1.1.21. Proxy ending
      • 1.1.22. Proxy destroy
      • 1.1.23. Error while stacking child proxy
      • 1.1.24. Stacking custom child
      • 1.1.25. User authentication successful
      • 1.1.26. Cache over shift-threshold, shifting
      • 1.1.27. Sender address administratively prohibited
      • 1.1.28. Sender check successful
      • 1.1.29. Forbidden percent found in address local-part
      • 1.1.30. Forbidden exclamation mark found in address local-part
      • 1.1.31. Relaying denied
      • 1.1.32. Relay check successful
      • 1.1.33. Recipient address administratively prohibited
      • 1.1.34. Recipient check successful
      • 1.1.35. Relay check, checking client_zone
      • 1.1.36. Relay check, checking mail domain
      • 1.1.37. Matching regexp found
      • 1.1.38. Error opening match file
      • 1.1.39. Error opening ignore file
      • 1.1.40. Cached recipient match found
      • 1.1.41. Recipient validity not cached, trying the direct way
      • 1.1.42. SMTP sender was rejected, unable to verify user existence
      • 1.1.43. Server accepted recipient
      • 1.1.44. Server rejected recipient
      • 1.1.45. SMTP error during recipient validity checking
      • 1.1.46. Unable to determine service, service lookup failed
      • 1.1.47. No applicable service found for this client zone (cached)
      • 1.1.48. No applicable service found for this client zone
      • 1.1.49. No applicable service found for this client & server zone (cached)
      • 1.1.50. No applicable service found for this client & server zone
      • 1.1.51. Starting proxy instance
      • 1.1.52. Ending proxy instance
      • 1.1.53. Before NAT mapping
      • 1.1.54. After NAT mapping
      • 1.1.55. Evaluating BACL rule
      • 1.1.56. BACL result
      • 1.1.57. Response count for the request reached limit, drop packets
      • 1.1.58. Response count for request reached limit, aborting connection
      • 1.1.59. Invalid value for response_overrun_action, falling back to LDAP_RSP_DROP
      • 1.1.60. Policy nesting do deep
      • 1.1.61. Policy type invalid
      • 1.1.62. Cannot parse policy line
      • 1.1.63. Error in policy calling
      • 1.1.64. Policy does not contain this header, using hard-coded default
      • 1.1.65. Policy does not contain this mime-type, using hard-coded default
      • 1.1.66. Answer type invalid
      • 1.1.67. Bad policy line
      • 1.1.68. Error in policy calling
      • 1.1.69. Return code invalid from policy function
      • 1.1.70. Policy does not contain this error, using hard-coded default
      • 1.1.71. Error parsing return code
      • 1.1.72. Policy type is invalid
      • 1.1.73. Cannot parse policy line
      • 1.1.74. Error in policy call
      • 1.1.75. Cannot parse the return code
      • 1.1.76. Buffer overflow during protocol decoding, aborting session
      • 1.1.77. Invalid stacking tuple returned by policy
      • 1.1.78. Invalid stacking type
      • 1.1.79. Invalid request, data transfer failed
      • 1.1.80. Data transfer failed
      • 1.1.81. Stacked proxy decision
      • 1.1.82. Stacked proxy accepted data
      • 1.1.83. Data connection accepted on client side
      • 1.1.84. Data connection accepted on server side
      • 1.1.85. Data connection established on client side
      • 1.1.86. Connected to client, but connection is not expected
      • 1.1.87. Data connection established on server side
      • 1.1.88. Connected to server, but connection is not expected
      • 1.1.89. Internal error, previous dispatcher not unregistered
      • 1.1.90. Internal error, previous attach not unregistered
      • 1.1.91. Internal error, previous attach not unregistered
      • 1.1.92. Resetting data connection
      • 1.1.93. Internal error, previous data connection is not closed properly
      • 1.1.94. Internal error, cannot start data proxy because peers are not yet connected
      • 1.1.95. Internal error, current command descriptor does not specify data transfer
      • 1.1.96. Data connection established
      • 1.1.97. Possible bounce attack
      • 1.1.98. Internal error, client side not connected
      • 1.1.99. Internal error, server side not connected
      • 1.1.100. Max_line_length above upper limit
      • 1.1.101. Max_username_length above max_line_length
      • 1.1.102. Max_password_length above max_line_length
      • 1.1.103. Max_hostname_length above max_line_length
      • 1.1.104. Error parsing valid_chars_username
      • 1.1.105. Internal error in stream write, side is wrong
      • 1.1.106. Cannot write full line
      • 1.1.107. Server answer doesn't begin with number
      • 1.1.108. Response arrived
      • 1.1.109. Error reading from server
      • 1.1.110. Line is too short to be a valid answer
      • 1.1.111. Server answer has wrong continuation mark
      • 1.1.112. Rejected answer
      • 1.1.113. Error reading from client
      • 1.1.114. Request fetched
      • 1.1.115. Empty command. Aborting
      • 1.1.116. Unknown command. Aborting
      • 1.1.117. Internal error, known command but command parse is unset
      • 1.1.118. This command not allowed in non-transparent mode
      • 1.1.119. Request rejected
      • 1.1.120. Proxy answer
      • 1.1.121. Rejected command (aborting)
      • 1.1.122. Bad policy type, aborting
      • 1.1.123. Too many continuous lines in the answer
      • 1.1.124. Reading from peer
      • 1.1.125. Invalid port specified in non-transparent destination
      • 1.1.126. Invalid character in username
      • 1.1.127. Hostname specified in username is too long
      • 1.1.128. Username too long
      • 1.1.129. Internal error, proxy in unknown state
      • 1.1.130. Password too long
      • 1.1.131. Unexpected response to data transfer command
      • 1.1.132. Invalid parameter for command
      • 1.1.133. Missing parameter for the TYPE command
      • 1.1.134. Valid, but unsupported transfer type specification
      • 1.1.135. Unknown transfer type specification
      • 1.1.136. Missing parameter to the MODE command
      • 1.1.137. Invalid parameter to the MODE command
      • 1.1.138. Missing parameter to the STRU command
      • 1.1.139. Invalid parameter to the STRU command
      • 1.1.140. Error preparing server-side data connection (PORT)
      • 1.1.141. There was an error binding a server-side listener
      • 1.1.142. Error parsing PASV response
      • 1.1.143. Error preparing data connection to the server (PASV)
      • 1.1.144. Error preparing server-side data connection listener (EPRT)
      • 1.1.145. Cannot bind to the given address (EPRT)
      • 1.1.146. Missing parameter (EPSV)
      • 1.1.147. Bad parameter (EPSV), not beginning with bracket
      • 1.1.148. Bad parameter (EPSV), not closing with bracket
      • 1.1.149. Error parsing EPSV response
      • 1.1.150. Bad parameter (EPSV), invalid port
      • 1.1.151. Internal error, cannot detect server address
      • 1.1.152. Unknown protocol type (EPSV)
      • 1.1.153. Error preparing data connection to the server (EPSV)
      • 1.1.154. Invalid parameters to the PORT command
      • 1.1.155. Connection mode not supported
      • 1.1.156. Error preparing client-side data connection (PORT->PASV)
      • 1.1.157. Error parsing the server answer to the PASV command (PORT->PASV)
      • 1.1.158. Error preparing client-side data connection (PORT)
      • 1.1.159. Error parsing the server answer to the PORT command
      • 1.1.160. Error preparing client-side data connection listener (PASV)
      • 1.1.161. Error preparing client-side data connection listener (PASV->PORT)
      • 1.1.162. Error parsing the server answer to the PORT command (PASV->PORT)
      • 1.1.163. Missing parameter (EPRT)
      • 1.1.164. Bad parameter (EPRT)
      • 1.1.165. Bad port parameter (EPRT)
      • 1.1.166. Unknown protocol method (EPRT)
      • 1.1.167. Bad host address (EPRT)
      • 1.1.168. Error preparing client connect (EPRT)
      • 1.1.169. Bad server answer (EPRT)
      • 1.1.170. Error preparing client listen (EPSV)
      • 1.1.171. Bad server answer (EPSV)
      • 1.1.172. Error parsing command (ALLO)
      • 1.1.173. Policy does not contain this request, using hard-coded default
      • 1.1.174. Policy type invalid
      • 1.1.175. Cannot parse policy line
      • 1.1.176. Error in policy calling
      • 1.1.177. Can't parsing return code
      • 1.1.178. Policy does not contain this response, using hard-coded default
      • 1.1.179. Answer type invalid
      • 1.1.180. Bad policy line
      • 1.1.181. Error in policy calling
      • 1.1.182. Return code invalid from policy function
      • 1.1.183. Policy does not contain this feature, dropping
      • 1.1.184. Policy value invalid
      • 1.1.185. Response line too long
      • 1.1.186. Response status is invalid
      • 1.1.187. Response fetched with parameter
      • 1.1.188. Response fetched
      • 1.1.189. Data transfer failed
      • 1.1.190. Request line too long
      • 1.1.191. Request fetched with parameter
      • 1.1.192. Request fetched
      • 1.1.193. Unknown request command
      • 1.1.194. Request command not allowed in this state
      • 1.1.195. Stacked proxy rejected contents
      • 1.1.196. Dropping request parameter, no parameter allowed
      • 1.1.197. The required numerical parameter of the request is missing
      • 1.1.198. The numerical parameter of the request is not in the given range
      • 1.1.199. The numerical parameter of the request is negative
      • 1.1.200. The numerical parameter of the request is zero
      • 1.1.201. The numerical parameter of the request contains junk after the number
      • 1.1.202. The first numerical parameter of the request is not in the given range
      • 1.1.203. The first numerical parameter of the request is negative
      • 1.1.204. Only one numerical argument in request
      • 1.1.205. The second numerical parameter of the request is not in the given range
      • 1.1.206. The second numerical parameter of the request is a negative number
      • 1.1.207. The numerical parameter of the request contain junk after the number
      • 1.1.208. Username is too long
      • 1.1.209. Password is too long
      • 1.1.210. The username parameter is too long or the digest parameter is missing
      • 1.1.211. Error parsing the MD5 digest
      • 1.1.212. The required numerical parameter of the response is missing
      • 1.1.213. The numerical parameter of the response is not in the given range
      • 1.1.214. The numerical parameter of the response is a negative number
      • 1.1.215. The numerical parameter of the response contains junk after the number
      • 1.1.216. The second numerical parameter of the response is not in the given range
      • 1.1.217. The required second numerical parameter of the response is missing
      • 1.1.218. The second numerical parameter of the response is a negative number
      • 1.1.219. The second numerical parameter of the response contains junk after the number
      • 1.1.220. Policy does not contain this request, using hard-coded default
      • 1.1.221. Policy type is invalid
      • 1.1.222. Cannot parse policy line
      • 1.1.223. Error in policy call
      • 1.1.224. Cannot parse the return code
      • 1.1.225. Policy does not contain this request, using hard-coded default
      • 1.1.226. Policy type is invalid
      • 1.1.227. Cannot parse policy line
      • 1.1.228. Cannot parse return code
      • 1.1.229. Stack policy type is invalid
      • 1.1.230. Cannot parse stack policy line
      • 1.1.231. Cannot parse stack policy line
      • 1.1.232. Error in policy call
      • 1.1.233. Cannot parse return code
      • 1.1.234. Invalid return value of packetStats(), integer required
      • 1.1.235. packetStats() requested to abort session
      • 1.1.236. Invalid command verb in request
      • 1.1.237. Request parsed
      • 1.1.238. Fetching request
      • 1.1.239. Request line too long
      • 1.1.240. Processing request
      • 1.1.241. Command not permitted in this state
      • 1.1.242. Unknown command
      • 1.1.243. Copying request to server
      • 1.1.244. Error sending request
      • 1.1.245. Fetching authentication request
      • 1.1.246. Auth request line too long
      • 1.1.247. Copying authentication request to server
      • 1.1.248. Error sending authentication request
      • 1.1.249. SMTP reply contains non-numeric characters
      • 1.1.250. Invalid continuation character
      • 1.1.251. Fetching response
      • 1.1.252. Response line too long
      • 1.1.253. Invalid SMTP reply, reply code changed
      • 1.1.254. Response parsed
      • 1.1.255. Processing response
      • 1.1.256. Copying response to client
      • 1.1.257. Error sending SMTP reply
      • 1.1.258. Invalid policy ignored, allowing 250 response to NOOP is required
      • 1.1.259. Invalid policy ignored, allowing 354 response to DATA is required
      • 1.1.260. Invalid contents
      • 1.1.261. Error occurred while scanning contents
      • 1.1.262. Rejecting empty message
      • 1.1.263. Error sending RSET to the server
      • 1.1.264. Exiting SMTP loop
      • 1.1.265. Error parsing local part
      • 1.1.266. Local part does not end in '@'
      • 1.1.267. Invalid domain name in path
      • 1.1.268. Path does not start with '<'
      • 1.1.269. Invalid source route information
      • 1.1.270. Invalid address information
      • 1.1.271. Path does not begin with '<' but ends with '>'
      • 1.1.272. Path begins with '<' but does not end with '>'
      • 1.1.273. Invalid SIZE extension in the MAIL command
      • 1.1.274. Invalid BODY extension in the MAIL command
      • 1.1.275. Invalid AUTH sender, not an xtext
      • 1.1.276. Invalid extension in the MAIL command
      • 1.1.277. Invalid request policy type
      • 1.1.278. Error in request policy
      • 1.1.279. The verdict returned by the policy is not an int
      • 1.1.280. Invalid response policy
      • 1.1.281. Error in response policy
      • 1.1.282. The verdict returned by the policy is not an int
      • 1.1.283. Invalid stacking type
      • 1.1.284. Invalid stacking tuple returned by policy
      • 1.1.285. Internal error, error code out of range
      • 1.1.286. An error occurred, serving error file
      • 1.1.287. Error writing stream, stream is NULL
      • 1.1.288. Error writing stream
      • 1.1.289. Only Basic authentication is supported
      • 1.1.290. Invalid base64 encoded username:password pair
      • 1.1.291. No colon is found in the decoded username:password pair
      • 1.1.292. Invalid HTTP request received
      • 1.1.293. CONNECT method without version specification
      • 1.1.294. This request type is not permitted in transparent mode
      • 1.1.295. No host header in transparent request, 'unknown' is used instead
      • 1.1.296. 'Host:' header is required, and HTTP/0.9 can't transfer headers
      • 1.1.297. No 'Host:' header in request, and policy requires this
      • 1.1.298. Error parsing URL
      • 1.1.299. Error formatting URL
      • 1.1.300. Client attempted to use FTP over HTTP, which is currently disabled
      • 1.1.301. Unsupported scheme in URL
      • 1.1.302. Too long hostname in URL
      • 1.1.303. Accounting
      • 1.1.304. Invalid item in request hash
      • 1.1.305. Error parsing HTTP_REQ_POLICY tuple in request hash
      • 1.1.306. Error parsing HTTP_REQ_REJECT in request hash
      • 1.1.307. Unknown request hash item
      • 1.1.308. Policy requested to send custom response
      • 1.1.309. Request not permitted by policy
      • 1.1.310. Connecting to this port is prohibited by policy
      • 1.1.311. Internal error initializing server stream
      • 1.1.312. Error in HTTP/0.9 compatibility code, line buffer full
      • 1.1.313. Server fell back to HTTP/0.9 which is prohibited by policy
      • 1.1.314. Invalid HTTP response heading
      • 1.1.315. Error parsing response version
      • 1.1.316. Unsupported protocol version
      • 1.1.317. Invalid response hash item
      • 1.1.318. Error parsing HTTP_RSP_POLICY in response hash
      • 1.1.319. Error parsing HTTP_RSP_REJECT in response hash
      • 1.1.320. Invalid response hash item
      • 1.1.321. Response not permitted by policy
      • 1.1.322. Missing port number in CONNECT request
      • 1.1.323. Parent proxy refused our CONNECT request
      • 1.1.324. Starting connect method
      • 1.1.325. Internal error, connectMethod is expected to return a proxy instance
      • 1.1.326. Fetching request and headers
      • 1.1.327. processing request and headers
      • 1.1.328. Maximum keep-alive request reached, setting connection mode to close
      • 1.1.329. Filtering request and headers
      • 1.1.330. Reprocessing filtered request
      • 1.1.331. Sending request and headers, copying request data
      • 1.1.332. Fetching response and headers
      • 1.1.333. Processing response and headers
      • 1.1.334. Filtering response and headers
      • 1.1.335. Copying response and headers, copying response data
      • 1.1.336. Internal error, invalid server_protocol
      • 1.1.337. exiting keep-alive loop
      • 1.1.338. Chunk length line too long
      • 1.1.339. Invalid chunk length
      • 1.1.340. Chunk too large
      • 1.1.341. Unexpected EOF while dechunking stream
      • 1.1.342. Chunk footer is not an empty line
      • 1.1.343. Stacked proxy sent a content-length hint, using it
      • 1.1.344. Invalid stacking tuple returned by policy
      • 1.1.345. Invalid stacking type
      • 1.1.346. The header 'Content-Length' was present, but is not a number
      • 1.1.347. Invalid request, data transfer failed
      • 1.1.348. Data transfer failed
      • 1.1.349. Stacked proxy decision
      • 1.1.350. Received an error hint from stacked proxy
      • 1.1.351. Received an error info string from stacked proxy
      • 1.1.352. Stacked proxy sent no error hint or info string, using default response
      • 1.1.353. Stacked proxy accepted data
      • 1.1.354. Request method empty, or too long
      • 1.1.355. URL missing, or too long
      • 1.1.356. Protocol version missing, or too long
      • 1.1.357. Request details
      • 1.1.358. Invalid HTTP status line
      • 1.1.359. Response version empty or too long
      • 1.1.360. Response code empty or too long
      • 1.1.361. Response details
      • 1.1.362. Unknown protocol version
      • 1.1.363. Unknown protocol version
      • 1.1.364. Invalid HTTP_HDR_CHANGE_NAME rule in header processing
      • 1.1.365. Invalid HTTP_HDR_CHANGE_VALUE rule in header processing
      • 1.1.366. Invalid HTTP_HDR_CHANGE_BOTH rule in header processing
      • 1.1.367. Invalid value in header action tuple
      • 1.1.368. Error reading from peer while fetching headers
      • 1.1.369. First header starts with white space
      • 1.1.370. Invalid HTTP header
      • 1.1.371. Too many header lines
      • 1.1.372. Invalid FTP response, line too short
      • 1.1.373. Invalid FTP response, response code not numeric
      • 1.1.374. Invalid FTP response, continuation line contains different status code
      • 1.1.375. FTP server returned an unhandled status code for the login request
      • 1.1.376. Error logging in
      • 1.1.377. Error in FTP greeting, expecting 220
      • 1.1.378. Error changing directory on server
      • 1.1.379. Error sending RETR or LIST command to FTP server
      • 1.1.380. Error establishing data connection to FTP server
      • 1.1.381. Error reading data channel confirmation from FTP server
      • 1.1.382. Error reading 226 from FTP server
      • 1.1.383. Stacked proxy rejected contents
      • 1.1.384. Policy type is invalid
      • 1.1.385. Cannot parse stack policy line
      • 1.1.386. Cannot parse stack policy line
      • 1.1.387. Error in policy call
      • 1.1.388. Cannot parse return code
      • 1.1.389. Internal error, not enough literals
      • 1.1.390. Internal error, too many literals
      • 1.1.391. Error while writing policy response
      • 1.1.392. Error while writing policy response
      • 1.1.393. Failed to parse command
      • 1.1.394. Error writing to client
      • 1.1.395. Reconstructed request
      • 1.1.396. Illegal tag
      • 1.1.397. Duplicate tag
      • 1.1.398. Command not allowed in this state
      • 1.1.399. Error parsing command
      • 1.1.400. Request denied by policy
      • 1.1.401. Dropping request
      • 1.1.402. Policy responds to client
      • 1.1.403. Aborting connection due to request
      • 1.1.404. Too many pending requests
      • 1.1.405. Error writing to server
      • 1.1.406. Stray continuation response
      • 1.1.407. Error writing to server
      • 1.1.408. Server returned untagged line during authentication exchange, dropping it
      • 1.1.409. Aborting connection due to a response
      • 1.1.410. Dropping response
      • 1.1.411. Invalid response
      • 1.1.412. Error writing to client
      • 1.1.413. Response arrived for unknown request
      • 1.1.414. Aborting connection due to a response
      • 1.1.415. Dropping response
      • 1.1.416. Complete response arrived
      • 1.1.417. Reconstructed response
      • 1.1.418. Reading literal
      • 1.1.419. No free literal space
      • 1.1.420. Illegal character
      • 1.1.421. Illegal literal length form
      • 1.1.422. Literal length attribute not closed
      • 1.1.423. Signal received, stackdump follows
      • 1.1.424. Error initializing Python policy engine
      • 1.1.425. eofmask updated
      • 1.1.426. Packet stats timeout elapsed, and no timeout callback specified
      • 1.1.427. Error opening policy file
      • 1.1.428. Error parsing policy file
      • 1.1.429. Internal error in v_policy_stream_new: input VStream is NULL
      • 1.1.430. Error writing vas stream
      • 1.1.431. Module successfully loaded
      • 1.1.432. Module loading failed
      • 1.1.433. Session ID not found for authorization
      • 1.1.434. calling event
      • 1.1.435. calling __destroy__() event
      • 1.1.436. Internal error, trying to look up a non-VProxyIface compatible interface
      • 1.1.437. Error creating proxy thread
      • 1.1.438. User initiated proxy termination request received
      • 1.1.439. Invalid maximum aggregator, no source node
      • 1.1.440. Failed to parse interval from node name
      • 1.1.441. Invalid average aggregator, no source node
      • 1.1.442. Failed to create SZIG socket
      • 1.1.443. Error booting & parsing policy
      • 1.1.444. Error initializing policy
      • 1.1.445. Error loading initial policy, exiting
      • 1.1.446. Reloading policy
      • 1.1.447. Error reloading policy, reverting to old
      • 1.1.448. Connecting to remote host
      • 1.1.449. Established connection
      • 1.1.450. Error creating client socketpair for stacked proxy
      • 1.1.451. Error creating server socketpair for stacked proxy
      • 1.1.452. Stacking subproxy
      • 1.1.453. Error creating control socketpair for stacked proxy
      • 1.1.454. Stacking program
      • 1.1.455. Error parsing auth_agent command
      • 1.1.456. Cannot find proxy module
      • 1.1.457. Attribute fetched
      • 1.1.458. Attribute changed
      • 1.1.459. Error calling AuthenticationProvider method
      • 1.1.460. Error opening socket
      • 1.1.461. Error connecting UDP socket (nf)
      • 1.1.462. Error querying local address (nf)
      • 1.1.463. Error during setsockopt(IPPROTO_IP, IP_RECVORIGADDRS)
      • 1.1.464. Error during setsockopt(IPPROTO_IPV6, IPV6_RECVORIGADDRS)
      • 1.1.465. Cannot create socket
      • 1.1.466. Dispatch thread starting
      • 1.1.467. Accept queue stats
      • 1.1.468. Dispatch thread exiting
      • 1.1.469. Error creating dispatch thread, falling back to non-threaded mode
      • 1.1.470. Incoming connection
      • 1.1.471. Nobody was interested in this connection
      • 1.1.472. Transparent listener connected directly, dropping connection
      • 1.1.473. Error registering dispatch, previous entry specified accept_one
      • 1.1.474. Internal error, dispatch entry not found (chain exists)
      • 1.1.475. Internal error, dispatch entry not found (no chain)
      • 1.1.476. Error connecting to auth_agentd
      • 1.1.477. AuthAgent authentication failed, unable to determine target address
      • 1.1.478. AuthAgent authentication failed, cannot connect to client
      • 1.1.479. Error connecting to auth_agent, TLS handshake failed
      • 1.1.480. AuthAgent authentication failed, unknown address family
      • 1.1.481. AuthAgent authentication failed, unable to write request information
      • 1.1.482. AuthAgent authentication failed, error reading answer
      • 1.1.483. Connection denied by policy
      • 1.1.484. Dispatcher on address
      • 1.1.485. Unexpected EOF while transferring from server
      • 1.1.486. Eofmask is updated
      • 1.1.487. Data transfer timed out
      • 1.1.488. Data transfer interrupted by progress
  • 2. Management Server log messages
    • 2.1.
      • 2.1.1. Module successfully loaded
      • 2.1.2. Module loading failed
      • 2.1.3. Module loading failed
      • 2.1.4. Module loading failed
      • 2.1.5. Module loading failed
      • 2.1.6. Module loading failed
      • 2.1.7. Cannot open plugin directory
      • 2.1.8. Module loading failed
      • 2.1.9. Cannot open plugin directory
      • 2.1.10. Signal received, stackdump follows
      • 2.1.11. SIGHUP received, reloading config
  • 3. MS Transfer Agent log messages
    • 3.1.
      • 3.1.1. Signal received, stackdump follows
  • 4. Authentication Server log messages
    • 4.1.
      • 4.1.1. Module successfully loaded
      • 4.1.2. Module initialization failed
      • 4.1.3. Error dlopening module
      • 4.1.4. Cannot open plugin directory
      • 4.1.5. Signal received, stackdump follows
  • 5. Authentication Agent log messages
    • 5.1.
      • 5.1.1. Signal received, stackdump follows
  • 6. Content Filtering log messages
    • 6.1.
      • 6.1.1. Module successfully loaded
      • 6.1.2. Module initialization failed
      • 6.1.3. Error dlopening module
      • 6.1.4. Cannot open plugin directory
      • 6.1.5. Signal received, stackdump follows
  • Appendix A. Creative Commons Attribution Non-commercial No Derivatives (by-nc-nd) License
 

Search Highlighter (On/Off)