How to get an HTTP Debug Log from the ProxySG?

book

Article ID: 166415

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

My ProxySG is having HTTP problems.
How can I generate an HTTP Debug Log to try to find the root of the problem?

Resolution

Please follow these steps when instructed to do so by Blue Coat Technical Support.

How to get a HTTP Debug Log:

1. Navigate to an advanced HTTP console url: https://<ip.address.of.proxy>:8082/HTTP/debug/SetDebugMask. Here you will need to specify exactly what you want traced. In most cases you will need to select all of the options if a HTTP Debug Log has been requested from you.

2. Go to the actual debug page at https://<ip.address.of.proxy>:8082/HTTP/Debug, or simply follow the 'Display HTTP Debug Info' from the SetDebugMask console page

3. Generate a request through the ProxySG, refresh the /HTTP/Debug console URL and observe the HTTP debug trace has been generated. Here is an example:

0901.678 --- End Log [13/Apr/2007:18:09:00 -0000] ---
0901.353 HTTP CW 5EB4BF20: Reset_per_usage_information
0901.352 HTTP CW D81EFF20: Reset_per_usage_information
0901.352 HTTP CW 5EB4BF20: Update_object_statistics
0901.352 HTTP CW 5EB4BF20: Close_source_variant_object called with OD: 0x0, claims: 0, source_variant_obj_state: 0
0901.352 HTTP CW 5EB4BF20: Close_variant_object called with OD: 0x0, claims: 0, variant_obj_state: 0
0901.352 HTTP CW 5EB4BF20: Close_base_object called with OD: 0x0, authenticated_obj_desc: 0x0, base_obj_state: 0
0901.352 HTTP CW 5EB4BF20: HTTP transaction terminated, cleaning up
0901.352 HTTP CW D81EFF20: Update_object_statistics
0901.351 HTTP CW D81EFF20: Close_source_variant_object called with OD: 0x0, claims: 0, source_variant_obj_state: 0
0901.351 HTTP CW D81EFF20: Close_variant_object called with OD: 0x0, claims: 0, variant_obj_state: 0
0901.351 HTTP CW D81EFF20: Close_base_object called with OD: 0x0, authenticated_obj_desc: 0x0, base_obj_state: 0
0901.351 HTTP CW D81EFF20: HTTP transaction terminated, cleaning up
0901.351 HTTP CW 5EB4BF20: Session memory usage just before cleanup:  0 blocks
0901.351 HTTP CW 5EB4BF20: Clean_up
0901.351 HTTP CW D81EFF20: Session memory usage just before cleanup:  0 blocks
0901.351 HTTP CW D81EFF20: Clean_up
0901.351 HTTP CW 5EB4BF20: Tunnel_clean_up
0901.350 HTTP CW D81EFF20: Tunnel_clean_up
0901.350 Tunnel: shutting down server socket (pid: 0x212A590 tunnel: 0x5EB4AC20 sock: 0x5EB4ACDC)
0901.350 Tunnel: shutting down server socket (pid: 0x212A660 tunnel: 0xD81EEC20 sock: 0xD81EECDC)
0901.350 Tunnel: shutting down client socket (pid: 0x212A590 tunnel: 0x5EB4AC20 sock: 0x5EB4ACC0)
0901.350 Tunnel: shutting down client socket (pid: 0x212A660 tunnel: 0xD81EEC20 sock: 0xD81EECC0)
0901.349 212A590: Recv_server
0901.349 212A590: Get_next_client_output_buffer
0901.349 212A660: Recv_server
0901.349 212A660: Get_next_client_output_buffer
0901.349 212A590: Send_client
0901.349 212A590: Get_next_client_output_buffer
0901.349 212A590: Processing finished i/o events
0901.348 212A660: Send_client
0901.348 212A660: Get_next_client_output_buffer
0901.348 212A660: Processing finished i/o events
0901.255 212A590: Wait_io_event
0901.255 212A660: Wait_io_event
0901.255 212A590: Recv_client
0901.255 212A590: Get_next_server_output_buffer
0901.254 212A660: Recv_client
0901.254 212A660: Get_next_server_output_buffer
0901.254 212A590: Send_server
0901.254 212A590: Get_next_server_output_buffer
0901.254 212A590: Processing finished i/o events
0901.254 212A660: Send_server
0901.254 212A660: Get_next_server_output_buffer
0901.254 212A660: Processing finished i/o events
0901.125 212A660: Wait_io_event
0901.124 212A660: Recv_server
0901.124 212A660: Get_next_client_output_buffer
0901.124 212A660: Send_client
0901.124 212A660: Get_next_client_output_buffer
0901.123 212A660: Processing finished i/o events
0901.122 212A590: Wait_io_event
0901.122 212A590: Recv_server
0901.122 212A590: Get_next_client_output_buffer
0901.122 212A590: Send_client
0901.122 212A590: Get_next_client_output_buffer
0901.122 212A590: Processing finished i/o events
0901.032 212A660: Wait_io_event
0901.031 212A660: Recv_client
0901.031 212A660: Get_next_server_output_buffer
0901.031 212A660: Send_server
0901.031 212A660: Get_next_server_output_buffer
0901.031 212A660: Processing finished i/o events
0901.031 212A590: Wait_io_event
0901.030 212A590: Recv_client
0901.030 212A590: Get_next_server_output_buffer
0901.030 212A590: Send_server
0901.030 212A590: Get_next_server_output_buffer
0901.030 212A590: Processing finished i/o events
0901.029 212A660: Wait_io_event
0901.029 212A660: Recv_server
0901.029 212A660: Get_next_client_output_buffer
0901.028 212A660: Send_client
0901.028 212A660: Get_next_client_output_buffer
0901.028 212A660: Processing finished i/o events
0901.028 212A590: Wait_io_event
0901.028 212A590: Recv_server
0901.028 212A590: Get_next_client_output_buffer
0901.027 212A590: Send_client
0901.027 212A590: Get_next_client_output_buffer
0901.027 212A590: Processing finished i/o events
0900.947 212A590: Wait_io_event
0900.946 212A590: Recv_server
0900.946 212A590: Get_next_client_output_buffer
0900.946 212A660: Wait_io_event
0900.946 212A590: Send_client
0900.946 212A590: Get_next_client_output_buffer
0900.946 212A590: Processing finished i/o events
0900.946 212A660: Recv_server
0900.946 212A660: Get_next_client_output_buffer
0900.946 212A590: Recv_server