Closed tim-fiola closed 2 years ago
I am seeing this when I start the containers via invoke debug
: dolt_worker_1 exited with code 2
:
Starting Nautobot in debug mode...
Running docker-compose command "up"
Starting dolt_redis_1 ...
Starting dolt_dolt_1 ...
Starting dolt_redis_1 ... done
Starting dolt_dolt_1 ... done
Starting dolt_nautobot_1 ...
Starting dolt_nautobot_1 ... done
Starting dolt_worker_1 ...
Starting dolt_worker_1 ... done
Attaching to dolt_redis_1, dolt_dolt_1, dolt_nautobot_1, dolt_worker_1
dolt_1 | Starting server with Config HP="0.0.0.0:3306"|U="nautobot"|P="notverysecurepwd"|T="28800000"|R="false"|L="info"
redis_1 | 1:C 01 Nov 2021 22:10:46.335 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 01 Nov 2021 22:10:46.335 # Redis version=6.2.2, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 01 Nov 2021 22:10:46.335 # Configuration loaded
redis_1 | 1:M 01 Nov 2021 22:10:46.336 * monotonic clock: POSIX clock_gettime
redis_1 | 1:M 01 Nov 2021 22:10:46.337 * Running mode=standalone, port=6379.
redis_1 | 1:M 01 Nov 2021 22:10:46.337 # Server initialized
redis_1 | 1:M 01 Nov 2021 22:10:46.338 * DB loaded from append only file: 0.001 seconds
redis_1 | 1:M 01 Nov 2021 22:10:46.338 * Ready to accept connections
dolt_1 | 2021-11-01T22:10:49Z INFO [conn 2] NewConnection {}
dolt_1 | 2021-11-01T22:10:49Z INFO [conn 1] NewConnection {}
worker_1 | Error: -l option requires an argument
dolt_1 | 2021-11-01T22:10:49Z INFO [conn 1] ConnectionClosed {}
dolt_worker_1 exited with code 2
nautobot_1 | Performing database migrations...
dolt_1 | 2021-11-01T22:10:50Z INFO [conn 3] NewConnection {}
nautobot_1 | Operations to perform:
nautobot_1 | Apply all migrations: admin, auth, circuits, contenttypes, dcim, dolt, extras, ipam, sessions, social_django,
worker_1 | Error: -l option requires an argument
Looks like the worker is being started up with the wrong (incomplete?) command. Looking at #130, do you have NAUTOBOT_LOG_LEVEL
defined in your creds.env
file?
I configured the following webhook in the container environment described in the README.md file:
This webhook should fire when a device object is created/updated/deleted. However, nothing fired when I made a change in the version control app container environment: (running
invoke debug
)When I configure the same webhook in the Nautobot dev container environment, the webhook fires and I see this info in the log: (running
invoke debug
)