Re: [help-serveez] DNS Coserver weirdness

[stefan]

On 29 Dec 2002, Andreas Rottmann wrote:

> Hi!

Hello!

> In my server instance initializer I try to connect to peers using
> coserver_dns calls (this is exactly what the gnutella server does,
> too). This works fine normally, but I get problems when running my
> server in GDB:
>
> ...
> [2002/12/29 14:56:35] notice: starting internal dns coserver
> [2002/12/29 14:56:35] debug: coserver pipes: 6-13
> [2002/12/29 14:56:35] debug: coserver pipes: 6-15
> [2002/12/29 14:56:35] debug: coserver process id is 28079
> [2002/12/29 14:56:35] notice: initializing all server instances
> [2002/12/29 14:56:35] notice: dstw: ID is 818082ca1e695eeb
> [2002/12/29 14:56:35] notice: dstw: enqueuing manu
> [2002/12/29 14:56:35] notice: entering server loop
> [2002/12/29 14:56:35] error: exception on receiving pipe 14
> [2002/12/29 14:56:35] debug: scheduling socket id 5 for shutdown
> [2002/12/29 14:56:35] error: exception on sending pipe 13
> [2002/12/29 14:56:35] debug: shutting down socket id 5
> [2002/12/29 14:56:35] debug: dns: killing coserver pid 28079
> [2002/12/29 14:56:35] debug: pipe (14-13) disconnected
> [2002/12/29 14:56:38] notice: starting internal dns coserver
> [2002/12/29 14:56:38] debug: coserver process id is 28080
> [2002/12/29 14:56:38] debug: coserver pipes: 6-15
> ...
>
> The 'dstw: ' messages come from my client, the 'enqueing manu' message
> is made directly before using the DNS coserver. I first figured that the
> coserver isn't started up fast enough, so it gets killed and restarted
> because of the too-early request...
>
> However, I then moved the coserver calls into the server notify
> function, which waited for two seconds before trying to use DNS the
> first time, and I got the same results... DNS coserver being killed
> and restarted, not returing any result.

If you had typed 'ps' you would have noticed that for some reason the
first dns coserver pid '28079' was not actually running at the time you
tried to send a request to it.  Just now I do not know why this occurs.
Can you figure out after how much time (setting the notifier time to more
than 2 seconds) it works again?

Cheers,
        address@hidden