[plug] Looking for assistance with a recent Debian upgrade
Bill Kenworthy
billk at iinet.net.au
Tue Dec 17 21:03:25 AWST 2019
Hi Joe,
how are you trying to log in? - ssh keys or password? If password,
what is the value of PermitRootPassword in /etc/ssh/sshd.conf?
BillK
On 17/12/19 7:07 pm, Dean Bergin wrote:
> Hello Joe,
>
> Ok, can you post sanitised vvv(v) output from a login attempt?
>
> Also, do you have console or out of band management access? You may
> want to check the server logs as well (if you haven't already) and
> consider increasing verbosity there too.
>
> I'm happy to take a look at sanitised logs (preferably filtered to
> just SSH) but no guarantees I can pinpoint the problem.
> Just hoping to spot wny clues that would hint at what the next step is
> in troubleshooting.
>
>
> Kind Regards,
>
> /Dean Bergin/.
>
> On Tue, 17 Dec 2019, 18:10 Joe Aquilina, <joe at chem.com.au
> <mailto:joe at chem.com.au>> wrote:
>
> Dean
>
> Yes, I have tried using the IPQoS throughput option, with no success.
>
> I have used -v(vv) when logging in, and am happy to provide
> examples when I login, but my knowledge is not good enough to be
> able to decipher what the extra verbosity is telling me.
>
> Cheers.
>
> Joe Aquilina
>
> On 17/12/19 4:55 pm, Dean Bergin wrote:
>> Hello Joe,
>>
>> Have you tried SSH with the IPQoS throughout option? The
>> following article suggested it (follow link from the post therein).
>>
>> Also, try increasing SSH verbosity with more v's ;-)
>>
>> https://bbs.archlinux.org/viewtopic.php?id=239982
>>
>> Hope that helps.
>>
>>
>> Kind Regards,
>>
>> /Dean Bergin/.
>>
>> On Tue, 17 Dec 2019, 16:18 Joe Aquilina, <joe at chem.com.au
>> <mailto:joe at chem.com.au>> wrote:
>>
>> Ben
>>
>> Thanks for that, and here goes:
>>
>> We have two Debian systems here, along with a bunch of
>> Kubuntu and Windows systems. Early last week I upgraded the
>> second of our Debian systems from stretch to buster. A few
>> days earlier, I had upgraded the other Debian system, also
>> from stretch to buster. That first upgrade went fine and
>> everything is working as expected.
>>
>> However the second (of course the more important system) did
>> not upgrade correctly. It is mostly ok, but I am unable to
>> ssh in to that machine. When I try to, I get this:
>>
>> packet_write_wait: Connection to 10.0.2.1 port 22: Broken pipe
>>
>> Searching on the net suggested I try adding
>> ServerAliveInterval and ServerAliveCountMax into the
>> sshd_config file - no luck there.
>>
>> I have tried removing (and purging) openssh again with no luck.
>>
>> I have also tried disabling ufw in case there problem was
>> there, no luck.
>>
>> Stopping ssh and sshd services and installing dropbear allows
>> me to login to the machine, and I can perform normal file
>> operations. However, this machine collects and distributes
>> our emails for all users on our LAN and the other machines
>> can't access the machine. There is another (off-site) Debian
>> machine that does an important overnight folder sync which it
>> is currently unable to do as it can't ssh in.
>>
>> My Linux/Debian knowledge is obviously pretty limited, and I
>> am not sure what to try next.
>>
>> What else can I provide that might help me solve this?
>>
>> Sorry to be a bit longwinded and possibly not precise enough
>> in my description of the problem. Thanks in advance for any
>> suggestions, advice or assistance.
>>
>> Cheers.
>>
>> Joe Aquilina
>>
>> On 17/12/19 3:55 pm, Benjamin wrote:
>>> Hi Joe,
>>>
>>> Yep, sounds good to me...
>>> ~ B
>>> (PLUG President)
>>>
>>> On Tue, Dec 17, 2019 at 2:57 PM Joe Aquilina
>>> <joe at chem.com.au <mailto:joe at chem.com.au>> wrote:
>>>
>>> Hello. I have just subscribed to this list with this
>>> address after being
>>> a long time lurker using my home email address.
>>>
>>> I am looking for technical assistance after a not quite
>>> successful
>>> recent Debian upgrade (from stretch to buster). Is it
>>> appropriate for me
>>> to do so here? My Linux knowledge is still pretty
>>> limited and I have not
>>> been able to find a solution to the problem through
>>> extensive searches
>>> on the internet.
>>>
>>> If that is a reasonable request, I will detail the
>>> problem, and what I
>>> have tried to do to fix it, in a separate email.
>>>
>>> Thanks in advance.
>>>
>>> Joe Aquilina
>>>
>>> --
>>> Joe Aquilina
>>> Central Chemical Consulting Pty Ltd
>>> PO Box 2546 Malaga WA 6944 Australia
>>> 1/11 Narloo St Malaga 6090 Australia
>>> Tel: +61 8 9248 2739 Fax: +61 8 9248 2749
>>> joe at chem.com.au <mailto:joe at chem.com.au> www.chem.com.au
>>> <http://www.chem.com.au>
>>>
>>> _______________________________________________
>>> PLUG discussion list: plug at plug.org.au
>>> <mailto:plug at plug.org.au>
>>> http://lists.plug.org.au/mailman/listinfo/plug
>>> Committee e-mail: committee at plug.org.au
>>> <mailto:committee at plug.org.au>
>>> PLUG Membership: http://www.plug.org.au/membership
>>>
>>
>> --
>> Joe Aquilina
>> Central Chemical Consulting Pty Ltd
>> PO Box 2546 Malaga WA 6944 Australia
>> 1/11 Narloo St Malaga 6090 Australia
>> Tel: +61 8 9248 2739 Fax: +61 8 9248 2749
>> joe at chem.com.au <mailto:joe at chem.com.au> www.chem.com.au <http://www.chem.com.au>
>>
>> _______________________________________________
>> PLUG discussion list: plug at plug.org.au <mailto:plug at plug.org.au>
>> http://lists.plug.org.au/mailman/listinfo/plug
>> Committee e-mail: committee at plug.org.au
>> <mailto:committee at plug.org.au>
>> PLUG Membership: http://www.plug.org.au/membership
>>
>
> --
> Joe Aquilina
> Central Chemical Consulting Pty Ltd
> PO Box 2546 Malaga WA 6944 Australia
> 1/11 Narloo St Malaga 6090 Australia
> Tel: +61 8 9248 2739 Fax: +61 8 9248 2749
> joe at chem.com.au <mailto:joe at chem.com.au> www.chem.com.au <http://www.chem.com.au>
>
> _______________________________________________
> PLUG discussion list: plug at plug.org.au <mailto:plug at plug.org.au>
> http://lists.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.org.au <mailto:committee at plug.org.au>
> PLUG Membership: http://www.plug.org.au/membership
>
>
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://lists.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.org.au
> PLUG Membership: http://www.plug.org.au/membership
More information about the plug
mailing list