error auto-restart problem..

[xing at litespeedtech.com]

The error happened again on instance 2 with the new build. The only 
meaningful config diff between instance 1 and instance 2 is that 2 is 
started with -s file,/raid0/varn.fp,10G

Fatal error at the end.

Cache child died pid=1688 status=0x6
Clean child
Child cleaned
start child pid 1699
Child said (2, 1699): <<Child starts
managed to mmap 10737418240 bytes of 10737418240
Ready
 >>
Child said (2, 1699): <<Missing errorhandling code in FetchHeaders(), 
cache_fetc 
                                h.c line 318:
   Condition(i == 0) not true.
   errno = 104 (Connection reset by peer)
 >>
Cache child died pid=1699 status=0x6
Clean child
Child cleaned
start child pid 1730
Child said (2, 1730): <<Child starts
managed to mmap 10737418240 bytes of 10737418240
Ready
 >>
Child said (2, 1730): <<Missing errorhandling code in FetchHeaders(), 
cache_fetc 
                                h.c line 318:
   Condition(i == 0) not true.
   errno = 104 (Connection reset by peer)
 >>
Cache child died pid=1730 status=0x6
Clean child
Child cleaned
start child pid 1740
Cache child died pid=1740 status=0x6
Clean child
Child cleaned
start child pid 1749
Child said (2, 1749): <<Child starts
managed to mmap 10737418240 bytes of 10737418240
Ready
Missing errorhandling code in FetchHeaders(), cache_fetch.c line 318:
   Condition(i == 0) not true.
   errno = 104 (Connection reset by peer)
 >>
Cache child died pid=1749 status=0x6
Clean child
Child cleaned
start child pid 1760
Child said (2, 1760): <<Child starts
managed to mmap 10737418240 bytes of 10737418240
Ready
Missing errorhandling code in FetchHeaders(), cache_fetch.c line 318:
   Condition(i == 0) not true.
   errno = 104 (Connection reset by peer)
 >>
Cache child died pid=1760 status=0x6
Clean child
Child cleaned
start child pid 1771
Pushing vcls failed:
CLI communication error
unlink /tmp/vcl.XXxgVLp9


Poul-Henning Kamp wrote:
> In message <450C9C42.2050809 at litespeedtech.com>, "xing at litespeedtech.com" write
> s:
> 
>> Pushing vcls failed:
>> CLI communication error
>> unlink /tmp/vcl.XXqufVqH
> 
> I have just committed a change to make sure we get the error messages
> from the child in this case.
> 
> If you can reproduce it I'm very interested in what it said.
> 
>> [...] Likely result of me running 2 instances on the same server.
> 
> I'm not so sure.
> 
> But regarding the multiple-instance thing:
> 
> I think my inclination is that each instance of varnish gets a
> user chosen "identifier".  The only requirement I have is that
> it can be part of a filename (ie: no '/' etc).
> 
> You will of course have to specify that identifier to all programs
> that need access to the shared memory.
> 
> Is that workable ?
>