• [6.12.0-rc4.1]winbindd and network loss

    mjorud

    By mjorud

      • Minor

    Not sure if this is related to the RC, but as I'm running RC...

     

    I was watching a movie using Plex Docker and all of a sudden the movie stopped. The Plex container and also the unraid webgui was not accessable. This has happened once before but I did not investigate it.

     

    Excerpt from the syslog: 

    May  1 20:41:33 nansen emhttpd: read SMART /dev/sdf
May  1 20:45:28 nansen winbindd[6714]: [2023/05/01 20:45:28.136962,  0] ../../source3/winbindd/winbindd.c:821(winbind_client_processed)
May  1 20:45:28 nansen winbindd[6714]:   winbind_client_processed: request took 128.989669 seconds
May  1 20:45:28 nansen winbindd[6714]:   [struct process_request_state] ../../source3/winbindd/winbindd.c:437 [2023/05/01 20:43:19.070099] ../../source3/winbindd/winbindd.c:618 [2023/05/01 20:45:28.059768] [128.989669] -> TEVENT_REQ_DONE (2 0))
May  1 20:45:28 nansen winbindd[6714]:    [struct resp_write_state] ../../nsswitch/wb_reqtrans.c:307 [2023/05/01 20:45:27.496398] ../../nsswitch/wb_reqtrans.c:344 [2023/05/01 20:45:28.059766] [0.563368] -> TEVENT_REQ_DONE (2 0))
May  1 20:45:28 nansen winbindd[6714]:     [struct writev_state] ../../lib/async_req/async_sock.c:267 [2023/05/01 20:45:27.496399] ../../lib/async_req/async_sock.c:373 [2023/05/01 20:45:27.509262] [0.012863] -> TEVENT_REQ_DONE (2 0))
May  1 21:15:33 nansen emhttpd: spinning down /dev/sdh
May  1 21:15:33 nansen emhttpd: spinning down /dev/sdd

     

    I think it took approx. 2 minutes before the server came online again.

    Tried to google a bit but came up short. Any idea what's happening?

    Thank you in advance.

    nansen-diagnostics-20230501-2141.zip

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    OneMeanRabbit

    same issue, and it still exists even after restoring 6.11 backup.  I SEE the shares from windows, but nothing will allow me to access it.  NFS is also down.

      

    2023-05-12	12:36:48	Error	tower	daemon	winbindd	initialize_winbindd_cache: clearing cache and re-creating with version number 2
2023-05-12	12:36:48	Error	tower	daemon	winbindd	[2023/05/12 12:36:48.977247, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache)
2023-05-12	12:36:48	Error	tower	daemon	winbindd	Copyright Andrew Tridgell and the Samba Team 1992-2022
2023-05-12	12:36:48	Error	tower	daemon	winbindd	winbindd version 4.17.3 started.
2023-05-12	12:36:48	Error	tower	daemon	winbindd	[2023/05/12 12:36:48.973483, 0] ../../source3/winbindd/winbindd.c:1440(main)
2023-05-12	12:36:48	Notice	tower	user	root	/usr/sbin/winbindd -D
2023-05-12	12:36:48	Error	tower	daemon	smbd	Copyright Andrew Tridgell and the Samba Team 1992-2022
2023-05-12	12:36:48	Error	tower	daemon	smbd	smbd version 4.17.3 started.
2023-05-12	12:36:48	Error	tower	daemon	smbd	[2023/05/12 12:36:48.956342, 0] ../../source3/smbd/server.c:1741(main)
2023-05-12	12:36:48	Notice	tower	user	root	Starting Samba: /usr/sbin/smbd -D

     

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.