Profile Details

Toggle Sidebar
Recent updates
  • Thanks again. I will rebuild my server and stick to webconfig as much as possible, certainly for using Samba. Hopefully this problem doesn't come back.

  • Thank you, Nick. Where would we be without you? I only blame myself, but I am not really aware what went wrong. Next to the webconfig I use webmin for things webconfig doesn't handle well like LVM, RAID or iSCSI configs and of course the file manager. Sometimes, while working in webmin, I would get a notification of new sofware which I normally blindly accept. That's probably the cause and, yes, I have probably also used webmin for making Samba changes. While I will not blame anybody besides myself I find it peculiar that this problem can still arise so easily and it is so difficult to deal with. Rebuilding my very simple server wouldn't be difficult. I am just a bit embarrassed this would still be necessary as this seems to have been a common problem for years. But your help is greatly appreciated!

  • Another Samba / slapd problem

    I have a few ClearOS systems, all running ClearOS7, latest update. One system (SAN2) is just a basic back-up system for the entire network. It networks happily with all othe systems using rsync, filezilla, etc. It used to work with Windows systems in the network, as I set it up without an Account Manager system, just a basic filesharing system. Suddenly, my SAN2 system has an Account Manager, and it is offline. I assume it was entered into the system via yum update, as I cannot remember having done that myself. Obviously I cannot use Samba now.
    I have seen the different posts on this forum, so I know it will not be easy to remove slapd. I can rebuild the system from scratch which would be a bit of an embarrasment. Before doing that and before I spend too much time on this common issue, I would be interested to know whether there currently is an easy fix so that I can re-use Samba for simple filesharing. Status of slapd:

  • 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:

    /code
    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: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- 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
    /code

    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)
    man:samba(7)
    man:smb.conf(5)

    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.