Good information!

I think a Windows domain controller in home environment is a bit overkill, but on the other hand it looks fun to play a bit with it.

If you really want to use domains and feel ambitious, there is a howto here to use ClearOS as a fully fledged Active Directory Domain Controller, but you will need a Business version of ClearOS or you will have to purchase the AD connector. AD runs in a docker instance in ClearOS and then you join ClearOS to the docker AD DC. Potentially it will be the future for domains in ClearOS8

ClearOS can act as an old-style NT4 domain server which has some benefits, including a single signon to the PC, Network Drives, e-mail and so on. You can also use logon scripts, but I don't use domains - we don't even sign on to the PC's at home.

Nick Howitt wrote:

Typo. dome -> some

Clear.

In PDC mode there is no requirement to join a domain.

..because ClearOS server acts as a domain server?

Typo. dome -> some

It looks like it for Homes but that is the only difference. In PDC mode there is no requirement to join a domain.

Nick Howitt wrote:

You should be able to change to Simple Server mode, but, to be honest, as far as Samba is concerned, both are PDC mode. I have a feeling the the webconfig just hides dome options. In smb.conf the only difference

I tried a few times but I can't change the mode.

What do you mean with "dome options"?

I see is that in the [homes] section, "available" = "Yes" on PDC mode and "No" in Simple Server mode.

That means the home directory is only available in PDC mode?

You should be able to change to Simple Server mode, but, to be honest, as far as Samba is concerned, both are PDC mode. I have a feeling the the webconfig just hides dome options. In smb.conf the only difference I see is that in the [homes] section, "available" = "Yes" on PDC mode and "No" in Simple Server mode.

I gave up on this install.

I did a re-install today! I still have to try the samba part.


Update:

Installed "Windows Networking (Samba) and "Flexshares". It's working fine now so there was something wrong with my previous install.

One thing I notice I can't change "Windows Networking" mode. It's set to "Primary Domain Controller / PDC". Is this a default setting?

When setting up the bind mounts, I wonder if you did not set the folder permissions correctly. Are you able to check? Which folders have you moved with the storage manager? A very nice command to check is "findmnt" which looks good in a larger console window. Can you also check here that the folders you think you moved are actually mounted correctly.

When I remove "/etc/clearos/webconfig.debug" the webconfig is accessable. So I can login again!

When I add the "webconfig.debug" file to "etc/clearos" I can't access the webconfig and it show this message:

on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139 Warning: error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in 

Not sue if this is by design....

I did installed the system yesterday. So it is a fresh install. I did add a RAID 6 array so I followed the storage manager guide. The storage manager guide moves some directories to the "/store" location including the system database. Not sure if this has anything to do with it..?

Storage Manager Technical Guide

I suspect you other problem may be caused by the edits Dave suggested. Can you undo them/it?

I never did any changes to files what Dave suggested because I couldn't find the file.

Can you try "touch /var/log/webconfig/debug.log" just to initialise the log file?

the file debug.log is already there. The last few rows:

Dec 31 11:25:01 UTC 2018: 0.1180: profile: debug: clearos\apps\base\File::get_contents (208):

Dec 31 11:25:01 UTC 2018: 0.1181: profile: debug: clearos\apps\base\File::get_contents_as_array (224):

Dec 31 11:25:01 UTC 2018: 0.1181: profile: debug: clearos\apps\base\File::get_size (423):

Dec 31 11:25:01 UTC 2018: 0.1182: profile: debug: clearos\apps\base\File::exists (392):

Dec 31 11:25:01 UTC 2018: 0.1182: profile: debug: clearos\apps\base\Shell::__construct (105):

Dec 31 11:25:01 UTC 2018: 0.1183: profile: debug: clearos\apps\base\Shell::execute (132): /bin/ls '/var/run/webconfig/network2db.pid'

Dec 31 11:25:01 UTC 2018: 0.1291: profile: debug: clearos\apps\base\File::_get_system_max_bytes (1599):

Dec 31 11:25:01 UTC 2018: 0.1292: profile: debug: clearos\apps\base\File::exists (392):

Dec 31 11:25:01 UTC 2018: 0.1293: profile: debug: clearos\apps\base\Shell::__construct (105):

Dec 31 11:25:01 UTC 2018: 0.1293: profile: debug: clearos\apps\base\Shell::execute (132): /bin/ls '/var/run/webconfig/network2db.pid'

Dec 31 11:25:01 UTC 2018: 0.1405: profile: debug: clearos\apps\base\File::replace (837):

Dec 31 11:25:01 UTC 2018: 0.1405: profile: debug: clearos\apps\base\File::_check_volume_for_space (1624):

Dec 31 11:25:01 UTC 2018: 0.1406: profile: debug: clearos\apps\base\File::exists (392):

Dec 31 11:25:01 UTC 2018: 0.1406: profile: debug: clearos\apps\base\Shell::__construct (105):

Dec 31 11:25:01 UTC 2018: 0.1407: profile: debug: clearos\apps\base\Shell::execute (132): /bin/ls '/var/run/webconfig/network2db.pid'

Dec 31 11:25:01 UTC 2018: 0.1532: profile: debug: clearos\apps\base\Shell::__construct (105):

Dec 31 11:25:01 UTC 2018: 0.1533: profile: debug: clearos\apps\base\Shell::execute (132): /usr/sbin/app-rename '/var/clearos/framework/tmp/network2db.pidGOM0HK' '/var/run/webconfig/network2db.pid'

Dec 31 11:25:01 UTC 2018: 0.1640: profile: debug: clearos\apps\network_report\Network_Report::insert_data (147):

Dec 31 11:25:01 UTC 2018: 0.1641: profile: debug: clearos\apps\reports_database\Database_Report::_initialize_tables (262):

Dec 31 11:25:01 UTC 2018: 0.1641: profile: debug: clearos\apps\reports_database\Database_Report::_get_db_handle (227):

Dec 31 11:25:01 UTC 2018: 0.1642: profile: debug: clearos\apps\base\Configuration_File::__construct (121):

Dec 31 11:25:01 UTC 2018: 0.1642: profile: debug: clearos\apps\base\Configuration_File::load (160):

Dec 31 11:25:01 UTC 2018: 0.1643: profile: debug: clearos\apps\base\File::__construct (176):

Dec 31 11:25:01 UTC 2018: 0.1643: profile: debug: clearos\apps\base\File::get_contents_as_array (224):

Dec 31 11:25:01 UTC 2018: 0.1643: profile: debug: clearos\apps\base\File::get_size (423):

Dec 31 11:25:01 UTC 2018: 0.1644: profile: debug: clearos\apps\base\File::exists (392):

Dec 31 11:25:01 UTC 2018: 0.1644: profile: debug: clearos\apps\base\File::_get_system_max_bytes (1599):

Dec 31 11:25:01 UTC 2018: 0.1644: profile: debug: clearos\apps\base\File::exists (392):

Dec 31 11:25:01 UTC 2018: 0.1659: exception: error: /usr/clearos/apps/reports_database/libraries/Database_Report.php (248): SQLSTATE[28000] [1045] Access denied for user 'reports'@'localhost' (using password: YES)

Dec 31 11:25:01 UTC 2018: exception: debug backtrace: /usr/clearos/apps/reports_database/libraries/Database_Report.php (268): _get_db_handle

Dec 31 11:25:01 UTC 2018: exception: debug backtrace: /usr/clearos/apps/network_report/libraries/Network_Report.php (152): _initialize_tables

Dec 31 11:25:01 UTC 2018: exception: debug backtrace: /usr/sbin/network2db (51): insert_data

Dec 31 11:25:01 UTC 2018: 0.1660: profile: debug: clearos\apps\base\Script::unlock (174):

Dec 31 11:25:01 UTC 2018: 0.1661: profile: debug: clearos\apps\base\File::__construct (176):

Dec 31 11:25:01 UTC 2018: 0.1661: profile: debug: clearos\apps\base\File::exists (392):

Dec 31 11:25:01 UTC 2018: 0.1661: profile: debug: clearos\apps\base\Shell::__construct (105):

Dec 31 11:25:01 UTC 2018: 0.1662: profile: debug: clearos\apps\base\Shell::execute (132): /bin/ls '/var/run/webconfig/network2db.pid'

Dec 31 11:25:01 UTC 2018: 0.1777: profile: debug: clearos\apps\base\File::delete (724):

Dec 31 11:25:01 UTC 2018: 0.1778: profile: debug: clearos\apps\base\File::exists (392):

Dec 31 11:25:01 UTC 2018: 0.1778: profile: debug: clearos\apps\base\Shell::__construct (105):

Dec 31 11:25:01 UTC 2018: 0.1779: profile: debug: clearos\apps\base\Shell::execute (132): /bin/ls '/var/run/webconfig/network2db.pid'

Dec 31 11:25:01 UTC 2018: 0.1892: profile: debug: clearos\apps\base\Shell::__construct (105):

Dec 31 11:25:01 UTC 2018: 0.1893: profile: debug: clearos\apps\base\Shell::execute (132): /bin/rm '/var/run/webconfig/network2db.pid'

Posts are crossing. Can you try "touch /var/log/webconfig/debug.log" just to initialise the log file?

Marcel van van Leeuwen wrote:

What do you mean with "It will lok in something like /var/log/webconfig."

Typo. should have read "log" but I could not remember the file name. From you next post, it looks like /var/log/webconfig/debug.log.

I suspect you other problem may be caused by the edits Dave suggested. Can you undo them/it?

When I check /var/log/webconfig/error.log. I see this error. The ip address is of my pc...

\

[Mon Dec 31 12:05:05.474151 2018] [:error] [pid 1825] [client 192.168.1.102:63235] PHP Warning:  error_log(/var/log/webconfig/debug.log): failed to open stream: Permission denied in /usr/clearos/framework/shared/libraries/Logger.php on line 139

This is a code snippet of Logger.php including line 139

   // Log messages to custom log file (if set) and standard out on

            if (ini_get('error_log')) {

                // date_default_timezone_set('EST');

                $timestamp = date('M j G:i:s T Y');

------->     error_log("{$timestamp}: $logline\n", 3, ini_get('error_log'));   <------ line 139 ---

                // only backtrace error exceptions

                if ($errno === Error::CODE_ERROR) {

                    foreach ($error->get_trace() as $traceinfo) {

                        if (isset($traceinfo['file'])) {

                            // Backtrace log format

                            $logline = sprintf(

                                "$typestring: debug backtrace: %s (%d): %s",

                                $traceinfo['file'],

                                $traceinfo['line'],

                                $traceinfo['function']

                            );

                            error_log("{$timestamp}: $logline\n", 3, ini_get('error_log'));

                        }

When I now try to login in the webconfig I see this in my browser.

What do you mean with "It will lok in something like /var/log/webconfig."

[root@discovery webconfig]# testparm -s

Load smb config files from /etc/samba/smb.conf

Processing section "[movies]"

Processing section "[homes]"

Processing section "[printers]"

NOTE: Service printers is flagged unavailable.

Processing section "[print$]"

NOTE: Service print$ is flagged unavailable.

Processing section "[netlogon]"

NOTE: Service netlogon is flagged unavailable.

Processing section "[profiles]"

WARNING: The "profile acls" option is deprecated

NOTE: Service profiles is flagged unavailable.

Loaded services file OK.

'winbind separator = +' might cause problems with group membership.



Server role: ROLE_DOMAIN_PDC



# Global parameters

[global]

        add machine script = /usr/sbin/samba-add-machine "%u"

        domain logons = Yes

        domain master = Yes

        guest account = guest

        interfaces = lo eno1

        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

        logon drive = U:

        logon home = \\%L\%U

        logon path =

        logon script = logon.cmd

        max log size = 0

        ntlm auth = ntlmv1-permitted

        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

        preferred master = Yes

        printcap name = /etc/printcap

        security = USER

        server string = ClearOS

        template homedir = /home/%U

        template shell = /sbin/nologin

        unix password sync = Yes

        username map = /etc/samba/smbusers

        utmp = Yes

        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





[movies]

        comment = Movies directory

        create mask = 0664

        directory mask = 0775

        path = /var/flexshare/shares/movies

        read only = No

        valid users = @%D\allusers @allusers

        veto files = /.flexshare*/





[homes]

        browseable = No

        comment = Home Directories

        path = /home/%U

        read only = No

        valid users = %D\%S %D+%S %S





[printers]

        available = No

        browseable = No

        comment = Print Spool

        cups options = raw

        path = /var/spool/samba

        printable = Yes

        read only = No

        use client driver = Yes





[print$]

        available = No

        browseable = No

        comment = Printer Drivers

        path = /var/samba/drivers

        read only = No





[netlogon]

        available = No

        browseable = No

        comment = Network Logon Service

        locking = No

        path = /var/samba/netlogon

        read only = No





[profiles]

        available = No

        browseable = No

        comment = Profile Share

        force directory mode = 02775

        force group = domain_users

        path = /var/samba/profiles

        profile acls = Yes

        read only = No

One quick notice my server is set to "simple server". This config file says "Server role: ROLE_DOMAIN_PDC".

To enable webconfig debugging do:

touch /etc/clearos/webconfig.debug

It will lok in something like /var/log/webconfig. Remove /etc/webconfig.debug when you've finished to stop logging.

Your version of samba is up to date and I think the bug you referenced is for a later version of samba.

What is the output of "testparm -s"?

@Dave

I can't find that file, and if I Google it is a file that is used by Phpmyadmin. I have not installed Phpmyadmin..

I found someone with a similar problem.

See this link

I checked the version of Samba and I'am on

samba.x86_64                    4.7.1-9.v7                       @clearos-verified

After the restart of yesterday evening "smb" has not started, and gives a error. The services "nmb" and "winbind" are okay.

[root@discovery ~]# systemctl status -l smb

● smb.service - Samba SMB Daemon

   Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)

   Active: failed (Result: exit-code) since Mon 2018-12-31 08:25:52 CET; 8s ago

  Process: 4897 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=255)

 Main PID: 4897 (code=exited, status=255)



Dec 31 08:25:52 discovery.lionux.lan smbd[4897]: [2018/12/31 08:25:52.160959,  0] ../source3/auth/auth_util.c:1306(get_guest_info3)

Dec 31 08:25:52 discovery.lionux.lan smbd[4897]:   SamInfo3_for_guest: Unable to locate guest account [guest]!

Dec 31 08:25:52 discovery.lionux.lan smbd[4897]: [2018/12/31 08:25:52.161037,  0] ../source3/auth/auth_util.c:1374(make_new_session_info_guest)

Dec 31 08:25:52 discovery.lionux.lan smbd[4897]:   get_guest_info3 failed with NT_STATUS_NO_SUCH_USER

Dec 31 08:25:52 discovery.lionux.lan smbd[4897]: [2018/12/31 08:25:52.161079,  0] ../source3/smbd/server.c:2011(main)

Dec 31 08:25:52 discovery.lionux.lan smbd[4897]:   ERROR: failed to setup guest info.

Dec 31 08:25:52 discovery.lionux.lan systemd[1]: smb.service: main process exited, code=exited, status=255/n/a

Dec 31 08:25:52 discovery.lionux.lan systemd[1]: Failed to start Samba SMB Daemon.

Dec 31 08:25:52 discovery.lionux.lan systemd[1]: Unit smb.service entered failed state.

Dec 31 08:25:52 discovery.lionux.lan systemd[1]: smb.service failed.

[root@discovery ~]# systemctl status -l nmb

● nmb.service - Samba NMB Daemon

   Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled)

   Active: active (running) since Sun 2018-12-30 22:41:33 CET; 9h ago

 Main PID: 855 (nmbd)

   Status: "nmbd: ready to serve connections..."

   CGroup: /system.slice/nmb.service

           ├─ 855 /usr/sbin/nmbd --foreground --no-process-group

           └─1014 /usr/sbin/nmbd --foreground --no-process-group



Dec 30 22:41:41 discovery.lionux.lan nmbd[855]:

Dec 30 22:41:41 discovery.lionux.lan nmbd[855]:   Samba server DISCOVERY is now a domain master browser for workgroup WORKGROUP on subnet 192.168.1.27

Dec 30 22:41:41 discovery.lionux.lan nmbd[855]:

Dec 30 22:41:41 discovery.lionux.lan nmbd[855]:   *****

Dec 30 22:41:57 discovery.lionux.lan nmbd[855]: [2018/12/30 22:41:57.523601,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)

Dec 30 22:41:57 discovery.lionux.lan nmbd[855]:   *****

Dec 30 22:41:57 discovery.lionux.lan nmbd[855]:

Dec 30 22:41:57 discovery.lionux.lan nmbd[855]:   Samba name server DISCOVERY is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.27

Dec 30 22:41:57 discovery.lionux.lan nmbd[855]:

Dec 30 22:41:57 discovery.lionux.lan nmbd[855]:   *****

[root@discovery ~]# systemctl status -l winbind

● winbind.service - Samba Winbind Daemon

   Loaded: loaded (/usr/lib/systemd/system/winbind.service; enabled; vendor preset: disabled)

   Active: active (running) since Sun 2018-12-30 22:41:33 CET; 9h ago

 Main PID: 2764 (winbindd)

   Status: "winbindd: ready to serve connections..."

   CGroup: /system.slice/winbind.service

           ├─2764 /usr/sbin/winbindd --foreground --no-process-group

           └─2767 /usr/sbin/winbindd --foreground --no-process-group



Dec 30 22:41:33 discovery.lionux.lan systemd[1]: Starting Samba Winbind Daemon...

Dec 30 22:41:33 discovery.lionux.lan winbindd[2764]: [2018/12/30 22:41:33.170086,  0] ../lib/util/become_daemon.c:124(daemon_ready)

Dec 30 22:41:33 discovery.lionux.lan winbindd[2764]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connections

Dec 30 22:41:33 discovery.lionux.lan systemd[1]: Started Samba Winbind Daemon.

Marcel,

You can turn up logging in Webconfig by modifying the following:

/var/webconfig/common/Config.inc.php

define('COMMON_DEBUG_MODE', TRUE);

// 

@ini_set('log_errors', true);

@ini_set('error_log', '/tmp/webconfig.log');

Then this will give us more info about what is going on in /var/log/system

Be sure to back up the file and remove the extra logging when you have your error snippet.

I don't like these Ooops's as I don't read php. Can you check that nmb, smb and winbind are running? You can also try changing the Windows Networking Administrator's password. Beyond that, post you smb.conf, but I'm away from home so it won't be so easy for me to check it.

I did a restart, but that didn't help either..


I made a screenshot! See attachment.

The share is on the ClearOS server. I did'nt see the share in file explorer, but that is solved now. It was a firewall issue. My problem still is the issue in the webconfig when I go to Windows Networking (samba) --> Settings --> Edit --> Update. I receive a error. "Ooops! state invalid" nothing more is displayed. Any idea?

Don't worry about smbusers. It is not used.

Is your network share in the server or is it remote. If it is remote, has it mounted OK?

After some thinking I realized the reason I can't access the network share where related to my firewall. I had set the server to standalone. This server is going to be moved to a data center. Now it's still at home I set the server to standalone no firewall.

I still the issue Windows Networking (samba) --> Settings --> Edit --> Update I receive a error. "Ooops! Any idea?

When I try to restart samba

systemctl restart smb

systemctl status smb

Dec 30 12:31:43 discovery.lionux.lan systemd[1]: Starting Samba SMB Daemon...

Dec 30 12:31:43 discovery.lionux.lan smbd[6120]: [2018/12/30 12:31:43.183261,  0] ../source3/auth/user_util.c:358(map_username)

Dec 30 12:31:43 discovery.lionux.lan smbd[6120]:   can't open username map /etc/samba/smbusers. Error No such file or directory

Dec 30 12:31:43 discovery.lionux.lan smbd[6120]: [2018/12/30 12:31:43.187078,  0] ../lib/util/become_daemon.c:124(daemon_ready)

Dec 30 12:31:43 discovery.lionux.lan smbd[6120]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections

Dec 30 12:31:43 discovery.lionux.lan systemd[1]: Started Samba SMB Daemon.

There is a error. The file "smbusers" is not created during my ClearOS install.

After some reading I'm not sure if this is related to my problem. A quote from another post:

The smbusers file does not exist until you create it. It is only needed if your windows users have a different username from the Linux/Samba username.