Hi all, I have my OTRS 2.1.6 running in debug mode and it produces a number of error messages ever since. However, these seem not to indicate real problems. I think. What's bothering me is that OTSR prefixes them with "Error" and if I scan the logs on a regularly basis I do find this messages which in turn do /not/ indicate problems. Ever had a log-file analysis script telling you "Found 83,545,334 errors"? I feel a heart-attack coming :-) Here an example: Debug: Config.pm ->Get('Database::Limit') --> Error: Config.pm No value for 'Database::Limit' in Config.pm found! Use of uninitialized value in concatenation (.) or string at /opt/otrs/Kernel/Config/Defaults.pm line 1697, <PRODUCT> line 4. Debug: Config.pm ->Get('Database::QuoteSingle') --> Error: Config.pm No value for 'Database::QuoteSingle' in Config.pm found! Use of uninitialized value in concatenation (.) or string at /opt/otrs/Kernel/Config/Defaults.pm line 1697, <PRODUCT> line 4. Debug: Config.pm ->Get('Database::QuoteBack') --> Error: Config.pm No value for 'Database::QuoteBack' in Config.pm found! Of course I tried to set these values in Kernel/Config.pm (though 'officially' these are not configuration options). Unfortunately, this does not impress OTRS at all. Anyway, the values are registered in Kernel/System/DB/<db>.pm and I do not see any need at all to store them in Config.pm additionally, since it's the right way to encapsulate these database-specific values in a DB driver module. Though this is no serious error (the system is running well) it is a rather bothering issue with regard to operations. I know, may of you are fighting with functional issues, but any ideas nonetheless? Thanks Tobias -- 21. Never wrestle with a pig. You both get dirty and the pig likes it. -- One of 21 Thoughts to Get You Through Almost Any Crisis