Bug 41852 - Point-and-print Windows driver upload fails with NT_STATUS_NETWORK_BUSY during rename
Point-and-print Windows driver upload fails with NT_STATUS_NETWORK_BUSY durin...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba
UCS 4.1
Other Linux
: P3 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on: 41849
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-25 21:38 CEST by Arvid Requate
Modified: 2023-03-29 15:19 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.257
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017032721000338, 2017112121000548
Bug group (optional): Troubleshooting
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2016-07-25 21:38:00 CEST
Same situation as Bug #41849  / Ticket#2016072221000163:

Windows printer driver upload failed with this error message:

"Ein Treiber EPSON Universal Print Driver Typ 3 – Benutzermodus, x64 konnte nicht installiert werden. Das Netzwerk ist ausgelastet."


On the print server (Samba/AD DC Master in this case) there are a couple of messages like this in log.smbd:
===============================================================
[2016/07/25 15:46:29.811999,  3, pid=22525] ../source3/smbd/open.c:881(open_file)
  Error opening file x64/E_2VIF0DE.VIF (NT_STATUS_NETWORK_BUSY) (local_flags=2048) (flags=2048)
[2016/07/25 15:46:29.812024,  0, pid=22525] ../source3/printing/nt_printing.c:1039(move_driver_file_to_download_area)
  move_driver_file_to_download_area: Unable to rename [x64/E_2VIF0DE.VIF] to [x64/3/E_2VIF0DE.VIF]: NT_STATUS_NETWORK_BUSY
===============================================================


AFAIK this was even after locally working around the issues of Bug #41849.

Temporarily disabling oplocks fixed the issue:

ucr set samba/oplocks=no; service samba restart


Looking at log.smbd I also see some occurrences of the error for GPO files, so there might be some general oplock issue here. Deactivating kernel oplocks alone didn't fix the issue.
Comment 1 Nico Stöckigt univentionstaff 2017-04-03 11:31:46 CEST
Occurred surprisingly in a customer environment after uploading drivers worked like a charm all the time. Switching off 'samba/oplocks=no' followed by a 'service samba force-reload' was able to working around this issue.
Comment 2 Arvid Requate univentionstaff 2017-04-03 11:46:22 CEST
Comment 1: UCS 4.1-2 errata239  up to UCS 4.1-4 errata408
Comment 3 Arvid Requate univentionstaff 2017-11-28 18:42:37 CET
Maybe related: https://bugzilla.samba.org/show_bug.cgi?id=13121 (fixed upstream in samba 4.6.10).
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:19:12 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
Comment 5 Arvid Requate univentionstaff 2019-05-09 13:56:23 CEST
Note: This seems to be https://bugzilla.samba.org/show_bug.cgi?id=12763 affecting Drivers with PackageArware=TRUE in the .inf file of the driver.

The characteristic error message in log.smbd at debug level 0 is:

[2019/05/08 00:24:46.659573,  0, pid=25265, effective(0, 5000), real(0, 0)] ../../source3/printing/nt_printing.c:1462(move_driver_file_to_download_area)
  move_driver_file_to_download_area: Unable to rename [x64/{236E11A7-F2BF-4F4F-B3C5-9093EAA7866D}/something] to [x64/3/SOMETHING]: NT_STATUS_OBJECT_NAME_NOT_FOUND