Forums

Resolved
0 votes
This morning some (note *NOT* all) of my machines indicated a lot of updates available together with dependency problems with samba and and kernel updates... (machines are all the same level - ClearOS 7.5 Community). Was alerted to these updates as all machines run"yum update -y --downloadonly" daily, the output being sent to me in emails.

Seems like these are updates associated with an update to 7.6. Seeing no update announced in these forums and heading to Community Dashboad to see if there was an announcement, was greeted with this...

ClearOS 7.3.0 Community Beta is Released
Posted by Devin Johnson on Friday, 17 February 2017 in ClearFoundation
[

[sarcasm] The ClearOS team really know how to keep this site updated...[/sarcasm]

So is it really released? If so it currently has problems. Needless to say didn't update anything - too risky even though by excluding the samba and kernel updates all the ClearOS updates would probably install...
Thursday, April 04 2019, 12:11 AM
Share this post:
Responses (27)
  • Accepted Answer

    Adam M
    Adam M
    Offline
    Tuesday, April 30 2019, 07:08 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    @Wouter,
    You have probably skipped the initial 7.6 update. Please do:
    yum clean all
    yum update app-base
    yum clean all
    yum update


    I just wanted to say thank you so much for this.

    I encountered the same issue today on my brand new month old install of ClearOS 7.

    These commands fixed it up right away. :)
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 04:11 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    @Wouter,
    You have probably skipped the initial 7.6 update. Please do:
    yum clean all
    yum update app-base
    yum clean all
    yum update

    Hi Nick, thank you very much!
    This fixed it and all is fine now. You're my hero!

    Best regards, Wouter
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 02:21 PM - #Permalink
    Resolved
    1 votes
    @Wouter,
    You have probably skipped the initial 7.6 update. Please do:
    yum clean all
    yum update app-base
    yum clean all
    yum update
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 01:11 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:
    Processing Conflict: kernel-3.10.0-957.5.1.v7.x86_64 conflicts selinux-policy-targeted < 3.13.1-201

    I'm sorry if this is the wrong place to ask, but I'm getting almost exactly this error. Automatic updates fail, and yum update delivers an error:
    Processing Conflict: kernel-3.10.0-957.10.1.v7.x86_64 conflicts selinux-policy-targeted < 3.13.1-192.el7_5.noarch
    and also
    samba-client-libs-4.8.3-4.3.v7.x86_64 requires libldb.so.1 (LDB_1.3.0)(64bit).
    yum update --skip-broken doesn't help either.

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

    Friday, April 05 2019, 05:03 PM - #Permalink
    Resolved
    0 votes
    For the Samba/Windows Networking issue, it looks like you can just restart winbind with a:
    service winbind restart
    This should allow Samba (the smb process) to restart. Once smb restarts successfully it does not appear to go wrong again.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 08:46 PM - #Permalink
    Resolved
    0 votes
    For now, we've withdrawn the kernel. It creates a chicken and egg problem that we are working through. Updates are set to work automatically, this typically works like this:

    - ClearOS 7.5 - currently pointing to ClearOS-CentOS 7.5.1804
    - Day1 auto-update: the ClearOS Community systems would be updated with many files, including app-base which points the users to the core CentOS 7.6.1810 packages
    - Day2 auto-update: the rest of the updates from CentOS 7.6.1810 would be upgraded

    This is how a system would typically update. The issue this morning was that the kernel causes a conflict with some of the packages included in the first phase of packages. If you did not get app-base manually, you should get it tonight. If you have any issue (or even notice anything) you can run the update manually:

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

    Thursday, April 04 2019, 04:55 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Can you restart your ldap and look at it as well:

    systemctl restart slapd
    systemctl status slapd


    ldap/slapd was running. restarting it did not yield a change.

    As lunch time arrived and a short downtime became reasonable, I rebooted the box, and samba is now working. I'm sorry this doesn't allow much for identifying the original cause, but it does mean we are back running here.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 04:45 PM - #Permalink
    Resolved
    0 votes
    Can you restart your ldap and look at it as well:

    systemctl restart slapd
    systemctl status slapd
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 03:51 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    At Michael, please do a:
    service smb start
    from the command line and post back the results. Also possibly the results of "journalctl -xe" once it fails to start.

    Also please then go to /var/log/samba and have a look for clues in there. Just look at the non-client files with very recent timestamps.


    Redirecting to /bin/systemctl start smb.service
    Job for smb.service failed because a timeout was exceeded. See "systemctl status smb.service" and "journalctl -xe" for details.

    journalctl -xe seems to be getting flooded with stuff that /isn't/ samba-related stuff, but scrolling up a bit, this is what I find:

    Apr 04 11:48:58 c7.glytch.lan slapd[31761]: conn=2199 op=15 SEARCH RESULT tag=101 err=0 nentries=0 text=
    Apr 04 11:48:58 c7.glytch.lan smbd[1330]: [2019/04/04 11:48:58.482600, 0] ../lib/util/become_daemon.c:138(daemon_ready)
    Apr 04 11:48:58 c7.glytch.lan smbd[1330]: daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
    Apr 04 11:48:58 c7.glytch.lan dbus[809]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Apr 04 11:48:58 c7.glytch.lan dbus[809]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit not found.
    Apr 04 11:48:58 c7.glytch.lan slapd[31761]: conn=2199 fd=36 closed (connection lost)
    Apr 04 11:48:58 c7.glytch.lan systemd[1]: Failed to start Samba SMB Daemon.
    -- Subject: Unit smb.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit smb.service has failed.
    --
    -- The result is failed.
    Apr 04 11:48:58 c7.glytch.lan systemd[1]: Unit smb.service entered failed state.
    Apr 04 11:48:58 c7.glytch.lan systemd[1]: smb.service failed.
    Apr 04 11:48:58 c7.glytch.lan polkitd[5426]: Unregistered Authentication Agent for unix-process:5895:112192172 (system bus name :1.42479, object path /org/fr
    Apr 04 11:48:58 c7.glytch.lan systemd[1]: Started Session c7011 of user root.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 03:35 PM - #Permalink
    Resolved
    0 votes
    At Michael, please do a:
    service smb start
    from the command line and post back the results. Also possibly the results of "journalctl -xe" once it fails to start.

    Also please then go to /var/log/samba and have a look for clues in there. Just look at the non-client files with very recent timestamps.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 03:17 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Here is a general workaround for people to try if they have problems:

    yum --skip-broken update app-*
    yum clean all
    yum update


    Let me know what results you have from this.


    Apr 04 10:52:37 c7.glytch.lan smbd[1914]: [2019/04/04 10:52:37.195737, 0] ../lib/param/loadparm.c:1844(lpcfg_do_service_parameter)
    Apr 04 10:52:37 c7.glytch.lan smbd[1914]: Ignoring unknown parameter "profile acls"
    Apr 04 10:52:37 c7.glytch.lan smbd[1914]: [2019/04/04 10:52:37.373489, 0] ../source3/auth/user_util.c:371(map_username)
    Apr 04 10:52:37 c7.glytch.lan smbd[1914]: can't open username map /etc/samba/smbusers. Error No such file or directory
    Apr 04 10:54:07 c7.glytch.lan systemd[1]: smb.service start operation timed out. Terminating.
    Apr 04 10:54:07 c7.glytch.lan smbd[1914]: [2019/04/04 10:54:07.208082, 0] ../lib/util/become_daemon.c:138(daemon_ready)
    Apr 04 10:54:07 c7.glytch.lan smbd[1914]: daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
    Apr 04 10:54:07 c7.glytch.lan systemd[1]: Failed to start Samba SMB Daemon.
    Apr 04 10:54:07 c7.glytch.lan systemd[1]: Unit smb.service entered failed state.
    Apr 04 10:54:07 c7.glytch.lan systemd[1]: smb.service failed.

    ... attempting to start smb via webconfig simply results in "Starting..." and then, after considerable delay, back to "Stopped."

    Above paste is the output of "systemctl status smb"
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 03:06 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Rodrigo,

    Did this leave you with a .rpmnew file in your /etc/yum.repos.d/clearos-centos.repo.rpmnew?


    This are the files in that folder

    CentOS-Base.repo.rpmsave
    centos-sclo-scl-unverified.repo
    centos-unverified.repo.rpmnew
    clearos-centos.repo.rpmnew
    clearos-epel.repo
    clearos.repo
    webmin.repo
    centos-sclo-scl-rh-unverified.repo
    centos-unverified.repo
    clearos-centos.repo
    clearos-centos-sclo-scl-rh.repo
    clearos-fast-updates.repo
    epel-unverified.repo
    zabbix.repo

    No .rpmnew file

    EDIT: I missunderstood your question. there is not a ".rpmnew" file but there is a clearos-centos.repo.rpmnew file.

    contents of that file:

    [clearos-centos]
    name=CentOS-7 - $basearch - Base
    baseurl=http://download1.clearsdn.com/centos/7.6.1810/os/$basearch
    http://download2.clearsdn.com/centos/7.6.1810/os/$basearch
    http://download3.clearsdn.com/centos/7.6.1810/os/$basearch
    http://download4.clearsdn.com/centos/7.6.1810/os/$basearch
    enabled=0
    gpgcheck=1
    exclude=centos-release centos-logos anaconda-* arpwatch cloud-init-* ctdb-* cyrus-imapd-* debugmode grub2-* initscripts iptables-* kernel-* libsmbclient-* libwbclient-* mokutil-* openldap-* perf ppp-* python-perf rp-pppoe samba-* shim-ia32-* shim-x64-*
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centos-fasttrack]
    name=CentOS-7 - $basearch - fasttrack
    baseurl=http://download1.clearsdn.com/centos/7.6.1810/fasttrack/$basearch
    http://download2.clearsdn.com/centos/7.6.1810/fasttrack/$basearch
    http://download3.clearsdn.com/centos/7.6.1810/fasttrack/$basearch
    http://download4.clearsdn.com/centos/7.6.1810/fasttrack/$basearch
    enabled=0
    gpgcheck=1
    exclude=centos-release centos-logos anaconda-* arpwatch cloud-init-* ctdb-* cyrus-imapd-* debugmode grub2-* initscripts iptables-* kernel-* libsmbclient-* libwbclient-* mokutil-* openldap-* perf ppp-* python-perf rp-pppoe samba-* shim-ia32-* shim-x64-*
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centos-updates]
    name=CentOS-7 - $basearch - Updates
    baseurl=http://download1.clearsdn.com/centos/7.6.1810/updates/$basearch
    http://download2.clearsdn.com/centos/7.6.1810/updates/$basearch
    http://download3.clearsdn.com/centos/7.6.1810/updates/$basearch
    http://download4.clearsdn.com/centos/7.6.1810/updates/$basearch
    enabled=0
    gpgcheck=1
    exclude=centos-release centos-logos anaconda-* arpwatch cloud-init-* ctdb-* cyrus-imapd-* debugmode grub2-* initscripts iptables-* kernel-* libsmbclient-* libwbclient-* mokutil-* openldap-* perf ppp-* python-perf rp-pppoe samba-* shim-ia32-* shim-x64-*
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centos-extras]
    name=CentOS-7 - $basearch - Extras
    baseurl=http://download1.clearsdn.com/centos/7.6.1810/extras/$basearch
    http://download2.clearsdn.com/centos/7.6.1810/extras/$basearch
    http://download3.clearsdn.com/centos/7.6.1810/extras/$basearch
    http://download4.clearsdn.com/centos/7.6.1810/extras/$basearch
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centosplus]
    name=CentOS-7 - $basearch - Plus
    baseurl=http://download1.clearsdn.com/centos/7.6.1810/centosplus/$basearch
    http://download2.clearsdn.com/centos/7.6.1810/centosplus/$basearch
    http://download3.clearsdn.com/centos/7.6.1810/centosplus/$basearch
    http://download4.clearsdn.com/centos/7.6.1810/centosplus/$basearch
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:45 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Here is a general workaround for people to try if they have problems:

    yum --skip-broken update app-*
    yum clean all
    yum update


    Let me know what results you have from this.


    It appears promising, but I won't have a definite answer until about 886 updates from now.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:42 PM - #Permalink
    Resolved
    0 votes
    Rodrigo,

    Did this leave you with a .rpmnew file in your /etc/yum.repos.d/clearos-centos.repo.rpmnew?
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:37 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Here is a general workaround for people to try if they have problems:

    yum --skip-broken update app-*
    yum clean all
    yum update


    Let me know what results you have from this.


    It worked for me.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:13 PM - #Permalink
    Resolved
    1 votes
    Here is a general workaround for people to try if they have problems:

    yum --skip-broken update app-*
    yum clean all
    yum update


    Let me know what results you have from this.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:03 PM - #Permalink
    Resolved
    0 votes
    I have the same issue, here is my repo file contents just in case

    [clearos-centos]
    name=CentOS-7 - $basearch - Base
    baseurl=http://download1.clearsdn.com/centos/7.5.1804/os/$basearch
    http://download2.clearsdn.com/centos/7.5.1804/os/$basearch
    http://download3.clearsdn.com/centos/7.5.1804/os/$basearch
    http://download4.clearsdn.com/centos/7.5.1804/os/$basearch
    enabled=1
    gpgcheck=1
    exclude=shim-x64-* shim-ia32-* centos-release centos-logos anaconda-* arpwatch cloud-init-* ctdb-* cyrus-imapd-* debugmode dnsmasq-* grub2-* initscripts iptables-* kernel-* libsmbclient-* libwbclient-* mokutil-* openldap-* perf ppp-* python-perf rp-pppoe samba-* shim-0*
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centos-fasttrack]
    name=CentOS-7 - $basearch - fasttrack
    baseurl=http://download1.clearsdn.com/centos/7.5.1804/fasttrack/$basearch
    http://download2.clearsdn.com/centos/7.5.1804/fasttrack/$basearch
    http://download3.clearsdn.com/centos/7.5.1804/fasttrack/$basearch
    http://download4.clearsdn.com/centos/7.5.1804/fasttrack/$basearch
    enabled=0
    gpgcheck=1
    exclude=shim-x64-* shim-ia32-* centos-release centos-logos anaconda-* arpwatch cloud-init-* ctdb-* cyrus-imapd-* debugmode dnsmasq-* grub2-* initscripts iptables-* kernel-* libsmbclient-* libwbclient-* mokutil-* openldap-* perf ppp-* python-perf rp-pppoe samba-* shim-0*
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centos-updates]
    name=CentOS-7 - $basearch - Updates
    baseurl=http://download1.clearsdn.com/centos/7.5.1804/updates/$basearch
    http://download2.clearsdn.com/centos/7.5.1804/updates/$basearch
    http://download3.clearsdn.com/centos/7.5.1804/updates/$basearch
    http://download4.clearsdn.com/centos/7.5.1804/updates/$basearch
    enabled=1
    gpgcheck=1
    exclude=shim-x64-* shim-ia32-* centos-release centos-logos anaconda-* arpwatch cloud-init-* ctdb-* cyrus-imapd-* debugmode dnsmasq-* grub2-* initscripts iptables-* kernel-* libsmbclient-* libwbclient-* mokutil-* openldap-* perf ppp-* python-perf rp-pppoe samba-* shim-0*
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centos-extras]
    name=CentOS-7 - $basearch - Extras
    baseurl=http://download1.clearsdn.com/centos/7.5.1804/extras/$basearch
    http://download2.clearsdn.com/centos/7.5.1804/extras/$basearch
    http://download3.clearsdn.com/centos/7.5.1804/extras/$basearch
    http://download4.clearsdn.com/centos/7.5.1804/extras/$basearch
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

    [clearos-centosplus]
    name=CentOS-7 - $basearch - Plus
    baseurl=http://download1.clearsdn.com/centos/7.5.1804/centosplus/$basearch
    http://download2.clearsdn.com/centos/7.5.1804/centosplus/$basearch
    http://download3.clearsdn.com/centos/7.5.1804/centosplus/$basearch
    http://download4.clearsdn.com/centos/7.5.1804/centosplus/$basearch
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:01 PM - #Permalink
    Resolved
    0 votes
    ... Alright, this thread appears to be related to the updates that crippled my network last night. I cannot move past this in order to update anything, and it is stopping samba from working. I have Windows users trying to work through ftp... which is insane.

    Bottom line, what must I do to move forward here? It APPEARS (to my only half-educated self) that I need to start with an updated linux-firmware but I can't find that anywhere.

    Results of "yum update"

    --> Processing Conflict: kernel-3.10.0-957.10.1.v7.x86_64 conflicts selinux-policy-targeted < 3.13.1-201
    --> Finished Dependency Resolution
    --> Running transaction check
    ---> Package kernel.x86_64 0:3.10.0-693.11.6.v7 will be erased
    ---> Package kernel.x86_64 0:3.10.0-957.10.1.v7 will be installed
    --> Processing Dependency: linux-firmware >= 20180911-68 for package: kernel-3.10.0-957.10.1.v7.x86_64
    ---> Package kernel-devel.x86_64 0:3.10.0-693.17.1.v7 will be erased
    --> Processing Conflict: kernel-3.10.0-957.10.1.v7.x86_64 conflicts selinux-policy-targeted < 3.13.1-201
    --> Finished Dependency Resolution
    Error: Package: kernel-3.10.0-957.10.1.v7.x86_64 (clearos-updates)
    Requires: linux-firmware >= 20180911-68
    Installed: linux-firmware-20180220-62.2.git6d51311.el7_5.noarch (@clearos-centos-updates)
    linux-firmware = 20180220-62.2.git6d51311.el7_5
    Available: linux-firmware-20180220-62.git6d51311.el7.noarch (clearos-centos)
    linux-firmware = 20180220-62.git6d51311.el7
    Available: linux-firmware-20180220-62.1.git6d51311.el7_5.noarch (clearos-centos-updates)
    linux-firmware = 20180220-62.1.git6d51311.el7_5
    Error: kernel conflicts with selinux-policy-targeted-3.13.1-192.el7_5.6.noarch
    You could try using --skip-broken to work around the problem
    You could try running: rpm -Va --nofiles --nodigest
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 01:53 PM - #Permalink
    Resolved
    0 votes
    Hi Tony,
    Can you please post your /etc/yum.repos.d/clearos-centos.repo. Also do you have an rpmnew version of it? I am trying to troubleshoot with Dave.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 01:17 PM - #Permalink
    Resolved
    0 votes
    Dave, I take back my last sentence in my last append just momentarily to say our appends crossed - thanks - apology accepted. Good luck with the update...
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 12:59 PM - #Permalink
    Resolved
    0 votes
    Nick - this is the error after installing the 3 rpms as mentioned in my previous append and trying an update... not willing to do any more on this...
    ... snipped
    Error: kernel conflicts with selinux-policy-targeted-3.13.1-192.el7_5.6.noarch
    Error: Package: kernel-3.10.0-957.10.1.v7.x86_64 (clearos-updates)
    Requires: linux-firmware >= 20180911-68
    Installed: linux-firmware-20180220-62.2.git6d51311.el7_5.noarch (@anaconda/7.5.0.228724)
    linux-firmware = 20180220-62.2.git6d51311.el7_5
    Available: linux-firmware-20180220-62.git6d51311.el7.noarch (clearos-centos)
    linux-firmware = 20180220-62.git6d51311.el7
    Available: linux-firmware-20180220-62.1.git6d51311.el7_5.noarch (clearos-centos-updates)
    linux-firmware = 20180220-62.1.git6d51311.el7_5
    Error: Package: samba-winbind-4.8.3-4.v7.x86_64 (clearos-updates)
    Requires: libtevent.so.0(TEVENT_0.9.36)(64bit)
    Error: Package: samba-client-libs-4.8.3-4.v7.x86_64 (clearos-updates)
    Requires: libldb.so.1(LDB_1.3.0)(64bit)
    You could try using --skip-broken to work around the problem
    You could try running: rpm -Va --nofiles --nodigest

    Nick, At this stage I am so pissed off with ClearOS - will be ignoring all updates and research until an authoritative append by ClearOS team indicates the update is available and installs correctly i.e. they learn how to communicate properly. I have better things to do with my life than mess around with this mess... sorry, but that is the way I feel at the moment... In addition to this, will probably need to re-compile some kmods, so will wait until ClearOS get their act together, then some... last append from me until this is sorted and the new mirror process actually working. (Signs of relief I hear :D )
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 12:53 PM - #Permalink
    Resolved
    0 votes
    Tony,

    I personally apologize to you for not performing the steps in a way that would have made this release more stable. I'm not going to attempt to offer excuses or reasons for why I did what I did since, as you point out, it is inexcusable. I take full responsibility. I'm glad that you are willing to help us throughout the years and even now you are helping with your feedback.

    I have a new kernel sitting in clearos-updates-testing that I built over last night to help with a potential issue but it doesn't resolve it fully. I'm waiting to hear back from a team member to bring this resolution to its finale.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 12:40 PM - #Permalink
    Resolved
    0 votes
    So I can't be understanding the error message Dave has mentioned. My kernel-3.10.0-957.5.1.v7.x86_64 installed fine this morning. My selinux-policy-targeted from a couple of months ago is 3.13.1-229.el7_6.9 which came from clearos-centos-updates:
    [root@7 ~]# yum list --show-dulicates selinux-policy-targeted --quiet
    Installed Packages
    selinux-policy-targeted.noarch 3.13.1-229.el7_6.9 @clearos-centos-updates
    Available Packages
    selinux-policy-targeted.noarch 3.13.1-192.el7_5.4 clearos
    selinux-policy-targeted.noarch 3.13.1-229.el7 centos-unverified
    selinux-policy-targeted.noarch 3.13.1-229.el7 clearos-centos
    selinux-policy-targeted.noarch 3.13.1-229.el7_6.5 centos-updates-unverified
    selinux-policy-targeted.noarch 3.13.1-229.el7_6.5 clearos-centos-updates
    selinux-policy-targeted.noarch 3.13.1-229.el7_6.6 centos-updates-unverified
    selinux-policy-targeted.noarch 3.13.1-229.el7_6.6 clearos-centos-updates
    selinux-policy-targeted.noarch 3.13.1-229.el7_6.9 centos-updates-unverified
    selinux-policy-targeted.noarch 3.13.1-229.el7_6.9 clearos-centos-updates

    I can't remember if clearos-centos and clearos-centos-updates are enabled by default, but if they are not then I think a step has been missed in the repo switchover to the centos 7.6 repos. What fom you get from:
    yum repolist
    yum list --show-duplicates selinux-policy-targeted --quiet
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 12:22 PM - #Permalink
    Resolved
    0 votes
    Nick - i know you are responding to Dave - if a version update is announced ready to install, then I usually do the following to perform the update on a test machinel :-
    Install (1/3): app-base, (2/3): clearos-release and (3/3): app-base-core
    then the rest of the updates... (unless yum/rpm is one of the updates - so would install that first).

    Just tried this on a test machine - those three rpms install just fine, but attempting to install the rest still results in the kernel error as indicated by Dave.
    I find it inexcusable to release updates with **known** problems without warning users first... I stumbled across this with a standard nightly yum update downloadonly command. Had I been for-warned - would have ignored the update report, and waited. As it was had to investigate what the hell was going on with the updates...

    in addition - we still have mirrors not updated. having older dated xmp files - the latest in this saga as of a few minutes ago:(


    clearos-centos | 3.0 kB 00:00:00
    Not using downloaded clearos-centos/repomd.xml because it is older than what we have:
    Current : Wed Apr 3 08:21:27 2019
    Downloaded: Thu Mar 7 02:36:52 2019
    clearos-centos-sclo-rh | 3.0 kB 00:00:00
    Not using downloaded clearos-centos-sclo-rh/repomd.xml because it is older than what we have:
    Current : Wed Apr 3 08:22:21 2019
    Downloaded: Thu Mar 7 02:37:26 2019
    clearos-centos-updates | 3.0 kB 00:00:00
    Not using downloaded clearos-centos-updates/repomd.xml because it is older than what we have:
    Current : Wed Apr 3 08:20:05 2019
    Downloaded: Thu Mar 7 02:37:42 2019
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 08:51 AM - #Permalink
    Resolved
    0 votes
    Hi Dave, as you know I did my updates weeks ago, but I did a two step process:
    yum update app-base --enablerepo=clearos-updates-testing
    yum update
    This was the way recommended during either the 7.4 or 7.5 update when testing. I believe this flipped something in the repo configs in app-base (or clearos-release) to look at different sections of the centos repos.

    [edit]
    ..... although I notice there is a now new app-base. The one I received earlier was 2.5.43 and it is now trying to update to 2.6.2. Also the kernel is updating again.
    [edit]
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:59 AM - #Permalink
    Resolved
    0 votes
    Thanks Dave for the update...

    Really think ClearOS needs to be pro-active in letting us know what is happening...

    Complained some weeks ago now (and yet again) about the web-site which finally elicited a response from Nick and some information about one piece of Web-site software being considered... a light at the end of the tunnel - but no idea of how far away that end is.

    Bitched the other day about updates which resulted in a very informative update regarding mirror and update process changes...

    Grumbled today about 7.6 seemingly released with problems - a prompt update from you regarding this update and the conflict which I had observed... Surely simply creating a thread indicating 7.6 was in the process of being released and there might be some initial problems would have circumvented being surprised by yum update conflicts for me and everybody else who notices such things...

    I don't like to be making very negative comments all the time - but seems to be the only way to obtain a response from ClearOS. Previous attempts a few years ago being rather "nicer" were often ignored and was getting rather annoyed at that. Found by being rather more forceful in my criticism resulted in responses... ClearOS is a decent product, though not without its flaws. Use it and want it to succeed.

    Although we live in an information technology age, we often find ourselves in failure to communicate situations.
    Johnny Tan, From My Mama's Kitchen
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 04 2019, 02:16 AM - #Permalink
    Resolved
    0 votes
    There is an issue that we are working through and some Community users will get a partial release of some files, nothing that should permanently break past what will get fixed in auto-updates but we are having an issue with some of the updates. We don't see a need yet for manual intervention but yes, we are in the middle of releasing 7.6 community version.

    Currently tracking on an issue with the clearos-releases file and an update from centos that requires a newer kernel.

    Processing Conflict: kernel-3.10.0-957.5.1.v7.x86_64 conflicts selinux-policy-targeted < 3.13.1-201
    The reply is currently minimized Show
Your Reply