Many thanks Nick - I didn't realise.
Rich

@Rich,
Beta3 has been released. See the sticky at the top for special upgrade instructions or install beta3 from scratch.

I am a little perplexed.
I have done a fresh install of 7.1b2, but am missing the ability to install a web server, FTP server, Port Forward, and many of the other items I expect to be selectable.
There are 47 items listed in the market place.
Basic packages have been installed and initiallise ok - Directory Services, DHCP, DNS- but I can not work out why I am missing so many packages.
I will try another install, and see if the same thing happens - but any pointers would be appreciated.

Regards
Rich

@Peter Baldwin and Dave Loper

I PM'd you both yesterday to say the beta 3 thread is password protected so unviewable. Can this be fixed, please?

TIA,

Nicl

EDIT:

Never mind! was missing the clearos.repo

Know idea where that went too

pete910 wrote:

I seem to have missing packages

Go to install say web-proxy via the market place and it just fails. As do many others.

Worked fine when I tried it yesterday in a VM

Wouldn't even initialise the directory as it fails on the download, was looking for app-samba-core. Only one I found was app-samba-common-core

Replying to myself but can some kind person give me the command to reset the deafult repos for beta 2?

All I get when I run yum update is this

yum update

Loaded plugins: clearcenter-marketplace, fastestmirror

ClearCenter Marketplace: fetching repositories...

Loading mirror speeds from cached hostfile

 * clearos-centos: mirror.econdc.com

 * clearos-centos-extras: mirror.bytemark.co.uk

 * clearos-centos-fasttrack: mirror.mhd.uk.as44574.net

 * clearos-centos-updates: mirror.econdc.com

 * private-clearcenter-dyndns: download1.clearsdn.com:80

 * private-clearcenter-plex: download2.clearsdn.com:80

 * zmrepo: zmrepo.connortechnology.com

Resolving Dependencies

--> Running transaction check

---> Package app-base.noarch 1:2.1.5-1.v7 will be updated

---> Package app-base.noarch 1:2.1.14-1.v7 will be an update

---> Package app-base-core.noarch 1:2.1.5-1.v7 will be updated

---> Package app-base-core.noarch 1:2.1.14-1.v7 will be an update

--> Processing Dependency: theme-clearos-admin >= 7.1.3 for package: 1:app-base-core-2.1.14-1.v7.noarch

--> Processing Dependency: clearos-release >= 7-1.7 for package: 1:app-base-core-2.1.14-1.v7.noarch

--> Processing Dependency: clearos-framework >= 7.1.2 for package: 1:app-base-core-2.1.14-1.v7.noarch

--> Finished Dependency Resolution

Error: Package: 1:app-base-core-2.1.14-1.v7.noarch (clearos-bootstrap)

           Requires: theme-clearos-admin >= 7.1.3

           Installed: theme-clearos-admin-7.1.1-1.v7.noarch (@anaconda/7.1beta2)

               theme-clearos-admin = 7.1.1-1.v7

Error: Package: 1:app-base-core-2.1.14-1.v7.noarch (clearos-bootstrap)

           Requires: clearos-framework >= 7.1.2

           Installed: clearos-framework-7.1.1-1.v7.noarch (@anaconda/7.1beta2)

               clearos-framework = 7.1.1-1.v7

Error: Package: 1:app-base-core-2.1.14-1.v7.noarch (clearos-bootstrap)

           Requires: clearos-release >= 7-1.7

           Installed: clearos-release-7-1.0.v7.x86_64 (@anaconda/7.1beta2)

               clearos-release = 7-1.0.v7

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

I've tried yum clean all but no luck there ether

yum repolist displays 

yum repolist

Loaded plugins: clearcenter-marketplace, fastestmirror

ClearCenter Marketplace: fetching repositories...

Loading mirror speeds from cached hostfile

 * clearos-centos: mirror.econdc.com

 * clearos-centos-extras: mirror.bytemark.co.uk

 * clearos-centos-fasttrack: mirror.mhd.uk.as44574.net

 * clearos-centos-updates: mirror.econdc.com

 * private-clearcenter-dyndns: download1.clearsdn.com:80

 * private-clearcenter-plex: download2.clearsdn.com:80

 * zmrepo: zmrepo.connortechnology.com

repo id                                                                                                                   repo name                                                                                                                                               status

clearos-bootstrap                                                                                                         ClearOS 7 - x86_64 - Bootstrap                                                                                                                                 5

clearos-centos/7/x86_64                                                                                                   CentOS-7 - Base                                                                                                                                         8,580+72

clearos-centos-extras/7/x86_64                                                                                            CentOS-7 - Extras                                                                                                                                            149

clearos-centos-fasttrack/7/x86_64                                                                                         CentOS-7 - fasttrack                                                                                                                                          51

clearos-centos-updates/7/x86_64                                                                                           CentOS-7 - Updates                                                                                                                                        928+72

private-clearcenter-dyndns                                                                                                private-clearcenter-dyndns                                                                                                                                     2

private-clearcenter-plex                                                                                                  private-clearcenter-plex                                                                                                                                       3

zmrepo/7/x86_64                                                                                                           Zoneminder and its dependencies for Enterprise Linux 7 - x86_64                                                                                               63

repolist: 9,781

I seem to have missing packages

Go to install say web-proxy via the market place and it just fails. As do many others.

Worked fine when I tried it yesterday in a VM

Wouldn't even initialise the directory as it fails on the download, was looking for app-samba-core. Only one I found was app-samba-common-core

Strange... there should be a warning message like the one shown in the attached file. Perhaps there's a use case that we aren't catching?

I can't say for sure that there wasn't a warning message. I don't have a machine or VM handy at the moment to try an install, but my recollection was that I was task oriented, e.g. "get to yum ... ssh doesn't work, maybe check the firewall in webconfig; ah: I need to open that port." I also don't remember looking at the ssh webconfig app, whether because I was trying to do other things or it didn't show up because the menu didn't expand to show it.

I don't suppose it would make sense to have the port opened in the firewall as part of installing the app, perhaps as part of choosing the port to use and whether to start the sshd server automatically -- in other words, don't start sshd until the user does something with the webconfig app, but do it via the sshd webconfig app, without requiring the user to find and open the firewall app too -- like a checkbox saying "open this port in the firewall". (It would be best practice not to install, let alone start, a server before the user requests it, with the exception of the firewall and other absolutely essential services.) That assumes the menus will expand to allow the user to find that widget... And I suppose it would mean that command line use would need an appropriate message, e.g. when using yum to install sshd.

Yes, sshd is very handy but not essential, and if it is blocked by the firewall, it's useless. So don't install it until requested, and don't start the daemon until the user does something in the webconfig app for sshd and firewall ... which I suppose means that when selecting a bunch of things from the "marketplace", they each need to get queued in a "to-do list" so the user must find the widget, do whatever configuration is essential, and click the button saying "go ahead and start the service" before the installation is completed.

Speaking of which (and going from memory here) I don't recall seeing a "start service automatically" choice in the webconfig app, for example, MariaDB, which I seem to recall didn't come up configured to start automatically, and I had to figure out how to set that up from the command line. Maybe it's there in the widget and I just didn't find it; or there is an assumption that having it installed AND configured means it starts automatically and something in the install didn't take care of that in that one case. (Configuration in the case of MariaDB apparently means setting the password, which I did.)

Hi Merrill,

Merrill Cook wrote:

I just answered by own question: neither the web server nor the samba file sharing apps will work in webconfig until directory services are running.

This is counterintuitive, because I don't want any accounts, besides root and an admin account, on the server, and I don't want them showing up in either web or samba. Maybe if I was going to have a bunch of windows users logging in so they could keep their files confidential from each other, I would need some way of keeping track of user accounts for samba, but I can't think of any sort of account or namespace that would be needed routinely by the web server.

ClearOS has a driver-based accounts system. That means an administrator can select from a variety of different options:

- OpenLDAP
- Samba 4 Directory
- Active Directory Connector

To meet your desired needs, we would need to develop a fourth accounts driver:

- Shadow

Many apps need the flexibility in LDAP/Directory services: OwnCloud, Zarafa, Mail Services, PPTP, and OpenVPN (to name a few) would not be compatible. Samba would need to be hacked to use the old school functionality, so work would be required for that too. I have always wanted to create the shadow driver, but there's not enough demand to justify the development time.

The Web Server needs user accounts in order to provide upload access (via FTP or Samba). Without the "shadow accounts driver", one of the other LDAP/directory options is required for uploads.

On previous Clark and Clear servers the LDAP functions just seem to get in the way, and the LDAP server was not very robust to sudden server shutdowns. I was hoping, since it wasn't included in the default install, that we wouldn't have to set up LDAP unless we needed the additional directory flexibility. Oh well. At least tell me that I won't have to deal with LDAP database failures every few months with the new version?

Just to clarify, the account system is only downloaded and initialized if it's requested by the administrator. If an admin doesn't use any user/group-dependent apps, then no LDAP is required (or Samba Directory, or AD Connector). That's fairly common on systems deployed as pure firewall/gateways.

From a UX perspective, if you are going to force us to also use directory services for the webconfig of webserver or samba, you need to have a clearer message like "YOU MUST INSTALL DIRECTORY SERVICE" rather than having something that looks like "other related apps you might be interested in getting from the marketplace".

Yes, it's not ideal in ClearOS 6, but it will be better in the next ClearOS 7 test release. In 7, the account driver selection (OpenLDAP, Samba4, AD Connector) will be part of the install wizard.

Merrill,

Thanks for going through the pains of installing beta 2, we appreciate the feedback.

Merrill Cook wrote:
I set up a regular user as an administrator (along with root) during install -- the form seemed to suggest it, and I figured it would be the preferred way to administer (sudo, etc). Just for kicks, later when I first got to the webmin setup, I tried logging in to the webmin interface with that user. I got some sort of "not authorized" error, but there was no option to log out or log in again as root, it just came back to the same error page. So I wasn't able to log in with root to continue the setup, even after restarting the browser. (I suppose the error could be because I didn't type the admin user's password properly, but I haven't tested that. And I suppose I could have figured out how to clear cookies in that browser for that page, but I was too lazy to figure that out.) I'd suggest root be "strongly suggested" somehow at least at that step in setup, even if the admin user can log in to webmin later in the process (which I haven't had a chance to test yet). If I just didn't notice the "try again" button, it probably needs to be easier to find.

For now, we'll make it so only the "root" account will be made available in the installer tracker #3341 . We'll tackle getting the administrator/sudo method implemented in a future release. With the option of having Samba 4 and the AD Connector for users & groups, the workflow is more awkward in ClearOS. We can't count on the availability of these account systems (e.g. when an AD server is offline or disconnected from the network), so putting an administrator/sudo account in these account systems is a bad idea. But that means the administrator/sudo account must live in the shadow (/etc/passwd) system which in turn means that it won't be a normal account that could access OpenVPN, Samba, etc. That's okay, but it will confuse end users who will:

1) create their sudo/admin account
2) not read the documentation (something we have to assume as software developers)
3) get frustrated with the inability to access a Flexshare with their sudo/admin account

In the end, this can all be resolved, but it will require training/documentation in addition to software changes.

Since that was with Chrome, I figured if I switched to Firefox I'd be able to get in. I learned after much trial and error that NoScript prevents some of the menus from working, but without triggering the NoScript alert (at least on my machine). Might be worth thinking about how to let people know about that, or else set it up so at least something happens if scripts are blocked.

I think there is just a general problem with the menus. I can duplicate menu issues, so I submitted a tracker item: tracker #3351

The first thing I noticed on the webmin, after install and setup finished, was dashboard configuration. At least I think that was where I was dumped. I didn't know what the dashboard was for or what kind of options I should choose, so I figured I'd just leave it at the defaults and customize it later. I guess that's not the best strategy, since there is no "shutdown/restart" option anywhere in webmin unless you place a widget for it on the dashboard. (Why isn't it one of the regular menu choices?) I'm not sure I like having either "reboot" or "restart" so easily clicked-on via the dashboard; I'd rather have to dig a bit deeper to find it; but I would like to find it.

For now, the dashboard is fairly empty, but we'll add more widgets and create a sane default for the next test release. It's just blank in beta 2.

After getting through initial setup, I was temporarily surprised that ssh wasn't working. I was able to open it on the firewall via webmin ... but still, maybe put a message that the firewall blocks ssh by default ... I mean, I like it that the firewall doesn't open all sorts of random ports by default, and I suppose those wanting to use ssh would be able to figure out to open the firewall for it, but the "ux" is a bit awkward. Anyway, I wasn't able to reboot the server via webmin (since I hadn't found the dashboard widget) and I couldn't get in with ssh until later, so it was frustrating.

Strange... there should be a warning message like the one shown in the attached file. Perhaps there's a use case that we aren't catching?

Tony Ellis wrote:

Nick - the NIC names are an attempt for them to be more meaningful in that the name now attempts to explain where in the machine the NIC is located.
More info on this if you do a web search, but there is a nice summary at http://ask.xmodulo.com/change-network-interface-name-centos7.html
BSD has had a similar naming scheme for a long time. If you look in dmesg you will actually see where the NICs are originally ethx and renamed (at least saw this on my aborted attempt at ClearOS 7.

Though I understand the reasoning, I'm not a big fan of the "predictable" naming convention. For all those standalone & cloud ClearOS servers, you have to take an extra step to determine the one and only network interface name on the system. I guess that's why Amazon Linux and CentOS 7 images disabled this "predictable" naming behavior by default - eth0 is still the default on those images.

I was on holiday for the week - it looks like we have a lot of feedback to review! More to come.

Hi

I managed to install the Samba Directory app via yum, but was unable to initialize it as I've got the Community version installed. Am I supposed to be able to install Samba Directory on the community version?

This might not be the right thread to ask it in, but what are the chances of seeing semi-manual Content Filter and IDS/IPS update apps ,using the free rule sets available, for the community version?

For the IDS/IPS update app I was thinking you could give the user the option of selecting which free rule sets to download ie: SnortVRT-open and/or ET-open, and then select the download frequency.

For the Content Filter update app it would be similar, using the free Shallalist. It would just be up to the user to register for the free commercial account with Shalla - http://www.shallalist.de/licence.html

I realize that these lists aren't as extensive or tested as the paid update apps, but it would be better than having no updates.

I just tried to configure and test SMTP/E-mail Notification Settings. It worked fine with a normal gmail address ([email protected]) but told me that the gmail option to add a code after + ([email protected]) is illegal, when it is not.

I notice the web server app for webconfig is not working in beta 2. Is that by design, or something worth noting? The web server itself seems to be fine.

I just answered by own question: neither the web server nor the samba file sharing apps will work in webconfig until directory services are running.

This is counterintuitive, because I don't want any accounts, besides root and an admin account, on the server, and I don't want them showing up in either web or samba. Maybe if I was going to have a bunch of windows users logging in so they could keep their files confidential from each other, I would need some way of keeping track of user accounts for samba, but I can't think of any sort of account or namespace that would be needed routinely by the web server.

On previous Clark and Clear servers the LDAP functions just seem to get in the way, and the LDAP server was not very robust to sudden server shutdowns. I was hoping, since it wasn't included in the default install, that we wouldn't have to set up LDAP unless we needed the additional directory flexibility. Oh well. At least tell me that I won't have to deal with LDAP database failures every few months with the new version?

From a UX perspective, if you are going to force us to also use directory services for the webconfig of webserver or samba, you need to have a clearer message like "YOU MUST INSTALL DIRECTORY SERVICE" rather than having something that looks like "other related apps you might be interested in getting from the marketplace".

I finally found Shutdown/Restart on the left-hand menu: System | Settings | General Settings.

The reason I couldn't find it was that it wasn't showing up in Chrome; that is, the ajax routine to make more room for it didn't, so I only saw the first few entries under system when I selected it, and it didn't have a scroll bar.

It doesn't happen all the time, which is how I found it; and now that I know there are more menu choices there, I can fiddle with it (changing the zoom, etc) to get to it. Having the zoom at 110% makes it break most of the time, reducing the zoom below 100% usually gets it working, after refreshing.

Peter Baldwin wrote:

Hi Marcel

The release notes is talking about Samba 4. How do I install Samba 4? I did install the "app-samba" via yum but I think I'll did get the old app.

There's still some uncertainty about the availability of the Samba Directory app, so it's only available on the command line for now:

yum install app-samba-directory

If you are kicking the tires, install this app first!

Okay, installed "app-samba-directory" as first app. I rebooted the server and now the samba service is dead. If I start the service it stays dead. Also the account manager is reporting "account system offline". Is it possible to resolve this issue? Maybe a bug?

Edit: The app status screen is showing the following: status: dead. Additional Info: Connection failure.

Edit: For some reason the service is now starting but when I'll go to the users app the screen is blank. I checked log.samba.

 STATUS=daemon 'samba' finished starting up and ready to serve connectionssamba_terminate: wreplsrv_task_init: wreplsrv_open_winsdb() failed

A couple of observations doing a first-time install of ClearOS 7 (beta 2)

I set up a regular user as an administrator (along with root) during install -- the form seemed to suggest it, and I figured it would be the preferred way to administer (sudo, etc). Just for kicks, later when I first got to the webmin setup, I tried logging in to the webmin interface with that user. I got some sort of "not authorized" error, but there was no option to log out or log in again as root, it just came back to the same error page. So I wasn't able to log in with root to continue the setup, even after restarting the browser. (I suppose the error could be because I didn't type the admin user's password properly, but I haven't tested that. And I suppose I could have figured out how to clear cookies in that browser for that page, but I was too lazy to figure that out.) I'd suggest root be "strongly suggested" somehow at least at that step in setup, even if the admin user can log in to webmin later in the process (which I haven't had a chance to test yet). If I just didn't notice the "try again" button, it probably needs to be easier to find.

Since that was with Chrome, I figured if I switched to Firefox I'd be able to get in. I learned after much trial and error that NoScript prevents some of the menus from working, but without triggering the NoScript alert (at least on my machine). Might be worth thinking about how to let people know about that, or else set it up so at least something happens if scripts are blocked.

When I first got in to the webmin interface in Firefox and got NoScript working, it locked up a few times, especially on the software update screen. After my patience ran out, I logged in to the console and ran yum update, then refreshed webmin, and it was able eventually to report that I was up to date. Not sure what was making the scripts take so long in Firefox.

The first thing I noticed on the webmin, after install and setup finished, was dashboard configuration. At least I think that was where I was dumped. I didn't know what the dashboard was for or what kind of options I should choose, so I figured I'd just leave it at the defaults and customize it later. I guess that's not the best strategy, since there is no "shutdown/restart" option anywhere in webmin unless you place a widget for it on the dashboard. (Why isn't it one of the regular menu choices?) I'm not sure I like having either "reboot" or "restart" so easily clicked-on via the dashboard; I'd rather have to dig a bit deeper to find it; but I would like to find it.

After getting through initial setup, I was temporarily surprised that ssh wasn't working. I was able to open it on the firewall via webmin ... but still, maybe put a message that the firewall blocks ssh by default ... I mean, I like it that the firewall doesn't open all sorts of random ports by default, and I suppose those wanting to use ssh would be able to figure out to open the firewall for it, but the "ux" is a bit awkward. Anyway, I wasn't able to reboot the server via webmin (since I hadn't found the dashboard widget) and I couldn't get in with ssh until later, so it was frustrating.

Hi Tony,
I had thought that ClearOS had turned off that option in 6 and not rhel. I guess it is back to stay.

Nick - the NIC names are an attempt for them to be more meaningful in that the name now attempts to explain where in the machine the NIC is located.
More info on this if you do a web search, but there is a nice summary at http://ask.xmodulo.com/change-network-interface-name-centos7.html
BSD has had a similar naming scheme for a long time. If you look in dmesg you will actually see where the NICs are originally ethx and renamed (at least saw this on my aborted attempt at ClearOS 7.

From an alpha installation, I think, but do you know why my NICs are enp0s3 and enp0s8 and not eth0 and eth1?

I give up for now...

Go to Accounts - System - Users... takes me to Account Manager Configuration...

Press "Configure Built-in Directory" button...

Directory Status show a circle of moving dots and "Directory is starting up."

It never finishes "starting"... the display never changes from here, just never ending dot circle,
machine is not locked up... ssh access to root is still working. Top shows 98.7 idle.

Maybe will try again later, or on a different machine, if one becomes available...

EDIT.

/usr/sbin/slapd -h 'ldap://127.0.0.1/ ldaps://127.0.0.1/ / ldaps://192.168.1.29/' -u ldap & helps...

Now getting "Database number selected via -n is out of range"

To be continued when I have more time...

(Only odd thing about this machine is an nforce NIC that is not supported. The previous machine I tried
EVERY single NIC {Qty 3} was NOT supported :-( Version 7 has dropped support for so many NICs.)

Thanks Ben, registered and now adding apps from the Marketplace...

Tony.

The software ID should be 20710.

B

Hi Peter!

Perhaps one of the updates has resolved this? because I am now able to access app/system_report

But for the record:

[root@xyz ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/clearos-root 240637132 10089292 230547840 5% /
devtmpfs 1318220 0 1318220 0% /dev
tmpfs 1328808 4 1328804 1% /dev/shm
tmpfs 1328808 41832 1286976 4% /run
tmpfs 1328808 0 1328808 0% /sys/fs/cgroup
/dev/sda1 508588 129096 379492 26% /boot

Thanks!

Peter Baldwin wrote:

Marc Laporte wrote:

"Server is running low on available disk space - preventing further modifications via API until disk space issues are resolved." is being reported at https://example:81/app/network_report even though only 26% of disk space is used.

Could you post the output from "df"? We'll have to tweak the disk space check to handle things like /run and /boot.

[root@madeleine-2 ~]# cat /etc/product

software_id = 10700

name = ClearOS Community

jws_nodes = 1

jws_prefix = cos6-ws

jws_domain = clearsdn.com

jws_realm = ws

jws_version = 1.1

[root@madeleine-2 ~]# 

Hi Tony,

I just downloaded the beta2 image and ran through the post-install wizard...I didn't have any issues on registration.

What's in your /etc/product file?

B

Hi Ben

No go - still exactly the same error displayed...

EDIT Tried "yum --enablerepo=clearos-test upgrade"

This installed a few updated rpms including two for app-registration.
However, still cannot register system - the original error persists...

Invalid Operating System (OS) type.

Sorry! That was my fault when we bumped from 7.0 to 7.1.

Try now.

B.

Thanks Peter - now I have moved on to the next problem - registration...

Warning

Invalid Operating System (OS) type.

and not allowed to continue...
(Yes I think I know how to bypass this - but let's get it working properly :-) )

Tony Ellis wrote:

Ooooops: Server is running low on available disk space - preventing further modifications via API until disk space issues are resolved.

We disabled that check and the fix is sitting in clearos-test:

yum --enablerepo=clearos-test upgrade app-base

I used code tags above - why is it not formatted correctly :-(

I'll post the issue in the "forum development" thread... that needs to get fixed!

Webconfig page "app/base/wizard/index/start"

Ooooops: Server is running low on available disk space - preventing further modifications via API until disk space issues are resolved.

as in a previous append

Filesystem      Size  Used Avail Use% Mounted on

/dev/sdb2        20G  1.2G   19G   6% /

devtmpfs        741M     0  741M   0% /dev

tmpfs           749M     0  749M   0% /dev/shm

tmpfs           749M  8.5M  741M   2% /run

tmpfs           749M     0  749M   0% /sys/fs/cgroup

/dev/sdb5        20G  153M   20G   1% /var

/dev/sdb1       237M  118M  119M  50% /boot

EDIT - I used code tags above - why is it not formatted correctly :-(

Marc Laporte wrote:

When you set up a website, default page /var/www/html/index.html contains a broken call to an image: <img src="/logo.png" alt="Powered by ClearOS">

Thanks for the report. That issue is in the tracker @ https://tracker.clearos.com/view.php?id=2124

Marc Laporte wrote:

"Server is running low on available disk space - preventing further modifications via API until disk space issues are resolved." is being reported at https://example:81/app/network_report even though only 26% of disk space is used.

Could you post the output from "df"? We'll have to tweak the disk space check to handle things like /run and /boot.

When you set up a website, default page /var/www/html/index.html contains a broken call to an image: <img src="/logo.png" alt="Powered by ClearOS">

Thanks!

"Server is running low on available disk space - preventing further modifications via API until disk space issues are resolved." is being reported at https://example:81/app/network_report even though only 26% of disk space is used.

Thanks!

Hi!

Source has:
<!-- Basic Head Information -->
<title>localhost.localdomain - Ooops!</title>

even though I set domains at
https://example.org:81/app/network
and rebooted.

Thanks!

Hi Chris,

Chris Winstanley wrote:

Hello All,
New to ClearOS, but I am hoping to use the new Samba 4 to replace my old 2K3 domain. Anyway, following Peter's advice above (below?), I ran yum install app-samba-directory as the first thing after the initial install, then ran the initialize directory, and it stops/hangs at the "Setting up display specifiers". I have left it in this state for a half hour now, so I would think that it should be done, correct? I am running this in a virtualbox environment, if that makes a difference.
Any thoughts or hints would be appreciated.

Something in the Samba 4 provisioning process must have failed. I'm not the Samba expert, but perhaps there are some clues somewhere in the /var/log/samba log files?

Shaun Ellensohn wrote:

I also have a small problem with the Beta's. Installed MariaDB and set a password via Dashboard but can not login to phpmyadmin :/
It was mentioned with the last beta as well but just want to mention the problem is still there.

I was just looking at this yesterday. There is a permissions problem with the phpMyAdmin package and it will need to be re-built. That should be resolved by next week.

I also have a small problem with the Beta's. Installed MariaDB and set a password via Dashboard but can not login to phpmyadmin :/
It was mentioned with the last beta as well but just want to mention the problem is still there.

Glad to see ClearOS7 is nearly here, finally got some hardware to do some proper testing! hope to report back soon with more
Thanks
Tim