It was an issue with the NICs. I had recently upgraded 8 servers. I
bought 3com 3c2000s for the lot of them, they use the marvell yukon
chip, and I have that chip on 2 linux servers, and it works REAL
well. For some reason, not an issue with the 2 webservers with the
new nics, but the 6 witango servers, many issues, like the one below.
Also, at night, they would lose connectivity. Reset the port on the
switch and they would come back up.
I had an issue like this many moons ago on mail server. NIC would
lose conn, when a certain user checked a certain email. Support said
change the nic to intel or 3com. I went with intel pro 1000, and no
more problem.
I changed my witango nics to intel pro 1000 GTs, and no more problems.
Like there is some incompatibility with something witango does, cuz I
have not seen any problems on other machines. Anyway, just
mentioning, in case any one runs into this.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Oct 28, 2005, at 12:39 PM, Robert Shubert wrote:
I have not seen this, and my efforts on Windows 2003 have worked
well, but I
have found that some ports are used that I wasn't expecting. For
example, I
provide a set range of ports for my Passive FTP to use, and I was
surprised
to find that one of the ports was already in use. This range had
worked fine
for me in the past.
My point is that perhaps something else, not necessarily Witango,
is already
using the port. I would suggest using some other port and see if
the problem
continues.
If it does, do you have any indication that Witango is launching
twice?
(check the event log) it might be possible to Witango to be
launching under
two different users, or failing to launch completely the first time
and
trying again.
Just some ideas to try.
Robert
-----Original Message-----
From: Robert Garcia [mailto:[EMAIL PROTECTED]
Sent: Friday, October 28, 2005 4:28 AM
To: [email protected]
Subject: Witango-Talk: Witango Startup problem
I recently upgraded all of our witango servers, we have a bank of 6
running on windows 2003 web edition. All identical.
On 3 of the servers, I get this on reboot, or initial start of
witango after it is been sitting stopped.
[ 1572] 2005-10-28 01:08:24 START INFO Listener Port: 18155
[ 1572] 2005-10-28 01:08:24 START ERROR Configuration: Cannot
use port 18155, another server is running
[ 1572] 2005-10-28 01:08:24 START ERROR Startup: Can't
initialize Witango Server. See the previous error for details.
There is no other server running, and if I just restart the service,
it starts fine. But on these 3 servers, after reboot, witango does
this each time.
Anyone else seen this?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
