<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<STYLE>BODY {
MARGIN: 0px
}
TABLE {
MARGIN: 0px
}
TR {
MARGIN: 0px
}
TD {
MARGIN: 0px
}
P {
MARGIN: 0px
}
.bgtabl {
BACKGROUND-REPEAT: no-repeat
}
</STYLE>
<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY bgProperties=fixed bgColor=#ffffff>
<DIV>Hi ...Younès & All</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Thanks for your quick reply.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Yes that can be done in this way, but I just wanted
to know that .... the internal support of <FONT
face="Times New Roman" size=3>access_log </FONT>log rotation in inets ... which
I don't no at the moment. If inets do not support that feature ... I might go
with your suggestion.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>But IF inets don't support that .... I think it's
better to show any error message .... rather than crashing after each
http request. (B'cos I have wasted some hours to find this ...
assumming as a problem in my code)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>So ... I will rais up my question again, Are there any way to automatically
rotate the inets access_log ? </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Sanjaya Vitharana</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=yerl@club-internet.fr
href="mailto:yerl@club-internet.fr">yerl@club-internet.fr</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=sanjaya@wavenet.lk
href="mailto:sanjaya@wavenet.lk">sanjaya@wavenet.lk</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=erlang-questions@erlang.org
href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, 18 September 2006 01:20
pm</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [erlang-questions] Fw: Fw:
inets - traverse exit from apply ?</DIV>
<DIV><BR></DIV>
<P>Hi Sanjaya!</P>
<P> </P>
<P>If you're using Unix or Unix like system, look to the logrotate in your
system.</P>
<P>A script you can use as a cron job to do the logs rotation
automagically.</P>
<P> </P>
<P>cheers</P>
<P>Younès</P>
<P><BR>----Message d'origine---- <BR>>De: "Sanjaya Vitharana"
<SANJAYA@WAVENET.LK><BR>>A: <ERLANG-QUESTIONS@ERLANG.ORG><BR>>Date: Mon,
18 Sep 2006 12:06:57 +0530 <BR>>Sujet: [erlang-questions] Fw: Fw: inets -
traverse exit from apply ? <BR>> <BR>>Hi All, <BR>> <BR>>Is this a
bug in Inets? <BR>> <BR>>OR <BR>> <BR>>Are there any way to
automatically rotate the access_log ? (or the only solution is manual
deletion/rename of the file) <BR>> <BR>>Regards, <BR>>
<BR>>Sanjaya Vitharana <BR>> <BR>> <BR>>----- Original Message
----- <BR>>From: Sanjaya Vitharana <BR>>To: erlang-questions@erlang.org
<BR>>Sent: Sunday, 17 September 2006 05:51 pm <BR>>Subject:
[erlang-questions] Fw: inets - traverse exit from apply ? <BR>> <BR>>
<BR>>Hi ... all, <BR>> <BR>>Problem was the file size of inets
<BR>>access_log 2,147,483,647 bytes (~2.00 GB) <BR>> <BR>>Are there
any way to rotate it ? <BR>> <BR>>Thanks in advance. <BR>>
<BR>>Sanjaya Vitharana <BR>> <BR>> <BR>>----- Original Message
----- <BR>>From: Sanjaya Vitharana <BR>>To: erlang-questions@erlang.org
<BR>>Sent: Sunday, 17 September 2006 03:15 pm <BR>>Subject:
[erlang-questions] inets - traverse exit from apply ? <BR>> <BR>>
<BR>>Hi ... all, <BR>> <BR>>After running the system for 6 months
time inets begin to crash, <BR>> <BR>>Try to replace the original
function with below 3 lines to make sure it is not other than the http call to
inets httpd. <BR>> <BR>>read_prof(SessionID,Env,Input)-> <BR>>
io:fwrite("***blocked for testing***~n"), <BR>> mod_esi:deliver(SessionID,
"{error,blocked}"). %%-- for testing <BR>> <BR>>same result, so my doubt
is the inet httpd. <BR>> <BR>>the error_log, error_disk_log.1 of inets
show the below errors ? what those means ? <BR>> <BR>>Need quick fix.
Anyone have experience with this error ? <BR>> <BR>>Please help.
<BR>> <BR>>Sanjaya Vitharana <BR>>
<BR>>------------------------------------------------------ <BR>>System
Info: <BR>> <BR>>[root@prof vm_profile]# erl -version <BR>>Erlang
(THREADS,HIPE) (BEAM) emulator version 5.4.10 <BR>> <BR>>[root@prof
vm_profile]# uname -a <BR>>Linux prof 2.4.21-27.ELsmp #1 SMP Wed Dec 1
21:59:02 EST 2004 i686 i686 i386 GNU/Linux <BR>> <BR>>[root@prof
vm_profile]# date <BR>>Sun Sep 17 14:49:32 IST 2006 <BR>>
<BR>>------------------------------------------------------ <BR>>
error_log -- inets <BR>> <BR>>[17/Sep/2006:09:20:23 +0530] reporting
error: traverse exit from apply: mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.221.0>,normal}
<BR>>[17/Sep/2006:09:20:25 +0530] reporting error: traverse exit from
apply: mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.225.0>,normal}
<BR>>[17/Sep/2006:10:05:56 +0530] server crash for 192.168.129.20, reason:
"Error reading request: No request received on keep-alive connectionbefore
server side timeout" <BR>>[17/Sep/2006:12:50:08 +0530] reporting error:
traverse exit from apply: mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.214.0>,normal}
<BR>>[17/Sep/2006:12:50:10 +0530] reporting error: traverse exit from
apply: mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.218.0>,normal} <BR>>
<BR>>------------------------------------------------------
<BR>>error_disk_log.1 -- inets <BR>>
<BR>>{mod_esi_linked_process_died,<0.305.0>,
normal}[17/Sep/2006:09:20:23 +0530] reporting error: traverse exit from apply:
mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.221.0>,normal}[17/Sep/2006:09:20:25
+0530] reporting error: traverse exit from apply: mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.225.0>,normal}[17/Sep/2006:10:05:56
+0530] server crash for 192.168.129.20, reason: "Error reading request: No
request received on keep-alive connectionbefore server side timeout"
<BR>>[17/Sep/2006:12:50:08 +0530] reporting error: traverse exit from
apply: mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.214.0>,normal}[17/Sep/2006:12:50:10
+0530] reporting error: traverse exit from apply: mod_esi:do =>
<BR>>{mod_esi_linked_process_died,<0.218.0>,normal} <BR>>
<BR>>------------------------------------------------------ <BR>>
<BR>>
<BR>>--------------------------------------------------------------------------------
<BR>> <BR>> <BR>> _______________________________________________
<BR>>erlang-questions mailing list <BR>>erlang-questions@erlang.org
<BR>>http://www.erlang.org/mailman/listinfo/erlang-questions <BR>>
<BR>> <BR>>
<BR>>--------------------------------------------------------------------------------
<BR>> <BR>> <BR>>_______________________________________________
<BR>>erlang-questions mailing list <BR>>erlang-questions@erlang.org
<BR>>http://www.erlang.org/mailman/listinfo/erlang- questions
<BR>>_______________________________________________
<BR>>erlang-questions mailing list <BR>>erlang-questions@erlang.org
<BR>>http://www.erlang.org/mailman/listinfo/erlang-questions <BR>>
<BR>> </P></BLOCKQUOTE></BODY></HTML>