Event timer

[Adelino Monteiro]

As it turns out the fault was on the client side (as always ;-))
Testing the request with a simple wget url proved that nginx was in fact
returned the data as requested by the client.

Thanks for your help nevertheless

On 16 January 2012 21:10, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Mon, Jan 16, 2012 at 07:25:52PM +0000, Adelino Monteiro wrote:
>
> > Hello,
> >
> > Could someone explain me why my nginx configuration has a delay when
> > sending file (from 19:07:39 to 19:09:59)
> > This same configuration used to work in my development environment but in
> > our staging server it has this behaviour.
> > The one thing that is different is that this last one is build on SAN
> > storage with RAID 5 but Linux sees it as an /dev/sdx partition.
> >
> > 2012/01/16 19:07:39 [debug] 4799#0: *3 http write filter 0000000001340500
> > 2012/01/16 19:07:39 [debug] 4799#0: *3 http copy filter: -2
> > "/local/NOAJR0600020_H.ogg?"
> > 2012/01/16 19:07:39 [debug] 4799#0: *3 http writer output filter: -2,
> > "/local/NOAJR0600020_H.ogg?"
> > 2012/01/16 19:07:39 [debug] 4799#0: *3 event timer: 24, old:
> 1326740919650,
> > new: 1326740919946
> > 2012/01/16 19:07:59 [debug] 4799#0: *3 post event 00000000013C6328
> > 2012/01/16 19:07:59 [debug] 4799#0: *3 delete posted event
> 00000000013C6328
> > 2012/01/16 19:07:59 [debug] 4799#0: *3 http run request:
> > "/local/NOAJR0600020_H.ogg?"
> > 2012/01/16 19:07:59 [debug] 4799#0: *3 http writer handler:
> > "/local/NOAJR0600020_H.ogg?"
> > 2012/01/16 19:07:59 [debug] 4799#0: *3 http output filter
> > "/local/NOAJR0600020_H.ogg?"
> > 2012/01/16 19:07:59 [debug] 4799#0: *3 http copy filter:
> > "/local/NOAJR0600020_H.ogg?"
> > 2012/01/16 19:07:59 [debug] 4799#0: *3 http postpone filter
> > "/local/NOAJR0600020_H.ogg?" 0000000000000000
> >
> > Any help would be greatly appreciated.
>
> It's hardly possible to tell anything from the above log snippet,
> as it basically doesn't contain any information related to file
> I/O calls and/or event processing.  You have to examine global
> logs to be able to view event processing logs, and at least one
> full event loop iteration is required to be able to tell
> something.
>
> Maxim Dounin
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20120117/3530dfd2/attachment.html>