/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


Has anyone had patching troubles since updating to 5.5?

12/04/2013 2770 views

Our patching doesn't seem to be working on the K1 since we upgraded to 5.5. It did previously work in 5.4

I did install the consolidated update patch that was released on 12/2/13 but still receive the below error.

THe folllowing is the "Patch Download Log" after forcing the K1 to download patches.

Dec 4, 2013 1:24:35 PM com.lumension.scr.client.SCRClient process
INFO: Starting Standalone Repository Client
Dec 4, 2013 1:24:35 PM com.lumension.scr.client.SCRClient process
INFO: Using runtime profile : osx-rt
Dec 4, 2013 1:24:35 PM com.lumension.scr.client.SCRClient process
INFO: System Configuration: ( {payload_folder=/kbox/kboxwww/patches, threshold=10737418240, force_refresh=false, keyFile=/kbox/kboxwww/patches/kace.plk, index=kbox4-ec-vega.xml, folder=/kbox/kboxwww/patches, refresh_metadata=false, extractOSX=false, program=/kbox/bin/SCR/bin, download_packages=false, proxyType=HTTP, payloadFolder=/kbox/kboxwww/patches/plp, listfiles_inclusive=/kbox/bin/SCR/bin/kaceconfig/listfiles_inclusive.lst, cacheResponseFolder=/kbox/bin/SCR/bin/cacherequest, checkPayload=true, download_signatures=true, download_mcescan=true, cacheRequestFolder=/kbox/bin/SCR/bin/cacherequest, exclusions=/kbox/kboxwww/patches/exclusions.lst, configlog=/kbox/bin/SCR/logs/OSX-Config.log, platform=OSX, arch=PPC,X86} )
Dec 4, 2013 1:24:36 PM com.lumension.scr.client.SCRClient process
SEVERE: Failed to decrypt password:Access denied for user 'report'@'localhost' (using password: YES)
Dec 4, 2013 1:24:36 PM com.lumension.scr.client.SCRClient process
SEVERE: Stopping download
Dec 4, 2013 1:24:36 PM com.lumension.scr.client.SCRClient process
INFO: System Configuration: ( {payload_folder=/kbox/kboxwww/patches, threshold=10737418240, force_refresh=false, keyFile=/kbox/kboxwww/patches/kace.plk, index=kbox4-ec-vega.xml, folder=/kbox/kboxwww/patches, refresh_metadata=false, extractOSX=false, program=/kbox/bin/SCR/bin, download_packages=false, proxyType=HTTP, payloadFolder=/kbox/kboxwww/patches/plp, listfiles_inclusive=/kbox/bin/SCR/bin/kaceconfig/listfiles_inclusive.lst, cacheResponseFolder=/kbox/bin/SCR/bin/cacherequest, checkPayload=true, download_signatures=true, download_mcescan=true, cacheRequestFolder=/kbox/bin/SCR/bin/cacherequest, exclusions=/kbox/kboxwww/patches/exclusions.lst, configlog=/kbox/bin/SCR/logs/OSX-Config.log, platform=OSX, arch=PPC,X86} )
[2013-12-04 13:24:36 -0600] KPatch [info] SCR Processing Complete
[Wed Dec 4 13:24:36 CST 2013] [notice] Exceptions(105:I/O error) occured while downloading signatures from CDN.Signatures might not be imported for Macintosh
[Wed Dec 4 13:24:36 CST 2013] [notice] To: jstrickland@afcu.org from:jstrickland@afcu.org subject : K1000 - Patch Download Failed Msg: <font color='red'>Error</font> downloading Signatures for Windows.<br>
Please check the server logs for more information.
<font color='red'>Error</font> downloading Signatures for Macintosh.<br>
Please check the server logs for more information.

6 Comments   [ + ] Show comments

Comments

  • I do currently have a ticket open with KACE support, but I haven't heard anything in quite a while.
  • I installed 2 patching hotfixes immediately following my 5.5 upgrade. Did you install those? I received the links from support prior to the upgrade.
  • I had to install about 5 different patches to get certain things to work. One of which was related to patching but it didn't seem to have an effect.
  • There's also a cumulative hotfix that fixes a patching issue but it was pulled yesterday (after I installed it yesterday afternoon). You might keep an eye out for this one to go live again:

    https://www.kace.com/support/resources/kb/solutiondetail?sol=SOL116901
  • The cumulative fix is back up and the link can be found in your KBOX home . summary page.

    To your point....after I applied some earlier hotfixes , i haven't seen any issues with patching.
    • The link on my KBOX leads to the KB article @rockhead44 posted but that KB article still says that the fix is not available.
      • It was there for me on 12/3 and said that it had only been put up there on 12/2. It didn't fix our problem anyway.
  • Yeah I ran that already before it was taken down and put back up or whatever happened.

Be the first to answer this question