We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the issue I cannot set the configuration value for mmap_log_buffer_size.
Expected Behavior Tempesta FW starts correctly but currently crashes when the mmap_log_buffer_size configuration parameter is set.
To Reproduce Add the following line to your Tempesta configuration and start the application:
mmap_log_buffer_size 4096;
Configuration file
listen 80; server localhost:8000; access_log dmesg mmap mmap_host=localhost mmap_log=/tmp/access.log; mmap_log_buffer_size 4096;
Version or commit hash 80598c9
Stacktrace or debug log
[23215.774224] Start test: t_clickhouse.test_clickhouse_logs.TestClickhouseLogsBaseTest2.test_missing_log [23215.933958] [tdb] Start Tempesta DB [23215.952773] [tempesta fw] Initializing Tempesta FW kernel module... [23216.038606] [tempesta fw] ERROR: the first character is not a letter: '4' [23216.038609] [tempesta fw] ERROR: syntax error [23216.038611] [tempesta fw] ERROR: configuration parsing error: 5: 4096; ^^^^^^^^^^^^^^^^^ [23216.038613] [tempesta fw] Warning: Configuration parsing has failed. Clean up... [23216.086674] [tempesta fw] exiting... [23216.180309] [tdb] Shutdown Tempesta DB
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the issue
I cannot set the configuration value for mmap_log_buffer_size.
Expected Behavior
Tempesta FW starts correctly but currently crashes when the mmap_log_buffer_size configuration parameter is set.
To Reproduce
Add the following line to your Tempesta configuration and start the application:
Configuration file
Version or commit hash
80598c9
Stacktrace or debug log
The text was updated successfully, but these errors were encountered: