Nick Howitt wrote:

I would not be looking forward to somehow issuing new OpenVPN certificates to my few remote users because I'd be in a catch 22. My users are not particularly capable so I'd need to be logged in with OpenVPN/TightVNC and the old certificates to tranfer the new certificates, and I don't think that is going to work.

I started work on getting ClearOS 6 configurations supported for the Configuration Backup app in ClearOS 7. Support should pop-up in the not-too-distant future (guessing about 4 weeks).

Jean-Francois,

You need clearos-updates enabled...run:

yum-config-manager --enable clearos-updates

This is likely a result of coming off the beta or RC release and timing around when you registered...should not be a widespread issue.

B.

audit log is being written to constantly with the following:

type=USER_CMD msg=audit(1444501641.520:195084): pid=26593 uid=998 auid=4294967295 ses=4294967295 msg='cwd="/usr/clearos/framework/htdocs/app" cmd=2F62696E2F6C73202F7661722F72756E2F6E7470642F6E7470642E706964 terminal=? res=success'
type=CRED_ACQ msg=audit(1444501641.521:195085): pid=26593 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
type=USER_START msg=audit(1444501641.521:195086): pid=26593 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
type=USER_END msg=audit(1444501641.523:195087): pid=26593 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
type=CRED_DISP msg=audit(1444501641.523:195088): pid=26593 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=? res=success'
type=USER_CMD msg=audit(1444501641.542:195089): pid=26598 uid=998 auid=4294967295 ses=4294967295 msg='cwd="/usr/clearos/framework/htdocs/app" cmd=2F7362696E2F657468746F6F6C2065746831 terminal=? res=success'

I would say there are 10-100 of these per second. Is there any way to slow this down? (SSDs will thank you).

[root@system audit]# while true : ; do ls -al audit.log ; sleep 10 ; done
-rw------- 1 root root 270687 Oct 10 11:33 audit.log
-rw------- 1 root root 318669 Oct 10 11:33 audit.log
-rw------- 1 root root 385566 Oct 10 11:33 audit.log

Mick Russom wrote:

Looks like the packages are in:

Oct 15 04:38:31 Updated: 1:app-ntp-core-2.1.25-1.v7.noarch
Oct 15 04:38:31 Updated: 1:app-ntp-2.1.25-1.v7.noarch

Did they fix the chronyd issue? Thanks.

Yup!

I was not able to install BackupPC, and it seems be same problem that has existed since at least RC - "Error, no packages selected for install". Are the necessary repos enabled that should be in order to install? I can't believe I am the only one unable to install, as this has occurred on several different installations in VMs over past several weeks.

BackupPC is definitely broken at the install from the marketplace. You can see it start the install and then halfway through it starts to back it out and gives an error about files missing.
Zarafa webaccess installs but is inaccessible for any user. Sometimes it lets you in to a white blank page other times it just hangs for ever at the login.
Ive installed 7.1 Community final 3 times now and its the same each time
I have to go through the market place 4 or 5 times installing apps. Apps are selected and it shows them installing. I go back in to the market place and its showing that some apps selected were not installed. Thats how I found the backupPC not installing.

Wow, how exciting. This couldn't have come at a better time for me.
Getting my copy now. Thanks for everyone's hard work on this.

Ben Chambers wrote:

Faucon,

Can you post the output from:

yum repolist all

B

# yum repolist all

Modules complémentaires chargés : clearcenter-marketplace, fastestmirror

ClearCenter Marketplace: fetching repositories...

Loading mirror speeds from cached hostfile

 * clearos: mirror1-frankfurt.clearos.com

 * clearos-centos: centos.mirror.ca.planethoster.net

 * clearos-centos-updates: centos.mirror.iweb.ca

 * clearos-contribs: mirror1-frankfurt.clearos.com

 * clearos-epel: mirror.cogentco.com

 * clearos-fast-updates: download2.clearsdn.com

 * clearos-infra: mirror1-frankfurt.clearos.com

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

id du dépôt                       nom du dépôt                                             statut

clearos/7                         ClearOS 7 - x86_64 - OS                                  activé:       712

clearos-centos/7/x86_64           CentOS-7 - Base                                          activé:  8 574+78

clearos-centos-extras/7/x86_64    CentOS-7 - Extras                                        désactivé

clearos-centos-fasttrack/7/x86_64 CentOS-7 - fasttrack                                     désactivé

clearos-centos-updates/7/x86_64   CentOS-7 - Updates                                       activé: 1 395+108

clearos-centosplus/7/x86_64       CentOS-7 - Plus                                          désactivé

clearos-contribs/7                ClearOS 7 - x86_64 - Contribs                            activé:        58

clearos-contribs-testing/7        ClearOS 7 - x86_64 - Contribs (Testing)                  désactivé

clearos-developer/7/x86_64        ClearOS Developer 7 - x86_64 - Developer Tools           désactivé

clearos-epel/7/x86_64             Extra Packages for Enterprise Linux 7 - x86_64           activé:  8 569+31

clearos-epel-testing/7/x86_64     Extra Packages for Enterprise Linux 7 - Testing - x86_64 désactivé

clearos-fast-updates/7/x86_64     ClearOS 7 - x86_64 - Fast Updates                        activé:         4

clearos-infra/7                   ClearOS 7 - x86_64 - Infrastructure                      activé:        17

clearos-infra-testing/7           ClearOS 7 - x86_64 - Infrastructure (Testing)            désactivé

clearos-updates/7                 ClearOS 7 - x86_64 - Updates                             désactivé

clearos-updates-testing/7         ClearOS 7 - x86_64 - Updates (Testing)                   désactivé

clearos-zfs/7/x86_64              ZFS on Linux for EL7                                     désactivé

clearos-zfs-testing/7/x86_64      ZFS on Linux for EL7 - Testing                           désactivé

private-clearcenter-dyndns        ClearCenter Dynamic DNS                                  activé:         2

repolist: 19 331

Great news. Well done.

Do you know when you'll be getting 6.x -> 7.1 migration instructions out?

Hi Nick,

There will be no upgrade path from 6 to 7. RedHat nor CentOS support it and their pockets and resources are a wee bit bigger than ours! ;-)

There was a good thread from the CentOS team a while back discussing the for/against...you can read it here.

The one thing we will be providing is a tool to migrate a configuration backup so that it can be taken from a 6 and restored on a 7. I don't have a timeline on availability (either time or version required) at this point.

B

Hi Ben,

I understand there is no direct migration path. It is the config backup tool and instructions I was asking about but you've answered that question.

I would not be looking forward to somehow issuing new OpenVPN certificates to my few remote users because I'd be in a catch 22. My users are not particularly capable so I'd need to be logged in with OpenVPN/TightVNC and the old certificates to tranfer the new certificates, and I don't think that is going to work.

Nick

is there a way to upgrade from 7.1RC1 to 7.1 Final using yum? i added all of the repository availaible through the web interface and yum update still show No packages marked for update.


Thanks !

I just did a "yum upgrade" on my VM and it worked. I can't remember if I was on RC1 or Beta3 before, and now it's upgraded I can't work out which - it was whatever was around on 26/09 and had clearos-release-7-1.14.v7.

Hi, really cool to have this new version but I can't seems to have the marketplace working.
Every app return: "Error, no packages selected for install."

Is this normal, known? What should I do?

Thank you.

Faucon,

Can you post the output from:

yum repolist all

B

Hello,

Can you explain:

Users of Community edition will have a 30-day window to upgrade to Home or Business version

There's will be no free version anymore?

@Jim Joomla...see my explanation here. A free Community Edition is here to stay.

B

repo id repo name status
clearos/7 ClearOS 7 - x86_64 - OS enabled: 712
clearos-centos/7/x86_64 CentOS-7 - Base enabled: 8,574+78
clearos-centos-extras/7/x86_64 CentOS-7 - Extras enabled: 214
clearos-centos-fasttrack/7/x86_64 CentOS-7 - fasttrack enabled: 109
clearos-centos-updates/7/x86_64 CentOS-7 - Updates enabled: 1,395+108
clearos-centosplus/7/x86_64 CentOS-7 - Plus enabled: 63
clearos-contribs/7 ClearOS 7 - x86_64 - Contribs enabled: 58
clearos-contribs-testing/7 ClearOS 7 - x86_64 - Contribs (Testing) enabled: 14
clearos-developer/7/x86_64 ClearOS Developer 7 - x86_64 - Developer Tools enabled: 2
clearos-epel/7/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 enabled: 8,569+31
clearos-epel-testing/7/x86_64 Extra Packages for Enterprise Linux 7 - Testing - x86_64 disabled
clearos-fast-updates/7/x86_64 ClearOS 7 - x86_64 - Fast Updates enabled: 4
clearos-infra/7 ClearOS 7 - x86_64 - Infrastructure enabled: 17
clearos-infra-testing/7 ClearOS 7 - x86_64 - Infrastructure (Testing) enabled: 0
clearos-updates/7 ClearOS 7 - x86_64 - Updates enabled: 375
clearos-updates-testing/7 ClearOS 7 - x86_64 - Updates (Testing) disabled
clearos-zfs/7/x86_64 ZFS on Linux for EL7 disabled
clearos-zfs-testing/7/x86_64 ZFS on Linux for EL7 - Testing disabled
private-clearcenter-dyndns ClearCenter Dynamic DNS enabled: 2
repolist: 20,108


Maybe i'm already on 7.1 Final ? But i know i did install RC1 few weeks ago

Ben Chambers wrote:

Jean-Francois,

You need clearos-updates enabled...run:

yum-config-manager --enable clearos-updates

This is likely a result of coming off the beta or RC release and timing around when you registered...should not be a widespread issue.

B.

Thank you very much work great now.

Faucon wrote:

repo id repo name status
clearos/7 ClearOS 7 - x86_64 - OS enabled: 712
clearos-centos/7/x86_64 CentOS-7 - Base enabled: 8,574+78
clearos-centos-extras/7/x86_64 CentOS-7 - Extras enabled: 214
clearos-centos-fasttrack/7/x86_64 CentOS-7 - fasttrack enabled: 109
clearos-centos-updates/7/x86_64 CentOS-7 - Updates enabled: 1,395+108
clearos-centosplus/7/x86_64 CentOS-7 - Plus enabled: 63
clearos-contribs/7 ClearOS 7 - x86_64 - Contribs enabled: 58
clearos-contribs-testing/7 ClearOS 7 - x86_64 - Contribs (Testing) enabled: 14
clearos-developer/7/x86_64 ClearOS Developer 7 - x86_64 - Developer Tools enabled: 2
clearos-epel/7/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 enabled: 8,569+31
clearos-epel-testing/7/x86_64 Extra Packages for Enterprise Linux 7 - Testing - x86_64 disabled
clearos-fast-updates/7/x86_64 ClearOS 7 - x86_64 - Fast Updates enabled: 4
clearos-infra/7 ClearOS 7 - x86_64 - Infrastructure enabled: 17
clearos-infra-testing/7 ClearOS 7 - x86_64 - Infrastructure (Testing) enabled: 0
clearos-updates/7 ClearOS 7 - x86_64 - Updates enabled: 375
clearos-updates-testing/7 ClearOS 7 - x86_64 - Updates (Testing) disabled
clearos-zfs/7/x86_64 ZFS on Linux for EL7 disabled
clearos-zfs-testing/7/x86_64 ZFS on Linux for EL7 - Testing disabled
private-clearcenter-dyndns ClearCenter Dynamic DNS enabled: 2
repolist: 20,108


Maybe i'm already on 7.1 Final ? But i know i did install RC1 few weeks ago

Have a look in /etc/clearos-release to see what version you are on. Also /var/log/yum.log will show your update history.

[root@pingouin Torrent]# cat /etc/clearos-release
ClearOS release 7.1.0 (Final)


Well.... don't need to re-install then !

Thanks for the tips !


EDIT: For the day-to-day use, should i leave all those repository enabled ?

"Loading software updates list, please be patient."

The installer seems to choke on the updates process. In the background yum makecache can choke on certain mirrors, some mirrors are very slow. The yum upgrade works in the background. Installer is not nearly putting enough output where "Loading software updates list, please be patient." is to even guess at what the issues is or what its waiting for.

Seems the choking is on urlgrabber processes:
root 3815 0.0 0.6 320084 11228 ? S 13:35 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4215 0.0 0.1 188748 2648 ? S 13:39 0:00 /usr/bin/sudo /usr/sbin/wc-yum -i app-users app-users-core
root 4216 0.1 1.4 426952 26512 ? S 13:39 0:00 /usr/bin/python -u /usr/sbin/wc-yum -i app-users app-users-core
root 4266 0.0 0.6 320080 11280 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4267 0.0 0.7 320080 13200 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4268 0.0 0.6 320084 11228 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4269 0.0 0.7 320212 13436 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4277 0.0 0.6 320080 11260 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4279 0.0 0.6 320080 11256 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4281 0.0 0.6 320212 11392 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down
root 4289 0.0 0.6 320080 11272 ? S 13:39 0:00 /usr/bin/python /usr/libexec/urlgrabber-ext-down

Killing them, yum makecache, yum uprgade, and restart wizard got it unstuck.

Is restore config from 6.x to 7.1 supported? I tried it and it mostly worked. It bonked yum.repos.d (I fixed that) and needed to update the dynamic dns bit, but the rest seemed to go ok. Let me know if it would be better to re-install from scratch and rebuild the config by hand or continue to use the restored from backup 7.1.

Note to everyone thinking of recycling their config - dont restore a 6.x config onto a 7.x clearos, it causes a number of problems. I migrated the DHCP and HOSTS by hand and rebuilt the rest.

I see a message about panic mode, but everything seems to be working ok.

Oct 9 16:03:49 system firewall: Running /etc/clearos/firewall.d/10-ntp
Oct 9 16:03:49 system firewall: Enabling NAT on WAN interface eth0
Oct 9 16:03:49 system firewall: Running user-defined outgoing block rules
Oct 9 16:03:49 system firewall: Running default forwarding rules

Oct 9 16:03:49 system firewall: Error: /usr/clearos/apps/firewall/deploy/firewall.lua:3075: Unable to commit: filter: Resource temporarily unavailable.

Oct 9 16:03:49 system firewall: Running firewall panic mode...
Oct 9 16:03:49 system firewall: Starting firewall...
Oct 9 16:03:49 system firewall: Loading environment
Oct 9 16:03:49 system firewall: Detected WAN role for interface: eth0

What can I do to debug this panic mode?

Note: seems related to restoring a 6.x config into a 7.x clearos.

Installed ClearOS Business 7.1 then installed Plex Media Server. All went well.

One thing that I notice is that the Plex.repo is installed. Not entirely sure but this repo isn't used anymore? Plex is now using this repo "private-clearcenter-plex" Correct? If so then this is a bug...

@Jim Joomla. The 30 day window is an opportunity rather than a requirement. ClearOS Community is and will always be a free version that you can run. For the first 30 days of your subscription, you will be using the Verified Updates which come with Home and Business versions as a trial. So even though it is a 'Community version' it will act in some ways like Business and Home in that the updates are verified. After that, it will begin behaving like the ClearOS Community version that you know and love. You will then be part of the pool of people that help make ClearOS well-tested through your participation in the community and your feedback on the forums.

@Marcel, the updates are now consolidated under a single repo. In ClearOS 6 we saw a scalability problem in that if many developers began to make apps then we would have to add a repo to a user for each and every app. Potentially, a box would have to process hundreds of repos in order to update. To remove this issue we now dynamically create all your repo data associated with your license in one repo call.

Hi,
It is not possible to install the print server due to a package dependency problem with liberation-fonts-common:

However, temporarily enabling clearos-centos-fasttrack works as an workaround.

yum install app-print-server --enablerepo=clearos-centos-fasttrack works.

Without clearos-centos-fasttrack enabled you will get the following error at the moment:

Error: Package: 1:liberation-mono-fonts-1.07.2-14.el7.noarch (clearos-centos)

           Requires: liberation-fonts-common = 1:1.07.2-14.el7

           Installed: 1:liberation-fonts-common-1.07.2-15.el7.noarch (@anaconda/7.1.0)

               liberation-fonts-common = 1:1.07.2-15.el7

           Available: 1:liberation-fonts-common-1.07.2-14.el7.noarch (clearos-centos)

               liberation-fonts-common = 1:1.07.2-14.el7

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

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

Maybe someone can move the new liberation-fonts-common into a default repo?

Then making CUPS work is another chapter...

/Fred

Fredrik Fornstad wrote:

Hi,
It is not possible to install the print server due to a package dependency problem with liberation-fonts-common:

However, temporarily enabling clearos-centos-fasttrack works as an workaround.

yum install app-print-server --enablerepo=clearos-centos-fasttrack works.

Very frustrating. That's related to this tracker issue reported a few weeks ago. The ClearOS ISO is built with the Fasttrack repository enabled (?), but we don't enable the Fasttrack repository on a ClearOS install. This situation causes library version mismatches like the one you discovered. We added a workaround in the verified CentOS repository for Home & Business, but neglected to resolve the issue for the Community Edition.

There's a workaround in place now, but we'll have to resolve that tracker issue to make sure this doesn't happen again!

Mick Russom wrote:

Is restore config from 6.x to 7.1 supported? I tried it and it mostly worked. It bonked yum.repos.d (I fixed that) and needed to update the dynamic dns bit, but the rest seemed to go ok. Let me know if it would be better to re-install from scratch and rebuild the config by hand or continue to use the restored from backup 7.1.

Note to everyone thinking of recycling their config - dont restore a 6.x config onto a 7.x clearos, it causes a number of problems. I migrated the DHCP and HOSTS by hand and rebuilt the rest.

That's not supported yet and I'm a bit surprised that the app even allowed you to do it! It's something that we're working on.

Dave Loper wrote:

@Marcel, the updates are now consolidated under a single repo. In ClearOS 6 we saw a scalability problem in that if many developers began to make apps then we would have to add a repo to a user for each and every app. Potentially, a box would have to process hundreds of repos in order to update.

@Dave, that can't be a real world reason why this was done. ClearOS 8 will arrive long before we even have hundreds of paid apps available. And even if hundreds of paid apps were available, how many users would install "hundreds" on a single system? Members of this community could recommend dozens of features and enhancements that are a bigger priority!

To remove this issue we now dynamically create all your repo data associated with your license in one repo call.

That's not yet live and I have yet to even see a technical specification for it.

Resolved very efficiently via Support.........

Since update to 7.1 release i can no longer access server from out of town. I've tried pinging and logging into web access without success.
I've had the server restarted and that didnt help. I've logged into the portal and can see that the external ip is right.
I cannot access anything on the server. I think there is something wrong with the firewall.
Anyone have an idea i can try to fix this?

Thanks
Sam

Fixed or kinda for now. Had to switch from gateway to standalone without firewall and then back to gateway.

Might be a problem to check out.

Hello. I want to install the new clearos 7 community version on a 32 bits computer. However i cant find if this new version is also suitable for this kind of computer. Can you elaborate?

Thans, Ron

Peter Baldwin wrote: That's not supported yet and I'm a bit surprised that the app even allowed you to do it! It's something that we're working on.

I would consider enabling a check for 6.x config files being used in a restore operation on 7.1. 7.1 did take the 6.x config and kind of worked. Given the errors I was seeing, I decided to rebuild by hand.

ratooren wrote:

Hello. I want to install the new clearos 7 community version on a 32 bits computer. However i cant find if this new version is also suitable for this kind of computer. Can you elaborate?

Thans, Ron

Red Hat nor CentOS 7 offers 7.x in 32-bit anymore. Its now x86_64 only, and it would probably be a huge effort for Clear to make 32-bit work well. Everything core2 and onwards is x86_64 so the last hardware that was made 32-bit only was about 2007.

Seems ntpd and chrony / chronyd are competing for the same port (123)

Oct 13 02:02:01 system ntpd[19190]: ntpd 4.2.6p5@1.2349-o Tue Jun 23 23:48:52 UTC 2015 (1)
Oct 13 02:02:01 system ntpd[19190]: proto: precision = 0.084 usec
Oct 13 02:02:01 system ntpd[19190]: 0.0.0.0 c01d 0d kern kernel time sync enabled
Oct 13 02:02:01 system ntpd[19190]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING

This seems to happen on restart or at some interval, however, If I click start in the NTP server section of the GUI, this happens:

(Click on NTP server in GUI)

Oct 13 09:46:34 system webconfig: Redirecting to /bin/systemctl start ntpd.service
Oct 13 09:46:34 system systemd: Stopping NTP client/server...
Oct 13 09:46:34 system chronyd[506]: chronyd exiting
Oct 13 09:46:34 system systemd: Stopped NTP client/server.
Oct 13 09:46:34 system systemd: Starting Network Time Service...
Oct 13 09:46:34 system ntpd[14148]: ntpd 4.2.6p5@1.2349-o Tue Jun 23 23:48:52 UTC 2015 (1)
Oct 13 09:46:34 system ntpd[14149]: proto: precision = 0.084 usec
Oct 13 09:46:34 system ntpd[14149]: 0.0.0.0 c01d 0d kern kernel time sync enabled
Oct 13 09:46:34 system systemd: Started Network Time Service.
Oct 13 09:46:34 system ntpd[14149]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listen normally on 3 eth0 x.x.x.x UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listen normally on 4 eth1 192.168.0.1 UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listen normally on 5 eth1 x::x UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listen normally on 6 eth0 x::x UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listen normally on 7 lo ::1 UDP 123
Oct 13 09:46:34 system ntpd[14149]: Listening on routing socket on fd #24 for interface updates
Oct 13 09:46:34 system systemd: Reloading.
Oct 13 09:46:34 system systemd: [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Oct 13 09:46:34 system systemd: [/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Oct 13 09:46:34 system ntpd[14149]: 0.0.0.0 c016 06 restart
Oct 13 09:46:34 system ntpd[14149]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
Oct 13 09:46:34 system ntpd[14149]: 0.0.0.0 c011 01 freq_not_set
Oct 13 09:46:35 system ntpd[14149]: 0.0.0.0 c614 04 freq_mode




So it looks like on restart chronyd wins, but if I start ntp in the GUI, then chronyd is stopped and ntpd is started.

Mick Russom wrote:
Red Hat nor CentOS 7 offers 7.x in 32-bit anymore. Its now x86_64 only, and it would probably be a huge effort for Clear to make 32-bit work well. Everything core2 and onwards is x86_64 so the last hardware that was made 32-bit only was about 2007.

Yup, confirmed. Sorry, no 32-bit support.

Mick Russom wrote:

Seems ntpd and chrony / chronyd are competing for the same port (123)

Oct 13 02:02:01 system ntpd[19190]: ntpd 4.2.6p5@1.2349-o Tue Jun 23 23:48:52 UTC 2015 (1)
Oct 13 02:02:01 system ntpd[19190]: proto: precision = 0.084 usec
Oct 13 02:02:01 system ntpd[19190]: 0.0.0.0 c01d 0d kern kernel time sync enabled
Oct 13 02:02:01 system ntpd[19190]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING

Chrony should not be running by default. Bug report and fix is on the way. Thanks Mick!

BackupPC does not seem to be released yet for some reason, that is why you get the "not so informative" error. The package still remains in the contribs-testing repo.

If you want to try BackupPC now: Temporarily enable the contribs-testing repo by using the Software Repository app in Marketplace, or by installing BackupPC from command line:

yum install --enablerepo=clearos-contribs-testing app-backuppc

I tried BackupPC a couple of weeks ago, and it seemed to work when I did a short test (small backup and restore test).

/Fred

Just to report: Windows networking (Samba simple networking) seems to work OK now even with Windows 10 clients. The fix with removing the "listen to ..." seems to do the trick.

/Fred