Avamar: Avamar Administration GUI events flooded by ERROR Code: 1 Type: System - kernel error - smbd[PID]: read_data: read failure for 4 bytes to client [IP-ADDRESS].
Summary: Avamar Administration GUI events flooded by ERROR Code: 1 Type: System - kernel error - smbd[PID]: read_data: read failure for 4 bytes to client [IP-ADDRESS].
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
The Avamar Administration GUI or output from "mccli events show" lists the following kernel error events:
admin@avamar:~/>: mccli event show --unack |head -10 0,23000,CLI command completed successfully. Date Type Code Category Summary ----------------------- ----- ---- -------- ---------------------------------------------------------------------------------------------------------------------------------------------------- 2018-09-06 10:57:24 UTC ERROR 1 SYSTEM kernel error: Sep 6 10:57:18 avamar smbd[32719]: read_data: read failure for 4 bytes to client 10.11.xx.xx. Error = Connection reset by peer 2018-09-06 10:57:24 UTC ERROR 1 SYSTEM kernel error: Sep 6 10:57:21 avamar smbd[32724]: read_data: read failure for 4 bytes to client 10.11.xx.xx. Error = Connection reset by peer 2018-09-06 10:53:24 UTC ERROR 1 SYSTEM kernel error: Sep 6 10:53:18 avamar smbd[32165]: read_data: read failure for 4 bytes to client 14.15.xx.xx. Error = Connection reset by peer 2018-09-06 10:53:24 UTC ERROR 1 SYSTEM kernel error: Sep 6 10:53:15 avamar smbd[32164]: read_data: read failure for 4 bytes to client 14.15.xx.xx. Error = Connection reset by peer 2018-09-06 07:32:00 UTC ERROR 1 SYSTEM kernel error: Sep 6 07:31:57 avamar smbd[7248]: read_data: read failure for 4 bytes to client 18.19.xx.xx. Error = Connection reset by peer 2018-09-06 07:32:00 UTC ERROR 1 SYSTEM kernel error: Sep 6 07:31:53 avamar smbd[7242]: read_data: read failure for 4 bytes to client 18.19.xx.xx. Error = Connection reset by peer 2018-09-06 00:27:21 UTC ERROR 1 SYSTEM kernel error: Sep 6 00:27:11 avamar smbd[23505]: read_data: read failure for 4 bytes to client 22.23.xx.xx. Error = Connection reset by peer
Cause
The smb (SAMBA) service, which is disabled by default, has been enabled.
Resolution
1 - Check if the smb service is running:
root@avamar:~/#: service smb status
smbd (pid 2260 2256) is running...
nmbd (pid 2261) is running...
2 - If it is running, manually stop it:
root@avamar:~/#: service smb stop
Shutting down SMB services: [ OK ]
Shutting down NMB services: [ OK ]
3 - Ensure the service will not be started during the upcoming reboots, by disabling it for all the O.S. run levels:
root@avamar:~/#: chkconfig --level 2345 smb off
root@avamar:~/#:
4 - Verify that service is now OFF for all O.S. run levels:
root@avamar:~/#: chkconfig --list |grep smb
smb 0:off 1:off 2:off 3:off 4:off 5:off 6:off
5 - Acknowledge all existent events:
admin@avamar:~/>: mccli event ack --all
0,23000,CLI command completed successfully.
Attribute Value
------------ -----
events-acked 81
6 - Allow several hours then check again to make sure the unwanted events are gone:
root@avamar:~/#: mccli event show --unack;date
0,23000,CLI command completed successfully.
ID Date Type Code Category Severity Domain Summary
-- ---- ---- ---- -------- -------- ------ -------
Thu Sep 6 16:08:36 UTC 2018
root@avamar:~/#: service smb status
smbd (pid 2260 2256) is running...
nmbd (pid 2261) is running...
2 - If it is running, manually stop it:
root@avamar:~/#: service smb stop
Shutting down SMB services: [ OK ]
Shutting down NMB services: [ OK ]
3 - Ensure the service will not be started during the upcoming reboots, by disabling it for all the O.S. run levels:
root@avamar:~/#: chkconfig --level 2345 smb off
root@avamar:~/#:
4 - Verify that service is now OFF for all O.S. run levels:
root@avamar:~/#: chkconfig --list |grep smb
smb 0:off 1:off 2:off 3:off 4:off 5:off 6:off
5 - Acknowledge all existent events:
admin@avamar:~/>: mccli event ack --all
0,23000,CLI command completed successfully.
Attribute Value
------------ -----
events-acked 81
6 - Allow several hours then check again to make sure the unwanted events are gone:
root@avamar:~/#: mccli event show --unack;date
0,23000,CLI command completed successfully.
ID Date Type Code Category Severity Domain Summary
-- ---- ---- ---- -------- -------- ------ -------
Thu Sep 6 16:08:36 UTC 2018
Affected Products
Avamar ServerProducts
Avamar ServerArticle Properties
Article Number: 000052375
Article Type: Solution
Last Modified: 30 May 2024
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.