[erlang-questions] Fw: Fw: inets - traverse exit from apply ?

Sanjaya Vitharana <>
Mon Sep 18 10:13:36 CEST 2006


Hi ...Younès & All

Thanks for your quick reply.

Yes that can be done in this way, but I just wanted to know that  .... the internal support of access_log 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.

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)

So ... I will rais up my question again, Are there any way to automatically rotate the inets access_log ? 

Regards,

Sanjaya Vitharana

  ----- Original Message ----- 
  From:  
  To:  
  Cc:  
  Sent: Monday, 18 September 2006 01:20 pm
  Subject: Re: [erlang-questions] Fw: Fw: inets - traverse exit from apply ?


  Hi Sanjaya!



  If you're using Unix or Unix like system, look to the logrotate in your system.

  A script you can use as a cron job to do the logs rotation automagically.



  cheers

  Younès


  ----Message d'origine---- 
  >De: "Sanjaya Vitharana" 
  >A: 
  >Date: Mon, 18 Sep 2006 12:06:57 +0530 
  >Sujet: [erlang-questions] Fw: Fw: inets - traverse exit from apply ? 
  > 
  >Hi All, 
  > 
  >Is this a bug in Inets? 
  > 
  >OR 
  > 
  >Are there any way to automatically rotate the access_log ? (or the only solution is manual deletion/rename of the file) 
  > 
  >Regards, 
  > 
  >Sanjaya Vitharana 
  > 
  > 
  >----- Original Message ----- 
  >From: Sanjaya Vitharana 
  >To:  
  >Sent: Sunday, 17 September 2006 05:51 pm 
  >Subject: [erlang-questions] Fw: inets - traverse exit from apply ? 
  > 
  > 
  >Hi ... all, 
  > 
  >Problem was the file size of inets 
  >access_log 2,147,483,647 bytes (~2.00 GB) 
  > 
  >Are there any way to rotate it ? 
  > 
  >Thanks in advance. 
  > 
  >Sanjaya Vitharana 
  > 
  > 
  >----- Original Message ----- 
  >From: Sanjaya Vitharana 
  >To:  
  >Sent: Sunday, 17 September 2006 03:15 pm 
  >Subject: [erlang-questions] inets - traverse exit from apply ? 
  > 
  > 
  >Hi ... all, 
  > 
  >After running the system for 6 months time inets begin to crash, 
  > 
  >Try to replace the original function with below 3 lines to make sure it is not other than the http call to inets httpd. 
  > 
  >read_prof(SessionID,Env,Input)-> 
  > io:fwrite("***blocked for testing***~n"), 
  > mod_esi:deliver(SessionID, "{error,blocked}"). %%-- for testing 
  > 
  >same result, so my doubt is the inet httpd. 
  > 
  >the error_log, error_disk_log.1 of inets show the below errors ? what those means ? 
  > 
  >Need quick fix. Anyone have experience with this error ? 
  > 
  >Please help. 
  > 
  >Sanjaya Vitharana 
  > 
  >------------------------------------------------------ 
  >System Info: 
  > 
  >[ vm_profile]# erl -version 
  >Erlang (THREADS,HIPE) (BEAM) emulator version 5.4.10 
  > 
  >[ vm_profile]# uname -a 
  >Linux prof 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02 EST 2004 i686 i686 i386 GNU/Linux 
  > 
  >[ vm_profile]# date 
  >Sun Sep 17 14:49:32 IST 2006 
  > 
  >------------------------------------------------------ 
  > error_log -- inets 
  > 
  >[17/Sep/2006:09:20:23 +0530] reporting error: traverse exit from apply: mod_esi:do => 
  >{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 => 
  >{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" 
  >[17/Sep/2006:12:50:08 +0530] reporting error: traverse exit from apply: mod_esi:do => 
  >{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 => 
  >{mod_esi_linked_process_died,<0.218.0>,normal} 
  > 
  >------------------------------------------------------ 
  >error_disk_log.1 -- inets 
  > 
  >{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 => 
  >{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 => 
  >{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" 
  >[17/Sep/2006:12:50:08 +0530] reporting error: traverse exit from apply: mod_esi:do => 
  >{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 => 
  >{mod_esi_linked_process_died,<0.218.0>,normal} 
  > 
  >------------------------------------------------------ 
  > 
  > 
  >-------------------------------------------------------------------------------- 
  > 
  > 
  > _______________________________________________ 
  >erlang-questions mailing list 
  > 
  >http://www.erlang.org/mailman/listinfo/erlang-questions 
  > 
  > 
  > 
  >-------------------------------------------------------------------------------- 
  > 
  > 
  >_______________________________________________ 
  >erlang-questions mailing list 
  > 
  >http://www.erlang.org/mailman/listinfo/erlang- questions 
  >_______________________________________________ 
  >erlang-questions mailing list 
  > 
  >http://www.erlang.org/mailman/listinfo/erlang-questions 
  > 
  > 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20060918/04a25a34/attachment.html>


More information about the erlang-questions mailing list