Docker Compose Openvas-1 spam

Community Containers
1

Is it normal that my logs are fully spammed with:

openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.54 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.54 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.54 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.55 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.55 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.56 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.56 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.56 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3
openvas-1              | libgvm util:  DEBUG:2024-10-04 09h59.56 utc:17365:f215bc40-c039-4f6d-b929-5696ef186c10: get_redis_ctx: connected to redis:///run/redis/redis.sock/3

Iā€™d like to know: :slight_smile:

2

By default, the Greenbone Community Containers are setup with debug log level enabled to support developers. You can change by modifying the docker-compose.yml file. There is discussion about accomplishing this in the forum already. :slight_smile:

2 Likes