1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2002-1 (1.68)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>4 FAQ</TITLE>
<META NAME="description" CONTENT="4 FAQ">
<META NAME="keywords" CONTENT="documentation">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="LaTeX2HTML v2002-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="documentation.css">
<LINK REL="next" HREF="node6.html">
<LINK REL="previous" HREF="node4.html">
<LINK REL="up" HREF="documentation.html">
<LINK REL="next" HREF="node6.html">
</HEAD>
<BODY >
<!--Navigation Panel-->
<A NAME="tex2html219"
HREF="node6.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html215"
HREF="documentation.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html209"
HREF="node4.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html217"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html220"
HREF="node6.html">About this document ...</A>
<B> Up:</B> <A NAME="tex2html216"
HREF="documentation.html">Installing and Running mod_log_sql</A>
<B> Previous:</B> <A NAME="tex2html210"
HREF="node4.html">3 Configuration</A>
<B> <A NAME="tex2html218"
HREF="node1.html">Contents</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A NAME="tex2html221"
HREF="node5.html#SECTION00051000000000000000">4.1 General module questions</A>
<UL>
<LI><A NAME="tex2html222"
HREF="node5.html#SECTION00051100000000000000">4.1.1 Why log to an SQL database?</A>
<LI><A NAME="tex2html223"
HREF="node5.html#SECTION00051200000000000000">4.1.2 Why use MySQL? Are there alternatives?</A>
<LI><A NAME="tex2html224"
HREF="node5.html#SECTION00051300000000000000">4.1.3 Is this code production-ready?</A>
<LI><A NAME="tex2html225"
HREF="node5.html#SECTION00051400000000000000">4.1.4 Who's using mod_log_sql?</A>
<LI><A NAME="tex2html226"
HREF="node5.html#SECTION00051500000000000000">4.1.5 Why doesn't the module also replace the Apache ErrorLog?</A>
<LI><A NAME="tex2html227"
HREF="node5.html#SECTION00051600000000000000">4.1.6 Does mod_log_sql work with Apache 2.x?</A>
<LI><A NAME="tex2html228"
HREF="node5.html#SECTION00051700000000000000">4.1.7 Does mod_log_sql connect to MySQL via TCP/IP or a socket?</A>
<LI><A NAME="tex2html229"
HREF="node5.html#SECTION00051800000000000000">4.1.8 I have discovered a bug. Who can I contact?</A>
</UL>
<BR>
<LI><A NAME="tex2html230"
HREF="node5.html#SECTION00052000000000000000">4.2 Problems</A>
<UL>
<LI><A NAME="tex2html231"
HREF="node5.html#SECTION00052100000000000000">4.2.1 Apache segfaults when using PHP and mod_log_sql</A>
<LI><A NAME="tex2html232"
HREF="node5.html#SECTION00052200000000000000">4.2.2 Apache appears to start up fine, but nothing
is getting logged in the database</A>
<LI><A NAME="tex2html233"
HREF="node5.html#SECTION00052300000000000000">4.2.3 Why do I get the message ``insufficient configuration info to
establish database link'' in my Apache error log?</A>
<LI><A NAME="tex2html234"
HREF="node5.html#SECTION00052400000000000000">4.2.4 My database cannot handle all the open connections from mod_log_sql,
is there anything I can do?</A>
<LI><A NAME="tex2html235"
HREF="node5.html#SECTION00052500000000000000">4.2.5 Why do I occasionally see a ``lost connection to MySQL server''
message in my Apache error log?</A>
</UL>
<BR>
<LI><A NAME="tex2html236"
HREF="node5.html#SECTION00053000000000000000">4.3 Performance and Tuning</A>
<UL>
<LI><A NAME="tex2html237"
HREF="node5.html#SECTION00053100000000000000">4.3.1 How well does it perform?</A>
<LI><A NAME="tex2html238"
HREF="node5.html#SECTION00053200000000000000">4.3.2 Do I need to be worried about all the running MySQL children? Will
holding open <I>n</I> Apache-to-MySQL connections consume a lot of
memory? </A>
<LI><A NAME="tex2html239"
HREF="node5.html#SECTION00053300000000000000">4.3.3 My webserver cannot handle all the traffic that my site receives,
is there anything I can do?</A>
<LI><A NAME="tex2html240"
HREF="node5.html#SECTION00053400000000000000">4.3.4 What is the issue with activating delayed
inserts?</A>
</UL>
<BR>
<LI><A NAME="tex2html241"
HREF="node5.html#SECTION00054000000000000000">4.4 ``How do I...?'' - accomplishing certain tasks</A>
<UL>
<LI><A NAME="tex2html242"
HREF="node5.html#SECTION00054100000000000000">4.4.1 I am using LogSQLMassVirtualHosting, and sometimes a single VirtualHost
gets logged to two different tables. How do I prevent that?</A>
<LI><A NAME="tex2html243"
HREF="node5.html#SECTION00054200000000000000">4.4.2 How do I extract the data in a format that my analysis tool can understand?</A>
<LI><A NAME="tex2html244"
HREF="node5.html#SECTION00054300000000000000">4.4.3 How can I log mod_usertrack cookies?</A>
<LI><A NAME="tex2html245"
HREF="node5.html#SECTION00054400000000000000">4.4.4 What if I want to log more than one cookie? What is the difference
between LogSQLWhichCookie and LogSQLWhichCookies?</A>
<LI><A NAME="tex2html246"
HREF="node5.html#SECTION00054500000000000000">4.4.5 What are the SSL logging features, and how do I activate them?</A>
</UL></UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION00050000000000000000">
4 FAQ</A>
</H1>
<P>
<H2><A NAME="SECTION00051000000000000000">
4.1 General module questions</A>
</H2>
<P>
<H3><A NAME="SECTION00051100000000000000"></A><A NAME="sub:why"></A>
<BR>
4.1.1 Why log to an SQL database?
</H3>
<P>
To begin with, let's get it out of the way: logging to a database
is not a panacea. But while there are complexities with this solution,
the benefit can be substantial for certain classes of administrator
or people with advanced requirements:
<P>
<UL>
<LI>Chores like log rotation go away, as you can DELETE records from the
SQL database once they are no longer useful. For example, the excellent
and popular log-analysis tool Webalizer (http://www.webalizer.com)
does not need historic logs after it has processed them, enabling
you to delete older logs.
</LI>
<LI>People with clusters of web servers (for high availability) will benefit
the most - all their webservers can log to a single SQL database.
This obviates the need to collate/interleave the many separate logfiles,
which can be / highly/ problematic.
</LI>
<LI>People acquainted with the power of SQL SELECT statements will know
the flexibility of the extraction possibilities at their fingertips.
</LI>
</UL>
For example, do you want to see all your 404's? Do this:
<P>
<DL COMPACT>
<DT>
<DD>select remote_host,status,request_uri,bytes_sent,from_unixtime(time_stamp)
<P>
from acc_log_tbl where status=404 order by time_stamp;
<P>
</DD>
</DL>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1">
<TR><TD ALIGN="LEFT">remote_host</TD>
<TD ALIGN="LEFT">status</TD>
<TD ALIGN="LEFT">request_uri</TD>
<TD ALIGN="LEFT">bytes_sent</TD>
<TD ALIGN="LEFT">from_unixtime(time_stamp)</TD>
</TR>
<TR><TD ALIGN="LEFT">marge.mmm.co.uk</TD>
<TD ALIGN="LEFT">404</TD>
<TD ALIGN="LEFT">/favicon.ico</TD>
<TD ALIGN="LEFT">321</TD>
<TD ALIGN="LEFT">2001-11-20 02:30:56</TD>
</TR>
<TR><TD ALIGN="LEFT">62.180.239.251</TD>
<TD ALIGN="LEFT">404</TD>
<TD ALIGN="LEFT">/favicon.ico</TD>
<TD ALIGN="LEFT">333</TD>
<TD ALIGN="LEFT">2001-11-20 02:45:25</TD>
</TR>
<TR><TD ALIGN="LEFT">212.234.12.66</TD>
<TD ALIGN="LEFT">404</TD>
<TD ALIGN="LEFT">/favicon.ico</TD>
<TD ALIGN="LEFT">321</TD>
<TD ALIGN="LEFT">2001-11-20 03:01:00</TD>
</TR>
<TR><TD ALIGN="LEFT">212.210.78.254</TD>
<TD ALIGN="LEFT">404</TD>
<TD ALIGN="LEFT">/favicon.ico</TD>
<TD ALIGN="LEFT">333</TD>
<TD ALIGN="LEFT">2001-11-20 03:26:05</TD>
</TR>
</TABLE>
</DIV>
<P>
<DL COMPACT>
<DT>
<DD><P>
</DD>
</DL>Or do you want to see how many bytes you've sent within a certain
directory or site? Do this:
<P>
<DL COMPACT>
<DT>
<DD>select request_uri,sum(bytes_sent) as bytes,count(request_uri) as howmany from
<P>
acc_log_tbl where request_uri like '%mod_log_sql%' group by request_uri order
<P>
by howmany desc;
<P>
</DD>
</DL>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1">
<TR><TD ALIGN="LEFT">request_uri</TD>
<TD ALIGN="LEFT">bytes</TD>
<TD ALIGN="LEFT">howmany</TD>
</TR>
<TR><TD ALIGN="LEFT">/mod_log_sql/style_1.css</TD>
<TD ALIGN="LEFT">157396</TD>
<TD ALIGN="LEFT">1288</TD>
</TR>
<TR><TD ALIGN="LEFT">/mod_log_sql/</TD>
<TD ALIGN="LEFT">2514337</TD>
<TD ALIGN="LEFT">801</TD>
</TR>
<TR><TD ALIGN="LEFT">/mod_log_sql/mod_log_sql.tar.gz</TD>
<TD ALIGN="LEFT">9769312</TD>
<TD ALIGN="LEFT">456</TD>
</TR>
<TR><TD ALIGN="LEFT">/mod_log_sql/faq.html</TD>
<TD ALIGN="LEFT">5038728</TD>
<TD ALIGN="LEFT">436</TD>
</TR>
</TABLE>
</DIV>
<P>
<DL COMPACT>
<DT>
<DD><P>
</DD>
</DL>Or maybe you want to see who's linking to you? Do this:
<P>
<DL COMPACT>
<DT>
<DD>select count(referer) as num,referer from acc_log_tbl where
<P>
request_uri='/mod_log_sql/' group by referer order by num desc;
<P>
</DD>
</DL>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1">
<TR><TD ALIGN="LEFT">num</TD>
<TD ALIGN="LEFT">referer</TD>
</TR>
<TR><TD ALIGN="LEFT">271</TD>
<TD ALIGN="LEFT">http://freshmeat.net/projects/mod_log_sql/</TD>
</TR>
<TR><TD ALIGN="LEFT">96</TD>
<TD ALIGN="LEFT">http://modules.apache.org/search?id=339</TD>
</TR>
<TR><TD ALIGN="LEFT">48</TD>
<TD ALIGN="LEFT">http://freshmeat.net/</TD>
</TR>
<TR><TD ALIGN="LEFT">8</TD>
<TD ALIGN="LEFT">http://freshmeat.net</TD>
</TR>
</TABLE>
</DIV>
<P>
<DL COMPACT>
<DT>
<DD><P>
</DD>
</DL>As you can see, there are myriad possibilities that can be constructed
with the wonderful SQL SELECT statement. Logging to an SQL database
can be really quite useful!
<P>
<H3><A NAME="SECTION00051200000000000000">
4.1.2 Why use MySQL? Are there alternatives?</A>
</H3>
<P>
MySQL is a robust, free, and very powerful production-quality database
engine. It is well supported and comes with detailed documentation.
Many 3rd-party software pacakges (e.g. Slashcode, the engine that
powers Slashdot) run exclusively with MySQL. In other words, you will
belong to a very robust and well-supported community by choosing MySQL.
<P>
That being said, there are alternatives. PostgreSQL is probably MySQL's
leading "competitor" in the free database world.
There is also an excellent module available for Apache to permit logging
to a PostgreSQL database, called pgLOGd (http://www.digitalstratum.com/pglogd/).
<P>
<H3><A NAME="SECTION00051300000000000000">
4.1.3 Is this code production-ready?</A>
</H3>
<P>
By all accounts it is. It is known to work without a problem on many-thousands-of-hits-per-day
webservers. Does that mean it is 100% bug free? Well, no software
is. But it is well-tested and believed to be fully compatible with
production environments. (The usual disclaimers apply. This software
is provided without warranty of any kind.)
<P>
<H3><A NAME="SECTION00051400000000000000">
4.1.4 Who's using mod_log_sql?</A>
</H3>
<P>
Good question! It would be great to find out! If you are a production-level
mod_log_sql user, please contact the maintainer, Chris Powell (chris@grubbybaby.com)
so that you can be mentioned here.
<P>
<H3><A NAME="SECTION00051500000000000000">
4.1.5 Why doesn't the module also replace the Apache ErrorLog?</A>
</H3>
<P>
There are circumstances when that would be quite unwise - for example,
if Apache could not reach the MySQL server for some reason and needed
to log that fact. Without a text-based error log you'd never know
anything was wrong, because Apache would be trying to log a database
connection error to the database... you get the point.
<P>
Error logs are usually not very high-traffic and are really best left
as text files on a web server machine.
<P>
<H3><A NAME="SECTION00051600000000000000">
4.1.6 Does mod_log_sql work with Apache 2.x?</A>
</H3>
<P>
As of this writing, no. The Apache Group significantly altered the
module API with the release of Apache 2.0. All modules written for
1.3, including mod_log_sql, will not work with 2.0.
<P>
mod_log_sql will eventually be ported to Apache 2.x, but not immediately.
It is going to take some time, and there are other features that have
higher priority. Please sign up for the announcements list (on the
main website) or monitor the website for updates to learn when the
port (and other releases) are available.
<P>
<OPINION>If you're a *NIX user, stick with Apache 1.3.x for now.
Major modules like mod_ssl and PHP are not even ready for 2.0 yet,
and the main benefits in 2.0 are for Win32 users anyway. Apache 1.3.x
is rock-stable and performs equally well on *NIX as 2.0.</OPINION>
<P>
<H3><A NAME="SECTION00051700000000000000">
4.1.7 Does mod_log_sql connect to MySQL via TCP/IP or a socket?</A>
</H3>
<P>
It depends! This is not determined by mod_log_sql. mod_log_sql
relies on a connection command that is supplied in the MySQL API,
and that command is somewhat intelligent. How it works:
<P>
<UL>
<LI>if the specified MySQL database is on the same machine, the connection
command uses a socket to communicate with MySQL
</LI>
<LI>if the specified MySQL database is on a different machine, mod_log_sql
connects using TCP/IP.
</LI>
</UL>
You don't have any control of which methodology is used. You can fine-tune
some of the configuration, however. The L<SMALL>OG</SMALL>SQLS<SMALL>OCKET</SMALL>F<SMALL>ILE</SMALL>
runtime configuration directive overrides the default of ``/var/lib/mysql/mysql.sock''
for socket-based connections, whereas the L<SMALL>OG</SMALL>SQLTCPP<SMALL>ORT</SMALL> command
allows to you override the default TCP port of 3306 for TCP/IP connections.
<P>
<H3><A NAME="SECTION00051800000000000000">
4.1.8 I have discovered a bug. Who can I contact?</A>
</H3>
<P>
Please contact the maintainer (chris@grubbybaby.com)! Your
comments, suggestions, bugfixes, bug catches, and usage testimonials
are always welcome. As free software, mod_log_sql is intended to
be a community effort - any code contributions or other ideas will
be fully and openly credited, of course.
<P>
<H2><A NAME="SECTION00052000000000000000">
4.2 Problems</A>
</H2>
<P>
<H3><A NAME="SECTION00052100000000000000">
4.2.1 Apache segfaults when using PHP and mod_log_sql</A>
</H3>
<P>
This occurs if you compiled PHP with MySQL database support. PHP utilizes
its internal, bundled MySQL libraries by default. These conflict with
the ``real'' MySQL libraries linked by mod_log_sql, causing
the segmentation fault.
<P>
The solution is to configure PHP to link against the real MySQL libraries
and recompile mod_php. Apache will run properly once the modules
are all using the same version of the MySQL libraries.
<P>
<H3><A NAME="SECTION00052200000000000000"></A><A NAME="faq:NothingLogged"></A>
<BR>
4.2.2 Apache appears to start up fine, but nothing
is getting logged in the database
</H3>
<P>
If you do not see any entries in the access_log, then something is
preventing the inserts from happening. This could be caused by several
things:
<P>
<UL>
<LI>Improper privileges set up in the MySQL database
</LI>
<LI>You aren't hitting a VirtualHost that has a LogSQLTransferLogTable
entry
</LI>
<LI>You didn't specify the right database host or login information
</LI>
<LI>Another factor is preventing a connection to the database
</LI>
</UL>
Important: it is improper to ask for help before you have followed
these steps.
<P>
First examine the MySQL log that you established in step <A HREF="node4.html#step:EnaLog">6</A>
of section <A HREF="node4.html#sub:PrepDb">3.1</A>. Ensure that the INSERT statements are
not being rejected because of a malformed table name or other typographical
error. By enabling that log, you instructed MySQL to log every connection
and command it receives - if you see no INSERT attempts in the log,
the module isn't successfully connecting to the database. If you see
nothing at all in the log - not even a record of your administrative
connection attempts, then you did not enable the log correctly. If
you do see INSERT attempts but they are failing, the log should tell
you why.
<P>
Second, confirm that your L<SMALL>OG</SMALL>SQL* directives are all correct.
<P>
Third, examine the Apache error logs for messages from mod_log_sql;
the module will offer hints as to why it cannot connect, etc.
<P>
The next thing to do is recompile the module with debugging output
activated. change the "#undef DEBUG" on line 8
of mod_log_sql.c to "#define DEBUG" and recompile/reinstall.
The module will now output copious notes about what it is doing, and
this will help you (and the maintainer) solve the problem. In order
to see the debugging messages, ensure that you make them visible using
the L<SMALL>OG</SMALL>L<SMALL>EVEL</SMALL> directive <B>in the main server config
as well as in each</B> <B>V<SMALL>IRTUAL</SMALL>H<SMALL>OST</SMALL></B> <B>config:</B>
<P>
<DL COMPACT>
<DT>
<DD>LogLevel debug
<P>
ErrorLog /var/log/httpd/server-messages
</DD>
</DL>
<P>
<H3><A NAME="SECTION00052300000000000000">
4.2.3 Why do I get the message ``insufficient configuration info to
establish database link'' in my Apache error log?</A>
</H3>
<P>
At a minimum, L<SMALL>OG</SMALL>SQLD<SMALL>ATABASE</SMALL> and L<SMALL>OG</SMALL>SQLL<SMALL>OGIN</SMALL>I<SMALL>NFO</SMALL>
must be defined in order for the module to be able to establish a
database link. If these are not defined or are incomplete you will
receive this error message.
<P>
<H3><A NAME="SECTION00052400000000000000">
4.2.4 My database cannot handle all the open connections from mod_log_sql,
is there anything I can do?</A>
</H3>
<P>
The rule of thumb: if you have <I>n</I> webservers each configured
to support <I>y</I> M<SMALL>AX</SMALL>C<SMALL>LIENTS</SMALL>, then your database must be
able to handle <IMG
WIDTH="41" HEIGHT="29" ALIGN="MIDDLE" BORDER="0"
SRC="img3.png"
ALT="$n\times y$"> simultenous connections <I>in the worst
case.</I> Certainly you must use common sense, consider reasonable traffic
expectations and structure things accordingly.
<P>
Tweaking my.cnf to scale to high connection loads is imperative. But
if hardware limitations prevent your MySQL server from gracefully
handling the number of incoming connections, it would be beneficial
to upgrade the memory or CPU on that server in order to handle the
load.
<P>
Jeremy Zawodny, a highly respected MySQL user and contributor to Linux
Magazine, has this very helpful and highly appropriate article on
tuning MySQL: http://jeremy.zawodny.com/blog/archives/000173.html
<P>
Please remember that mod_log_sql's overriding principle is <B>performance</B>
- that is what the target audience demands and expects. Other database
logging solutions do not open and maintain many database connections,
but their performance suffers drastically. For example, pgLOGd funnels
all log connections through a separate daemon that connects to the
database, but that bottlenecks the entire process. mod_log_sql achieves
performance numbers an order of magnitude greater than the alternatives
because it dispenses with the overhead associated with rapid connection
cycling, and it doesn't attempt to shoehorn all the database traffic
through a single extra daemon or proxy process.
<P>
<H3><A NAME="SECTION00052500000000000000">
4.2.5 Why do I occasionally see a ``lost connection to MySQL server''
message in my Apache error log?</A>
</H3>
<P>
This message may appear every now and then in your Apache error log,
especially on very lightly loaded servers. This doesn't mean that
anything is necessarily wrong. Within each httpd child process, mod_log_sql
will open (and keep open) a connection to the MySQL server. MySQL,
however, will close connections that haven't been used in a while;
the default timeout is 8 hours. When this occurs, mod_log_sql will
notice and re-open the connection. That event is what is being logged,
and looks like this:
<P>
<DL COMPACT>
<DT>
<DD>[Tue Nov 12 19:04:10 2002] [error] mod_log_sql: first attempt failed,
<P>
API said: error 2013, Lost connection to MySQL server during query
<P>
[Tue Nov 12 19:04:10 2002] [error] mod_log_sql: reconnect successful
<P>
[Tue Nov 12 19:04:10 2002] [error] mod_log_sql: second attempt successful
</DD>
</DL>Reference: MySQL documentation (http://www.mysql.com/documentation/mysql/bychapter/manual_Problems.html#Gone_away)
<P>
<H2><A NAME="SECTION00053000000000000000">
4.3 Performance and Tuning</A>
</H2>
<P>
<H3><A NAME="SECTION00053100000000000000">
4.3.1 How well does it perform?</A>
</H3>
<P>
mod_log_sql scales to very high loads. Apache 1.3.22 + mod_log_sql
was benchmarked using the "ab" (Apache Bench) program
that comes with the Apache distribution; here are the results.
<P>
Overall configuration:
<P>
<UL>
<LI>Machine A: Apache webserver
</LI>
<LI>Machine B: MySQL server
</LI>
<LI>Machines A and B connected with 100Mbps Ethernet
</LI>
<LI>Webserver: Celeron 400, 128 MB RAM, IDE storage
</LI>
</UL>
Apache configuration:
<P>
<DL COMPACT>
<DT>
<DD>Timeout 300
<P>
KeepAlive On
<P>
MaxKeepAliveRequests 100
<P>
KeepAliveTimeout 15
<P>
MinSpareServers 5
<P>
StartServers 10
<P>
MaxSpareServers 15
<P>
MaxClients 256
<P>
MaxRequestsPerChild 5000
<P>
LogSQLTransferLogFormat AbHhmRSsTUuvc
<P>
LogSQLWhichCookie Clicks
<P>
CookieTracking on
<P>
CookieName Clicks
</DD>
</DL>"ab" commandline:
<P>
<DL COMPACT>
<DT>
<DD>./ab -c 10 -t 20 -v 2 -C Clicks=ab_run http://www.hostname.com/target
</DD>
</DL>( 10 concurrent requests; 20 second test; setting a cookie "Clicks=ab_run";
target = the mod_log_sql homepage. )
<P>
Ten total ab runs were conducted: five with MySQL logging enabled,
and five with all MySQL directives commented out of httpd.conf. Then
each five were averaged. The results:
<P>
<UL>
<LI>Average of five runs employing MySQL <I>and</I> standard text logging:
<B>139.01 requests per second, zero errors</B>.
</LI>
<LI>Average of five runs employing <I>only</I> standard text logging:
<B>139.96 requests per second, zero errors</B>.
</LI>
</UL>
In other words, any rate-limiting effects on this particular hardware
setup are not caused by MySQL. Note that although this very simple
webserver setup is hardly cutting-edge - it is, after all, a fairly
small machine - 139 requests per second equal over <I>twelve million
hits per day.</I>
<P>
If you run this benchmark yourself, take note of three things:
<P>
<OL>
<LI>Use a target URL that is on your own webserver :-).
</LI>
<LI>Wait until all your connections are closed out between runs; after
several thousand requests your TCP/IP stack will be filled with hundreds
of connections in TIME_WAIT that need to close. Do a "netstat
-t|wc -l" on the webserver to see. If you don't wait, you
can expect to see a lot of messages like "ip_conntrack:
table full, dropping packet" in your logs. (This has nothing
to do with mod_log_sql, this is simply the nature of the TCP/IP
stack in the Linux kernel.)
</LI>
<LI>When done with your runs, clean these many thousands of requests out
of your database:
</LI>
</OL>
<DL COMPACT>
<DT>
<DD>mysql> delete from access_log where agent like 'ApacheBench%';
<P>
mysql> optimize table access_log;
</DD>
</DL>
<P>
<H3><A NAME="SECTION00053200000000000000">
4.3.2 Do I need to be worried about all the running MySQL children? Will
holding open <I>n</I> Apache-to-MySQL connections consume a lot of
memory? </A>
</H3>
<P>
Short answer: you shouldn't be worried.
<P>
Long answer: you might be evaluating at the output of ``ps -aufxw''
and becoming alarmed at all the 7MB httpd processes or 22MB mysqld
children that you see. Don't be alarmed<I>.</I> It's true that mod_log_sql
opens and holds open many MySQL connections: each httpd child maintains
one open database connection (and holds it open for performance reasons).
Four webservers, each running 20 Apache children, will hold open 80
MySQL connections, which means that your MySQL server needs to handle
80 simultaneous connections. In truth, your MySQL server needs to
handle far more than that if traffic to your website spikes and the
Apache webservers spawn off an additional 30 children each...
<P>
Fortunately the cost reported by 'ps -aufxw' is deceptive. This is
due to an OS memory-management feature called ``copy-on-write.''
When you have a number of identical child processes (e.g. Apache,
MySQL), it would appear in ``ps'' as though each one occupies
a great deal of RAM - as much as 7MB per httpd child! In actuality
each additional child only occupies a small bit of extra memory -
most of the memory pages are common to each child and therefore shared
in a ``read-only'' fashion. The OS can get away with this because
the majority of memory pages for one child are identical across all
children. Instead of thinking of each child as a rubber stamp of the
others, think of each child as a basket of links to a common memory
area.
<P>
A memory page is only duplicated when it needs to be written to, hence
``copy-on-write.'' The result is efficiency and decreased memory
consumption. ``ps'' may report 7MB per child, but it might really
only ``cost'' 900K of extra memory to add one more child. It is
<B>not</B> <B>correct</B> to assume that 20 Apache
children with a VSZ of 7MB each equals <!-- MATH
$(20\times 7MB)$
-->
<IMG
WIDTH="90" HEIGHT="32" ALIGN="MIDDLE" BORDER="0"
SRC="img4.png"
ALT="$(20\times 7MB)$"> of memory
consumption - the real answer is much, much lower. The same ``copy-on-write''
rules apply to all your MySQL children: 40 mysqld children @ 22MB
each <B>do not</B> occupy 880MB of RAM.
<P>
The bottom line: although there is a cost to spawn extra httpd or
mysqld children, that cost is not as great as ``ps'' would lead
you to believe.
<P>
<H3><A NAME="SECTION00053300000000000000">
4.3.3 My webserver cannot handle all the traffic that my site receives,
is there anything I can do?</A>
</H3>
<P>
If you have exhausted all the tuning possibilities on your existing
server, it is probably time you evaluated the benefits of clustering
two or more webservers together in a load-balanced fashion. In fact,
users of such a setup are mod_log_sql's target audience!
<P>
<H3><A NAME="SECTION00053400000000000000"></A><A NAME="sub:DelayedInsFAQ"></A>
<BR>
4.3.4 What is the issue with activating delayed
inserts?
</H3>
<P>
There are several.
<P>
<OL>
<LI>INSERT DELAYED is a specific syntax to MySQL and is not supported
by any other database. Ergo, why is it needed, and what MySQL deficiency
is it working around? INSERT DELAYED is a kluge.
</LI>
<LI>The MySQL documentation is unclear whether INSERT DELAYED is even
necessary for an optimized database. It says, ``The DELAYED option
for the INSERT statement is a MySQL-specific option that is very useful
if you have clients that can't wait for the INSERT to complete.''
But then it goes on to say, ``Note that as MyISAM tables supports
concurrent SELECT and INSERT, if there is no free blocks in the middle
of the data file, you very seldom need to use INSERT DELAYED with
MyISAM.''
</LI>
<LI>Because INSERT DELAYED returns without waiting for the data to be
written, a hard kill of your MySQL database at the right (wrong?)
moment could lose those logfile entries.
</LI>
<LI>As of MySQL version 3.23.52, the error return functions disagree after
a failed INSERT DELAYED: mysql_errno() always returns 0, even if
mysql_error() returns a textual error. I have reported this bug to
the MySQL folks. However, we have no way of knowing what solution
they will adopt to fix this, and with the worst case solution mod_log_sql
would not be able to tell if anything went wrong with a delayed insert.
</LI>
</OL>
Instead of delayed inserts, you may wish to utilize InnoDB tables
(instead of the standard MyISAM tables). InnoDB tables suppot row-level
locking and are recommended for high-volume databases.
<P>
If after understanding these problems you still wish to enable delayed
inserts, section <A HREF="node4.html#sub:DelayedIns">3.5.4</A> discusses how.
<P>
<H2><A NAME="SECTION00054000000000000000">
4.4 ``How do I...?'' - accomplishing certain tasks</A>
</H2>
<P>
<H3><A NAME="SECTION00054100000000000000">
4.4.1 I am using LogSQLMassVirtualHosting, and sometimes a single VirtualHost
gets logged to two different tables. How do I prevent that?</A>
</H3>
<P>
Proper usage of the Apache runtime S<SMALL>ERVER</SMALL>N<SMALL>AME</SMALL> directive and
the directive U<SMALL>SE</SMALL>C<SMALL>ANONICAL</SMALL>N<SMALL>AME </SMALL>O<SMALL>N</SMALL> (or DNS) are necessary
to prevent this problem. ``On'' is the default for U<SMALL>SE</SMALL>C<SMALL>ANONICAL</SMALL>N<SMALL>AME</SMALL>,
and specifies that self-referential URLs are generated from the S<SMALL>ERVER</SMALL>N<SMALL>AME</SMALL>
part of your VirtualHost:
<P>
<BLOCKQUOTE>
With UseCanonicalName on (and in all versions prior to 1.3) Apache
will use the ServerName and Port directives to construct the canonical
name for the server. With UseCanonicalName off Apache will form self-referential
URLs using the hostname and port supplied by the client if any are
supplied (otherwise it will use the canonical name, as defined above).
[From the Apache documentation http://httpd.apache.org/docs/mod/core.html#usecanonicalname]
</BLOCKQUOTE>
The module inherits Apache's ``knowledge'' about the server name
being accessed. As long as those two directives are properly configured,
mod_log_sql will log to only one table per virtual host while using
L<SMALL>OG</SMALL>SQLM<SMALL>ASS</SMALL>V<SMALL>IRTUAL</SMALL>H<SMALL>OSTING</SMALL>.
<P>
<H3><A NAME="SECTION00054200000000000000">
4.4.2 How do I extract the data in a format that my analysis tool can understand?</A>
</H3>
<P>
mod_log_sql would be virtually useless if there weren't a way for
you to extract the data from your database in a somewhat meaningful
fashion. To that end there's a Perl script enclosed with the distribution.
That script (make_combined_log.pl) is designed to extract N-many
days worth of access logs and provide them in a Combined Log Format
output. You can use this very tool right in /etc/crontab to extract
logs on a regular basis so that your favorite web analysis tool can
read them. Or you can examine the Perl code to construct your own
custom tool.
<P>
For example, let's say that you want your web statistics updated once
per day in the wee hours of the morning. A good way to accomplish
that could be the following entries in /etc/crontab:
<P>
<DL COMPACT>
<DT>
<DD># Generate the temporary apache logs from the MySQL database (for webalizer)
<P>
05 04 * * * root make_combined_log.pl 1 www.grubbybaby.com > /var/log/temp01
<P>
# Run webalizer on httpd log
<P>
30 04 * * * root webalizer -c /etc/webalizer.conf; rm -f /var/log/temp01
</DD>
</DL>Or if you have a newer system that puts files in /etc/cron.daily etc.,
create a file called ``webalizer'' in the cron.daily subdirectory.
Use the following as the contents of your file, and make sure to chmod
755 it when done.
<P>
<DL COMPACT>
<DT>
<DD>#!/bin/sh
<P>
/usr/local/sbin/make_combined_log.pl 1 www.yourdomain.com > /var/log/httpd/templog
<P>
/usr/local/bin/webalizer -q -c /etc/webalizer.conf
<P>
rm -f /var/log/httpd/templog
</DD>
</DL>See? Easy.
<P>
<H3><A NAME="SECTION00054300000000000000"></A><A NAME="sec:cookie"></A>
<BR>
4.4.3 How can I log mod_usertrack cookies?
</H3>
<P>
A number of people like to log mod_usertrack cookies in their Apache
TransferLog to aid in understanding their visitors' clickstreams.
This is accomplished, for example, with a statement as follows:
<P>
<DL COMPACT>
<DT>
<DD>LogFormat "%h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" \"%{cookie}n\""
</DD>
</DL>Naturally it would be nice for mod_log_sql to permit the admin to
log the cookie data as well, so as of version 1.10 you can do this.
You need to have already compiled mod_usertrack into httpd - it's
one of the standard Apache modules.
<P>
First make sure you have a column called "cookie"
in the MySQL database to hold the cookies, which can be done as follows
if you already have a working database:
<P>
<DL COMPACT>
<DT>
<DD>alter table acc_log_tbl add column cookie varchar(255);
</DD>
</DL>Next configure your server to set usertracking cookies as follows,
and make sure you include the new 'c' directive in your L<SMALL>OG</SMALL>SQLT<SMALL>RANSFER</SMALL>L<SMALL>OG</SMALL>F<SMALL>ORMAT</SMALL>,
which activates cookie logging. Here's an example:
<P>
<DL COMPACT>
<DT>
<DD><VirtualHost 1.2.3.4>
<P>
CookieTracking on
<P>
CookieStyle Cookie
<P>
CookieName Foobar
<P>
LogSQLTransferLogFormat huSUsbTvRAc
<P>
LogSQLWhichCookie Foobar
<P>
</VirtualHost>
</DD>
</DL>The first three lines configure mod_usertrack to create a COOKIE
(RFC 2109) format cookie called Foobar. The last two lines tell mod_log_sql
to log cookies named Foobar. You have to choose which cookie to log
because more than one cookie can/will be sent to the server by the
client.
<P>
Recap: the 'c' character <I>activates</I> cookie logging, and the
L<SMALL>OG</SMALL>SQLW<SMALL>HICH</SMALL>C<SMALL>OOKIE</SMALL> directive <I>chooses</I> which cookie to
log.
<P>
FYI, you are advised NOT to use C<SMALL>OOKIE</SMALL>S<SMALL>TYLE </SMALL>C<SMALL>OOKIE2</SMALL> - it
seems that even newer browsers (IE 5.5, etc.) have trouble with the
new COOKIE2 (RFC 2965) format. Just stick with the standard COOKIE
format and you'll be fine.
<P>
Perform some hits on your server and run a select:
<P>
<DL COMPACT>
<DT>
<DD>mysql> select request_uri,cookie from access_log where cookie is not null;
<P>
</DD>
</DL>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1">
<TR><TD ALIGN="LEFT">request_uri</TD>
<TD ALIGN="LEFT">cookie</TD>
</TR>
<TR><TD ALIGN="LEFT">/mod_log_sql/</TD>
<TD ALIGN="LEFT">ool-18e4.dyn.optonline.net.130051007102700823</TD>
</TR>
<TR><TD ALIGN="LEFT">/mod_log_sql/usa.gif</TD>
<TD ALIGN="LEFT">ool-18e4.dyn.optonline.net.130051007102700823</TD>
</TR>
<TR><TD ALIGN="LEFT">/mod_log_sql/style_1.css</TD>
<TD ALIGN="LEFT">ool-18e4.dyn.optonline.net.130051007102700823</TD>
</TR>
</TABLE>
</DIV>
<P>
<DL COMPACT>
<DT>
<DD><P>
</DD>
</DL>
<P>
<H3><A NAME="SECTION00054400000000000000">
4.4.4 What if I want to log more than one cookie? What is the difference
between LogSQLWhichCookie and LogSQLWhichCookies?</A>
</H3>
<P>
As of version 1.17, you have a choice in how you want cookie logging
handled.
<P>
If you are interested in logging only one cookie per request, follow
the instructions in section <A HREF="node5.html#sec:cookie">4.4.3</A> above. That cookie will
be logged to a column in the regular access_log table, and the actual
cookie you want to log is specified with L<SMALL>OG</SMALL>SQLW<SMALL>HICH</SMALL>C<SMALL>OOKIE</SMALL>.
Don't forget to specify the 'c' character in L<SMALL>OG</SMALL>SQLT<SMALL>RANSFER</SMALL>L<SMALL>OG</SMALL>F<SMALL>ORMAT</SMALL>.
<P>
If, however, you need to log multiple cookies per request, you must
employ the L<SMALL>OG</SMALL>SQLW<SMALL>HICH</SMALL>C<SMALL>OOKIES</SMALL> (note the plural) directive.
The cookies you specify will be logged to a separate table (as discussed
in section <A HREF="node4.html#secMulTable">3.5.2</A>), and entries in that table will be
linked to the regular access_log entries via the unique ID that is
supplied by mod_unique_id. Without mod_unique_id the information
will still be logged but you will be unable to correlate which cookies
go with which access-requests. Furthermore, with L<SMALL>OG</SMALL>SQLW<SMALL>HICH</SMALL>C<SMALL>OOKIES</SMALL>,
you do <B>not</B> need to include the 'c' character in L<SMALL>OG</SMALL>SQLT<SMALL>RANSFER</SMALL>L<SMALL>OG</SMALL>F<SMALL>ORMAT</SMALL>.
<P>
L<SMALL>OG</SMALL>SQLW<SMALL>HICH</SMALL>C<SMALL>OOKIE</SMALL> and L<SMALL>OG</SMALL>SQLW<SMALL>HICH</SMALL>C<SMALL>OOKIES</SMALL> can coexist
without conflict because they operate on entireley different tables,
but you're better off choosing the one you need.
<P>
<H3><A NAME="SECTION00054500000000000000">
4.4.5 What are the SSL logging features, and how do I activate them?</A>
</H3>
<P>
Note: you do <B>not</B> need to compile SSL support into mod_log_sql
in order to simply use it with a secure site. You only need to compile
SSL support into mod_log_sql if you want to log SSL-specific data
such as the cipher type used, or the keysize that was negotiated.
If that information is unimportant to you, you can ignore this FAQ.
<P>
By adding certain characters to your L<SMALL>OG</SMALL>SQLT<SMALL>RANSFER</SMALL>L<SMALL>OG</SMALL>F<SMALL>ORMAT</SMALL>
string you can tell mod_log_sql to log the SSL cipher, the SSL keysize
of the connection, and the maximum keysize that was available. This
would let you tell, for example, which clients were using only export-grade
security to access your secure software area.
<P>
You can compile mod_log_sql with SSL logging support if you have
the right packages installed. If you already have an SSL-enabled Apache
then you by definition have the correct packages already installed:
OpenSSL and mod_ssl.
<P>
You need to ensure that your database is set up to log the SSL data.
Issue the following commands to MySQL if your access table does not
already have them:
<P>
<DL COMPACT>
<DT>
<DD>alter table access_log add column ssl_cipher varchar(25);
<P>
alter table access_log add column ssl_keysize smallint unsigned;
<P>
alter table access_log add column ssl_maxkeysize smallint unsigned;
</DD>
</DL>Finally configure httpd.conf to activate the SSL fields. Note that
this is only meaningful in a VirtualHost that is set up for SSL.
<P>
<DL COMPACT>
<DT>
<DD><VirtualHost 1.2.3.4:443>
<P>
LogSQLTransferLogFormat AbHhmRSsTUuvc<B>Qqz</B>
<P>
</VirtualHost>
</DD>
</DL>The last three characters (Qqz) in the directive are the SSL ones;
see section <A HREF="node4.html#sub:Frmat">3.6.17</A> in the directives documentation for details
of the L<SMALL>OG</SMALL>SQLT<SMALL>RANSFER</SMALL>L<SMALL>OG</SMALL>F<SMALL>ORMAT</SMALL> directive.
<P>
Restart Apache, then perform some hits on your server. Then run the
following select statement:
<P>
<DL COMPACT>
<DT>
<DD>mysql> select remote_host,request_uri,ssl_cipher,ssl_keysize,ssl_maxkeysize
<P>
from access_log where ssl_cipher is not null;
<P>
</DD>
</DL>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1">
<TR><TD ALIGN="LEFT">remote_host</TD>
<TD ALIGN="LEFT">request_uri</TD>
<TD ALIGN="LEFT">ssl_cipher</TD>
<TD ALIGN="LEFT">ssl_keysize</TD>
<TD ALIGN="LEFT">ssl_maxkeysize</TD>
</TR>
<TR><TD ALIGN="LEFT">216.190.52.4</TD>
<TD ALIGN="LEFT">/dir/somefile.html</TD>
<TD ALIGN="LEFT">RC4-MD5</TD>
<TD ALIGN="LEFT">128</TD>
<TD ALIGN="LEFT">128</TD>
</TR>
<TR><TD ALIGN="LEFT">216.190.52.4</TD>
<TD ALIGN="LEFT">/dir/somefile.gif</TD>
<TD ALIGN="LEFT">RC4-MD5</TD>
<TD ALIGN="LEFT">128</TD>
<TD ALIGN="LEFT">128</TD>
</TR>
<TR><TD ALIGN="LEFT">216.190.52.4</TD>
<TD ALIGN="LEFT">/dir/somefile.jpg</TD>
<TD ALIGN="LEFT">RC4-MD5</TD>
<TD ALIGN="LEFT">128</TD>
<TD ALIGN="LEFT">128</TD>
</TR>
</TABLE>
</DIV>
<P>
<DL COMPACT>
<DT>
<DD>
</DD>
</DL>
<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html219"
HREF="node6.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html215"
HREF="documentation.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html209"
HREF="node4.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html217"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html220"
HREF="node6.html">About this document ...</A>
<B> Up:</B> <A NAME="tex2html216"
HREF="documentation.html">Installing and Running mod_log_sql</A>
<B> Previous:</B> <A NAME="tex2html210"
HREF="node4.html">3 Configuration</A>
<B> <A NAME="tex2html218"
HREF="node1.html">Contents</A></B>
<!--End of Navigation Panel-->
<ADDRESS>
Chris Powell
2002-12-18
</ADDRESS>
</BODY>
</HTML>
|
