[AOLSERVER] Logging
Apart from asking myself Why here is how to do it: a) Setup NGINX on one server in reverse proxy mode: http:// cognovis.de/developer/en/nginx_virtual_hosts b) In the NGINX configuration make sure that for each server running in the backend you use the *SAME* logfile. You might have to play around with the logformat to get the server name in there, see http:// wiki.codemongers.com/NginxHttpLogModule and I have forgotten what the global variable for the servername is, just look on the wiki or ask on the mailinglist. Cheers Malte Am 18.09.2007 um 06:00 schrieb AOLSERVER automatic digest system: Is there any sane way to get combined logs from more than one instance of AOLserver? I would like to have the entries interleaved with an identifier of which instance they came from. From what I have read it seems impossible. These instances are on different physical servers too. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Logging
Ian Harding wrote: Is there any sane way to get combined logs from more than one instance of AOLserver? I would like to have the entries interleaved with an identifier of which instance they came from. From what I have read it seems impossible. These instances are on different physical servers too. Thanks, Ian One way to address this issue with apache is mod_log_spread which sends log messages over the spread group communications toolkit[1]. It wouldn't be difficult to set up something similar for aolserver. I don't know offhand if the tcl spread library is threadsafe (I suspect it isn't), but it would probably be better in any case to redo it as a ns_spread module that would share one spread connection across all threads. Still, the api is straightforward and the implementation would fairly simple. Once that's in place just use a filter proc to log to the spread channel. Another route would be to use syslog; I'm not familiar with any tcl libs for that, but again a C implementation wouldn't be too tough. -J [1] http://spread.org/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Logging
We use logresolvemerge.pl which is included with AWStats. Jade On 9/17/07, Jeff Rogers [EMAIL PROTECTED] wrote: Ian Harding wrote: Is there any sane way to get combined logs from more than one instance of AOLserver? I would like to have the entries interleaved with an identifier of which instance they came from. From what I have read it seems impossible. These instances are on different physical servers too. Thanks, Ian One way to address this issue with apache is mod_log_spread which sends log messages over the spread group communications toolkit[1]. It wouldn't be difficult to set up something similar for aolserver. I don't know offhand if the tcl spread library is threadsafe (I suspect it isn't), but it would probably be better in any case to redo it as a ns_spread module that would share one spread connection across all threads. Still, the api is straightforward and the implementation would fairly simple. Once that's in place just use a filter proc to log to the spread channel. Another route would be to use syslog; I'm not familiar with any tcl libs for that, but again a C implementation wouldn't be too tough. -J [1] http://spread.org/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- Jade Rubick Acting Chief Information Officer United eWay [EMAIL PROTECTED] tel (503)285-4963 fax (707)671-1333 www.UNITEDeWAY.org -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] Logging
Jeff Rogers wrote: One way to address this issue with apache is mod_log_spread which sends log messages over the spread group communications toolkit[1]. It wouldn't be difficult to set up something similar for aolserver. I don't know offhand if the tcl spread library is threadsafe (I suspect it isn't), but it would probably be better in any case to redo it as a ns_spread module that would share one spread connection across all threads. Still, the api is straightforward and the implementation would fairly simple. Once that's in place just use a filter proc to log to the spread channel. I ripped out most of the tcl_spread module and changed it into an AOLserver module that implements a single command with no options, to send a message to a channel. I'd consider it proof-of-concept quality code; there's plenty that could be done to improve it if there's interest. http://home.diphi.com/users/jeffr/software/ -J -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Logging
Is there any sane way to get combined logs from more than one instance of AOLserver? I would like to have the entries interleaved with an identifier of which instance they came from. From what I have read it seems impossible. These instances are on different physical servers too. Thanks, Ian -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] Logging: reverse dns lookups and file access permissions
I have a patch at http://www.theashergroup. com/download, ns_log_modes, that modifies nsd/log.c to examine a new config.tcl parameter ns_section ns/parameters ns_param serverlogmode 0664 nsd/log.c will open the server log and then change its mode to serverlogmode. Serverlogmode defaults to 0644. Also, the access log has a similar change: ns_section ns/server/yourserver/module/nslog ns_param accessmode 0664 ns_param iplookups true nslog/nslog.c will open the access log and then change its mode to accessmode. Accessmode also defaults to 0644. I find that opening logs to different modes is useful for ISPs or corporate installations of AOLserver, in which different users, at different times, may need to start/stop AOLserver, and/or delete the log files. I also added a new parameter, iplookups that defaults to off. If set to on, then the access log will perform Reverse DNS Lookups for you. The usual caveat applies, that this can slow down overall AOLserver performance. = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688