-
#1
Hi guys for me its very long ago that i made a build, i am trying to install catalina i made the usb put multibeast on it withous any succes i keep getting this error, (pictures)
Not found while reopening our self handeling
The setup is:
Intel core i7 6800k 3,40ghz
Ati Amd radeon rx5700
Msi x99a sli plus
Ssd formatted journaled on a mac
-
2922E5F7-C760-4A8E-BA32-8F6D21FA10D4.jpeg
3.6 MB
· Views: 40
-
501DDF1D-3284-448D-A80B-2C00E6F5BE92.jpeg
529.3 KB
· Views: 38
-
#2
Hi guys for me its very long ago that i made a build, i am trying to install catalina i made the usb put multibeast on it withous any succes i keep getting this error, (pictures)
Not found while reopening our self handeling
The setup is:
Intel core i7 6800k 3,40ghz
Ati Amd radeon rx5700
Msi x99a sli plus
Ssd formatted journaled on a mac
I have moved your post to Desktop Support
As per rules, please update your hardware profile to allow others to help you easier
-
#3
Hi guys for me its very long ago that i made a build, i am trying to install catalina i made the usb put multibeast on it withous any succes i keep getting this error, (pictures)
Not found while reopening our self handeling
The setup is:
Intel core i7 6800k 3,40ghz
Ati Amd radeon rx5700
Msi x99a sli plus
Ssd formatted journaled on a mac
Hi Geert,
First of all welcome back! 10 years as a member is a long-time!
As to the issue of it not booting, I am guessing you’re not aware of some of the changes made to macOS in recent years. Since Mojave, memory access has been further restricted by Apple, which has complicated things on the Hackintosh front. Unfortunately this has meant some tools we used before like Multibeast no longer work for newer setups (although an update of Multibeast is anticipated). Today the community mostly uses the Opencore (OC) boot loader, which was developed by members of the Clover team. Clover is still being developed but not as much as OC.
So about your system you’ll need to look at this general guide here > https://dortania.github.io/OpenCore-Install-Guide/ and follow the guide for Skylake (X99) configuration. Although some of the patches/terms have changed names to reflect those used in macOS natively, it still works very similar to Clover.
If it helps I have a working build here already on Skylake Z170 for Big Sur/Catalina you can look at (or even test) > https://www.tonymacx86.com/threads/…4-ga-z170n-wifi-samsung-860-evo-rx550.313767/
I’m trying to deploy a Django app to Heroku, it starts to build, download and installs everything, but that’s what I get when it comes to collecting static files
$ python manage.py collectstatic --noinput
remote: Traceback (most recent call last):
remote: File "manage.py", line 10, in <module>
remote: execute_from_command_line(sys.argv)
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
remote: utility.execute()
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/__init__.py", line 330, in execute
remote: self.fetch_command(subcommand).run_from_argv(self.argv)
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/base.py", line 390, in run_from_argv
remote: self.execute(*args, **cmd_options)
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/base.py", line 441, in execute
remote: output = self.handle(*args, **options)
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py", line 168, in handle
remote: collected = self.collect()
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py", line 98, in collect
remote: for path, storage in finder.list(self.ignore_patterns):
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/staticfiles/finders.py", line 112, in list
remote: for path in utils.get_files(storage, ignore_patterns):
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/staticfiles/utils.py", line 28, in get_files
remote: directories, files = storage.listdir(location)
remote: File "/app/.heroku/python/lib/python2.7/site-packages/django/core/files/storage.py", line 300, in listdir
remote: for entry in os.listdir(path):
remote: OSError: [Errno 2] No such file or directory: '/app/blogproject/static'
remote:
remote: ! Error while running '$ python manage.py collectstatic --noinput'.
remote: See traceback above for details.
remote:
remote: You may need to update application code to resolve this error.
remote: Or, you can disable collectstatic for this application:
remote:
remote: $ heroku config:set DISABLE_COLLECTSTATIC=1
remote:
remote: https://devcenter.heroku.com/articles/django-assets
remote:
remote: ! Push rejected, failed to compile Python app
remote:
remote: Verifying deploy...
remote:
remote: ! Push rejected to pin-a-voyage.
This is the whole settings.py file
# Build paths inside the project like this: os.path.join(BASE_DIR, ...)
import os
import dj_database_url
BASE_DIR = os.path.dirname(os.path.dirname(__file__))
PROJECT_ROOT = os.path.dirname(os.path.abspath(__file__))
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/1.8/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = '*********************'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
# Application definition
INSTALLED_APPS = (
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'blog',
'custom_user',
'django_markdown',
'parsley',
)
#### AUTH ###
AUTH_USER_MODEL = 'custom_user.CustomUser'
AUTHENTICATION_BACKENDS = (
'custom_user.backends.CustomUserAuth',
'django.contrib.auth.backends.ModelBackend',
# 'django.contrib.auth.backends.RemoteUserBackend',
)
#############
#### EMAIL ###
EMAIL_USE_TLS = True
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_HOST_PASSWORD = '***' #my gmail password
EMAIL_HOST_USER = 'voyage.pin@gmail.com' #my gmail username
DEFAULT_FROM_EMAIL = 'voyage.pin@gmail.com'
SERVER_EMAIL = 'voyage.pin@gmail.com'
EMAIL_PORT = 587
DEFAULT_FROM_EMAIL = EMAIL_HOST_USER
##############
MIDDLEWARE_CLASSES = (
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'django.middleware.security.SecurityMiddleware',
)
ROOT_URLCONF = 'blogproject.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'blogproject.wsgi.application'
# Database
# https://docs.djangoproject.com/en/1.8/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql_psycopg2',
'NAME': 'blogproject',
'USER': '***',
'PASSWORD': '***',
'HOST': 'localhost',
'PORT': '',
}
}
# Internationalization
# https://docs.djangoproject.com/en/1.8/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_L10N = True
USE_TZ = True
# Update database configuration with $DATABASE_URL.
db_from_env = dj_database_url.config(conn_max_age=500)
DATABASES['default'].update(db_from_env)
# Honor the 'X-Forwarded-Proto' header for request.is_secure()
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
# Allow all host headers
ALLOWED_HOSTS = ['*']
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/1.8/howto/static-files/
STATIC_ROOT = os.path.join(PROJECT_ROOT, 'staticfiles')
STATIC_URL = '/static/'
# Extra places for collectstatic to find static files.
STATICFILES_DIRS = (
os.path.join(PROJECT_ROOT, 'static'),
)
# Simplified static file serving.
# https://warehouse.python.org/project/whitenoise/
STATICFILES_STORAGE = 'whitenoise.django.GzipManifestStaticFilesStorage'
This is the structure of the project
blog-project -- blog -- migrations
-- static
-- templates
-- blogproject
-- blogprojectenv
-- custom_user
-- media
-- .git
Any thoughts?
Hi
Having recently upgraded from Cinnamon 19.3 to 20.1 I am getting a bunch of error messages flash up during boot.
I have a dual boot Windows 10/Linux Mint system with Windows on an SSD and Linux root on the SSD and Linux home on a separate HDD drive. I allowed the Mint installation to format the Linux root partition but not the home partition.
The errors I am getting are:
Code: Select all
russell@russell-GA-MA770T-UD3:~$ dmesg | grep -i error
[ 0.160044] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160052] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160058] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160063] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160074] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160079] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160084] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160089] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160100] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160105] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160109] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160115] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160127] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160132] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160138] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160143] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160154] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160160] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160165] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160170] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160182] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160188] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160193] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160198] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160210] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160215] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160220] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160225] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160237] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160242] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160248] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160253] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160265] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160270] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160275] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160280] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160292] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 0.160298] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160303] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160308] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160320] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20190816/dspkginit-438)
[ 0.160325] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20190816/dspkginit-438)
[ 0.160331] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20190816/dspkginit-438)
[ 0.160336] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20190816/dspkginit-438)
[ 1.322389] RAS: Correctable Errors collector initialized.
[ 14.144189] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 14.144373] floppy: error 10 while reading block 0
[ 28.127569] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 28.127573] floppy: error 10 while reading block 0
[ 28.919353] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[ 41.800231] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 41.800243] floppy: error 10 while reading block 0
[ 54.079629] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 54.079634] floppy: error 10 while reading block 0
[ 66.360159] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 66.360171] floppy: error 10 while reading block 0
System information from inixi:
Code: Select all
russell@russell-GA-MA770T-UD3:~$ inxi -F
System: Host: russell-GA-MA770T-UD3 Kernel: 5.4.0-73-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6
Distro: Linux Mint 20.1 Ulyssa
Machine: Type: Desktop System: Gigabyte product: GA-MA770T-UD3 v: N/A serial: <superuser/root required>
Mobo: Gigabyte model: GA-MA770T-UD3 v: x.x serial: <superuser/root required> BIOS: Award v: F7
date: 07/09/2010
CPU: Topology: Quad Core model: AMD Phenom II X4 945 bits: 64 type: MCP L2 cache: 2048 KiB
Speed: 800 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
Graphics: Device-1: NVIDIA GT218 [GeForce 210] driver: nvidia v: 340.108
Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce 210/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108
Audio: Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia driver: snd_hda_intel
Device-2: NVIDIA High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.4.0-73-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:e0:4c:70:45:01
Drives: Local Storage: total: 577.55 GiB used: 69.00 GiB (11.9%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB
Partition: ID-1: / size: 23.40 GiB used: 9.80 GiB (41.9%) fs: ext4 dev: /dev/sda3
ID-2: /home size: 91.54 GiB used: 59.18 GiB (64.7%) fs: ext4 dev: /dev/sdb1
ID-3: /tmp size: 9.04 GiB used: 21.0 MiB (0.2%) fs: ext4 dev: /dev/sdb6
ID-4: swap-1 size: 3.72 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb5
Sensors: System Temperatures: cpu: 30.1 C mobo: N/A gpu: nvidia temp: 38 C
Fan Speeds (RPM): N/A
Info: Processes: 216 Uptime: 4m Memory: 3.84 GiB used: 1.11 GiB (28.9%) Shell: bash inxi: 3.0.38
Can anyone point me towards what is causing this problem and how I can fix it? Everything seems to be working despite the errors but it does slow down the boot.
Thanks
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Laptop: HP17bs086nf, Intel Core i5-7200U, Intel HD Graphics 620 . Mint Cinnamon 20.1
Desktop: Gigabyte GA-MA770T-UD3 motherboard, NVIDIA GeForce 210, AMD Phenom II Quad Core Processor 3GHz, 4GB ram, 120GB SSD, 500GB HDD. Mint Cinnamon 20.1
# (отредактировано 11 месяцев, 4 недели назад) |
|
Темы: 2 Сообщения: 5 Участник с: 18 февраля 2022 |
Доброго времени суток!
Приспичило на днях посмотреть в journalctl и нашёл пару неприятных «надписей»: Вывод journalctl -p 3:
Вывод journalctl -p 2:
Форумчане, дайте знать если это что-то важное и ядро бьётся в конвульсиях моля добить =) P.S: Каждую строчку гуглил, где-то пишут что ничего страшного, другие бьют тревогу. я пони, у меня копыта, не могу и не хочУ |
vs220 |
# |
Темы: 22 Сообщения: 8092 Участник с: 16 августа 2009 |
Ничего страшного нет, ACPI часто ошибки выдает . А watchdog просто при выключении и перезагрузки не останавливается |
alien175 |
# |
Темы: 20 Сообщения: 177 Участник с: 27 декабря 2010 |
acpi ругается на устаревшие таблицы. По факту, они не должны попадать в dmesg (ибо warning), но решили, что лучше отображать и сделать error. у меня:
|
vasek |
# (отредактировано 11 месяцев, 4 недели назад) |
Темы: 47 Сообщения: 11421 Участник с: 17 февраля 2013 |
Согласно DOC значение параметра —priority=3 означает вывод ошибок (error) … и логично предположить, что в идеале этот вывод должен быть пустым.
Если вывод не пустой, то следует понять, что это за ошибка, чем она обусловлена, как влияет на работу системы и как ее можно устронить. Желательно смотреть этот вывод после каждого серъезного обновления системы. В части ошибки
В системе имеется модуль pcspkr В части ошибки
Можно предположить, что cpu имеет поддережку технологии SGX, но в BIOS она не активирована … вот об этом логи и говорят. В части ошибок ACPI — по идее этих ошибок в выводе journalctl -b -p3 —no-pager быть не должно, как правило, ошибки ACPI имеют приоритет warning и выскакивают с уровня p4. Хочешь понять суть плоблемы — больше гугли и читай … EDIT — Дополнение в части ошибок ACPI — ошибки, насколько я понимаю, связаны с методом _GTF — это метод ACPI, который используется для повторной инициализации диска.
Исключить эти ошибки помогает, но не всегда, загрузка с параметром ядра libata.noacpi=1 Ошибки не исчезают с опытом — они просто умнеют |
.
Traceback (most recent call last):
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/backends/base/base.py", line 197, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/sql_server/pyodbc/base.py", line 314, in get_new_connection
timeout=timeout)
pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib 'ODBC Driver 13 for SQL Server' : file not found (0) (SQLDriverConnect)")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "manage.py", line 22, in <module>
main()
File "manage.py", line 18, in main
execute_from_command_line(sys.argv)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/core/management/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/core/management/base.py", line 328, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/core/management/base.py", line 369, in execute
output = self.handle(*args, **options)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 86, in handle
executor = MigrationExecutor(connection, self.migration_progress_callback)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/migrations/executor.py", line 18, in __init__
self.loader = MigrationLoader(self.connection)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/migrations/loader.py", line 49, in __init__
self.build_graph()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/migrations/loader.py", line 212, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/migrations/recorder.py", line 76, in applied_migrations
if self.has_table():
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/migrations/recorder.py", line 56, in has_table
return self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor())
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/backends/base/base.py", line 260, in cursor
return self._cursor()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/sql_server/pyodbc/base.py", line 218, in _cursor
conn = super()._cursor()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/backends/base/base.py", line 236, in _cursor
self.ensure_connection()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/utils.py", line 90, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/django/db/backends/base/base.py", line 197, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/nipponApi/.virtualenvs/nipponapi.pythonanywhere.com/lib/python3.6/site-packages/sql_server/pyodbc/base.py", line 314, in get_new_connection
timeout=timeout)
django.db.utils.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib 'ODBC Driver 13 for SQL Server' : file not found (0) (SQLDriverConnect)")