7 More Discussions You Might Find Interesting
1. Web Development
I have the following setup in my apache vhost:
ProxyPass /abc http://www.newest.com/
ProxyPassReverse /abc http://www.newest.com/
I want to setup a failover approach in which if after a particular timeout say 10secs the load shifts to some other website like Refer.com | The world. The timeout... (0 Replies)
Discussion started by: ankur328
0 Replies
2. Web Development
Hi team,
I was like unable to solve this interview question, Any help from them experts here please..
"Your supervisor requires that all web requests for "http://dev.example.net" be passed to "http://newdev.example.net". She states that upon redirect, the URL in the web browser must remain... (1 Reply)
Discussion started by: leo_ultra_leo
1 Replies
3. Red Hat
Hi to all member's forum.
I have an httpd server with mod_proxy that forward any request to an another server.
the flow is: client --> requesto proxy https://miosito.it --> forward to server https://192.168.0.10:8443/
I'm reading this error in my httpd log in LogLevel debug (after some... (0 Replies)
Discussion started by: lain
0 Replies
4. UNIX and Linux Applications
I am using Apache 2.2.3 on RHEL5 and having problems to get mod_deflate work with mod_proxy. mod_deflate will compress files by mime-type just fine as long as those files are served statically from the local server. However, files served via dynamic php application (ie, MediaWiki) or via... (2 Replies)
Discussion started by: otheus
2 Replies
5. IP Networking
My company has a private network, including a Apache web server (Linux) and some WinXP machines. The web server had been configured to use mod_proxy to connect to window update site via another company proxy server. It works for few years.
Recently, some parties had setup a DNS server on the... (2 Replies)
Discussion started by: donaldfung
2 Replies
6. UNIX for Advanced & Expert Users
Double question here ... Running on Debian Etch and Apache 2.0
1) Using mod_proxy and/or mod_proxy_http in apache 2.0.
The basics of using mod_proxy are pretty simple so long as you're using a static config. I'm trying to figure out how to do it dynamically - that is, allow the entry of a... (4 Replies)
Discussion started by: Halfwalker
4 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I need an ActiveX com component to raise events in a Unix program. Is it possible for Unix programs to interop with Win32 ActiveX exe?
Thanks,
Lee. (1 Reply)
Discussion started by: lee_b
1 Replies
Perlbal::Manual::Debugging(3pm) User Contributed Perl Documentation Perlbal::Manual::Debugging(3pm)
NAME
Perlbal::Manual::Debugging - Debugging Perlbal
VERSION
Perlbal 1.78.
DESCRIPTION
Perlbal has two ways of debugging.
One of them is through a management console; the other is through debugging messages.
Debugging in a console
You'll need to set up a management service and use it to dump all the information you require.
The comprehensive documentation on this process can be found at Perlbal::Manual::Management.
Debugging messages
You can control the ammount of debugging messages Perlbal dumps by setting the environment variable "PERLBAL_DEBUG" to a value between 0
and 4:
PERLBAL_DEBUG = 0 # no debug
PERLBAL_DEBUG = 4 # debug everything
Debug level 1
You can activate basic debug by setting "PERLBAL_DEBUG" to 1:
PERLBAL_DEBUG = 1
The following debugging messages are turned on:
o When a connection to a backend is closed, Perlbal::BackendHTTP prints "Backend $self is done; closing..."
o When a connection to a backend is killed, Perlbal::ClientProxy prints "Client ($self) closing backend ($backend)"
o When an HTTP request fails to be parsed, Perlbal::HTTPHeaders prints "HTTP parse failure: $reason"
o When the connection is promoted to SSL, Perlbal::TCPListener prints " .. socket upgraded to SSL!"
Debug level 2
By setting the debug level to 2 you'll get all the messages from level 1.
PERLBAL_DEBUG = 2
You will also get a few others:
o When a connection to a backend is opened and ready to be written to, Perlbal::BackendHTTP prints "Backend $self is writeable!"
o When a response is about to be handled, Perlbal::BackendHTTP prints "BackendHTTP: handle_response"
o When a backend is ready to be read from, Perlbal::BackendHTTP prints "Backend $self is readable!"
o When there's an error with the connection to the backend, Perlbal::BackendHTTP prints "BACKEND event_err"
o Whenever we're determining if we should be sending keep-alive header information back to the client, Perlbal::ClientHTTPBase prints
"ClientHTTPBase::setup_keepalive($self)"
o Whenever the client is ready for more of its file, Perlbal::ClientHTTPBase prints "REPROXY SSL done"
o Right after we've read a chunk of a file and when a reproxy request is about to be sent, Perlbal::ClientHTTPBase prints "REPROXY Sent:
$sent"
o When we've written all data in the queue (and are about to stop waiting for write notifications), Perlbal::ClientHTTPBase prints "All
writing done to $self"
o Whenever a client proxy is about to be closed, Perlbal::ClientProxy prints "Perlbal::ClientProxy closed", followed by a possible
"again" and a possible "saying $reason"
o When a client has disconnected, Perlbal::ClientProxy prints "ClientProxy::client_disconnected"
o When a backend requests a client of a high priority request and the client is available, "Service" in Perlbal prints "Got from fast
queue, in front of $backlog others"
o When a backend requests a client of a normal priority request and the client is available, "Service" in Perlbal prints "Backend
requesting client, got PRIORITY = $cp-"{fd}.>
o When a backend requests a client of a low priority request and the client is available, "Service" in Perlbal prints "Backend requesting
client, got low priority = $cp-"{fd}.>
o When header are being read, Perlbal::Socket prints "Perlbal::Socket::read_headers($self) is_res=$is_res"
Debug level 3
PERLBAL_DEBUG = 3
By setting the debug level to 3 you'll get all the messages from level 1 and 2 plus the following:
o Right before response headers are written to the client, Perlbal::BackendHTTP prints " writing response headers to client"
o As we're writing to the client, Perlbal::BackendHTTP prints " content_length=VALUE" and " remain=VALUE", where the values are "undef"
if they are not defined
o If we're done writing to the client, Perlbal::BackendHTTP prints " done. detaching."
o Whenever we're determining if we should be sending keep-alive header information back to the client, Perlbal::ClientHTTPBase prints "
service's persist_client = $persist_client"
o While determining if we should be sending keep-alive header information back to the client, if we were sent "content-length" or it's a
head request, as we're doing a keep alive Perlbal::ClientHTTPBase prints " doing keep-alive to client"
o If we're not sending keep-alive header information back ot the client, Perlbal::ClientHTTPBase prints " doing connection: close"
o Right after we've finished sending all of the results to the user, Perlbal::ClientProxy prints "ClientProxy::backend_finished"
o When we've sent a response to a user fully and we need to reset state, Perlbal::ClientProxy prints "ClientProxy::http_response_sent --
resetting state"
o When we're writing a response to a client, Perlbal::ClientProxy prints "ClientProxy::event_write"
o After writing a response to a client, if it is still connected and we're triggering trigger our backend to keep reading,
Perlbal::ClientProxy prints " unstalling backend"
o When reading a request, Perlbal::ClientProxy prints "ClientProxy::event_read"
o When reading a request and just before we read the headers, Perlbal::ClientProxy prints " no headers. reading."
o When reading a request, if we're not buffering to disk or we're no longer reading, as we disable reads, Perlbal::ClientProxy prints "
disabling reads."
o As we're reading, Perlbal::ClientProxy prints " reading $read_size bytes (VALUE bytes remain)", where "VALUE bytes remain" can be
<undef>
o After each read, Perlbal::ClientProxy prints " read $len bytes"
o After we finished reading the request, Perlbal::ClientProxy prints " done_reading = $done_reading, backend = BACKEND", where "BACKEND"
can be "undef"
o When we send the headers to the backend and it responds before we're done reading from the client, further reads from the client are
discarded; in this situation Perlbal::ClientProxy prints " already responded.". If the client continues to send data,
Perlbal::ClientProxy prints " already responded [2]." and then gives up on reading
o After reading, and having a backend available where we can write to, just before we do, Perlbal::ClientProxy prints " got a backend.
sending write to it."
o After reading, if there's no backend available, Perlbal::ClientProxy prints " no backend. read_ahead = $self-"{read_ahead}.>
o If we know we've already started spooling a file to disk and we're about to continue doing so, Perlbal::ClientProxy prints " bureason
= $self-"{bureason}>
o If a backend wasn't available and we're about to request one, Perlbal::ClientProxy prints " finally requesting a backend"
o When we're trying to read headers and the client has disconnected, Perlbal::Socket prints " client disconnected"
o If we need to remove a trailing "
" from the headers, Perlbal::Socket prints " throwing away leading
"
o If we've read a packet with headers and by the end of it we can't find the end of them, Perlbal::Socket prints " can't find end of
headers"
o Once we've read some headers, Perlbal::Socket prints " pre-parsed headers: [$hstr]"
o After reading headers, if there's additional content that we've read, we push it back; when we do so, Perlbal::Socket prints " pushing
back $len bytes after header"
o If we got bogus headers, and right before we close the connection due to a parsing failure, Perlbal::Socket prints " bogus headers"
o If we got valid headers, Perlbal::Socket prints " got valid headers"
o If we're reading buffered data from a client, Perlbal::Socket prints "draining readbuf from $self to $dest: [$$bref]"
Debug level 4
By setting the debug level to 4 you get all the messages from levels 1 to 3.
Plus, "write" is redefined so that whenever "write" is called it first prints "write($self, <$clen>"$content") from ($pkg, $filename,
$line)".
PERLBAL_DEBUG = 4
SEE ALSO
Perlbal::Manual::Configuration, Perlbal::Manual::Management.
perl v5.14.2 2011-01-23 Perlbal::Manual::Debugging(3pm)