Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Any smbclient command is not logging to the log.smbclient file. The command is issued with the "-l" flag with a directory location set to "/var/log/smb"
He is running:
smbclient -l /var/log/smb //<REMOTE SERVER>/log_share -A /usr/local/bin/.smbclient -c "prompt; lcd /home/drs/log; cd <REMOTE DIRECTORY>\\\Logs\SM; put <LOCAL FILENAME> drs.status; exit;"
But no logs are being generated "for a simple file transfer to a Windows server". According to the customer.
Version-Release number of selected component (if applicable):
samba-common-tools-4.9.1-10.el7_7.x86_64
samba-libs-4.9.1-10.el7_7.x86_64
samba-common-4.9.1-10.el7_7.noarch
samba-client-4.9.1-10.el7_7.x86_64
samba-client-libs-4.9.1-10.el7_7.x86_64
samba-common-libs-4.9.1-10.el7_7.x86_64
How reproducible:
always
Steps to Reproduce:
smbclient -l /var/log/smb //<REMOTE SERVER>/log_share -A /usr/local/bin/.smbclient -c "prompt; lcd /home/drs/log; cd <REMOTE DIRECTORY>\\\Logs\SM; put <LOCAL FILENAME> drs.status; exit;"
But no logs are being generated "for a simple file transfer to a Windows server". According to the customer.
Actual results:
He is expecting to see the same as what he sees in RHEL 6:
As I have previously stated, the SAME command on a RHEL 6 server logs the following in /var/log/smb/log.smbclient :
(executed on server "CA1-V" running RHEL 6.10)
[2020/03/10 05:00:03, 0] libsmb/clidfs.c:234(do_connect)
Domain=[CLS-V] OS=[Windows Server 2008 R2 Enterprise 7601 Service Pack 1] Server=[Windows Server 2008 R2 Enterprise 6.1]
[2020/03/10 05:00:03, 1] client/client.c:1883(do_put)
putting file DRSsend_0_20200310041653.log as \CA1\Logs\SM\drs.status (1.2 kb/s) (average 1.2 kb/s)
Expected results:
no output
Additional info:
costumer asking for the result of any logs in rhel 7 for sambaclient by doing a file transfer to another server.
Comment 15Andreas Schneider
2020-04-06 15:59:46 UTC
Yes, write a test for it. You don't have to create a new share as I did, just use the 'tmp' share to connect to and e.g. call 'ls; quit'.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: samba security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:3981