Profile Details

Toggle Sidebar
Recent updates
  • That makes sense.
    I now need to recollect some special installation requirements for non-ClearOS apps that I have and then I will rebuild my system.
    But first remove app-samba. The slow disk-IO turned out to be a harddisk flaw though, so nothing related to winbind.
    Thanks again.

  • Thank you very much Nick, for the excellent explanations and for all the work you're doing for all of us.
    Trying to be helpful, here are my 2 cents:

    yum reinstall app-samba
    systemctl restart winbind.service
    journalctl -xe
    .. systemd[1]: Unit winbind.service entered failed state.
    .. systemd[1]: winbind.service failed.
    .. servicewatch[22102]: restarting winbind
    .. polkitd[919]: Registered Authentication Agent for unix-process:24734:8819234 (system bus name :1.18811 [/usr/bin/pkttyagent --notify-fd 5 --fallback],
    .. systemd[1]: winbind.service: main process exited, code=exited, status=1/FAILURE
    .. systemd[1]: Failed to start Samba Winbind Daemon.
    -- Subject: Unit winbind.service has failed
    -- Defined-By: systemd
    -- Support:
    -- Unit winbind.service has failed.
    -- The result is failed.
    .. systemd[1]: Unit winbind.service entered failed state.
    .. systemd[1]: winbind.service failed.
    .. polkitd[919]: Unregistered Authentication Agent for unix-process:24734:8819234 (system bus name :1.18811, object path /org/freedesktop/PolicyKit1/Authe

    Hope this helps

  • Winbind automatically restarting every 5 mins

    Today I noticed a sudden slowness of disk-IO on my ClearOS7 server. Looking at the logs there has been a constant repetition of 2 commands every (exactly) 5 mins for the last 8 hours and counting :
    servicewatch: sanity checking winbind , followed by
    servicewatch: restarting winbind after 30 secs.
    The system was not actively used when this started.

    This system was originally set up with Samba Domain, which I had removed 2 weeks ago, trying to replace it by Samba. That substitution having failed I knew I had to rebuild my server from scratch but had been too busy doing that while I could do without Samba. The system has worked fine and not been updated during the last 2 weeks. This problem started quite suddenly.

    I'm out of clues as to what this is all about. I will rebuild my server but this is just nagging me.

  • Thanks again, but no success.
    There is a connected NIC, I can webconfig and FTP to the sytem. Indeed, there seems to be no way back once Samba Directory has been installed (and removed). So the only way is re-installing ClearOS which I already intended doing. I think it would be very helpful if the Samba initilizing process would give a clue as to why it's not processing, instead of sitting idle forever.

  • Nick,

    I'm ready for re-installing ClearOS but I would really like to understand what's happening. Maybe you could shed some light.

    This is what I've done:
    - removed Samba Directory after a Win10 upgrade made it inoperable
    - installed OpenLDAP and Samba
    - tried to configure Samba but it gets stuck in a loop (Connecting ....)
    - checked status of slapd and smb

    slapd seems OK: green dot. Status returns 2 messages that seem OK to me:
    Configuration directory '/etc/openldap/slapd.d' does not exist.
    Warning: Usage of a configuration file is obsolete!

    Running /bin/systemctl status smb.service
    ● smb.service - Samba SMB Daemon [dot is not green]
    Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: disabled)
    Active: inactive (dead)
    Docs: man:smbd(8)

    I have read some of your other posts indicating that the problem why Samba cannot initialize might be with the Directory service. As my slapd status seems OK there seems to be some remainer of Samba Directory causing the blocking. Re-installing the system would probably help. Or am I overlooking an obvious issue? (Wouldn't be for the first time :-))

    Kind regards, Roel

  • Yes, Samba Directory of course, sorry for that. I installed it a few years ago by co-incidence. Didn't need it at all but it worked anyway, until now.
    SMB vs 1.0 has been removed from my systems long ago. Config backups would bring me back to Samba Directory, that's not an option as I don't use AD at all.
    I have read the thorough HowTo on AD and I'm compelled to using it if I can find a good reason for it. My ClearOS systems have all been modified away from the original gateway functions (Clark, 2005) as those functions are all taken over by my ISP's modem/routers. ClearOS for me now is just Linux.
    My current problem is only the non-initializing Samba. I think it may be caused by an unsuccessful removal of Samba Directory. That was impossible to do via webconfig so I used yum remove app-samba-directory-core which ran just fine. But some reminiscence of Samba Directory seems to block the new Samba from initializing.
    I agree very much to the remarks about SMB and I could add some bad experiences of my own, but this is not about SMB. It does help solidifying my trust in ClearOS, though.
    Thanks for the replies. I think a clean reset will be the quickest way to solve the problem.

  • SMB connection disappeared after upgrading Win10 to 1903

    I am running a private network featuring a workgroup with some Windows computers and some Linux Computers, all of them ClearOS7 in Standalone Mode. The network is only used for simple file and printer sharing and it has run satisfactory for many years,
    Recently my Windowes systems were upgraded to Win10 build 1903. Now the Windows computers can still communicate with each other and with all ClearOS systems but one. The problematic system is the only system running not plain Samba but Samba Domain.
    I had expected to easily justify the problem by removing app-samba-domain-core and install samba. Not so. I can't even initialize Samba as it's stuck in a loop.
    Obviously the Windows computers cannot see this computer in File Explorer, while the other ClearOS systems are visible as normal. There was no change to the ClearOS system prior to removing Samba Domain.
    A complete re-install of the system wouldn't be too problematic but if I can avoid that by obtaining some good advice I would appreciate it.

  • That makes more sense expaining my problems. I had not expected to suspect the NIC driver. Excellent analysis!

  • Roel  van der Heide
    Roel van der Heide likes the reply for the discussion, Re: DNS problems after changing ISP

    You have a NIC with a known issue. The RTL8111/8168/8411 NIC automatically uses the built-in r8169 but it is not a good match and can cause a number of seemingly unrelated issues. Can I suggest to update to the r8168 driver? You'll need to do:You'll get two drivers rpm's. Install them both then reboot to make the driver take effect.

  • It seems like the problem has been solved.
    I decided to not only switch off the router and the client machines, but also disconnect the Ethernet cables. That seems to have worked.
    My analysis is, that powering off a client while keeping the network cable in place may leave enough current from the router network card to keep the memory of the client card active. If you subsequently power off the router, it will preserve the latest config info from the client card's memory. Thus, after restarting the router it will use the old memory.
    I don't know whether this makes enough sense to explain my problem, but the problem seems to be over now. Thanks again for the help. -- Roel