I'm getting the following error from the E-mail Log Alerts script:
tail: cannot open '/mnt/ip_redacted-8089_logs/data/channels-dvr.log' for reading: No such file or directory
I can see the logs on the CDVR browser UI at http://ip_redacted:8089/admin/log
What are you using for your LOGS_SHARE value?
/mnt/c/CHANNELS_DVR/Logs
I'm curious: in my CDVR installation I have ~Logs/comskip, ~Logs/recording, and I see a big log file at http://ip_redacted:8089/admin/log. What are the differences between these logs, and which one(s) do the Email Log Alerts draw from?
There is a Logs directory in with your recordings, but that's for Comskip and recording logs -- that's not the one you want. I've posted to you a couple of times about this:
Also @Edwin_Perez gave you the values he uses, and your LOGS_SHARE will very likely be the same. You can translate his Windows path to a WSL path if you like. But either way use the Filtered Log Action described above to verify:
Has anyone gotten any emails from this? I put in mine along with the app password and I haven't been getting any updates from it
If you're talking about email log alerts, that was just recently fixed in the new version
I already got that version. I'm not getting any emails on that nor the channel changes
Not too sure what I'm doing wrong
EDIT: Wait a minute. I forgot to map the Program Data folder and also forgot an argument on the Channel Changes script. Yay 
I'm still having only intermittent emails from the Log Alerts script. It sounds like some fixes have been pushed but I'm not sure I have them fully pulled and deployed. In the upper left corner of OT there is a date displayed. Can I tell from this date if I am running the latest?
You have the latest version of OliveTin.
Log alerts appear to be working fine for me. Can you give me an example of an alert you believe should have triggered an e-mail -- but didn't?
Some supporting detail, including your settings for the Log Alerts Action, along with output from the Filtered Logs Action showing the specific log lines using the same keywords would be very helpful.
I started the Log Alerts script last night at 8:27 PM (Pic1).
I got the expected email about 2 minutes later (Pic2). I am using the partial word "etch" for the filter pattern as I find I get a lot of (F|f)etch(ing) log entries without having to otherwise stimulate the system.
I let the script run all night. No new emails even though in the morning the log file shows lots of entries with "etch" in it (Pic3, Pic4)
I am also running the Channel Lineup Notifications script. It was working fine a while back but now I don't even get an email when I start it up. I don't know if these problems are related but I think the CLN script email stopped when I pulled the recent email fixes.
I know you are busy and I appreciate your help, so no rush and thanks.
Sounds exactly like the problem that was fixed with the last update.
I trust you have the following two environment variables set to true (yes, the value needs to be lowercase) in your OliveTin Portainer stack:
If that's not the issue, I should have more for you tomorrow, as I'm running some tests now...
For what it's worth, I have been running the email log alerts, with the filter of "[DVR] Error", and the Channel Line Up Changes routines since the last Olivetin update. They have both been consistently sending appropriate notifications by email. 
Yes, I checked and found this:
I'm a Docker/Portainer noob so I probably have something screwed up.
Does your OT screen show the 2024.07.23 date in the upper left corner as shown in my earlier post?
They’re not in your junk/spam folder are they? A filter as broad as “etch” is bound to trigger lots of emails.
What did you set the E-Mail Log Alerts frequency to?
Default is once 2 minutes
Edited: Default is 2 minutes
Don't feel too bad about being a "noob". I'm fairly new to all of this, too. Yep, I have the same date on Olivetin. I was having problems just prior to that date. This recent update fixed it. After I updated Olivetin by running Watchtower, I cancelled each of the notification tasks and then re-deployed them. So far, so good.
There's some amazing help/support in this community. You'll get it figured out! 
Yes, my default was pre-populated with 2 minutes. I did not re-enter it, I let it stand as presented. Do I have to re-type it in? I assumed not.
