Alex Korobkin
2016-Dec-13 15:48 UTC
[Samba] Semaphore timeout hardcoded at 12 seconds somewhere?
Hi team, I use Samba 4.3.12 as a printserver with ~900 printers, and it takes about 20 seconds for rpcclient enumprinters command to finish. However, sometimes it gets stuck and returns WERR_SEM_TIMEOUT for no apparent reason, and this timeout always takes exactly 12 seconds. I was thinking maybe there is a hardcoded timeout somewhere that is shorter than expected 20 sec time for returning my list of printers? Also, is it reasonable time for Samba to take this long for returning a list of printers? -- -Alex
Jeremy Allison
2016-Dec-13 17:41 UTC
[Samba] Semaphore timeout hardcoded at 12 seconds somewhere?
On Tue, Dec 13, 2016 at 10:48:38AM -0500, Alex Korobkin via samba wrote:> Hi team, > > I use Samba 4.3.12 as a printserver with ~900 printers, and it takes about > 20 seconds for rpcclient enumprinters command to finish. However, sometimes > it gets stuck and returns WERR_SEM_TIMEOUT for no apparent reason, and this > timeout always takes exactly 12 seconds. > > I was thinking maybe there is a hardcoded timeout somewhere that is shorter > than expected 20 sec time for returning my list of printers? > > Also, is it reasonable time for Samba to take this long for returning a > list of printers?That's a strange one. There are only definitions of WERR_SEM_TIMEOUT in the Samba code, no places where I see it returned :-). Can you get me a debug level 10 log from client and server so we can see where the time is going ?
Alex Korobkin
2017-Jun-06 21:16 UTC
[Samba] Semaphore timeout hardcoded at 12 seconds somewhere?
Jeremy helped me off-thread to discover that the issue is on the client side. rpcclient has a 10 sec timeout, which can be easily changed with a command, say, rpcclient localhost -c 'timeout 30000; enumprinters 1' On Tue, Dec 13, 2016 at 12:41 PM, Jeremy Allison <jra at samba.org> wrote:> On Tue, Dec 13, 2016 at 10:48:38AM -0500, Alex Korobkin via samba wrote: > > Hi team, > > > > I use Samba 4.3.12 as a printserver with ~900 printers, and it takes > about > > 20 seconds for rpcclient enumprinters command to finish. However, > sometimes > > it gets stuck and returns WERR_SEM_TIMEOUT for no apparent reason, and > this > > timeout always takes exactly 12 seconds. > > > > I was thinking maybe there is a hardcoded timeout somewhere that is > shorter > > than expected 20 sec time for returning my list of printers? > > > > Also, is it reasonable time for Samba to take this long for returning a > > list of printers? > > That's a strange one. There are only definitions of WERR_SEM_TIMEOUT > in the Samba code, no places where I see it returned :-). > > Can you get me a debug level 10 log from client and server so > we can see where the time is going ? >-- -Alex
Possibly Parallel Threads
- Semaphore timeout hardcoded at 12 seconds somewhere?
- Connection refused - port 445
- "Windows couldn't connect to the printer" 0x00000709 when using server short name
- Problem downloading driver from Samba.
- RSAT Print Management won't show shared printers under the "Printers" section