Kumo version : dev build 2024.04.03-c3cf0d46
Environment : AL3
instance type : c5a.large
Question : currently I have set my time zone to local but the logs are genrating as per different timezone, how can I set it to the same time?
Hey there @responsible-porcupin, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.
Logging is a Unix timestamp (UTC). It may be possible to use the date time filter in minijinja
I have not tested this but you may be able to use a date time filter in a custom template
Though I’m not sure how valuable that is. If you are feeding the logs as webhooks to use with a reporting tool, it it probably easier to transform the Unix timestamp in the reporting tool.
These extra filters are supported:
Though that will just change the formatting, not shift the TZ. But I am curious why this is not showing the right time already. It should be reporting based on your server’s time
rust doesn’t generally know things about the timezone, because posix’s interface to that stuff is unsafe. It looks like there is a way to specify the preferred timezone in the format/filter thingy
let me try that
Sorry, but I am looking for a segment creation format as mentioned in the doc it is YYYYMMDD-HHMMSS as per the current time but filename is not getting created as per the local time set in the os.
are @responsible-porcupin and @youthful-zorse asking the same question? (Same person?)
Is this about the log file name or about the format of the timestamp in the log?
I am also checking for the same things, but my question is different reference to this question only
So are you asking about the file name of the log?
yes
@responsible-porcupin is your question about log file names, or about the timestamp inside the logs?
Yes, mike my question is about the time stamp only. and ther is an one more concern of mine I am trying to build from source but I am getting the below error
error[E0599]: no method named standard_name found for reference &SslCipherRef in the current scope
→ crates/rfc5321/src/client.rs:403:40
|
403 | Some(cipher) => cipher.standard_name().unwrap_or(cipher.name()).to_string(),
| ^^^^^^^^^^^^^ method not found in &SslCipherRef
error[E0599]: no method named dane_authority found for reference &SslRef in the current scope
→ crates/rfc5321/src/client.rs:411:53
|
411 | if let Ok(authority) = ssl_stream.ssl().dane_authority() {
| ^^^^^^^^^^^^^^ method not found in &SslRef
error[E0599]: no method named dane_enable found for struct SslConnectorBuilder in the current scope
→ crates/rfc5321/src/client.rs:621:13
|
621 | builder.dane_enable()?;
| ^^^^^^^^^^^ method not found in SslConnectorBuilder
error[E0599]: no method named set_no_dane_ee_namechecks found for struct SslConnectorBuilder in the current scope
→ crates/rfc5321/src/client.rs:622:13
|
622 | builder.set_no_dane_ee_namechecks();
| ^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in SslConnectorBuilder
error[E0599]: no method named dane_enable found for struct ConnectConfiguration in the current scope
→ crates/rfc5321/src/client.rs:628:12
|
628 | config.dane_enable(hostname)?;
| ^^^^^^^^^^^ method not found in ConnectConfiguration
error[E0599]: no method named dane_tlsa_add found for struct ConnectConfiguration in the current scope
→ crates/rfc5321/src/client.rs:631:29
|
631 | let usable = config.dane_tlsa_add(
| -------^^^^^^^^^^^^^ method not found in ConnectConfiguration
If you are building from source we need a lot more info. Can you also please open that question in a separate get-help thread? It is easier to keep these focussed and separated. We will definitely need your OS, environment details, etc.
@responsible-porcupin I think I answered your timestamp question with the minijinja info above.
@youthful-zorse please open a separate thread for the Log file name question
I am working on that