Re: 1.1.1 progress

2007-08-21 Thread Janis Putrams
Hi! Thank you. I added the line yesterday as soon as you sent it and seems that it has helped and no slave processes die with that message any more. Slave processes do restart from time to time (with no additional information) but management process has been running ok so far. janis On Monday 2

Re: 1.1.1 progress

2007-08-20 Thread Dag-Erling Smørgrav
Janis Putrams <[EMAIL PROTECTED]> writes: > Child said (2, 25738): < Condition(!isnan(w->used)) not true. > errno = 104 (Connection reset by peer) >>> See ticket #150. DES -- Dag-Erling Smørgrav Senior Software Developer Linpro AS - www.linpro.no _

Re: 1.1.1 progress

2007-08-20 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Janis Putrams writes: >Assert error in wrk_do_one(), cache_pool.c line 199: > Condition(!isnan(w->used)) not true. > errno =3D 104 (Connection reset by peer) Try this fix: In cache_center.c, function cnt_lookup(), before the call to SES_Charge(), insert:

Re: 1.1.1 progress

2007-08-20 Thread Janis Putrams
Hi! Tnx for advice, i increased core file size to unlimited, run in foreground and wait for crash. Meanwhile encountered slave process restart that did not kill management process, but gave this log: ... Cache child died pid=25094 status=0xb Clean child Child cleaned start child pid 25738 Child

Re: 1.1.1 progress

2007-08-20 Thread Dag-Erling Smørgrav
Janis Putrams <[EMAIL PROTECTED]> writes: > Anyway I wanted to capture core file so run varnishd in foreground. > [...] > 05:17:28 root[pts/[EMAIL PROTECTED] ~# ulimit -a|grep core > core file size (blocks, -c) 65 you should use 'unlimited' instead; a varnishd core dump can easily rea

Re: 1.1.1 progress

2007-08-20 Thread Janis Putrams
Hi! With "master crash log" i meant output of varnishlog when management process dies. Anyway I wanted to capture core file so run varnishd in foreground. I set CXXFLAGS="-g" LDFLAGS="-g" in configure.ac. then run ./configure --prefix=/usr --enable-debug && make clean && make 05:17:28 root[pt

Re: 1.1.1 progress

2007-08-18 Thread Dag-Erling Smørgrav
Janis Putrams <[EMAIL PROTECTED]> writes: > I have been running varnishd from svn @Aug 16 06:17 and I managed to > capture master crash log. I have no idea what a "master crash log" is, but the varnish log you included is corrupted and doesn't tell me much, except that most of your traffic is pipe

Re: 1.1.1 progress

2007-08-17 Thread Janis Putrams
Hi! I have been running varnishd from svn @Aug 16 06:17 and I managed to capture master crash log. It is 900MB in size but it goes as follow: --- ... 317 VCL_call c deliver 317 VCL_return c deliver 317 TxProtocol c HTTP/1.1 317 TxStatus

Re: 1.1.1 progress

2007-08-13 Thread Dag-Erling Smørgrav
Ricardo Newbery <[EMAIL PROTECTED]> writes: > Without the updated automake, I get this... > > $ ./autogen.sh > > + aclocal > + glibtoolize --copy --force > You should update your `aclocal.m4' by running aclocal. > + autoheader > + automake --add-missing --copy --foreign > configure.ac: installing `

Re: 1.1.1 progress

2007-08-13 Thread Ricardo Newbery
On Aug 13, 2007, at 3:49 AM, Dag-Erling Smørgrav wrote: > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: >> Ricardo Newbery <[EMAIL PROTECTED]> writes: >>> Not so fast. I still needed to update automake as per the >>> instructions on http://varnish.projects.linpro.no/wiki/Installation >>> (slig

Re: 1.1.1 progress

2007-08-13 Thread Dag-Erling Smørgrav
Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > Ricardo Newbery <[EMAIL PROTECTED]> writes: > > Not so fast. I still needed to update automake as per the > > instructions on http://varnish.projects.linpro.no/wiki/Installation > > (slightly modified since the autogen.sh file is now a little > > d

Re: 1.1.1 progress

2007-08-13 Thread Dag-Erling Smørgrav
Ricardo Newbery <[EMAIL PROTECTED]> writes: > Not so fast. I still needed to update automake as per the > instructions on http://varnish.projects.linpro.no/wiki/Installation > (slightly modified since the autogen.sh file is now a little > different). Why? I would expect that /opt/local/bin would

Re: 1.1.1 progress

2007-08-13 Thread Ricardo Newbery
On Aug 12, 2007, at 2:48 PM, Martin Aspeli wrote: > Dag-Erling Smørgrav wrote: >> Martin Aspeli <[EMAIL PROTECTED]> writes: >>> Are there any OS X fixes in the 1.1 branch? >> >> Some, yes. At least, I hope the -flat_namespace hack is no longer >> required, but I don't have a Mac to test on right

Re: 1.1.1 progress

2007-08-12 Thread Martin Aspeli
Dag-Erling Smørgrav wrote: > Martin Aspeli <[EMAIL PROTECTED]> writes: >> Are there any OS X fixes in the 1.1 branch? > > Some, yes. At least, I hope the -flat_namespace hack is no longer > required, but I don't have a Mac to test on right now. I just tried it, doing the following: $ svn co h

Re: 1.1.1 progress

2007-08-10 Thread Dag-Erling Smørgrav
"C. Handel" <[EMAIL PROTECTED]> writes: > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > You still haven't told me what OS you're running. > GNU/LInux (there is a uname in the last post: Linux slow > 2.6.16.52-1smp, from the kernel version i guess distribution > pld-linux) Linux is not an OS.

Re: 1.1.1 progress

2007-08-10 Thread Janis Putrams
PLD Linux Distribution . PLD 2.0 (Ac) janis On Friday 10 August 2007 16:40, Dag-Erling Smørgrav wrote: > Janis Putrams <[EMAIL PROTECTED]> writes: > > On Thursday 09 August 2007 18:49, Dag-Erling Smørgrav wrote: > > > Janis Putrams <[EMAIL PROTECTED]> writes: > > > > I

Re: 1.1.1 progress

2007-08-10 Thread C. Handel
> > > What OS are you running on, and where is your curses.h installed? > > [...] > > You still haven't told me what OS you're running. GNU/LInux (there is a uname in the last post: Linux slow 2.6.16.52-1smp, from the kernel version i guess distribution pld-linux) Greetings Christoph _

Re: 1.1.1 progress

2007-08-10 Thread Dag-Erling Smørgrav
Janis Putrams <[EMAIL PROTECTED]> writes: > On Thursday 09 August 2007 18:49, Dag-Erling Smørgrav wrote: > > Janis Putrams <[EMAIL PROTECTED]> writes: > > > I had to modify Makefiles manually for it to find curses.h but that > > > could as well be problem on my side. > > What OS are you running on,

Re: 1.1.1 progress

2007-08-10 Thread Janis Putrams
07:37:04 root[pts/[EMAIL PROTECTED] ~# uname -a Linux slow 2.6.16.52-1smp #1 SMP Thu May 31 19:32:54 CEST 2007 i686 Intel(R)_Xeon(R)[EMAIL PROTECTED] PLD Linux 07:37:05 root[pts/[EMAIL PROTECTED] ~# locate curses.h /usr/include/ncurses/ncurses.h /usr/include/ncurses/curses.h /usr/include/ncursesw/

Re: 1.1.1 progress

2007-08-10 Thread Dag-Erling Smørgrav
Martin Aspeli <[EMAIL PROTECTED]> writes: > Are there any OS X fixes in the 1.1 branch? Some, yes. At least, I hope the -flat_namespace hack is no longer required, but I don't have a Mac to test on right now. DES -- Dag-Erling Smørgrav Senior Software Developer Linpro AS - www.linpro.no ___

Re: 1.1.1 progress

2007-08-09 Thread Martin Aspeli
Dag-Erling Smørgrav wrote: > I thought I'd let you know what's currently going on at our top-secret > underground Varnish R&D facility: > > - Poul-Henning has been working hard to resolve the stability issues >and assertion failures some of you have reported (#136, #137, #138, >#139, #140

Re: 1.1.1 progress

2007-08-09 Thread Dag-Erling Smørgrav
Janis Putrams <[EMAIL PROTECTED]> writes: > I had to modify Makefiles manually for it to find curses.h but that > could as well be problem on my side. What OS are you running on, and where is your curses.h installed? DES -- Dag-Erling Smørgrav Senior Software Developer Linpro AS - www.linpro.no

Re: 1.1.1 progress

2007-08-09 Thread Janis Putrams
Tnx for the fixes. I have just installed latest svn from branches/1.1. It's been running ok for 20min with arround 600req/sec with no slave process restarts. I had to modify Makefiles manually for it to find curses.h but that could as well be problem on my side. Thanks once again and will see

1.1.1 progress

2007-08-09 Thread Dag-Erling Smørgrav
I thought I'd let you know what's currently going on at our top-secret underground Varnish R&D facility: - Poul-Henning has been working hard to resolve the stability issues and assertion failures some of you have reported (#136, #137, #138, #139, #140, #141 and #143 should be fixed, while