ImportError: No module named _sqlite3 on RHEL 6.7

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

ImportError: No module named _sqlite3 on RHEL 6.7

L0 Member

Looking to install MM on RHEL 7.6

# cat /etc/*elease*
NAME="Red Hat Enterprise Linux Server"
VERSION="7.6 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.6 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.6:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.6"
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Red Hat Enterprise Linux Server release 7.6 (Maipo)
cpe:/o:redhat:enterprise_linux:7.6:ga:server

Minemeld was installed on this system in the past, so to start fresh we deleted the folder and started fresh following the instructions in the link below

 

https://github.com/PaloAltoNetworks/minemeld-ansible#howto-on-centos-7rhel-7

 

After installation we are runnning into this issue. The minemeld-web will not start.

 

# sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/supervisor/config/supervisord.conf status

minemeld-engine                  RUNNING   pid 119286, uptime 0:03:11
minemeld-supervisord-listener    RUNNING   pid 119285, uptime 0:03:11
minemeld-traced                  RUNNING   pid 119287, uptime 0:03:11
minemeld-web                     FATAL     Exited too quickly (process log may have details)

 Here is the logs from minemeld-web.log, looks like it is unable import a module named "_sqlite3"

 

# cat minemeld-web.log
[2019-08-14 10:27:52 +0000] [115958] [INFO] Starting gunicorn 19.5.0
[2019-08-14 10:27:52 +0000] [115958] [INFO] Listening at: http://127.0.0.1:5000 (115958)
[2019-08-14 10:27:52 +0000] [115958] [INFO] Using worker: gevent
[2019-08-14 10:27:52 +0000] [115962] [INFO] Booting worker with pid: 115962
[2019-08-14 10:27:52 EDT] [115962] [INFO] MMLogger started
/opt/minemeld/engine/core/minemeld/flask/aaa.py:21: ExtDeprecationWarning: Importing flask.ext.login is deprecated, use flask_login instead.
  import flask.ext.login
[2019-08-14 10:27:53 EDT] [115962] [INFO] Config loaded: {'MINEMELD_LOCAL_LIBRARY_PATH': '/opt/minemeld/local/library', 'USERS_DB': 'wsgi.htpasswd', 'MINEMELD_LOCAL_PROTOTYPE_PATH': '/opt/minemeld/local/prototypes', 'SUPERVISOR_URL': 'unix:///var/run/minemeld/minemeld.sock', 'MINEMELD_PROTOTYPE_PATH': '/opt/minemeld/local/prototypes:/opt/minemeld/prototypes/current', 'MINEMELD_PIP_PATH': '/opt/minemeld/engine/current/bin/pip', 'MINEMELD_TRACED_PURGE_PATH': '/opt/minemeld/engine/current/bin/mm-traced-purge', 'API_AUTH_ENABLED': True, 'MINEMELD_LOG_DIRECTORY_PATH': '/opt/minemeld/log', 'MINEMELD_7Z_PATH': '/usr/bin/7z', 'MINEMELD_RESTORE_PATH': '/opt/minemeld/engine/current/bin/mm-restore', 'MINEMELD_LOCAL_PATH': '/opt/minemeld/local', 'MINEMELD_GIT_PATH': '/usr/bin/git', 'SNS_ENABLED': True}
[2019-08-14 10:27:53 EDT] [115962] [INFO] USERS_DB loaded from /opt/minemeld/local/config/api/wsgi.htpasswd
[2019-08-14 10:27:53 EDT] [115962] [INFO] FEEDS_USERS_DB loaded from /opt/minemeld/local/config/api/feeds.htpasswd
[2019-08-14 10:27:54 EDT] [115962] [DEBUG] New uuid file created.
[2019-08-14 10:27:54 EDT] [115962] [DEBUG] Instance uuid = 1c3e52e875934395a163bc5d601c4d6e
[2019-08-14 10:27:54 EDT] [115962] [DEBUG] MineMeld cloud notification service is ready.
[2019-08-14 10:27:55 +0000] [115962] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/opt/minemeld/engine/current/lib/python2.7/site packages/gunicorn/arbiter.py", line 517, in spawn_worker
    worker.init_process()
  File "/opt/minemeld/engine/current/lib/python2.7/site packages/gunicorn/workers/ggevent.py", line 190, in init_process
    super(GeventWorker, self).init_process()
  File "/opt/minemeld/engine/current/lib/python2.7/site-packages/gunicorn/workers/base.py", line 122, in init_process
    self.load_wsgi()
  File "/opt/minemeld/engine/current/lib/python2.7/site-packages/gunicorn/workers/base.py", line 132, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/opt/minemeld/engine/current/lib/python2.7/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/opt/minemeld/engine/current/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 65, in load
    return self.load_wsgiapp()
  File "/opt/minemeld/engine/current/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 52, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/opt/minemeld/engine/current/lib/python2.7/site-packages/gunicorn/util.py", line 357, in import_app
    __import__(module)
  File "/opt/minemeld/engine/core/minemeld/flask/main.py", line 3, in <module>
    app = create_app()
  File "/opt/minemeld/engine/core/minemeld/flask/__init__.py", line 70, in create_app
    from . import configdataapi  # noqa
  File "/opt/minemeld/engine/core/minemeld/flask/configdataapi.py", line 18, in <module>
    import sqlite3
  File "/usr/local/lib/python2.7/sqlite3/__init__.py", line 24, in <module>
    from dbapi2 import *
  File "/usr/local/lib/python2.7/sqlite3/dbapi2.py", line 28, in <module>
    from _sqlite3 import *
ImportError: No module named _sqlite3
[2019-08-14 10:27:55 +0000] [115962] [INFO] Worker exiting (pid: 115962)
[2019-08-14 10:27:55 +0000] [115958] [INFO] Shutting down: Master
[2019-08-14 10:27:55 +0000] [115958] [INFO] Reason: Worker failed to boot.

Any ideas on getting MM up and runnnig? 

 

We have tried the solution in this article but no luck

https://live.paloaltonetworks.com/t5/MineMeld-Discussions/minemeld-web-FATAL-CENTOS-Latest-Dev-Editi...

0 REPLIES 0
  • 2574 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!