Zorp 3.4 LTS Log Messages Guide
Table of Contents
- Preface
- 1. Log message details
- 1.1. Established connection
- 1.2. Error calling AuthenticationProvider method
- 1.3. Module successfully loaded
- 1.4. Module loading failed
- 1.5. Connecting to remote host
- 1.6. Cannot find proxy module
- 1.7. Cannot find proxy module
- 1.8. Attribute fetched
- 1.9. Attribute changed
- 1.10. Error parsing satyr command
- 1.11. Internal error in z_policy_stream_new: input ZStream is NULL
- 1.12. Error connecting to satyrd
- 1.13. Satyr authentication failed, unable to determine target address
- 1.14. Satyr authentication failed, cannot connect to client
- 1.15. Error connecting to satyr, SSL handshake failed
- 1.16. Satyr authentication failed, unknown address family
- 1.17. Satyr authentication failed, unable to write request information
- 1.18. Satyr authentication failed, error reading answer
- 1.19. Error booting & parsing policy
- 1.20. Error initializing policy
- 1.21. Error loading initial policy, exiting
- 1.22. Error initializing audit system
- 1.23. Reloading policy
- 1.24. Error reloading policy, reverting to old
- 1.25. Failed to parse URL filter database
- 1.26. Error opening socket
- 1.27. Error connecting UDP socket (nf)
- 1.28. Error querying local address (nf)
- 1.29. Error during setsockopt(SOL_IP, IP_RECVORIGADDRS)
- 1.30. Cannot create socket
- 1.31. Dispatch thread starting
- 1.32. Accept queue stats
- 1.33. Dispatch thread exiting
- 1.34. Error creating dispatch thread, falling back to non-threaded mode
- 1.35. Incoming connection
- 1.36. Nobody was interested in this connection
- 1.37. Transparent listener connected directly, dropping connection
- 1.38. Error registering dispatch, previous entry specified accept_one
- 1.39. Internal error, dispatch entry not found (chain exists)
- 1.40. Internal error, dispatch entry not found (no chain)
- 1.41. Accepting certficate even though CRL was missing as directed by the policy
- 1.42. CRL has invalid nextUpdate field
- 1.43. CRL is expired
- 1.44. CRL not found for certificate
- 1.45. CRL not found for certificate
- 1.46. Error creating client socketpair for stacked proxy
- 1.47. Error creating server socketpair for stacked proxy
- 1.48. Stacking subproxy
- 1.49. Error creating control socketpair for stacked proxy
- 1.50. Stacking program
- 1.51. Error changing MARK
- 1.52. Error opening policy.boot file
- 1.53. Error opening policy file
- 1.54. Error parsing policy file
- 1.55. Error writing zas stream
- 1.56. eofmask updated
- 1.57. Packet stats timeout elapsed, and no timeout callback specified
- 1.58. Connection denied by policy
- 1.59. Dispatcher on address
- 1.60. Session ID not found for authorization
- 1.61. calling event
- 1.62. calling __destroy__() event
- 1.63. Internal error, trying to look up a non-ZProxyIface compatible interface
- 1.64. Error creating proxy thread
- 1.65. User initiated proxy termination request received
- 1.66. Invalid maximum aggregator, no source node
- 1.67. Invalid maximum aggregator, no source node
- 1.68. Failed to parse interval from node name
- 1.69. Invalid average aggregator, no source node
- 1.70. Failed to create SZIG socket
- 1.71. I/O error opening error file
- 1.72. Unexpected EOF while transferring from server
- 1.73. Eofmask is updated
- 1.74. Data transfer timed out
- 1.75. Data transfer interrupted by progress
- 1.76. Error reading request
- 1.77. Request details
- 1.78. Parse error, dropping request
- 1.79. Invalid character, dropping request
- 1.80. Username too long, dropping request
- 1.81. One hostname is too long in hostname chain, dropping request
- 1.82. Error write request
- 1.83. Error write request
- 1.84. Error write request
- 1.85. Error write request
- 1.86. Policy violation, abort session
- 1.87. Policy violation, drop session
- 1.88. fetching request
- 1.89. asking policy
- 1.90. connecting server
- 1.91. sending request
- 1.92. copying response
- 1.93. everything is done
- 1.94. Invalid stacking tuple returned by policy
- 1.95. Invalid stacking type
- 1.96. Invalid request, data transfer failed
- 1.97. Data transfer failed
- 1.98. Stacked proxy decision
- 1.99. Stacked proxy accepted data
- 1.100. Policy does not contain this request, using hard-coded default
- 1.101. Policy type invalid
- 1.102. Cannot parse policy line
- 1.103. Error in policy calling
- 1.104. Can't parsing return code
- 1.105. Policy does not contain this response, using hard-coded default
- 1.106. Answer type invalid
- 1.107. Bad policy line
- 1.108. Error in policy calling
- 1.109. Return code invalid from policy function
- 1.110. Policy does not contain this feature, dropping
- 1.111. Policy value invalid
- 1.112. Invalid port specified in non-transparent destination
- 1.113. Invalid character in username
- 1.114. Hostname specified in username is too long
- 1.115. Username too long
- 1.116. Username too long
- 1.117. Invalid character in username
- 1.118. Internal error, proxy in unknown state
- 1.119. Internal error, proxy in unknown state
- 1.120. Password too long
- 1.121. Password too long
- 1.122. Internal error, proxy in unknown state
- 1.123. Internal error, proxy in unknown state
- 1.124. Internal error, proxy in unknown state
- 1.125. Unexpected response to data transfer command
- 1.126. Internal error, proxy in unknown state
- 1.127. Invalid parameter for command
- 1.128. Invalid parameter for command
- 1.129. Internal error, proxy in unknown state
- 1.130. Missing parameter for the TYPE command
- 1.131. Valid, but unsupported transfer type specification
- 1.132. Unknown transfer type specification
- 1.133. Missing parameter to the MODE command
- 1.134. Invalid parameter to the MODE command
- 1.135. Missing parameter to the STRU command
- 1.136. Invalid parameter to the STRU command
- 1.137. Error preparing server-side data connection (PORT)
- 1.138. There was an error binding a server-side listener
- 1.139. Error parsing PASV response
- 1.140. Error preparing data connection to the server (PASV)
- 1.141. Error preparing server-side data connection listener (EPRT)
- 1.142. Cannot bind to the given address (EPRT)
- 1.143. Missing parameter (EPSV)
- 1.144. Bad parameter (EPSV), not beginning with bracket
- 1.145. Bad parameter (EPSV), not closing with bracket
- 1.146. Error parsing EPSV response
- 1.147. Bad parameter (EPSV), invalid port
- 1.148. Internal error, cannot detect server address
- 1.149. Unknown protocol type (EPSV)
- 1.150. Error preparing data connection to the server (EPSV)
- 1.151. Invalid parameters to the PORT command
- 1.152. Connection mode not supported
- 1.153. Error preparing client-side data connection (PORT-<;PASV)
- 1.154. Error parsing the server answer to the PASV command (PORT-<;PASV)
- 1.155. Error preparing client-side data connection (PORT)
- 1.156. Error parsing the server answer to the PORT command
- 1.157. Connection mode not supported
- 1.158. Error preparing client-side data connection listener (PASV)
- 1.159. Error preparing client-side data connection listener (PASV)
- 1.160. Error preparing client-side data connection listener (PASV-<;PORT)
- 1.161. Error preparing client-side data connection listener (PASV-<;PORT)
- 1.162. Error parsing the server answer to the PORT command (PASV-<;PORT)
- 1.163. Missing parameter (EPRT)
- 1.164. Bad parameter (EPRT)
- 1.165. Bad port parameter (EPRT)
- 1.166. Unknown protocol method (EPRT)
- 1.167. Bad host address (EPRT)
- 1.168. Connection mode not supported
- 1.169. Error preparing client connect (EPRT)
- 1.170. Bad server answer (EPRT)
- 1.171. Error preparing client connect (EPRT)
- 1.172. Connection mode not supported
- 1.173. Error preparing client listen (EPSV)
- 1.174. Error preparing client listen (EPSV)
- 1.175. Error preparing client listen (EPSV)
- 1.176. Error preparing client listen (EPSV)
- 1.177. Bad server answer (EPSV)
- 1.178. Error parsing command (ALLO)
- 1.179. Client foreign port below 1024
- 1.180. Server foreign port below 1024 in passive mode
- 1.181. Server foreign port is not good in active mode
- 1.182. Unknown side when calling bounceCheck
- 1.183. Data connection accepted on client side
- 1.184. Data connection accepted on server side
- 1.185. Data connection established on client side
- 1.186. Connected to client, but connection is not expected
- 1.187. Data connection established on server side
- 1.188. Connected to server, but connection is not expected
- 1.189. Internal error, previous dispatcher not unregistered
- 1.190. Internal error, previous attach not unregistered
- 1.191. Internal error, previous attach not unregistered
- 1.192. Internal error, previous dispatcher not unregistered
- 1.193. Resetting data connection
- 1.194. Internal error, previous data connection is not closed properly
- 1.195. Internal error, cannot start data proxy because peers are not yet connected
- 1.196. Internal error, current command descriptor does not specify data transfer
- 1.197. Data connection established
- 1.198. Possible bounce attack
- 1.199. Possible bounce attack
- 1.200. Possible bounce attack
- 1.201. Possible bounce attack
- 1.202. Internal error, client side not connected
- 1.203. Internal error, server side not connected
- 1.204. Max_line_length above upper limit
- 1.205. Max_username_length above max_line_length
- 1.206. Max_password_length above max_line_length
- 1.207. Max_hostname_length above max_line_length
- 1.208. Error parsing valid_chars_username
- 1.209. Internal error in stream write, side is wrong
- 1.210. Cannot write full line
- 1.211. Server answer doesn't begin with number
- 1.212. Response arrived
- 1.213. Error reading from server
- 1.214. Line is too short to be a valid answer
- 1.215. Server answer has wrong continuation mark
- 1.216. Rejected answer
- 1.217. Error reading from client
- 1.218. Request fetched
- 1.219. Empty command. Aborting
- 1.220. Unknown command. Aborting
- 1.221. Internal error, known command but command parse is unset
- 1.222. This command not allowed in non-transparent mode
- 1.223. Request rejected
- 1.224. Proxy answer
- 1.225. Rejected command (aborting)
- 1.226. Bad policy type, aborting
- 1.227. Too many continuous lines in the answer
- 1.228. Reading from peer
- 1.229. Invalid HTTP_HDR_CHANGE_NAME rule in header processing
- 1.230. Invalid HTTP_HDR_CHANGE_VALUE rule in header processing
- 1.231. Invalid HTTP_HDR_CHANGE_BOTH rule in header processing
- 1.232. Invalid value in header action tuple
- 1.233. Error reading from peer while fetching headers
- 1.234. First header starts with white space
- 1.235. Invalid HTTP header
- 1.236. Too many header lines
- 1.237. Request method empty, or too long
- 1.238. URL missing, or too long
- 1.239. Protocol version missing, or too long
- 1.240. Request details
- 1.241. Invalid HTTP status line
- 1.242. Response version empty or too long
- 1.243. Response code empty or too long
- 1.244. Response details
- 1.245. Unknown protocol version
- 1.246. Unknown protocol version
- 1.247. Invalid FTP response, line too short
- 1.248. Invalid FTP response, response code not numeric
- 1.249. Invalid FTP response, continuation line contains different status code
- 1.250. FTP server returned an unhandled status code for the login request
- 1.251. Error logging in
- 1.252. Error in FTP greeting, expecting 220
- 1.253. Error changing directory on server
- 1.254. Error changing directory on server
- 1.255. Error changing directory on server
- 1.256. Error sending RETR or LIST command to FTP server
- 1.257. Error establishing data connection to FTP server
- 1.258. Error reading data channel confirmation from FTP server
- 1.259. Error reading 226 from FTP server
- 1.260. Http accounting
- 1.261. Request administratively prohibited
- 1.262. Internal error, error code out of range
- 1.263. An error occurred, would serve error file, but silent mode is enabled
- 1.264. An error occurred, serving error file
- 1.265. Error writing stream, stream is NULL
- 1.266. Error writing stream
- 1.267. Only Basic authentication is supported
- 1.268. Invalid base64 encoded username:password pair
- 1.269. No colon is found in the decoded username:password pair
- 1.270. Invalid HTTP request received
- 1.271. Found category match for URL
- 1.272. CONNECT method without version specification
- 1.273. Both Proxy-Connection and Connection headers exist
- 1.274. This request type is not permitted in transparent mode
- 1.275. No host header in transparent request, 'unknown' is used instead
- 1.276. 'Host:' header is required, and HTTP/0.9 can't transfer headers
- 1.277. No 'Host:' header in request, and policy requires this
- 1.278. Error parsing URL
- 1.279. Error parsing URL
- 1.280. Client attempted to use FTP over HTTP, which is currently disabled
- 1.281. Unsupported scheme in URL
- 1.282. Too long hostname in URL
- 1.283. Accounting
- 1.284. Invalid item in request hash
- 1.285. Error parsing HTTP_REQ_POLICY tuple in request hash
- 1.286. Error parsing HTTP_REQ_REJECT in request hash
- 1.287. Unknown request hash item
- 1.288. Request not permitted by policy
- 1.289. Request not permitted by policy
- 1.290. Connecting to this port is prohibited by policy
- 1.291. Internal error initializing server stream
- 1.292. Error in HTTP/0.9 compatibility code, line buffer full
- 1.293. Server falled back to HTTP/0.9 which is prohibited by policy
- 1.294. Invalid HTTP response heading
- 1.295. Error parsing response version
- 1.296. Unsupported protocol version
- 1.297. Invalid response hash item
- 1.298. Error parsing HTTP_RSP_POLICY in response hash
- 1.299. Error parsing HTTP_RSP_REJECT in response hash
- 1.300. Invalid response hash item
- 1.301. Response not permitted by policy
- 1.302. Missing port number in CONNECT request
- 1.303. Parent proxy refused our CONNECT request
- 1.304. Starting connect method
- 1.305. Internal error, connectMethod is expected to return a proxy instance
- 1.306. Fetching request and headers
- 1.307. processing request and headers
- 1.308. Maximum keep-alive request reached, setting connection mode to close
- 1.309. Filtering request and headers
- 1.310. Reprocessing filtered request
- 1.311. Sending request and headers, copying request data
- 1.312. Fetching response and headers
- 1.313. Processing response and headers
- 1.314. Filtering response and headers
- 1.315. Copying response and headers, copying response data
- 1.316. Internal error, invalid server_protocol
- 1.317. exiting keep-alive loop
- 1.318. Chunk length line too long
- 1.319. Invalid chunk length
- 1.320. Invalid chunk length
- 1.321. Chunk too large
- 1.322. Unexpected EOF while dechunking stream
- 1.323. Chunk footer is not an empty line
- 1.324. Stacked proxy sent a content-length hint, using it
- 1.325. Invalid stacking tuple returned by policy
- 1.326. Invalid stacking type
- 1.327. The header 'Content-Length' was present, but is not a number
- 1.328. Invalid request, data transfer failed
- 1.329. Data transfer failed
- 1.330. Stacked proxy decision
- 1.331. Stacked proxy accepted data
- 1.332. Internal error, not enough literals
- 1.333. Internal error, too many literals
- 1.334. Error while writing policy response
- 1.335. Error while writing policy response
- 1.336. Failed to parse command
- 1.337. Error writing to client
- 1.338. Reconstructed request
- 1.339. Illegal tag
- 1.340. Duplicate tag
- 1.341. Command not allowed in this state
- 1.342. Error parsing command
- 1.343. Request denied by policy
- 1.344. Dropping request
- 1.345. Policy responds to client
- 1.346. Aborting connection due to request
- 1.347. Too many pending requests
- 1.348. Error writing to server
- 1.349. Stray continuation response
- 1.350. Error writing to server
- 1.351. Error writing to server
- 1.352. Error writing to server
- 1.353. Server returned untagged line during authentication exchange, dropping it
- 1.354. Aborting connection due to a response
- 1.355. Dropping response
- 1.356. Invalid response
- 1.357. Error writing to client
- 1.358. Response arrived for unknown request
- 1.359. Aborting connection due to a response
- 1.360. Dropping response
- 1.361. Invalid response
- 1.362. Error writing to client
- 1.363. Complete response arrived
- 1.364. Reconstructed response
- 1.365. Reading literal
- 1.366. No free literal space
- 1.367. Illegal character
- 1.368. Illegal literal length form
- 1.369. Literal length attribute not closed
- 1.370. Stacked proxy rejected contents
- 1.371. Policy type is invalid
- 1.372. Cannot parse stack policy line
- 1.373. Cannot parse stack policy line
- 1.374. Error in policy call
- 1.375. Cannot parse return code
- 1.376. Response count for the request reached limit, drop packets
- 1.377. Response count for request reached limit, aborting connection
- 1.378. Invalid value for response_overrun_action, falling back to LDAP_RSP_DROP
- 1.379. Policy nesting do deep
- 1.380. Policy type invalid
- 1.381. Cannot parse policy line
- 1.382. Cannot parse policy line
- 1.383. Cannot parse policy line
- 1.384. Cannot parse policy line
- 1.385. Error in policy calling
- 1.386. Policy does not contain this header, using hard-coded default
- 1.387. Policy does not contain this mime-type, using hard-coded default
- 1.388. Answer type invalid
- 1.389. Bad policy line
- 1.390. Error in policy calling
- 1.391. Return code invalid from policy function
- 1.392. Policy does not contain this error, using hard-coded default
- 1.393. Cannot parse policy line
- 1.394. Error in policy calling
- 1.395. Error parsing return code
- 1.396. Stacked proxy rejected contents
- 1.397. Stack policy type is invalid
- 1.398. Cannot parse stack policy line
- 1.399. Error in policy call
- 1.400. Cannot parse return code
- 1.401. Invalid return value of packetStats(), integer required
- 1.402. packetStats() requested to abort session
- 1.403. Dropping request parameter, no parameter allowed
- 1.404. The required numerical parameter of the request is missing
- 1.405. The numerical parameter of the request is not in the given range
- 1.406. The numerical parameter of the request is negative
- 1.407. The numerical parameter of the request is zero
- 1.408. The numerical parameter of the request contains junk after the number
- 1.409. The first numerical parameter of the request is not in the given range
- 1.410. The first numerical parameter of the request is negative
- 1.411. Only one numerical argument in request
- 1.412. The second numerical parameter of the request is not in the given range
- 1.413. The second numerical parameter of the request is a negative number
- 1.414. The numerical parameter of the request contain junk after the number
- 1.415. Username is too long
- 1.416. Password is too long
- 1.417. The username parameter is too long or the digest parameter is missing
- 1.418. Error parsing the MD5 digest
- 1.419. The required numerical parameter of the response is missing
- 1.420. The numerical parameter of the response is not in the given range
- 1.421. The numerical parameter of the response is a negative number
- 1.422. The numerical parameter of the response contains junk after the number
- 1.423. The numerical parameter of the response is not in the given range
- 1.424. The required numerical parameter of the response is missing
- 1.425. The numerical parameter of the response is a negative number
- 1.426. The second numerical parameter of the response is not in the given range
- 1.427. The required second numerical parameter of the response is missing
- 1.428. The second numerical parameter of the response is a negative number
- 1.429. The second numerical parameter of the response contains junk after the number
- 1.430. Response line too long
- 1.431. Response status is invalid
- 1.432. Response fetched with parameter
- 1.433. Response fetched
- 1.434. Data transfer failed
- 1.435. Request line too long
- 1.436. Request fetched with parameter
- 1.437. Request fetched
- 1.438. Unknown request command
- 1.439. Request command not allowed in this state
- 1.440. Stacked proxy rejected contents
- 1.441. Policy does not contain this request, using hard-coded default
- 1.442. Policy type is invalid
- 1.443. Cannot parse policy line
- 1.444. Error in policy call
- 1.445. Cannot parse the return code
- 1.446. Policy does not contain this request, using hard-coded default
- 1.447. Policy type is invalid
- 1.448. Cannot parse policy line
- 1.449. Error in policy call
- 1.450. Cannot parse return code
- 1.451. Stack policy type is invalid
- 1.452. Cannot parse stack policy line
- 1.453. Cannot parse stack policy line
- 1.454. Error in policy call
- 1.455. Cannot parse return code
- 1.456. Error parsing local part
- 1.457. Local part does not end in '@'
- 1.458. Invalid domain name in path
- 1.459. Path does not start with '>;'
- 1.460. Invalid source route information
- 1.461. Invalid address information
- 1.462. Path does not begin with '>;' but ends with '<;'
- 1.463. Path begins with '>;' but does not end with '<;'
- 1.464. Invalid SIZE extension in the MAIL command
- 1.465. Invalid BODY extension in the MAIL command
- 1.466. Invalid AUTH sender, not an xtext
- 1.467. Invalid extension in the MAIL command
- 1.468. Invalid request policy type
- 1.469. Error in request policy
- 1.470. Error in request policy
- 1.471. The verdict returned by the policy is not an int
- 1.472. Invalid response policy
- 1.473. Error in response policy
- 1.474. Error in response policy
- 1.475. The verdict returned by the policy is not an int
- 1.476. Sender address administratively prohibited
- 1.477. Sender check successful
- 1.478. Forbidden percent found in address local-part
- 1.479. Forbidden exclamation mark found in address local-part
- 1.480. Relaying denied
- 1.481. Relay check successful
- 1.482. Recipient address administratively prohibited
- 1.483. Recipient check successful
- 1.484. Relay check, checking client_zone
- 1.485. Relay check, checking mail domain
- 1.486. Invalid command verb in request
- 1.487. Request parsed
- 1.488. Fetching request
- 1.489. Request line too long
- 1.490. Processing request
- 1.491. Command not permitted in this state
- 1.492. Unknown command
- 1.493. Copying request to server
- 1.494. Error sending request
- 1.495. Fetching authentication request
- 1.496. Auth request line too long
- 1.497. Copying authentication request to server
- 1.498. Error sending authentication request
- 1.499. SMTP reply contains non-numeric characters
- 1.500. Invalid continuation character
- 1.501. Fetching response
- 1.502. Response line too long
- 1.503. Invalid SMTP reply, reply code changed
- 1.504. Response parsed
- 1.505. Processing response
- 1.506. Copying response to client
- 1.507. Error sending SMTP reply
- 1.508. Invalid policy ignored, allowing 250 response to NOOP is required
- 1.509. Invalid policy ignored, allowing 354 response to DATA is required
- 1.510. Invalid contents
- 1.511. Error occured while scanning contents
- 1.512. Rejecting empty message
- 1.513. Error sending RSET to the server
- 1.514. Exiting SMTP loop
- 1.515. Invalid stacking type
- 1.516. Invalid stacking tuple returned by policy
- 1.517. Evaluating BACL rule
- 1.518. BACL result
- 1.519. Cache over shift-threshold, shifting
- 1.520. Server connection failure
- 1.521. Server connection established
- 1.522. Server connection failure, no destination
- 1.523. All destinations are down, clearing cache and trying again
- 1.524. Destination is down, skipping
- 1.525. Destination is down, keeping state
- 1.526. Side stacking failed, socketPair failed
- 1.527. Side-stacking proxy instance
- 1.528. Side-stacking failed
- 1.529. Before NAT mapping
- 1.530. After NAT mapping
- 1.531. Starting proxy instance
- 1.532. Ending proxy instance
- 1.533. Outbound service
- 1.534. Inbound service
- 1.535. Proxy ending
- 1.536. Proxy destroy
- 1.537. Stacking child proxy on right side
- 1.538. Stacking child proxy
- 1.539. Error while stacking child proxy
- 1.540. Stacking custom child
- 1.541. Error resolving hostname
- 1.542. Internal error, stacked proxy reconnected to server multiple times
- 1.543. Zone not found
- 1.544. DAC policy violation
- 1.545. MAC policy violation
- 1.546. Connection accepted
- 1.547. Zone not found
- 1.548. DAC policy violation
- 1.549. MAC policy violation
- 1.550. Authentication failure
- 1.551. Connection over permitted limits
- 1.552. Attempt to use an unlicensed component, or number of licensed hosts exceeded
- 1.553. No applicable service found for this client zone (cached)
- 1.554. No applicable service found for this client zone
- 1.555. No applicable service found for this client & server zone (cached)
- 1.556. No applicable service found for this client & server zone
- 1.557. Matching regexp found
- 1.558. Error opening match file
- 1.559. Error opening ignore file
- 1.560. Cached recipient match found
- 1.561. Recipient validity not cached, trying the direct way
- 1.562. SMTP sender was rejected, unable to verify user existence
- 1.563. Server accepted recipient
- 1.564. Server rejected recipient
- 1.565. SMTP error during recipient validity checking
- 1.566. Starting service
- 1.567. Outbound service not permitted (cached)
- 1.568. Outbound service not permitted
- 1.569. Inbound service not permitted (cached)
- 1.570. Inbound service not permitted
- 1.571. Instance definition not found in policy
- 1.572. Error downloading KZorp configuration, Python traceback follows
- 1.573. Deinitialization requested for instance
- 1.574. Cleaning up instance
- 1.575. Error flushing KZorp configuration
- 1.576. Signal received, stackdump follows
- 1.577. Invalid license file
- 1.578. Error initializing Python policy engine
- Appendix 1. Creative Commons Attribution Non-commercial No Derivatives (by-nc-nd) License
© 2007-2012 BalaBit IT Security
Please send your comments or documentation bugs to: documentation@balabit.com