FreePBX / framework

This module provides a facility to install bug fixes to the framework code that is not otherwise housed in a module
http://www.freepbx.org
GNU General Public License v3.0
64 stars 61 forks source link

[bug]: RPM command errored, Delete /dev/shm/yumwrapper/* and try again. Exit code 2 - see FreePBX log for more info. #128

Open danardf opened 4 months ago

danardf commented 4 months ago

FreePBX Version

FreePBX 16

Issue Description

After some days when we try to use module admin, we've got this error. Need to run; rm -rf /dev/shm/yumwrapper/* I've got this exception on several systems with the same framework.

Operating Environment

Framework 16.0.40.7

Relevant log output

RPM command errored, Delete /dev/shm/yumwrapper/* and try again. Exit code 2 - see FreePBX log for more info.
kguptasangoma commented 4 months ago

Hey @danardf this happens when yum is already locked either could be other yum process is running or previous yum didnt exited properly. As log message says, solution is to delete the yum lock file and re-try. thanks

danardf commented 4 months ago

@kguptasangoma This problem happened 2 or 3 times after cleaning this directory and on 3 systems. Please check. You can imagine I know this kind of issue and how to fix it. But here. 3 times on 3 systems, it's not usual isn't it? For sure, I know sometimes we need to do that but maybe 1 time a year. I'm use to work on FreePBX dev too. ;) You know as well isn't it?

kguptasangoma commented 4 months ago

are you sure when the issue happens , yum was not running in the system or does previous command failed abruptly ?

danardf commented 4 months ago

I have 3 systems. Two locally and another on Vultr. It will be weird, these systems have the same problem without a possible bug. This is why I created a ticket for you to check on your side.

Agree on local systems if I had a problem with my internet, But on local + on Vultr, it's weird. It's not to bother you Kapil that I create a ticket. ;)

To answer you. Honestly I did not check the yum status.

danardf commented 4 months ago

Anyway, My systems launch the automatic update every night, So, I could check again tomorrow as well.

kguptasangoma commented 4 months ago

okay, i have re-open the jira to check locally. Right now just fully busy in 17/Debian so not able to focus on SNg7/CentOS.

Stevehans commented 4 months ago

Seeing the same here, (twice in the last two weeks). ideally the handler should check for "locked by another process" type status and retry.

This is on a standard image, automatic updates and no additional cron tasks running

danardf commented 4 months ago

@Stevehans Ha, I'm not crazy then. It's a good news. :D

danardf commented 2 months ago

@kguptasangoma Hi Have you got any news? The issue is still present.

Current PBX Version: 16.0.40.9 Current System Version: 12.7.8-2306-1.sng7
Total Module Count: 77 Enabled: 57

kguptasangoma commented 2 months ago

Hey @danardf not really. no update as of now.