SystemError: ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time) post upgrade

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
devops

Research direction

Start by reviewing the attached yumsiteissue.txt and the reported Python 3.6 requests, cffi, and libffi errors. The payload names no source file or test; done would mean yum or dnf and the affected services work after the CloudLinux 7-to-8 upgrade without the reported failures.

Written by the indexing model from the issue text.

Description

bug

Describe the bug

Hi Team,

Need your advise on this. We have successfully upgraded CL7 to CL8 with plesk 18.0.66 . Post upgrade when we tried to do yum of dnf we are getting below warnings and errors. Due to this none of the services is coming up and the RPMDB or yum is no longer working.
yumsiteissue.txt

I have attached the full error report as attached . Please have a look and advise us on that

/usr/lib/python3.6/site-packages/requests/init.py:91: RequestsDependencyWarning: urllib3 (1.26.8) or chardet (3.0.4) doesn't match a supported version!
RequestsDependencyWarning)

SystemError: ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time)

Action taken:

  1. We have tried to overcome that warning by "pip install -U urllib3 requests"
  2. For that SystemError: ffi_prep_closure(): bad user_data we have tried this " pip install --force-reinstall --no-binary :all: cffi" and " pip install --upgrade cffi xcffib"

Still No luck

Dominant language
Python
Stars
7
Forks
5
Avg merge
14m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plesk/cloudlinux7to8

All issues in plesk/cloudlinux7to8

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.