docker-alerta: Alerta not starting after 8.6.2 update
Issue Summary After updating to 8.6.2, alerta is no longer starting. Here is all the logs I get:
ALERTA_CONF_FILE=/app/alerta.conf
ALERTA_SVR_CONF_FILE=/app/alertad.conf
ALERTA_WEB_CONF_FILE=/web/config.json
CLIENT_VERSION=8.5.1
DATABASE_URL=postgres://alerta@alerta_db:5432/monitoring
GPG_KEY=E3FF2839C048B25C084DEBE9B26995E310250568
HEARTBEAT_SEVERITY=major
HK_EXPIRED_DELETE_HRS=2
HK_INFO_DELETE_HRS=12
HOME=/app
HOSTNAME=c58548c5f2f2
LANG=C.UTF-8
PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/venv/bin
PIP_DISABLE_PIP_VERSION_CHECK=1
PIP_NO_CACHE_DIR=1
PWD=/
PYTHONUNBUFFERED=1
PYTHON_GET_PIP_SHA256=c518250e91a70d7b20cceb15272209a4ded2a0c263ae5776f129e0d9b5674309
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/3cb8888cc2869620f57d5d2da64da38f516078c7/public/get-pip.py
PYTHON_PIP_VERSION=21.2.4
PYTHON_SETUPTOOLS_VERSION=57.5.0
PYTHON_VERSION=3.8.12
SERVER_VERSION=8.6.2
SHLVL=0
UWSGI_BUFFER_SIZE=8192
UWSGI_LISTEN=256
UWSGI_PROCESSES=5
WEBUI_VERSION=8.6.0
_=/usr/bin/env
# Create supervisord configuration file.
# Create nginx configuration file.
# Create web configuration file.
nginx: the configuration file /app/nginx.conf syntax is ok
nginx: configuration file /app/nginx.conf test is successful
# Checking versions.
Alerta Server 8.6.2
Alerta Client 8.5.1
Alerta WebUI 8.6.0
nginx version: nginx/1.20.2
uwsgi 2.0.19.1
MongoDB shell version v4.2.17
psql (PostgreSQL) 11.14 (Debian 11.14-0+deb10u1)
Python 3.8.12
Package Version
------------------------ ---------
aiohttp 3.8.1
aiosignal 1.2.0
alerta 8.5.1
alerta-alertops 1.0.0.1
alerta-amqp 5.4.1
alerta-azure-monitor 5.0.2
alerta-cachet 5.0.1
alerta-ding 0.0.1
alerta-enhance 5.3.3
alerta-geoip 5.4.0
alerta-influxdb 5.4.3
alerta-logger 5.3.2
alerta-logstash 5.3.3
alerta-mattermost 1.1.3
alerta-msteams 5.2.1
alerta-normalise 5.3.1
alerta-op5 5.0.2
alerta-opsgenie 5.0.3
alerta-pagerduty 5.3.1
alerta-prometheus 5.4.0
alerta-pubsub 5.2.2
alerta-pushover 5.3.2
alerta-rocketchat 5.0.0
alerta-server 8.6.2
alerta-slack 5.5.2
alerta-sns 5.3.1
alerta-telegram 5.1.3
alerta-twilio 5.4.0
alerta-zabbix 5.1.2
amqp 5.0.6
async-timeout 4.0.1
attrs 21.2.0
bcrypt 3.2.0
blinker 1.4
boto 2.49.0
Brotli 1.0.9
cachetools 4.2.4
certifi 2021.10.8
cffi 1.15.0
chardet 4.0.0
charset-normalizer 2.0.7
click 8.0.3
cryptography 3.4.6
decorator 5.1.0
defusedxml 0.7.1
dnspython 2.1.0
elementpath 2.4.0
Flask 2.0.2
Flask-Compress 1.9.0
Flask-Cors 3.0.10
frozenlist 1.2.0
google-api-core 1.31.4
google-auth 1.35.0
google-cloud-pubsub 2.6.0
googleapis-common-protos 1.53.0
grpc-google-iam-v1 0.12.3
grpcio 1.30.0
httplib2 0.20.2
idna 2.10
importlib-resources 5.4.0
influxdb 5.3.1
itsdangerous 2.0.1
Jinja2 3.0.3
kombu 5.2.2
libcst 0.3.21
lxml 4.6.3
MarkupSafe 2.0.1
matterhook 0.2
mohawk 1.1.0
msgpack 1.0.2
multidict 5.2.0
mypy-extensions 0.4.3
oauth2client 4.1.3
op5lib 1.0
packaging 21.3
pbr 5.8.0
pip 21.1.1
proto-plus 1.19.8
protobuf 3.19.1
psycopg2 2.8.6
pyasn1 0.4.8
pyasn1-modules 0.2.8
pycparser 2.21
PyJWT 2.1.0
pymongo 3.12.1
pymsteams 0.1.16
pyOpenSSL 21.0.0
pyparsing 2.4.7
pysaml2 6.5.1
python-cachetclient 0.2.5
python-dateutil 2.8.1
python-ldap 3.3.1
pytz 2021.1
PyYAML 5.4.1
pyzabbix 1.0.0
requests 2.25.1
requests-hawk 1.1.0
rsa 4.7.2
semantic-version 2.8.5
sentry-sdk 0.19.4
setuptools 59.2.0
six 1.16.0
tabulate 0.8.9
telepot 12.7
termcolor 1.1.0
twilio 6.50.1
typing-extensions 4.0.0
typing-inspect 0.7.1
urllib3 1.26.7
uWSGI 2.0.19.1
vine 5.0.0
Werkzeug 2.0.2
xmlschema 1.8.2
yarl 1.7.2
zipp 3.6.0
Alerta init process complete; ready for start up.
If I try to curl the api endpoint:
$ curl localhost:8080/api
Internal Server Error
Nothing in the logs…
Here are my config files:
$ cat /app/alerta.conf
[DEFAULT]
endpoint = http://localhost:8080/api
key = -sDbuP8C7vFU_O45zGpa_n2SWkOXITZeDvbeeBhH
debug = yes
$ cat app/alertad.conf
DEBUG = True
SECRET = '^Bpa%i8_nCAc8fI4l9)nhn2EG2!@GJga'
AUTH_REQUIRED = True
CUSTOMER_VIEWS = False
AUTH_PROVIDER='ldap'
ADMIN_USERS = ['osterman01', 'carlsson04']
LDAP_URL = 'ldaps://**********' //Hiding due to security..
LDAP_DEFAULT_DOMAIN = '*****'
LDAP_CACERT = '/venv/lib/python3.7/site-packages/alerta/auth/cert.pem'
LDAP_DOMAINS = {
'***l'
}
LDAP_DOMAINS_SEARCH_DN = {
'***'
}
LDAP_DOMAINS_SEARCH_FILTER = {
'***'
}
ALLOWED_ENVIRONMENTS = [
'Infra','CRM','ERP','CIC','Revenue', 'Cloud', 'OpenShift'
]
COLUMNS = ['severity', 'status', 'lastReceiveTime', 'duplicateCount',
'service', 'resource', 'text' ]
I had to hide some information in the config since this is public. But all my configs worked fine in 8.5.0.
Environment
-
OS: Linux
-
API version: 8.6.2
-
Deployment: Docker
-
Database: Postgres
-
Server config: Auth enabled? Yes Auth provider? LDAP Customer views? No (or provide the
/config
endpoint output) -
web UI version: 8.6.2
-
CLI version: 8.6.2
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (16 by maintainers)
Works in both RHEL and OpenShift Environment… 👍 Thanks alot for the help! (In OpenShift I still see this
Listen queue size is greater than the system max net.core.somaxconn (128)
also… so will just have to turn it down to 128 instead of 256… Because I don’t know how we can change it inside OpenShift…)@satterly please see my pull request for this
@satterly thank you 👍 One major change between K8S Core and OpenShift from Red Hat is that you can not do ex. copy/move/create in the container itself… It will fail with read-only errors… We are hoping that Red Hat provides some sort of functionality for this…
Thank you. FYI It doesn’t overwrite my alerta.conf and alertad.conf , only the supervisord.conf.