2193379 – Regression: OpenSSH log format changed, zillion unmatched output lines in logwatch [rhel-7.5.z]

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2193379 - Regression: OpenSSH log format changed, zillion unmatched output lines in logwatch [rhel-7.5.z]

Summary: Regression: OpenSSH log format changed, zillion unmatched output lines in log...

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	logwatch
Sub Component:
Version:	9.2
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Lukáš Nykrýn
QA Contact:	qe-baseos-daemons
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-05-05 12:52 UTC by Karel Volný
Modified:	2023-09-21 09:56 UTC (History)
CC List:	0 users
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-21 09:56:33 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-5783	0	None	Migrated	None	2023-09-21 09:56:28 UTC
Red Hat Issue Tracker	RHELPLAN-156524	0	None	None	None	2023-05-05 12:54:51 UTC

Description Karel Volný 2023-05-05 12:52:47 UTC

This bug was initially created as a copy of Bug #2012815

I am copying this bug because: 
same with logwatch-7.5.5-6.el9.noarch

 ################### Logwatch 7.5.5 (01/22/21) #################### 
        Processing Initiated: Fri May  5 08:49:57 2023
        Date Range Processed: all
        Detail Level of Output: 10
        Type of Output/Format: stdout / text
        Logfiles for Host: ci-vm-10-0-136-191.hosted.upshift.rdu2.redhat.com
 ################################################################## 
 
 --------------------- SSHD Begin ------------------------ 

 Network Read Write Errors: 1
 
 SSHD Killed: 1 Time
 
 SSHD Started: 4 Times
 
 Negotiation failed:
    no matching host key type found
       10.37.128.108: 1 Time
         ssh-rsa: 1 Time
       10.43.2.5: 2 Times
         sk-ecdsa-sha2-nistp256: 1 Time
         sk-ssh-ed25519: 1 Time
 
 Disconnecting after too many authentication failures for user:
    root : 1 Time
 
 Users logging in through sshd:
    root:
       10.37.128.108 (liver3.lab.eng.brq2.redhat.com): 2 Times
       ::1 (localhost): 1 Time
       10.43.2.5: 1 Time
 
 **Unmatched Entries**
 dispatch_protocol_error: type 90 seq 5 [preauth] : 1 Time
 invalid public DH value: <= 1 [preauth] : 1 Time
 main: sshd: ssh-rsa algorithm is disabled : 14 Times
 
 ---------------------- SSHD End ------------------------- 




This bug was initially created as a copy of Bug #1593588

I am copying this bug because: 
it looks like we have the same problem in RHEL8 ...

https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2021/05/53504/5350480/9956463/125671844/taskout.log

:: [ 16:41:52 ] :: [   LOG    ] ::  
 ################### Logwatch 7.4.3 (04/27/16) #################### 
        Processing Initiated: Fri May  7 16:41:52 2021
        Date Range Processed: all
        Detail Level of Output: 10
        Type of Output/Format: stdout / text
        Logfiles for Host: ibm-x3650m4-01-vm-04.ibm2.lab.eng.bos.redhat.com
 ################################################################## 
 
 --------------------- SSHD Begin ------------------------ 

 SSHD Killed: 1 Time(s)
 
 SSHD Started: 6 Time(s)
 
 Users logging in through sshd:
    root:
       ::1 (localhost): 1 time
 
 **Unmatched Entries**
 error: maximum authentication attempts exceeded for root from 222.186.15.26 port 54348 ssh2 [preauth] : 1 time(s)
 dispatch_protocol_error: type 90 seq 5 [preauth] : 1 time(s)
 Connection reset by 198.98.59.151 port 52432 [preauth] : 1 time(s)
 pam_sepermit(sshd:auth): Cannot determine the user's name : 1 time(s)
 invalid public DH value: <= 1 [preauth] : 1 time(s)
 
 ---------------------- SSHD End ------------------------- 

 
 ###################### Logwatch End ######################### 
:: [ 16:41:52 ] :: [   PASS   ] :: Files /dev/null and logwatch.out should differ 
:: [ 16:41:52 ] :: [   FAIL   ] :: File 'logwatch.out' should not contain 'Unmatched Entries' 


or when run in 1minutetip:

:: [ 07:05:11 ] :: [   LOG    ] ::  
 ################### Logwatch 7.4.3 (04/27/16) #################### 
        Processing Initiated: Mon Oct 11 07:05:11 2021
        Date Range Processed: all
        Detail Level of Output: 10
        Type of Output/Format: stdout / text
        Logfiles for Host: ci-vm-10-0-139-60.hosted.upshift.rdu2.redhat.com
 ################################################################## 
 
 --------------------- SSHD Begin ------------------------ 

 SSHD Started: 2 Time(s)
 
 Users logging in through sshd:
    root:
       10.37.128.108 (liver3.lab.eng.brq.redhat.com): 2 times
       ::1 (localhost): 1 time
       10.43.2.140: 1 time
 
 **Unmatched Entries**
 Unable to negotiate with 10.43.2.140 port 37430: no matching host key type found. Their offer: sk-ssh-ed25519 [preauth] : 1 time(s)
 Disconnected from user root 10.37.128.108 port 60118 : 1 time(s)
 error: maximum authentication attempts exceeded for root from 222.186.15.26 port 54348 ssh2 [preauth] : 1 time(s)
 Disconnected from user root ::1 port 38784 : 1 time(s)
 dispatch_protocol_error: type 90 seq 5 [preauth] : 1 time(s)
 pam_sepermit(sshd:auth): Cannot determine the user's name : 1 time(s)
 invalid public DH value: <= 1 [preauth] : 1 time(s)
 Connection reset by 198.98.59.151 port 52432 [preauth] : 1 time(s)
 Unable to negotiate with 10.43.2.140 port 37428: no matching host key type found. Their offer: sk-ecdsa-sha2-nistp256 [preauth] : 1 time(s)
 
 ---------------------- SSHD End ------------------------- 

 
 ###################### Logwatch End ######################### 
:: [ 07:05:11 ] :: [   PASS   ] :: Files /dev/null and logwatch.out should differ 
:: [ 07:05:11 ] :: [   FAIL   ] :: File 'logwatch.out' should not contain 'Unmatched Entries' 


This bug has been copied from bug #1504979 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 1 RHEL Program Management 2023-09-21 09:56:10 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 09:56:33 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Note You need to log in before you can comment on or make changes to this bug.