gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

Log unused module configuration entries that cause redis to abort (#132)

Browse Source 
Log unused module configuration entries that cause redis to abort
on startup.

Example:
```
17797:M 31 Mar 2024 12:26:12.146 # Unused Module Configuration: module1.whatever
17797:M 31 Mar 2024 12:26:12.146 # Unused Module Configuration: module2.test
17797:M 31 Mar 2024 12:26:12.146 # Module Configuration detected without loadmodule directive or no ApplyConfig call: aborting
```

Signed-off-by: Gabi Ganam <ggabi@amazon.com>
This commit is contained in:
Gabi Ganam 2024-04-03 02:03:31 +03:00 committed by GitHub
parent c0a83c0058
commit 7a7288b292
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/module.c
View File

@ -12109,6 +12109,13 @@ void moduleLoadFromQueue(void) {
listDelNode(server.loadmodule_queue, ln);
}
if (dictSize(server.module_configs_queue)) {
dictIterator *di = dictGetSafeIterator(server.module_configs_queue);
dictEntry *de;
while ((de = dictNext(di)) != NULL) {
const char *moduleConfigName = dictGetKey(de);
serverLog(LL_WARNING, "Unused Module Configuration: %s", moduleConfigName);
}
dictReleaseIterator(di);
serverLog(LL_WARNING, "Module Configuration detected without loadmodule directive or no ApplyConfig call: aborting");
exit(1);
}