Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
danardf opened this issue May 21, 2024 · 10 comments
Labels

Comments

@danardf
Copy link
Contributor

danardf commented May 21, 2024

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 kguptasangoma removed the triage Triage label May 21, 2024
@kguptasangoma
Copy link
Member

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
Copy link
Contributor Author

danardf commented May 21, 2024

@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
Copy link
Member

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

@kguptasangoma kguptasangoma reopened this May 21, 2024
@danardf
Copy link
Contributor Author

danardf commented May 21, 2024

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
Copy link
Contributor Author

danardf commented May 21, 2024

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

@kguptasangoma
Copy link
Member

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
Copy link
Contributor

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
Copy link
Contributor Author

danardf commented May 22, 2024

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

@danardf
Copy link
Contributor Author

danardf commented Aug 12, 2024

@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
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants