/etc/yum/universal-hooks/posttrans/cp_clear_packman_cache is not executable

Peter Grahn a.k.a Lite

• April 21, 2016 15:21

Hi :) Recently I receive the following while using yum: !!!! /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache is not executable Trying chmod +x !!!! /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache I receive: chmod: cannot operate on dangling symlink "/etc/yum/universal-hooks/posttrans/cp_clear_packman_cache" This has occurred since installing EA4 with CouLinux however, CloudLinux referred me to cPanel. My question is, is this anything I should worry about? I like to keep my systems clean. Yours, Pete.

• 

  cPanelMichael

  • April 21, 2016 20:41

  Hello :) You can check to see if it's a working symbolic link. EX:
  ls -al /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache
  Does the destination file exist? Here's how it looks on a test system:
  # ls -al /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache lrwxrwxrwx 1 root root 45 Mar 22 17:57 /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache -> /usr/local/cpanel/scripts/clear_packman_cache*
  Thank you.

  0
• 

  Peter Grahn a.k.a Lite

  • April 21, 2016 21:04

  Yes, it came up as red; lrwxrwxrwx. 1 root root 45 Apr 19 19:30 /etc/yum/universal-hooks/posttrans/cp_cl ear_packman_cache -> /usr/local/cpanel/scripts/clear_packman_cache But chmod +x seems to have sorted it. Anyway, this has occurred on two different severs now so it seems to be a bug in the code..? Thanks!

  0
• 

  TerranceR

  • April 22, 2016 03:18

  Hello, It seems like you may have not used CloudLinux's Conversion Script, did you follow the instructions at Beta: EasyApache 4 released for CloudLinux ?

  0
• 

  Peter Grahn a.k.a Lite

  • April 22, 2016 19:04

  I did indeed and for all installations I had to follow the instruction: If you have some conflicts with Installing profile during migration "/etc/cpanel/ea4/profiles/custom/ea3_state_at_migration-****************.json", just install cPanel default profile. Three servers, same result all installed fresh.

  0
• 

  TerranceR

  • April 23, 2016 02:34

  It does appear that there is a bug with this as I have checked my own server and have the same situation, does "/scripts/clear_packman_cache" exist for you?

  0
• 

  rootbase

  • April 27, 2016 12:18

  saw the same behavior on my non Cloud Linux cPanel install today, last night it upgraded to Release 56: seans@whm [~]# ls -las /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache 0 lrwxrwxrwx. 1 root root 45 Mar 17 21:47 /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache -> /usr/local/cpanel/scripts/clear_packman_cache seans@whm [~]# /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache -bash: /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache: No such file or directory seans@whm [~]# ls -las /scripts/clear_packman_cache /bin/ls: cannot access /scripts/clear_packman_cache: No such file or directory

  0
• 

  cPanelMichael

  • April 27, 2016 17:03

  Hello :) The "/usr/local/cpanel/scripts/clear_packman_cache" file was intentionally removed in cPanel version 56 per the following case: Fixed case CPANEL-3874: Removing caching from packman that is no longer needed. A new case, EA-4362, is open to resolve an issue where the following message appears whenever a package is updated in EasyApache 4: !!!! /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache is not executable You can safely ignore this output until we release a resolution, as it should not prevent YUM from successfully updating. Thank you.

  0
• 

  freedomizer

  • July 03, 2016 18:25

  This message still appears as of July 3, 2016. Just upgraded to EA4, non CloudLinux server.
  cat: /scripts/clear_packman_cache: No such file or directory
  

  0
• 

  cPanelMichael

  • July 04, 2016 19:57

  Hello, The case is still open at this time. I'll update this thread once the resolution has been published. Thanks!

  0
• 

  kernow

  • October 12, 2016 10:31

  3 months on,.............. any update on this?

  0
• 

  cPanelMichael

  • October 12, 2016 18:29

  Hello, There's no update to report on case EA-4362 at this time, however I've linked this thread to the case to ensure the customer feedback is noted. In the meantime, the message output should not prevent EasyApache from working as intended. Thank you.

  0
• 

  cPDan

  • October 19, 2016 13:22

  Greetings! quick update on this. TL;DR: an autofixer is in progress that will fix this (ref: CPANEL-9364) Details: When the packman caching was removed the script that ensured the yum hook symlink was correct, clear_packman_cache, was removed but the symlink was overlooked. In the meantime: [LIST]

  the error does not affect the yum transaction so it is safe to ignore

  if you'd rather not wait for the autofixer it is safe to `rm /etc/yum/universal-hooks/posttrans/cp_clear_packman_cache` Thanks!

  0

Please sign in to leave a comment.