[226] in Zephyr_Bugs
bdump problems with 3 servers
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Wed Jan 9 03:25:28 1991
Date: Wed, 9 Jan 91 03:25:18 -0500
From: Ken Raeburn <Raeburn@MIT.Edu>
To: zephyr-bugs@ATHENA.MIT.EDU
I tried starting up arilinn a short while ago. After it exchanged
information with neskaya, arilinn and b11zephyr started refusing to
talk to each other, and doing it a lot:
Jan 9 03:05:48 arilinn zephyrd[16179]: gbd connect: Connection refused
Jan 9 03:06:19 arilinn last message repeated 32 times
Jan 9 03:06:46 arilinn last message repeated 27 times
Jan 9 03:06:47 arilinn zephyrd[16179]: bdump_send: Broken pipe
Jan 9 03:06:48 arilinn zephyrd[16179]: gbd connect: Connection refused
Jan 9 03:07:19 arilinn last message repeated 31 times
Jan 9 03:07:22 arilinn last message repeated 3 times
Jan 9 03:07:23 arilinn zephyrd[16179]: bdump_send: Broken pipe
Jan 9 03:07:24 arilinn zephyrd[16179]: gbd connect: Connection refused
Jan 9 03:07:55 arilinn last message repeated 31 times
kill 16179
arilinn# Jan 9 03:08:04 arilinn last message repeated 9 times
Jan 9 03:08:04 arilinn zephyrd[16179]: goodbye (sig 15)
At the same time, b11zephyr logged a lot of messages also:
Jan 9 03:06:55 b11zephyr zephyrd[18692]: bdump_send:
Jan 9 03:06:56 b11zephyr zephyrd[18692]: gbd connect: Connection refused
Jan 9 03:06:57 b11zephyr zephyrd[18692]: gbd connect: Connection refused
Jan 9 03:06:58 b11zephyr zephyrd[18692]: bdump_send:
Jan 9 03:06:59 b11zephyr zephyrd[18692]: gbd connect: Connection refused
Jan 9 03:07:30 b11zephyr last message repeated 31 times
Jan 9 03:07:31 b11zephyr zephyrd[18692]: gbd connect: Connection refused
Jan 9 03:07:32 b11zephyr zephyrd[18692]: bdump_send:
Jan 9 03:07:33 b11zephyr zephyrd[18692]: gbd connect: Connection refused
Jan 9 03:07:51 b11zephyr last message repeated 18 times
A previous attempt worked okay, with the dump going smoothly all
around. (It runs fast enough now that I think there's little point in
trying to speed it up any further while the old servers are still in
use. I suspect they are the bottleneck now. Making the dump really
run concurrently with other service is about the only thing left.)
While this was going on, b11zephyr did continue responding to other
traffic, though it might have been a bit slower than normal.
