Do you have an upstream proxy? Your system is making many remote calls (using HTTPS) to connect to the ClearCenter site to get to the stage you're at...the software updates then uses YUM (non SSL) to fetch the updates...I wonder if a proxy in front of ClearOS is denying or disrupting downloads.
Sounds like your users don't have home directories...try install the Windows Networking app (via Marketplace or yum install app-samba). I think your home directories will get created automatically...then go through the process of setting up your Dropbox accounts.
For whatever reason, ClearOS is very popular in South Africa and has a large user install base (community and business).
Thinking out loud, perhaps its time to start a thread asking to organize a SA ClearOS user group (SACOSG....sounds military cool!) with the goal of finding an local ISP or tech company that has bandwidth to host an official SA-based mirror. The YUM plugin to locate the closest mirror would automatically pick up this location and safe everyone on bandwidth going out of country.
We can provide documentation and I'm sure ClearFoundation would give some mention to any organization supporting a local mirror. Seems like a win-win for everyone.
That repo doesn't exist any more...we made changes to the private repos wrt to packages that need to be tested before going to the masses.
Edit the conf file that has the zarafa_community_testing entry and disable it...
grep zarafa_community_testing /etc/yum.repos.d/*
You need to be running 6.5beta2, but the new way to update packages from private repositories like Zarafa Community is to add a flag supported in the new yum Marketplace Plugin. So, running:
yum clean all
yum --enablebeta upgrade zarafa-community
This will pull updates down for Zarafa 7.0.15.
BTW, this is fixed in an upcoming package release so you won't need to do this manually...Pete just hasn't pushed out the updates to zarafa-community that makes the changes to your /etc/yum.repos.d/ entries.
All went fine for me too except I bumped into the same problem as Tim reported (blank /usr/clearos/sandbox/etc/httpd/conf.d/devel-paths.conf file)...even after 'clearos reload' when checking the sudoers file.
As soon as I added the directives you posted in a previous post, everything worked.
Thanks Paul. The drive itself tested OK, so I used mdadm --add to add the missing one. So far it is resyncing without incident. I've heard of RAID arrays dropping members before, but this is my first experience with it. These are enterprise level drives.
Yes, it is backed up. Its a RAID 1 mirror plus a daily sync with a 3rd drive. Probably time to buy a spare too.
mdadm reports this:
Version : 1.2
Creation Time : Fri May 10 15:36:33 2013
Raid Level : raid1
Array Size : 1953380736 (1862.89 GiB 2000.26 GB)
Used Dev Size : 1953380736 (1862.89 GiB 2000.26 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent
Update Time : Mon Nov 25 19:27:29 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Name : ent.whisperingwoods.org:0 (local to host ent.whisperingwoods.org)
UUID : 433ed07d:673c3a75:594247ab:891b255d
Events : 18010
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 0 0 1 removed
Did it remove a drive on its own? Shouldnt it tell me the device name?
Yes, I do have SMART monotor installed. All drive PASSED, no problems reported.
Paul wrote: What does
mdadm --detail /dev/md0
show where md0 is your array?
Do you have the SMART monitor app installed? If so you can run
smartctl -a /dev/sda
and repeat for all your drives to work out which has a fault
I think that comment is wrong/old...that function is in /usr/clearos/framework/shared/globals.php. I'm stumped though, because that function has been there a while...are you running the 6.5 beta? Pete might have to chime in here.
I'm stumped...not seeing this across the board, so it is something with your configuration. PM me your account username and the device 'nickname' and I'll set up an environment to reproduce your exact settings and see if I can come up with a reason.
I just received a system email that my RAID array has degraded.. I've never had this happen before. This is a RAID 1 (mirror) array, How can I tell which of the two drives has the problem? Also, what is the best procedure to repair? Should I try to resync them once, and how? Or should I just replace one and rejoin it? Any background info or references appreciated? I can find plenty on how to build the array, but not so much on diagnosis and repair...