Hi.
>From time to time i see in the log the following:
[Sun Oct 14 00:42:05 2007] [notice] Apache/2.2.6 (Unix) PHP/5.2.4
mod_ssl/2.2.6 Path:\t\tmessage/news\t8bit\n0\tstring\t\tXref:\t\tmess
age/news\t8bit\n0\tstring\t\tFrom:\t\tmessage/rfc822\t7bit\n0\tstring\t\tArticle
\tmessage/news\t8bit\n#-------------------------------
-----------------------------------------------\n# msword: file(1) magic
for MS Word files\n#\n# Contributor claims:\n# Reversed-engine
ered MS Word magic
numbers\n#\n\n0\tstring\t\t\\376\\067\\0\\043\t\t\tapplication/msword\n0\tstring\t\t\\333\\245-\\0\\0\\0\t\t\tapplic
ation/msword\n\n# disable this one because it applies also to other\n#
Office/OLE documents for which msword is not correct. See PR#260
8.\n#0\tstring\t\t\\320\\317\\021\\340\\241\\261\tapplication/msword\n\n\n\n#---------------------------------------------------
+-------
--------------------\n# printer: file(1) magic for printer-formatted
files\n#\n\n# PostScript\n0\tstring\t\t%!\t\tapplication/postscri
pt\n0\tstring\t\t\\004%!\t\tapplication/postscript\n\n# Acrobat\n# (due
to clamen@xxxxxxxxxx)\n0\tstring\t\t%PDF-\t\tapplication/pdf\n\
n#------------------------------------------------------------------------------\n#
sc: file(1) magic for "sc" spreadsheet\n#\n38\tstr
ing\t\tSpreadsheet\tapplication/x-sc\n\n#------------------------------------------------------------------------------\n#
tex: file(1
) magic for TeX files\n#\n# XXX - needs byte-endian stuff (big-endian
and little-endian DVI?)\n#\n# From <conklin@xxxxxxxxxxxxxxxxxxxx>
\n\n# Although we may know the offset of certain text fields in TeX
DVI\n# and font files, we can't use them reliably because they are
not\n# zero terminated. [but we do anyway,
christos]\n0\tstring\t\t\\367\\002\tapplication/x-dvi\n#0\tstring\t\t\\367\\203\tTeX
generic
font data\n#0\tstring\t\t\\367\\131\tTeX packed font
data\n#0\tstring\t\t\\367\\312\tTeX virtual font
data\n#0\tstring\t\tThis\\ is\\
TeX,\tTeX transcript text\t\n#0\tstring\t\tThis\\ is\\
METAFONT,\tMETAFONT transcript text\n\n# There is no way to detect TeX
Font Metr
ic (*.tfm) files without\n# breaking them apart and reading the data.
The following patterns\n# match most *.tfm files generated by ME
TAFONT or afm2tfm.\n#2\tstring\t\t\\000\\021\tTeX font metric
data\n#2\tstring\t\t\\000\\022\tTeX font metric
data\n#>34\tstring\t\t>\\
0\t\t(%s)\n\n# Texinfo and GNU Info, from Daniel Quinlan
(quinlan@xxxxxxxxxxxxx)\n#0\tstring\t\t\\\\input\\ texinfo\tTexinfo
source tex
t\n#0\tstring\t\tThis\\ is\\ Info\\ file\tGNU Info text\n\n# correct TeX
magic for Linux (and maybe more)\n# from Peter Tobias (tobias@
server.et-inf.fho-emden.de)\n#\n0\tleshort\t\t0x02f7\t\tapplication/x-dvi\n\n#
RTF - Rich Text Format\n0\tstring\t\t{\\\\rtf\t\tapplica
tion/rtf\n\n#------------------------------------------------------------------------------\n#
animation: file(1) magic for animation/
movie formats\n#\n# animation formats, originally from
vax@xxxxxxxxxxxxxxxxxx (VaX#n8)\n#\t\t\t\t\t\tMPEG
file\n0\tstring\t\t\\000\\000
\\001\\263\tvideo/mpeg\n#\n#`KF\b\x16 configured -- resuming normal
operations
What can this mean?
And by the way, after working for a while Apache stops giving back
pictures, and there's nothing wrong in access log, for example:
85.141.82.175 - - [14/Oct/2007:16:11:32 +0400] "GET /img/ts.png
HTTP/1.1" 200 6330 "http://example.net/"; "Mozilla/4.0 (compatible; M
SIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)"
but in the browser picture is not displayed, as if the picture file was
broken.
In this case all I can do stop/start Apache.
Use Apache 2.2.6 (MPM Worker), FreeBSD 6.2.
--
BRGDS. Alesha.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|