1.1.1 progress

[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 said (2, 25738): <<Child starts
managed to mmap 536870912 bytes of 536870912
Ready
CLI ready
>>
Child said (2, 25738): <<socktest: linger=0 sndtimeo=0 rcvtimeo=0
>>
Child said (2, 25738): <<Assert error in wrk_do_one(), cache_pool.c line 199:
  Condition(!isnan(w->used)) not true.
  errno = 104 (Connection reset by peer)
Assert error in wrk_do_one(), cache_pool.c line 199:
  Condition(!isnan(w->used)) not true.
  errno = 104 (Connection reset by peer)
>>
Cache child died pid=25738 status=0x6
Clean child
Child cleaned
start child pid 26209
Child said (2, 26209): <<Child starts
managed to mmap 536870912 bytes of 536870912
Ready
CLI ready
...

Hope that it gives some help.
Janis

p.s.
please let me know if I should be sending these messages to tickets, privately 
or smth.

On Saturday 18 August 2007 13:39, Dag-Erling Smørgrav wrote:
> Janis Putrams <janis.putrams at delfi.lv> 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 piped to the backend rather than cached.  If you're
> having trouble with the management and / or worker process crashing,
> you should run varnish in the foreground (-d -d) to capture the error
> messages (most likely assertion failures), and get a backtrace.
>
> DES