Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!ereborbbs.duckdns.org!.POSTED.192.168.18.18!pyrite.ereborbbs.duckdns.org!not-for-mail
From: kyonshi <smaug@ereborbbs.duckdns.org>
Newsgroups: comp.mail.uucp,comp.os.linux.misc
Subject: Re: UUCP connection "Timed out in chat script"
Date: Wed, 14 Aug 2024 15:57:11 +0200
Organization: Erebor InterNetNews
Message-ID: <nmpuok-nk5.ln1@pyrite.ereborbbs.duckdns.org>
References: <tm2sok-9lo1.ln1@pyrite.ereborbbs.duckdns.org>
	<v9gap3$48g$1@reader1.panix.com>
NNTP-Posting-Host: c3066ed76bae8bcc0e476efb157ff758
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Info: ereborbbs.duckdns.org; posting-host="192.168.18.18";
	logging-data="9000"; mail-complaints-to="usenet@ereborbbs.duckdns.org"
User-Agent: Pan/0.154 (Izium; 517acf4)
Bytes: 2331
Lines: 29

On Tue, 13 Aug 2024 19:05:08 -0000 (UTC), Ed Ravin wrote:

> From somewhere in cyberspace, kyonshi <gmkeros@gmail.com> said:
>>I already have an installation on one of my machines in which I can
>>connect to multiple other machines (both Debian) via tcp and Taylor
>>UUCP.
>>
>>Now I want to make a connection between my notebook and my server, and
>>for some reason the connection eludes me so far. It clearly connects
>>(via ssh pipe), but then times out in chat script according to the log.
>>This happens from both sides, and I cannot see any issue with the
>>configuration on either side.
> 
> I assume you've already tested ssh from the notebook to the server on
> the command line to make sure you have connectivity?
> 
>>Is there a way to get more information as to why it times out? Or what
>>exactly it is doing when it tries to connect?
> 
> Yes and yes. Read up on the --debug option in
> https://www.oreilly.com/openbook/linag2/book/ch16.html#AUTOID-13819 I'm
> guessing you want "--debug chat".

Ah, your prompting to the debug feature helped, and I really should have 
found that myself...

In the end it was a combination of two issues with both the ssh connection 
(I forgot to address the changed ssh port on the target machine) and the 
chat script. Luckily with the Debug log activated I was able to figure it 
out.