Community Forum

Resolved
0 votes
Having hit problems trying to FTP to a clearOS 7 server from a Mac, I installed Windows Networking (Samba) (I believe smb is much better supported on the Mac). I was pleasantly surprised to be able to connect via smb, which was nice.

I then shut the server down to add a 6TB hard disk, just for the hell of it. Rebooted and Samba would not start. Fearing (not based on any logic or knowledge) that the additional disk was creating the problem, I shut down again and removed it. Rebooted and Samba again will not start.

It's always curious when something works and then fails to work after a reboot. Anyone got any ideas on what's going on and how I might attempt to restore my Samba access?
Monday, October 30 2017, 07:31 PM
Share this post:
Responses (32)
  • Accepted Answer

    Tuesday, November 14 2017, 08:54 AM - #Permalink
    Resolved
    0 votes
    Hi Frans

    I'm using an hpe Microserver Gen10, base model with 16 GB RAM.

    I let the clearOS devs access my box and they 'pinned down the issue into some low level library upstream in Openldap' (something about nslcd starting before the network) which means little to me. They got me to create a simple file and change its attributes and bingo, it now runs.

    No idea why it's happened to my box and (apparently) no others but, for the time being, I'm sorted.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 13 2017, 11:14 PM - #Permalink
    Resolved
    0 votes
    Hello Steve,

    What HP hardware are you running on. I run on a proliant microserver Gen 7 and nerver had any problem.
    I moved to a proliant microserver gen8 and had to reinstall and do a restore of my configuration.

    SNB, NMB and WINBIND service did not wanted to start afther i did the restore.
    Looked high and low and found out that it complained about a lib that i could not find while it was installed.
    I reinstalled the lib and the problem was solved.
    it might be that you have a compleet different problem so that why i wonder on what hardware you run.

    Frans
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 08 2017, 06:27 PM - #Permalink
    Resolved
    0 votes
    PM sent
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 08 2017, 11:00 AM - #Permalink
    Resolved
    0 votes
    Well I've submitted the ticket. Let's see what the techies find that we've missed!
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 08 2017, 10:40 AM - #Permalink
    Resolved
    0 votes
    Thanks for you cooperation in this. It is good that it is reproducible so it should be easier to find (fingers crossed). To raise a ticket, go straight to the Clearcenter portal and raise a ticket as a General Enquiry, select Method of Communication = Remote Login and fill in your login credentials, changing the port if necessary. You should not need any subscription for that. Let me know if you have issues.

    Ben is in Canada so won't be in the office for a few hours yet.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 08 2017, 09:35 AM - #Permalink
    Resolved
    0 votes
    Hi Nick. Indeed, I chose the clearOS route precisely because hpe were pushing what a wonderful solution it was. Ironic, eh?

    I have reinstalled and recreated the problem (it is at least reliable in that respect :) ) and opened a port for TCP.

    One question, though: how do I create a general ticket without upgrading?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, November 07 2017, 06:58 PM - #Permalink
    Resolved
    0 votes
    Hi Steve,
    The devs are quite interested in this, especially as you are using HPE hardware. If you are happy to reinstall ClearOS and set up Directory Server, Flexshares, FTP and Windows Networking then reboot and give access to the devs, they will be happy to look around. If you raise a General Enquiry ticket, for the attention of Ben Chambers, he or someone else will have a look. Enter the login credentials where it asks on the ticket. Please make sure you have a strong password and, presumably you need to port forward to the box. You are welcome to change the port, but specify it with the credentials.

    Thanks, Nick
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, November 07 2017, 01:27 PM - #Permalink
    Resolved
    0 votes
    Well, Nick, the plot moistens, I fear :D . I installed Ubuntu server and could ftp and smb my way in and out to my heart's content, rebooting at will, so there doesn't seem to be anything intrinsically wrong with the box.

    I then dug up a 10-year old Toshiba laptop and installed clearOS on it. It worked fine, even after rebooting, so it would seem not to be that I am doing/not doing something dumb.

    Clutching ever more desperately at the most inconsequential of straws, the two differences between my server and something straight out of the box are the SSD I fitted and an additional 8 GB of RAM. I removed the RAM - same problem. I then installed clearOS on a 64 GB USB stick and booted from that - still no cure, so it's not something weird with the SSD.

    What really winds me up is that it works on install but doesn't after reboot. I have now run out of ideas :-(
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 06 2017, 10:45 AM - #Permalink
    Resolved
    0 votes
    I just cannot reproduce :(

    I've installed the latest 7.3 iso in Standalone, No Firewall mode (configured the spare NIC as LAN)
    In the wizard I installed no apps but let it do its update. This seems to give a partial 7.4, but is what you'd have had yesterday.
    From the Marketplace I just installed the Directory Server, Flexshares, FTP and Windows Networking
    Tried setting up a user. This forced me to configure the Directory Server, then let me set up the user which I enabled as an FTP Server User
    Initialised the Windows Networking and changed the Mode to Simple Server
    Tried setting a Flexshare. This forced me to run the Certificate Manager to set up the server certificates
    In the Flexshare app, added one flexshare, enabled for Windows Fileshare and FTP
    Connected to the share with Windows and FTP and used both to place a file there then delete it
    Confirmed the Share permissions were owned by flexshare:allusers
    Rebooted
    Could still read and write to flexshare by Windows Explorer and FTP (WinSCP).
    Permissions were still the same
    Did a "yum update" for a full 7.4
    Everything still works

    I'm stumped.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 06 2017, 08:42 AM - #Permalink
    Resolved
    0 votes
    Even stranger that it is an HPE box. Clearcenter went into partnership with them earlier and now the Gen10 Microserver comes pre-installed with ClearOS if you buy it with a disk, and I believe ClearOS is available by smart provisioning for other servers as well.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 06 2017, 07:55 AM - #Permalink
    Resolved
    0 votes
    You're right, Nick. This is now pure frustration. As I see it there are essentially two possibilities:


    I am doing/not doing something so basic that it is not occurring to either of us; or
    it's a hardware problem


    HP sells thousands of these machines and I don't believe they're all running Windows or RedHat. Trawling the interweb I cannot find any other report of similar problems.

    I think that when I have time I will see if I can get Ubuntu to work in these areas. If it won't, it's probably a hardware issue; if it will, it's probably a clearOS issue.

    Forwards!
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 09:30 PM - #Permalink
    Resolved
    0 votes
    Sometimes these problems are just an intellectual challenge which I enjoy but yours is beginning to get frustrating.

    I've downloaded the latest iso and burned it to SD ready for installation, but I'm not going to do any more on it today. I'm off work for a few days so I may give it another go.

    At the moment Clearcenter are watching LDAP issues which is probably why Dave posted to your thread. There were a number of issues on Friday when Home/Business went from 7.3 -> 7.4 which they want to get to the bottom of. It looks like just a few systems as nothing has been posted at the weekend. Yours is not a 7.3 -> 7.4 issue as you had it on 7.3, but it is perplexing.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 08:48 PM - #Permalink
    Resolved
    0 votes
    Hi Nick. I cannot see what specific iso I have used in my Mac - it just shows http://mirror.clearos.com/clearos/7/iso/x86_64/ClearOS-DVD-x86_64.iso as the origin. I pulled it today.

    But the weird issue is what happens between install and reboot.

    And surely you have other more pressing matters than sorting me out? I hesitate to contemplate the time you have spent addressing my problems. I do appreciate the attention and effort you have expended on my behalf :)

    Steve
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 08:10 PM - #Permalink
    Resolved
    0 votes
    I am also totally puzzled. I've just installed ClearOS7.3, Installed Flexshare, Directory Server, Windows Networking Samba, FTP Server, Certificate Manager and Custom Firewall, initialised the Certificate Manager, Directory Server and Windows networking, set up one user and one flexshare then rebooted. The flexshare is still owned by flexshares:allusers. I then did the 7.4 update and rebooted and the flexshare is still owned by flexshares:allusers. so I have not a clue what is happening to your set up.

    Do you know which ISO are you using. I am using 7.3.0.180516 which is probably a little old. I can try the current one (7.3.0.162627), but, as you know it takes a an hour more so I won't get that done tonight.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 04:44 PM - #Permalink
    Resolved
    0 votes
    Nick/Dave, I am now thoroughly confused ;) . I had a quick look at the file Dave mentioned and it seemed populated, so I bit the bullet, removed my 6TB drive and did a fresh install with a new download on my 250 GB SSD (just as before). Updated all in the install wizard. Installed Flexshare, Directory Server, Windows Networking Samba and FTP Server (the latter just for the hell of it).

    Samba worked fine. I logged on, put a file on the server and deleted it, all from my Mac Finder. I tried to ftp to the server but that would not work. All just like before.

    I then made the fatal mistake of rebooting. This time I purposely did not install the additional 6TB drive, so I was just rebooting exactly the same physical configuration that I had at install. Guess what? Windows Networking will not start. It's not the addition of the further disk that is causing the problem. What could possibly have changed between installation and rebooting to prevent it starting?
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 02:08 PM - #Permalink
    Resolved
    0 votes
    Check and see if your LDAP database has any data in it.

    slapcat -n3

    If not, we need to get your database restored. If so, we need to check to see if your samba objects are all using the correct SIDs. Entries in the sambaSID attribute that begin with a minus sign (-63000, for example) do not have the proper domain SID. Validate your SID on the domain controller is the same for local and domain with:

    net getdomainsid

    Then validate that all of your entries except for the built-in entries use that SID. User accounts, computer accounts, and other types use the SID with the resource ID appended (RID)

    NOTE: DON'T SHARE YOUR SID ON THE FORUMS. There is a reason why it is called a Security ID
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 01:57 PM - #Permalink
    Resolved
    0 votes
    Hi again Nick. I haven't tried the other Directory Servers on the basis that LDAP was the most stable. I haven't set a password for LDAP - it's set for anonymous access. The BaseDN connection shows dc=system,dc=lan.

    What confuses me is that LDAP is running but Samba can't connect to it.

    I will try another installation with a fresh install image.

    Onwards!
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 10:20 AM - #Permalink
    Resolved
    0 votes
    Like you I am completely confused. Did you try either of the other Directory Servers (Samba Directory or AD Connector). I cannot see why Samba is not communicating with LDAP. Did you set an LDAP password in Server > Directory > Directory Server? Also, from there is your Base Domain system.lan and does that tie up with the Base DN further down the screen?

    FWIW, from your other output, "journalctl -xe" showed nothing useful as something else is getting in the way. The output of "mount" showed where your extra disk was mounting. A lot of the info is not relevant there. Your testparm showed you were not using your new disk in your flexhare among other things.

    To be honest, as this looks like a test system, you may want to try a re-installation with your extra disk removed. Then get the Certificate Manager, LDAP/Directory Server and Windows Networking initialised early on.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 05 2017, 08:56 AM - #Permalink
    Resolved
    0 votes
    Hi Nick. Rebooted and cat /etc/redhat - release tells me I'm running ClearOS 7.4.0 (Final).

    Once again your suspicion is proved correct. No difference to Windows Networking starting.

    Firewall is disabled. enp2s0f0 confirmed as ethernet port. "ntlm auth = yes" is in the global section of smb.conf.

    Puzzling, eh? Dump of iptables -nvL follows:

    Chain INPUT (policy ACCEPT 2596 packets, 409K bytes)
    pkts bytes target prot opt in out source destination

    Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
    pkts bytes target prot opt in out source destination
    0 0 ACCEPT all -- pptp+ * 0.0.0.0/0 0.0.0.0/0
    0 0 ACCEPT all -- tun+ * 0.0.0.0/0 0.0.0.0/0
    0 0 ACCEPT all -- * pptp+ 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
    0 0 ACCEPT all -- * tun+ 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED

    Chain OUTPUT (policy ACCEPT 1995 packets, 803K bytes)
    pkts bytes target prot opt in out source destination

    Chain DROP-lan (0 references)
    pkts bytes target prot opt in out source destination
    0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 09:49 PM - #Permalink
    Resolved
    0 votes
    That is the update to 7.4, released for Home, Business and the Community version less than 30 days old on Thursday. Community more than 30 days old was released about 3 weeks ago. Which version are you running? I have a feeling this is not going to fix the issues but let's wait and see,
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 09:21 PM - #Permalink
    Resolved
    0 votes
    Interesting. I ran Software Update and found 320 apps that need updating. The system now tells me "Software update is in progress. Please come back later.", which is exactly what I will do - tomorrow.

    Thanks again for your help. Let's see where this takes us on our Magical Mystery Tour of clearOS!

    Regards

    Steve
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 08:53 PM - #Permalink
    Resolved
    0 votes
    Steve Pospisil wrote:

    Nick Howitt wrote:

    1 Lets get Windows networking going first Works for me
    2 This is normal. You will need the Shell Extension App to make the changes through the webconfig. Understood
    3 They should be able to, but will get minimal access unless set up ad administrators. Understood, but not sure why they can't - not top of the list
    4 I'll try this one first Works for me
    5 Good Agreed
    Totally confused now. If smb is not starting then Windows Networking cannot be working - they are the same thing.

    Looking at your output, there is very little significant difference between yours and mine. Can you confirm that enp2s0f0 is your LAN interface (Webconfig > Network > Settings > IP Settings). One ting I notice is that your system does not seem up to date if you are running ClearOS 7. There should be a parameter "ntlm auth = Yes" in the global section of /etc/samba/smb.conf (which the command testparm reads). Can you please bring your system up to date then reboot it.

    As a sideways thought, have you changed any of the firewall so you are perhaps blocking localhost/127.0.0.1? You can dump the relevant part of it with an "iptables -nvL".
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 07:58 PM - #Permalink
    Resolved
    0 votes
    [quote]Nick Howitt wrote:

    1 Lets get Windows networking going first Works for me
    2 This is normal. You will need the Shell Extension App to make the changes through the webconfig. Understood
    3 They should be able to, but will get minimal access unless set up ad administrators. Understood, but not sure why they can't - not top of the list
    4 I'll try this one first Works for me
    5 Good Agreed
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 06:42 PM - #Permalink
    Resolved
    0 votes
    Hi Nick. What appear (to me) to be relevant error messages.

    /var/log/messages

    Nov 4 17:04:57 server systemd: Starting Samba SMB Daemon...
    Nov 4 17:04:57 server systemd: smb.service: Supervising process 19370 which is not our child. We'll most likely not notice when it exits.
    Nov 4 17:04:57 server nslcd[1105]: [fe3625] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Nov 4 17:04:57 server nslcd[1105]: [fe3625] <passwd="guest"> no available LDAP server found: Can't contact LDAP server
    Nov 4 17:04:57 server nslcd[1105]: [a88ecf] <passwd="GUEST"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
    Nov 4 17:04:57 server systemd: smb.service: main process exited, code=exited, status=255/n/a
    Nov 4 17:04:57 server systemd: Failed to start Samba SMB Daemon.
    Nov 4 17:04:57 server systemd: Unit smb.service entered failed state.
    Nov 4 17:04:57 server systemd: smb.service failed.
    Nov 4 17:04:57 server webconfig: Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for d$
    Nov 4 17:05:01 server systemd: Started Session 107 of user root.

    and

    Nov 4 17:35:01 server systemd: Starting Session 120 of user root.
    Nov 4 17:35:58 server nslcd[1105]: [4a08ec] <group/member="postfix"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Nov 4 17:35:58 server nslcd[1105]: [4a08ec] <group/member="postfix"> no available LDAP server found: Can't contact LDAP server
    Nov 4 17:35:58 server nslcd[1105]: [4a08ec] <group/member="postfix"> no available LDAP server found: Server is unavailable

    /var/log/system - no obviously relevant (to me) error messages, but should I be looking for something specific?

    /var/log/samba/smbd - seems to be empty

    Again, appreciate your help.

    Steve
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 06:30 PM - #Permalink
    Resolved
    0 votes
    This is going to be a big one.

    testparm

    Load smb config files from /etc/samba/smb.conf
    WARNING: The "syslog" option is deprecated
    Processing section "[test]"
    Processing section "[homes]"
    Processing section "[printers]"
    NOTE: Service printers is flagged unavailable.
    Processing section "[print$]"
    NOTE: Service print$ is flagged unavailable.
    Processing section "[netlogon]"
    Processing section "[profiles]"
    Unknown parameter encountered: "force directory security mode"
    Ignoring unknown parameter "force directory security mode"
    NOTE: Service profiles is flagged unavailable.
    Loaded services file OK.
    'winbind separator = +' might cause problems with group membership.

    Server role: ROLE_DOMAIN_PDC

    Press enter to see a dump of your service definitions

    # Global parameters
    [global]
    interfaces = lo enp2s0f0
    netbios name = MYSERVER
    server string = MyServer
    workgroup = CLEARSYSTEM
    domain master = Yes
    preferred master = Yes
    ldap admin dn = cn=manager,ou=Internal,dc=system,dc=lan
    ldap connection timeout = 8
    ldap group suffix = ou=Groups,ou=Accounts
    ldap idmap suffix = ou=Idmap
    ldap machine suffix = ou=Computers,ou=Accounts
    ldap ssl = no
    ldap suffix = dc=system,dc=lan
    ldap user suffix = ou=Users,ou=Accounts
    log file = /var/log/samba/%L-%m
    max log size = 0
    syslog = 0
    add machine script = /usr/sbin/samba-add-machine "%u"
    domain logons = Yes
    logon drive = U:
    logon home = \\%L\%U
    logon path =
    logon script = logon.cmd
    utmp = Yes
    printcap name = /etc/printcap
    server max protocol = NT1
    allow trusted domains = No
    guest account = guest
    passdb backend = ldapsam:ldap://127.0.0.1
    passwd chat = *password:* %n\n *password:* %n\n *successfully.*
    passwd chat timeout = 10
    passwd program = /usr/sbin/userpasswd %u
    security = USER
    unix password sync = Yes
    username map = /etc/samba/smbusers
    template homedir = /home/%U
    template shell = /sbin/nologin
    winbind enum groups = Yes
    winbind enum users = Yes
    winbind expand groups = 1
    winbind offline logon = Yes
    winbind separator = +
    winbind use default domain = Yes
    wins support = Yes
    idmap config * : ldap_user_dn = cn=manager,ou=Internal,dc=system,dc=lan
    idmap config * : ldap_base_dn = ou=Idmap,dc=system,dc=lan
    idmap config * : ldap_url = ldap://127.0.0.1
    idmap config * : range = 20000000-29999999
    idmap config * : backend = ldap
    include = /etc/samba/flexshare.conf


    [test]
    comment = Just to test Flexshare
    path = /var/flexshare/shares/test
    veto files = /.flexshare*/
    create mask = 0664
    directory mask = 0775
    read only = No
    valid users = @%D\theloft @theloft


    [homes]
    comment = Home Directories
    path = /home/%U
    browseable = No
    read only = No
    valid users = %D\%S %D+%S %S


    [printers]
    comment = Print Spool
    path = /var/spool/samba
    browseable = No
    available = No
    cups options = raw
    printable = Yes
    use client driver = Yes
    read only = No


    [print$]
    comment = Printer Drivers
    path = /var/samba/drivers
    browseable = No
    available = No
    read only = No


    [netlogon]
    comment = Network Logon Service
    path = /var/samba/netlogon
    browseable = No
    locking = No
    read only = No


    [profiles]
    comment = Profile Share
    path = /var/samba/profiles
    browseable = No
    available = No
    profile acls = Yes
    force directory mode = 02775
    force group = domain_users
    read only = No

    mount

    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    devtmpfs on /dev type devtmpfs (rw,nosuid,size=7927436k,nr_inodes=1981859,mode=755)
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
    tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
    pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
    efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
    cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
    cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
    cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
    cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
    cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
    cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
    cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
    cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
    cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
    configfs on /sys/kernel/config type configfs (rw,relatime)
    /dev/mapper/clearos-root on / type xfs (rw,relatime,attr2,inode64,noquota)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    mqueue on /dev/mqueue type mqueue (rw,relatime)
    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
    /dev/sda2 on /boot type xfs (rw,relatime,attr2,inode64,noquota)
    /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
    /dev/sdb1 on /media/newhd1 type ext4 (rw,relatime,data=ordered)
    tmpfs on /run/user/992 type tmpfs (rw,nosuid,nodev,relatime,size=1587876k,mode=700,uid=992,gid=990)
    tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=1587876k,mode=700)

    systemctl status smb.service

    ● smb.service - Samba SMB Daemon
    Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Sat 2017-11-04 17:04:57 GMT; 1h 20min ago
    Process: 19370 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=255)
    Main PID: 19370 (code=exited, status=255)
    Status: "Starting process..."

    Nov 04 17:04:57 server.prague.com systemd[1]: Starting Samba SMB Daemon...
    Nov 04 17:04:57 server.prague.com systemd[1]: smb.service: Supervising process 19370 which is not our child. We'll most likely not notice when it exits.
    Nov 04 17:04:57 server.prague.com systemd[1]: smb.service: main process exited, code=exited, status=255/n/a
    Nov 04 17:04:57 server.prague.com systemd[1]: Failed to start Samba SMB Daemon.
    Nov 04 17:04:57 server.prague.com systemd[1]: Unit smb.service entered failed state.
    Nov 04 17:04:57 server.prague.com systemd[1]: smb.service failed.

    journalctl -xe

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-138.scope has begun starting up.
    Nov 04 18:20:01 server.prague.com systemd[1]: Started Session 139 of user root.
    -- Subject: Unit session-139.scope has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-139.scope has finished starting up.
    --
    -- The start-up result is done.
    Nov 04 18:20:01 server.prague.com systemd[1]: Starting Session 139 of user root.
    -- Subject: Unit session-139.scope has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-139.scope has begun starting up.
    Nov 04 18:20:01 server.prague.com CROND[2547]: (root) CMD (/usr/sbin/events-notification -i > /dev/null 2>&1)
    Nov 04 18:20:01 server.prague.com CROND[2548]: (root) CMD (LANG=en_US /usr/clearos/apps/base/deploy/servicewatch >/dev/null 2>&1)
    Nov 04 18:25:01 server.prague.com systemd[1]: Started Session 140 of user root.
    -- Subject: Unit session-140.scope has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-140.scope has finished starting up.
    --
    -- The start-up result is done.
    Nov 04 18:25:01 server.prague.com systemd[1]: Starting Session 140 of user root.
    -- Subject: Unit session-140.scope has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-140.scope has begun starting up.
    Nov 04 18:25:01 server.prague.com systemd[1]: Started Session 141 of user root.
    -- Subject: Unit session-141.scope has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-141.scope has finished starting up.
    --
    -- The start-up result is done.
    Nov 04 18:25:01 server.prague.com systemd[1]: Starting Session 141 of user root.
    -- Subject: Unit session-141.scope has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-141.scope has begun starting up.
    Nov 04 18:25:01 server.prague.com CROND[2785]: (root) CMD (/usr/sbin/events-notification -i > /dev/null 2>&1)
    Nov 04 18:25:01 server.prague.com CROND[2786]: (root) CMD (LANG=en_US /usr/clearos/apps/base/deploy/servicewatch >/dev/null 2>&1)
    lines 2986-3034/3034 (END)

    I have to confess that this is gobbledegook to me!
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 05:39 PM - #Permalink
    Resolved
    0 votes
    Steve Pospisil wrote:
    Nick, is this your job, or just your passion?
    It became a passion and has developed from there.....

    1 Lets get Windows networking going first
    2 This is normal. You will need the Shell Extension App to make the changes through the webconfig.
    3 They should be able to, but will get minimal access unless set up ad administrators.
    4 I'll try this one first
    5 Good

    What is the output of "testparm" and "mount"?
    When you start smb manually, can you try "systemctl status smb.service" and "journalctl -xe" for more details. Can you also look in /var/log/messages, /var/log/system and /var/log/samba/smbd for any error messages?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 05:06 PM - #Permalink
    Resolved
    0 votes
    Nick, you're confused? At least you know what you're talking about :D - I'm flying by the seat of my pants.

    I fear that I have multiple issues (that's why I have posted separate questions) but I suspect they might be related. To summarise my issues:

    1 Cannot ftp to server (either as root or user)
    2 Users other than root cannot ssh to server (someone has suggested some solutions which I have yet to try)
    3 Users other than root cannot log in to server (I have not posted this yet, because I think the ftp and ssh issues might be related)
    4 Samba will not start (although it did once, only change was to add hard disk, since removed but did not solve, hard disk now mounted but still Samba will not start)
    5 Could not edit or delete Flexshare, but problem since resolved with no action on my part, so flagged as resolved)

    Output you asked for:

    netstat -peanut | grep LISTEN.*slapd

    tcp 0 0 127.0.0.1:389 0.0.0.0:* LISTEN 0 23795 1966/slapd

    grep ^BIND /etc/sysconfig/slapd

    BIND_POLICY=localhost

    As for starting Samba manually:

    systemctl start smb.service

    Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details.

    systemctl start nmb.service

    No apparent effect

    Nick, is this your job, or just your passion?

    Regards

    Steve
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 04:37 PM - #Permalink
    Resolved
    0 votes
    I am not sure where we are now with parallel threads. You can now edit your flexshares (from the other thread). Is Windows Networking running and working? If not, can you try starting it from the command line with a:
    systemctl start smb.service
    systemctl start nmb.service


    Also, what is the output of:
    netstat -peanut | grep LISTEN.*slapd
    grep ^BIND /etc/sysconfig/slapd
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 04 2017, 02:40 PM - #Permalink
    Resolved
    0 votes
    LDAP is running:

    slapd.service - OpenLDAP Server Daemon
    Loaded: loaded (/usr/lib/systemd/system/slapd.service; enabled; vendor preset: disabled)
    Active: active (running) since Sat 2017-11-04 12:55:09 GMT; 1min 13s ago

    So I'm not sure why I'm getting the message:

    Nov 4 13:17:34 server nslcd[1105]: [e4ccaf] <passwd(all)> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Nov 4 13:17:34 server nslcd[1105]: [e4ccaf] <passwd(all)> no available LDAP server found: Can't contact LDAP server

    I'll trawl through the LDAP issues and see if I can find something there, but it seems to me (I'm no expert) that they are about LDAP not starting rather than not being contactable. I may well be wrong.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 03 2017, 10:18 PM - #Permalink
    Resolved
    0 votes
    Can you please check that LDAP is running with a "service slpad status" or "systemctl status slapd.service"? You may have hit this LDAP issue some people are getting with the recent upgrade. If it is not running, please try staring it with a "service slpad restart" or "systemctl restart slapd.service". If it won't start, please raise a ticket or try the fixes Dave has posted in some of the current LDAP threads.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 03 2017, 09:14 PM - #Permalink
    Resolved
    0 votes
    Nick, I am back from work and have mounted the new hard disk at media/newhd and still no luck with Samba - it just won't start. I'm not sure how relevant it is but the following is in /var/log/messages:

    Oct 30 21:29:34 server webconfig: Redirecting to /bin/systemctl start smb.service
    Oct 30 21:29:34 server systemd: Starting Samba SMB Daemon...
    Oct 30 21:29:34 server systemd: smb.service: Supervising process 26874 which is not our child. We'll most likely not notice when it exits.
    Oct 30 21:29:34 server nslcd[1080]: [0d8dbe] <passwd="guest"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
    Oct 30 21:29:34 server nslcd[1080]: [0d8dbe] <passwd="guest"> no available LDAP server found: Can't contact LDAP server
    Oct 30 21:29:34 server nslcd[1080]: [80ec70] <passwd="GUEST"> no available LDAP server found: Server is unavailable: Resource temporarily unavailable
    Oct 30 21:29:34 server systemd: smb.service: main process exited, code=exited, status=255/n/a
    Oct 30 21:29:34 server systemd: Failed to start Samba SMB Daemon.
    Oct 30 21:29:34 server systemd: Unit smb.service entered failed state.
    Oct 30 21:29:34 server webconfig: Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for d$
    Oct 30 21:29:34 server systemd: smb.service failed.

    Appreciate any guidance you can share.

    Steve
    The reply is currently minimized Show
  • Accepted Answer

    Monday, October 30 2017, 09:12 PM - #Permalink
    Resolved
    0 votes
    When you added your disk, did you use it by manually mounting it? Did you use flexshares to make your shares? Typically to start hunting errors you'd look at /var/log/messages and /var/log/system, but samba has stacks of logs in /var/log/samba.

    If you configured any shares to use your new disk, flexshares are configured in /etc/samba/flexshare.conf. You could try removing the share definition (back it up first).

    Alternatively, if you manually mounted your disk first time round, you could try remounting it the same way and to the same place. To mount it permanently, you need to edit /etc/fstab and it is bettter to use UUID's than device names such as /dev/sdb1 - check out the "blkid" command
    The reply is currently minimized Show
Your Reply