-
-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
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
newsletter not working, linux #2739
Comments
So the newsletter triggers on a set schedule. Every Friday IIRC. You can change this in the jobs setting page. You can also press trigger now to trigger the newsletter. |
Thanks tidusjar, |
What's in your log file when this happens? |
Can you point me to where logs are located? I assumed they would be in /opt/Ombi but i see nothing, or is it in the webinterface somewhere? |
There is a logs directory where ombi is installed |
well never assume anything. after running "dpkg -L ombi" I can see logs are actually in /etc/Ombi/Logs. I did trigger a newsletter to run now as well as tried the test option. Log isn't updating with those. Log file is there and I see a few of these: but nothing to indicate that a newsletter job was initiated. Also I remembered you said it will automatically trigger a newsletter every friday. Well fridays logs were actually empty. I'm going to uninstall Ombi and install the hardway. I'll report back |
Okay this time I installed from the tarball https://github.com/tidusjar/Ombi/releases/download/v3.0.4119/linux.tar.gz this is basically the same thing. installing this way does put the Logs folder and Ombi.db* into /opt/Ombi. The result is the same however, newsleter doesnt initiate and nothing in the Logs for me to troubleshoot. |
This is the only thing i see in a logfile: Newtonsoft.Json.JsonSerializationException: Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Gene$ |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Felt like revisiting after the numerous updates to Ombi to see if the newsletter works on linux. I do actually see something of value here. 2019-10-12 20:26:22.610 -04:00 [Debug] Calling Execute on job System.INewsletterJob The newsletter is still not being sent however. The email is working, This is just a test! Success! any ideas with that info in logfile? |
Very strange, are items being marked as available in Ombi automatically? Are using receiving the availability notification? |
Yes to both of those. Do you have any idea on the errors I posted. I decided to look in /var/log/syslog and there are more here, thought could be unrelated.
|
Run build 4887
…On Sat, 16 Nov 2019, 1:54 pm amanalar, ***@***.***> wrote:
Yes to both of those. Do you have any idea on the errors I posted.
I decided to look in /var/log/syslog and there are more here, thought
could be unrelated.
Nov 16 08:30:00 SERVER Ombi[1535]: Microsoft.Data.Sqlite.SqliteException
(0x80004005): SQLite Error 1: 'no such column: x.RequestId'. Nov 16
08:30:00 SERVER Ombi[1535]: at
Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3
db) Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements(Stopwatch
timer)+MoveNext() Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior
behavior, CancellationToken cancellationToken) Nov 16 08:30:00 SERVER
Ombi[1535]: at
Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior
behavior, CancellationToken cancellationToken) Nov 16 08:30:00 SERVER
Ombi[1535]: at
Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.ExecuteAsync(IRelationalConnection
connection, DbCommandMethod executeMethod, IReadOnlyDictionary2
parameterValues, CancellationToken cancellationToken)
Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable1.AsyncEnumerator.BufferlessMoveNext(DbContext
_, Boolean buffer, CancellationToken cancellationToken) Nov 16 08:30:00
SERVER Ombi[1535]: at
Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable1.AsyncEnumerator.MoveNext(CancellationToken
cancellationToken)
Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.AsyncSelectEnumerable2.AsyncSelectEnumerator.MoveNext(CancellationToken
cancellationToken) Nov 16 08:30:00 SERVER Ombi[1535]: at
System.Linq.AsyncEnumerable.FirstOrDefault_[TSource](IAsyncEnumerable1
source, CancellationToken cancellationToken) in
D:\a\1\s\Ix.NET\Source\System.Interactive.Async\First.cs:line 144
Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.TaskResultAsyncEnumerable1.Enumerator.MoveNext(CancellationToken
cancellationToken) Nov 16 08:30:00 SERVER Ombi[1535]: at
System.Linq.AsyncEnumerable.SelectEnumerableAsyncIterator2.MoveNextCore(CancellationToken
cancellationToken) in
D:\a\1\s\Ix.NET\Source\System.Interactive.Async\Select.cs:line 106
Nov 16 08:30:00 SERVER Ombi[1535]: at
System.Linq.AsyncEnumerable.AsyncIterator1.MoveNext(CancellationToken
cancellationToken) in
D:\a\1\s\Ix.NET\Source\System.Interactive.Async\AsyncIterator.cs:line 98
Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.ExceptionInterceptor1.EnumeratorExceptionInterceptor.MoveNext(CancellationToken
cancellationToken)
Nov 16 08:30:00 SERVER Ombi[1535]: at
Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.ExecuteSingletonAsyncQuery[TResult](QueryContext
queryContext, Func2 compiledQuery, IDiagnosticsLogger1 logger, Type
contextType)
Nov 16 08:30:00 SERVER Ombi[1535]: at
Ombi.Store.Repository.PlexServerContentRepository.GetFirstContentByCustom(Expression1
predicate) in
C:\projects\requestplex\src\Ombi.Store\Repository\PlexContentRepository.cs:line
90 Nov 16 08:30:00 SERVER Ombi[1535]: at
Ombi.Schedule.Jobs.Plex.PlexContentSync.ProcessServer(PlexServers servers,
Boolean recentlyAddedSearch) in
C:\projects\requestplex\src\Ombi.Schedule\Jobs\Plex\PlexContentSync.cs:line
246 Nov 16 08:30:00 SERVER Ombi[1535]:
#33[41m#033[30mfail#033[39m#033[22m#033[49m:
Ombi.Schedule.Jobs.Plex.PlexContentSync[2008] Nov 16 08:30:00 SERVER
Ombi[1535]: Exception when adding new Movie Operation Condor
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2739>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSVULHQ2HCRG2VOM3JZN2TQT73Q7ANCNFSM4GQQQWQQ>
.
|
This is how my setup looks right now
` |
I'm running into the same problem... Newsletter runs if manually triggered, but does not run automatically. I noticed this started more a month or so ago. The last time mine automatically triggered was on Sept 20, 2019. I'm not sure what version I was on back then. Below are the logs from this past Friday when it tried to execute: 2019-11-29 12:00:20.908 -05:00 [Information] Quartz scheduler 'DefaultQuartzScheduler' initialized I'm guessing the issue has something to do with the Quartz scheduler? I'm running my instance (version 3.0.4892) in an x64 Linux 4.19.41-Unraid #1 SMP docker container. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Just wanted to bump this as I'm having the same issue, the newsletter works when manually run but not automatically. Running Ombi version 4.0.1131 installed through apt if that helps (Ubuntu 20.04.2 LTS). Would having Requestrr installed as well cause issues if it makes Ombi think that movies have already been announced to people? |
Ombi build Version:
v3.0.4119/linux-arm64.tar.gz
(The easy Way)
Update Branch:
Master
Media Sever:
Plex
Media Server Version:
Version 1.14.1.5488
Operating System:
ubuntu-18.04.1.0
Ombi Applicable Logs (from /logs/ directory or the Admin page):
Problem Description:
Newsletter not working, no idea how to troubleshoot
Reproduction Steps:
smtp set up with gmail. test emails working ok. user forgot password email working.
updated database, test user with admin role and receives newsletter role.
added new content from request. went for lunch ombi reports content available.
From some initial searching is the linux ombi different. some of the screenshots i've dont look like what i have.
The text was updated successfully, but these errors were encountered: