Mailing List Archive

On Tue, 2003-03-25 at 12:51, Richard Zinar wrote:
> Hi,
>
> I'm trying to get conserver (V7.2.6) working in our environment,
> I have run into the following problem - as soon as I start conserver,
> the consoles I'm using it to manage come down almost immediately:
>
> [-- Console up -- Tue Mar 25 09:26:30 2003]
> [-- Console down -- Tue Mar 25 09:26:30 2003]
>
> I also noticed I'm unable to telnet into our console servers (e.g.,
> wti10.admin.sc.p4pnet.net) while conserver is running. I wouldn't
> expect to be able to access individual ports on the console server while
> conserver is controlling them, but it's not clear to me why the console
> server itself should become inaccessible.

Maybe reverse tcp is using up all the pseudo connections.

>
> The conserver.cf file looks as follows:
>
>
> LOGDIR=/var/log/consoles
> TIMESTAMP=1ha
>
> holmium : !wti11.admin.sc.p4pnet.net :2103:&.log::1
> nitrogen : !wti11.admin.sc.p4pnet.net :2104:&.log::1
> barium : !wti11.admin.sc.p4pnet.net :2105:&.log::1
> fermium : !wti11.admin.sc.p4pnet.net :2106:&.log::1
> hassium : !wti11.admin.sc.p4pnet.net :2107:&.log::1
> uranium : !wti11.admin.sc.p4pnet.net :2108:&.log::1
> terbium : !wti11.admin.sc.p4pnet.net :2109:&.log::1
> thurium : !wti11.admin.sc.p4pnet.net :2110:&.log::1
> cerium : !wti11.admin.sc.p4pnet.net :2111:&.log::1
>
> brie : !wti10.admin.sc.p4pnet.net :2103:&.log::1
> radon : !wti10.admin.sc.p4pnet.net :2104:&.log::1
> cheddar : !wti10.admin.sc.p4pnet.net :2105:&.log::1
> edam : !wti10.admin.sc.p4pnet.net :2107:&.log::1
> titanium : !wti10.admin.sc.p4pnet.net :2109:&.log::1
> beaufort : !wti10.admin.sc.p4pnet.net :2111:&.log::1
> blarney : !wti10.admin.sc.p4pnet.net :2112:&.log::1
> iridium : !wti10.admin.sc.p4pnet.net :2113:&.log::1
> tantalum : !wti10.admin.sc.p4pnet.net :2115:&.log::1
> astatine : !wti10.admin.sc.p4pnet.net :2116:&.log::1
>
> Any suggestions on what I might be doing wrong? The console
> servers are WTI CMS-16 units. Thanks ...
>
> Richard
>
>
> ----
>

> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users

Have you tried commenting one of the conserver.cf port entries, so that it's
out of conserver control, and directly telneting to the port:

# telnet wti10.admin.sc.p4pnet.net 2105

If this doesn't work, then conserver may not be the problem, as the
underlying utility is preventing connections. Mt two cents for initial
troubleshooting I guess :) If telnet works, we need to troubleshoot further.

Shal Halka




_________________________________________________________________
Hotmail now available on Australian mobile phones. Go to
http://ninemsn.com.au/mobilecentral/hotmail_mobile.asp

FWIW - this problem was resolved by upgrading our
WTI CMS-16 console servers to the latest firmware
release (V4.0). The older version we were running
couldn't handle more than four simultaneous connections ...

Richard


-----Original Message-----
From: Richard Zinar [mailto:Richard.Zinar@overture.com]
Sent: Tuesday, March 25, 2003 9:51 AM
To: 'users@conserver.com'
Subject: Console connections won't stay up


Hi,

I'm trying to get conserver (V7.2.6) working in our environment,
I have run into the following problem - as soon as I start conserver,
the consoles I'm using it to manage come down almost immediately:

[-- Console up -- Tue Mar 25 09:26:30 2003]
[-- Console down -- Tue Mar 25 09:26:30 2003]

I also noticed I'm unable to telnet into our console servers (e.g.,
wti10.admin.sc.p4pnet.net) while conserver is running. I wouldn't
expect to be able to access individual ports on the console server while
conserver is controlling them, but it's not clear to me why the console
server itself should become inaccessible.

The conserver.cf file looks as follows:


LOGDIR=/var/log/consoles
TIMESTAMP=1ha

holmium : !wti11.admin.sc.p4pnet.net :2103:&.log::1
nitrogen : !wti11.admin.sc.p4pnet.net :2104:&.log::1
barium : !wti11.admin.sc.p4pnet.net :2105:&.log::1
fermium : !wti11.admin.sc.p4pnet.net :2106:&.log::1
hassium : !wti11.admin.sc.p4pnet.net :2107:&.log::1
uranium : !wti11.admin.sc.p4pnet.net :2108:&.log::1
terbium : !wti11.admin.sc.p4pnet.net :2109:&.log::1
thurium : !wti11.admin.sc.p4pnet.net :2110:&.log::1
cerium : !wti11.admin.sc.p4pnet.net :2111:&.log::1

brie : !wti10.admin.sc.p4pnet.net :2103:&.log::1
radon : !wti10.admin.sc.p4pnet.net :2104:&.log::1
cheddar : !wti10.admin.sc.p4pnet.net :2105:&.log::1
edam : !wti10.admin.sc.p4pnet.net :2107:&.log::1
titanium : !wti10.admin.sc.p4pnet.net :2109:&.log::1
beaufort : !wti10.admin.sc.p4pnet.net :2111:&.log::1
blarney : !wti10.admin.sc.p4pnet.net :2112:&.log::1
iridium : !wti10.admin.sc.p4pnet.net :2113:&.log::1
tantalum : !wti10.admin.sc.p4pnet.net :2115:&.log::1
astatine : !wti10.admin.sc.p4pnet.net :2116:&.log::1

Any suggestions on what I might be doing wrong? The console
servers are WTI CMS-16 units. Thanks ...

Richard