Community Forum

Resolved
0 votes
ClearOS 7.3 beta3 is out and ready for testing. The most significant holdup so far is community testing which currently stands at 33 environments and we want to get it to at least 100. As you can see from the tracker, we are pretty much done on all the tasks and bugs. I've pinned Peter's post which illustrates how you can upgrade now/early to 7.3. If you want to go through the paces on a test rig or vm, you can download and use the new 7.3 beta 3 ISO here:

http://mirror.clearos.com/clearos/7.2.0.179092-beta3/x86_64/iso/ClearOS-DVD-x86_64-7.iso

Alternate link:

http://mirror1-orem.clearos.com/clearos/7.2.0.179092-beta3/x86_64/iso/ClearOS-DVD-x86_64-7.iso

Per usual, you can report bugs here on the forums or on the bug tracker (if you have access, requires permission.)
Thursday, February 16 2017, 09:46 PM
Like
1
Share this post:
Responses (17)
  • Accepted Answer

    Thursday, February 23 2017, 09:50 PM - #Permalink
    Resolved
    0 votes
    The upgrade went OK. See 5 "issues" so far:
    1. The kernel that the server is running is 3.10.0-229.7.2.v7.x86_64, but kernel-headers etc is 3.10.0-514.2.2.v7.x86_64
    2. The clearos-centos repo was not updated but instead saved as ".rpmnew"
    3. The new "+" and "-" icons are placed over the text in "Recent Software Activity" in the Dashboard
    4. My system lost its registration. A re-registering went OK.
    5. BackupPC does not work anymore in my LAN. I am using rsyncd to my Windows machines, but I think samba is used to "ping" (I have seen there is a ticket and I hope it is solved soon)
    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 23 2017, 08:21 PM - #Permalink
    Resolved
    0 votes
    I did the
    yum upgrade app-base
    first and now it seems to work (yum is still working on the big upgrade). However, when app-base installed I got the following warning message:
    warning: /etc/yum.repos.d/clearos-centos.repo created as /etc/yum.repos.d/clearos-centos.repo.rpmnew
    That did not seem to be a good thing as I guess my server is still using the old clearos-centos repo, or?

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 23 2017, 07:40 PM - #Permalink
    Resolved
    0 votes
    In the next hour-ish, this will be back to normal:


    yum clean all
    yum upgrade
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 23 2017, 07:04 PM - #Permalink
    Resolved
    0 votes
    Igor,

    That bug appeared on an older ISO. You should be able to do a yum update from command line and resolve the issue.

    yum update app-base
    yum upgrade
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 23 2017, 05:12 PM - #Permalink
    Resolved
    0 votes
    After a fresh install i have the webconfig white screen and nothing i can do.
    It downloaded all the updates in the webconfig and still in the middle of the install wizard it just point to a white page.

    What to do ?
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 23 2017, 04:31 PM - #Permalink
    Resolved
    0 votes
    Fredrik Fornstad wrote:

    OOoops!
    Have you aready released 7.3 ??? Last night my server that runs 7.2 community edition was 100% up to date, but now when I checked it has 113 packages that can not be installed due to dependency problems...


    We're kind of in a weird limbo state with the Community Edition. To upgrade to 7.3.0, you will need to run:


    yum upgrade app-base
    yum upgrade


    The "app-base" upgrade will point your yum repos to CentOS 7.3 (7.3.1611). Without that step, your ClearOS system will still be pointing to the CentOS 7.2 (7.2.1511) repos. There was a tracker item added last month to improve this workflow for ClearOS 7.4.0, but it's just something we have to live with for the first 48 hours of this release. Here's the tracker item - https://tracker.clearos.com/view.php?id=12141
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 23 2017, 10:05 AM - #Permalink
    Resolved
    0 votes
    OOoops!
    Have you aready released 7.3 ??? Last night my server that runs 7.2 community edition was 100% up to date, but now when I checked it has 113 packages that can not be installed due to dependency problems...

    It is hard to do proper trouble shooting via webconfig, but I can see that it has installed kernel-headers-3.10.0-514.2.2 and that it has erased kernel-3.10.0-327.28.3.
    I can also see that the batch of 113 packages are stopped since kernel-3.10.0-514.2.2 requires more modern versions of xfsprogs and kmod
    Feb 23 06:48:22 garaget software-updates: log: --> Processing Conflict: kernel-3.10.0-514.2.2.v7.x86_64 conflicts xfsprogs < 4.3.0 
    Feb 23 06:48:22 garaget software-updates: log: --> Processing Conflict: kernel-3.10.0-514.2.2.v7.x86_64 conflicts kmod < 20-9

    Since my server installed a batch of 12 packages and erased 1, and then later failed in installing 113 packages I wonder if the packages was being rolled out while my server did its nightly automatic update.

    Something is not right, but I can not do more trouble shooting from remote (I have just webconfig open for remote access). Will look more at this tonight.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, February 22 2017, 08:16 AM - #Permalink
    Resolved
    0 votes
    I had last night the following message in cron deamon:

    PHP notice: Undefined index: event_types - /usr/clearos/apps/events/libraries/Event_Utils.php (221)


    This was earlier reported by Nick in the thread : https://www.clearos.com/clearfoundation/social/community/clearos-7-3-0-beta-1-available#reply-167091
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, February 21 2017, 04:42 PM - #Permalink
    Resolved
    0 votes
    MikeCindi,

    This is a great place to report that sort of thing. I've added your bug to the tracker:

    https://tracker.clearos.com/view.php?id=13161
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, February 21 2017, 07:16 AM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Thanks Patrick!!!

    I've placed your report in the bug tracker here:

    https://tracker.clearos.com/view.php?id=13101

    Look for a formal resolution there but it also might appear here. Thanks for taking the risk and doing the update. Did you manage to find a fix for the issue? If so, I'll put your steps in as well or if you are waiting for some guidance, let us know and we'll get those in the bug notes.

    Hi Dave,

    It was simple to do the "fix" .
    Just select the correct certificate in the menu "https://serverip:81/app/base/settings/edit";

    http://i68.tinypic.com/24xhn5h.png
    The reply is currently minimized Show
  • Accepted Answer

    MikeCindi
    MikeCindi
    Offline
    Tuesday, February 21 2017, 01:54 AM - #Permalink
    Resolved
    0 votes
    Installed 7.3b3 in a VM and got the following when trying to install Samba from the marketplace:
    Exception: [u'ERROR with transaction check vs depsolve:', 'libpytalloc-util.so.2(PYTALLOC_UTIL_2.1.6)(64bit) is needed by samba-libs-0:4.4.4-12.v7.1.x86_64', 'glibc = 2.17-106.el7_2.8 is needed by nscd-2.17-106.el7_2.8.x86_64', 'libpytalloc-util.so.2(PYTALLOC_UTIL_2.1.6)(64bit) is needed by samba-python-0:4.4.4-12.v7.1.x86_64']

    I had similar issues when trying to install 7.0 during beta testing.

    BTW, is this the thread for reporting such issues or would a new thread for each issue be preferred?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, February 20 2017, 09:25 PM - #Permalink
    Resolved
    0 votes
    Thanks Patrick!!!

    I've placed your report in the bug tracker here:

    https://tracker.clearos.com/view.php?id=13101

    Look for a formal resolution there but it also might appear here. Thanks for taking the risk and doing the update. Did you manage to find a fix for the issue? If so, I'll put your steps in as well or if you are waiting for some guidance, let us know and we'll get those in the bug notes.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Monday, February 20 2017, 07:23 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    @Patrick,
    Interesting. How does this work? Do you set LetsEncrypt as the CA? If so, how do you generate user certificates for thing like OpenVPN? I can't find any documentation on it.
    Please feel free to take this question privately if you don't think it lives here.
    Nick

    Hi Nick,

    I'm not using OpenVPN or any VPN and therefor not using user certificates.
    For the discussion it is better to continue on the LetsEncrypt thread : https://www.clearos.com/clearfoundation/social/community/letsencrypt-clearos-7
    The reply is currently minimized Show
  • Accepted Answer

    Monday, February 20 2017, 05:59 PM - #Permalink
    Resolved
    0 votes
    @Patrick,
    Interesting. How does this work? Do you set LetsEncrypt as the CA? If so, how do you generate user certificates for thing like OpenVPN? I can't find any documentation on it.
    Please feel free to take this question privately if you don't think it lives here.
    Nick
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, February 19 2017, 06:18 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    I suspect the certificate manager can only really handle imported certificates. Didn't you have to manually configure ClearOS to use the LetsEncrypt certificates?


    Hi Nick,

    ClearOS has the option to use External certificates and is handling this nicely in "Certificate Manager"
    The only thin i ran in to was after the upgrade the setting was changed from "External" to "Internal" certificate
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 18 2017, 10:43 AM - #Permalink
    Resolved
    0 votes
    I suspect the certificate manager can only really handle imported certificates. Didn't you have to manually configure ClearOS to use the LetsEncrypt certificates?

    I use LetsEncrypt for apache only and had to manually configure apache. At a guess, to use the Certificate Manager for these certificates you need to export them to a PC then import them using Certificate Manager. Then, because of the auto-renewal mechanism (which won't update the certificates you've just imported), you need to locate the certificates you've just imported, delete them and replace them with symlinks to the certificates in /etc/letsencrypt/live (which are in themselves symlinks to the latest certificates).

    I don't know how this would work using LetsEncrypt at the system level like you.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 18 2017, 09:21 AM - #Permalink
    Resolved
    0 votes
    The SSL certificate setting for webconfig is changed after the upgrade in https://serverip:81/app/base
    I've installed a LetEncrypt SSL certificate, but after the upgrade this is set back to : Install default instead of External - LetsEncrypt
    The reply is currently minimized Show
Your Reply