Changes between Version 5 and Version 6 of tipimaid

Show
Ignore:
Timestamp:
10/21/09 21:01:52 (8 years ago)
Author:
walter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • tipimaid

    v5 v6  
    1111 
    1212 
    13 == You didn't explain tipimaid_mergelogs! == 
     13== You didn't explain `tipimaid_mergelogs`! == 
    1414 
    1515Patience, my young padawan...  
     
    8080 
    8181 
    82 == What is tipimaid_server? == 
     82== What is `tipimaid_server`? == 
    8383 
    8484`tipimaid_server` listens on a port and redirects everything it receives to `stdout`. 
     
    107107== `tipimaid_mergelogs` == 
    108108 
    109 Let's say you used tipimaid to send logs over a network and really bad things happened (`tipimaid_sender` lost the connection to `tipimaid` for more than `[buffertime]` seconds, i.e. even if `tipimaid_sender` could establish the connection again, there are some log lines which were written to a local (local at the apache computer) recovery file and were not sent over the network).  
     109Let's say you used tipimaid to send logs over a network and really bad things happened (`tipimaid_sender` lost the connection to `tipimaid` for more than `buffertime` seconds, i.e. even if `tipimaid_sender` could establish the connection again, there are some log lines which were written to a local (local at the Apache computer) recovery file and were not sent over the network).  
    110110 
    111 Of course you want to have one coplete log file and that's why we have `tipimaid_mergelogs`. Unfortunately, you have to wait until a new logfile is started (i.e. if you have daily rotation of logfiles you have to wait until tomorrow). 
    112 Then you copy the finished logfile which has been written by `tipimaid` and the recovery file(s) written by `tipimaid_sender`(s) to one directory and start 
     111Of course you want to have one complete log file and that's why we have `tipimaid_mergelogs`. Unfortunately, you have to wait until a new logfile is started (i.e. if you have daily rotation of logfiles you have to wait until tomorrow). 
     112Then you copy the finished logfile which has been written by `tipimaid` and the recovery file(s) written by `tipimaid_sender` to one directory and start 
    113113{{{ 
    114114/path/to/tipimaid_mergelogs.py [tipimaid_logfile] [recovery_file_1] [recovery_file_2] ... > my_new_logfile.log 
     
    127127and they should be `gzip`ped after they were rotated. 
    128128 
    129 The place to go is apache's log configuration file. We choose a `LogFormat` like `vhost_combined` which has `%v` in its first column (this format is defined as 
     129The place to go is Apache's log configuration file. We choose a `LogFormat` like `vhost_combined` which has `%v` in its first column (this format is defined as 
    130130{{{ 
    131131LogFormat "%v %h %l %u %t \"%r\" %>s %b \ 
     
    175175With `tipimaid_server` running, we can configure the senders. 
    176176 
    177 As we already know that we have to talk port 40000 and have a buffertime of 10 minutes (600 seconds), the only thing we have to think about is a local (local at `apache1` and `apache2`) directory where `tipimaid_server` may write temporary recovery files. 
     177As we already know that we have to talk to port 40000 on `logger` and have a buffertime of 10 minutes (600 seconds), the only thing we have to think about is a local (local at `apache1` and `apache2`) directory where `tipimaid_server` may write temporary recovery files. 
    178178So, let's say that `/var/log/recovery` is such a directory. 
    179179 
     
    183183}}} 
    184184 
    185 and as we want to use apache's piped logging, we have to write this line to apache's `.conf` file: 
     185and as we want to use Apache's piped logging, we have to write this line to Apache's `.conf` file: 
    186186 
    187187{{{ 
     
    189189}}} 
    190190 
    191 After this, reload your apache config and after 10 minutes you should see growing logfiles at `logger`. 
     191After this, reload your Apache config and after 10 minutes you should see growing logfiles at `logger`.