# Log exceptions of concern
**URL:** https://gramps.discourse.group/t/log-exceptions-of-concern/4799
**Category:** Gramps Web
**Tags:** websolutions
**Created:** [February 3, 2024, 3:53pm UTC](https://gramps.discourse.group/t/log-exceptions-of-concern/4799 "2024-02-03T15:53:42Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@joea](https://gramps.discourse.group/u/joea)
#### Post date: [February 3, 2024, 3:53pm UTC](https://gramps.discourse.group/t/log-exceptions-of-concern/4799/1 "2024-02-03T15:53:42Z")
Gramps 5.1.6
Gramps Web API 1.5.1
Gramps Web Frontend 24.1.2
locale: en
multi-tree: false
task queue: true
Logs seen on initial ‘docker-control up -d’ concerns highlighted.
joea@Gramps-Dock:~\> docker-compose logs -f
joea-grampsweb-1 | INFO [alembic.runtime.migration] Context impl SQLiteImpl.
joea-grampsweb-1 | INFO [alembic.runtime.migration] Will assume non-transactional DDL.
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [12] [INFO] Starting gunicorn 21.2.0
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [12] [INFO] Listening at: [http://0.0.0.0:5000](http://0.0.0.0:5000) (12)
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [12] [INFO] Using worker: sync
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [13] [INFO] Booting worker with pid: 13
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [14] [INFO] Booting worker with pid: 14
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [15] [INFO] Booting worker with pid: 15
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [16] [INFO] Booting worker with pid: 16
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [17] [INFO] Booting worker with pid: 17
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [18] [INFO] Booting worker with pid: 18
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [19] [INFO] Booting worker with pid: 19
joea-grampsweb-1 | [2024-02-03 15:20:36 +0000] [20] [INFO] Booting worker with pid: 20
grampsweb\_celery | INFO [alembic.runtime.migration] Context impl SQLiteImpl.
grampsweb\_celery | INFO [alembic.runtime.migration] Will assume non-transactional DDL.
grampsweb\_celery | /usr/local/lib/python3.11/dist-packages/celery/platforms.py:829: SecurityWarning: You’re running the worker with superuser privileges: this is
grampsweb\_celery | absolutely not recommended!
grampsweb\_celery |
grampsweb\_celery | Please specify a different user using the --uid option.
grampsweb\_celery |
grampsweb\_celery | User information: uid=0 euid=0 gid=0 egid=0
grampsweb\_celery |
grampsweb\_celery | warnings.warn(SecurityWarning(ROOT\_DISCOURAGED.format(
grampsweb\_celery |
grampsweb\_celery | -------------- celery@dd2fd5531e1a v5.3.6 (emerald-rush)
grampsweb\_celery | — \*\*\*\*\* -----
grampsweb\_celery | – \*\*\*\*\*\*\* ---- Linux-5.14.21-150500.55.44-default-x86\_64-with-glibc2.36 2024-02-03 15:20:40
grampsweb\_celery | - \*\*\* — \* —
grampsweb\_celery | - \*\* ---------- [config]
grampsweb\_celery | - \*\* ---------- .\> app: default:0x7f3185184a90 (.default.Loader)
grampsweb\_celery | - \*\* ---------- .\> transport: redis://grampsweb\_redis:6379/0
grampsweb\_celery | - \*\* ---------- .\> results: redis://grampsweb\_redis:6379/0
grampsweb\_celery | - \*\*\* — \* — .\> concurrency: 1 (prefork)
grampsweb\_celery | – \*\*\*\*\*\*\* ---- .\> task events: OFF (enable -E to monitor tasks in this worker)
grampsweb\_celery | — \*\*\*\*\* -----
grampsweb\_celery | -------------- [queues]
grampsweb\_celery | .\> celery exchange=celery(direct) key=celery
grampsweb\_celery |
grampsweb\_celery |
grampsweb\_celery | [tasks]
grampsweb\_celery | . gramps\_webapi.api.tasks.export\_db
grampsweb\_celery | . gramps\_webapi.api.tasks.export\_media
grampsweb\_celery | . gramps\_webapi.api.tasks.generate\_report
grampsweb\_celery | . gramps\_webapi.api.tasks.import\_file
grampsweb\_celery | . gramps\_webapi.api.tasks.import\_media\_archive
grampsweb\_celery | . gramps\_webapi.api.tasks.media\_ocr
grampsweb\_celery | . gramps\_webapi.api.tasks.search\_reindex\_full
grampsweb\_celery | . gramps\_webapi.api.tasks.search\_reindex\_incremental
grampsweb\_celery | . gramps\_webapi.api.tasks.send\_email\_confirm\_email
grampsweb\_celery | . gramps\_webapi.api.tasks.send\_email\_new\_user
grampsweb\_celery | . gramps\_webapi.api.tasks.send\_email\_reset\_password
grampsweb\_celery |
grampsweb\_celery | [2024-02-03 15:20:40,476: WARNING/MainProcess] /usr/local/lib/python3.11/dist-packages/celery/worker/consumer/consumer.py:507: CPendingDeprecationWarning: The broker\_connection\_retry configuration setting will no longer determine
grampsweb\_celery | whether broker connection retries are made during startup in Celery 6.0 and above.
grampsweb\_celery | If you wish to retain the existing behavior for retrying connections on startup,
grampsweb\_celery | you should set broker\_connection\_retry\_on\_startup to True.
grampsweb\_celery | warnings.warn(
grampsweb\_celery |
grampsweb\_celery | [2024-02-03 15:20:40,548: INFO/MainProcess] Connected to redis://grampsweb\_redis:6379/0
grampsweb\_celery | [2024-02-03 15:20:40,550: WARNING/MainProcess] /usr/local/lib/python3.11/dist-packages/celery/worker/consumer/consumer.py:507: CPendingDeprecationWarning: The broker\_connection\_retry configuration setting will no longer determine
grampsweb\_celery | whether broker connection retries are made during startup in Celery 6.0 and above.
grampsweb\_celery | If you wish to retain the existing behavior for retrying connections on startup,
grampsweb\_celery | you should set broker\_connection\_retry\_on\_startup to True.
grampsweb\_celery | warnings.warn(
grampsweb\_celery |
grampsweb\_celery | [2024-02-03 15:20:40,560: INFO/MainProcess] mingle: searching for neighbors
grampsweb\_celery | [2024-02-03 15:20:41,571: INFO/MainProcess] mingle: all alone
grampsweb\_celery | [2024-02-03 15:20:41,585: INFO/MainProcess] celery@dd2fd5531e1a ready.
grampsweb\_redis | 1:C 03 Feb 2024 15:20:24.951 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see [vm.max\_map\_count growing steadily when vm.overcommit\_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub](https://github.com/jemalloc/jemalloc/issues/1328). To fix this issue add ‘vm.overcommit\_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit\_memory=1’ for this to take effect.
grampsweb\_redis | 1:C 03 Feb 2024 15:20:24.951 \* oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
grampsweb\_redis | 1:C 03 Feb 2024 15:20:24.951 \* Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started
grampsweb\_redis | 1:C 03 Feb 2024 15:20:24.951 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.951 \* monotonic clock: POSIX clock\_gettime
grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.952 \* Running mode=standalone, port=6379.
grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.952 \* Server initialized
grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.952 \* Ready to accept connections tcp
mps version and Operating System)
---
### Author:  [@DaveSch](https://gramps.discourse.group/u/DaveSch)
#### Post date: [February 3, 2024, 4:59pm UTC](https://gramps.discourse.group/t/log-exceptions-of-concern/4799/2 "2024-02-03T16:59:18Z")
Please use the **Gramps Web** category. The Gramps web API are unique help requests separate from the Gramps Project’s Help category.
---
### Author:  [@joea](https://gramps.discourse.group/u/joea)
#### Post date: [February 3, 2024, 6:20pm UTC](https://gramps.discourse.group/t/log-exceptions-of-concern/4799/3 "2024-02-03T18:20:56Z")
Is that for future reference, or an action I must take? It appears now in “Gramps Web”, did you move it for me?
---
### Author:  [@emyoulation](https://gramps.discourse.group/u/emyoulation)
#### Post date: [February 3, 2024, 6:24pm UTC](https://gramps.discourse.group/t/log-exceptions-of-concern/4799/4 "2024-02-03T18:24:46Z")
> [@joea](#):
>
> did you move it for me?
Yes. Dave moved the topic to “Gramps Web”. That was, indeed, for future reference.
---
### Author:  [@joea](https://gramps.discourse.group/u/joea)
#### Post date: [February 4, 2024, 5:35pm UTC](https://gramps.discourse.group/t/log-exceptions-of-concern/4799/5 "2024-02-04T17:35:28Z")
> [@joea](#):
>
> grampsweb\_redis | 1:C 03 Feb 2024 15:20:24.951 \* Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started
> grampsweb\_redis | 1:C 03 Feb 2024 15:20:24.951 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
> grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.951 \* monotonic clock: POSIX clock\_gettime
> grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.952 \* Running mode=standalone, port=6379.
> grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.952 \* Server initialized
> grampsweb\_redis | 1:M 03 Feb 2024 15:20:24.952 \* Ready to accept connections tcp
> mps version and Operating System)
The memory overcommit error is gone, with application of the fix suggested in the log, but the missing config file message continues.
I see many mentions of this in other posts, but did not notice a “fix” or it being noted as a “cosmetic” issue.
---
### Author:  [@system](https://gramps.discourse.group/u/system)
#### Post date: [March 5, 2024, 5:35pm UTC](https://gramps.discourse.group/t/log-exceptions-of-concern/4799/6 "2024-03-05T17:35:34Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.