Connection problems/resets/broken pipe with 3.08

lch · #1 May 11th, 2007, 11:06 AM

Yes, there are workarounds floating around which might work in some or even most situations, but we should be rather more interested about isolating the problem so that the devs can fix it for good. If it would happen rarely and due to other circumstances with the net connection itself it would be excusable that this happens, but it really seems to be a problem with the server software, after all.

Gandalf Parker · #2 May 11th, 2007, 11:36 AM

Thats what I was saying also.
Up until now I thought it might have been a problem only with my servers. I have now reported it in the beta group to the devs.

Argitoth · #3 March 2nd, 2008, 05:03 PM

Dominions in text mode on windows is completely invisible. "Broken pipe" is a message I only get on Mac. When I get that message, the Mac closes the server for no apparent reason.

lch · #4 March 2nd, 2008, 05:20 PM

Dominions in Windows writes its output to .txt files since it can't divide between a message log and an error log on the screen.

Your mac problem doesn't have anything to do with the things described in this thread, I think.

Lingchih · #5 March 2nd, 2008, 09:31 PM

All of Zachariah's games exhibit this problem, but unfortunately he has mysteriously disappeared. We are still playing one game though, Testament of Blood, because one of the players has kindly left a client permanently connected on the "waiting for info" screen.

One of Velusions games exhibited the problem for a few turns, but it has subsequently gone away.

The workaround is unusable for me, because if I leave multiple, windowed instances of the game open so that I can connect, my graphics card overheats and shuts down.

lch · #6 March 3rd, 2008, 08:18 AM

Quote:

Lingchih said:
The workaround is unusable for me, because if I leave multiple, windowed instances of the game open so that I can connect, my graphics card overheats and shuts down.

I don't know about Wraithlord's server info program, but the Dominion 3 Server Monitor Tool that I inherited from MarcinM definitely does not disconnect from a server unless you tell it to. So it should be sufficient for the purpose of holding a connection, without any burden to the CPU. It hasn't been updated to accomodate the 3.14 changes yet, but that would be negligible for this task, anyway.

vfb · #7 March 3rd, 2008, 08:27 AM

You could also try turning off the animated backgrounds.

Foodstamp · #8 March 3rd, 2008, 03:41 PM

Quote:

Lingchih said:
All of Zachariah's games exhibit this problem, but unfortunately he has mysteriously disappeared. We are still playing one game though, Testament of Blood, because one of the players has kindly left a client permanently connected on the "waiting for info" screen.

One of Velusions games exhibited the problem for a few turns, but it has subsequently gone away.

The workaround is unusable for me, because if I leave multiple, windowed instances of the game open so that I can connect, my graphics card overheats and shuts down.

Just to clarify, you are not keeping them open once you connect, correct? You only need to open the extra clients long enough for it to prompt you for your pretender's password. Then you can close the other client(s). I've never had to launch more than one extra client, guess I am lucky

.

Lingchih · #9 March 3rd, 2008, 04:56 PM

yeah, i was leaving them open in the background, and I also had animated backgrounds turned on, so the combination of the two probably caused the overheating.