Skip to content
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

Emby notifications not working #4576

Closed
johnvick opened this issue Jul 5, 2018 · 9 comments
Closed

Emby notifications not working #4576

johnvick opened this issue Jul 5, 2018 · 9 comments
Assignees

Comments

@johnvick
Copy link

johnvick commented Jul 5, 2018

Branch: master
Commit: 7cfc79d5280b719c6288090fb805521dfc0402cd
Version: v0.2.6
Database: 44.11
Python Version: | 2.7.9 (default, Aug 13 2016, 17:56:53) [GCC 4.9.2]
SSL Version: | OpenSSL 1.0.1t 3 May 2016
OS: | Linux-4.9.61+-armv7l-with-debian-8.11
Locale: | en_GB.UTF-8

I haven't changed the IP, port or API of the Emby device but notifications no longer work.

This is in the log:

2018-07-05 22:43:11 WARNING  Thread_34 :: [7cfc79d] EMBY: Warning: Unable to contact Emby at http://**********/emby/Notifications/Admin: 500 Server Error: Internal Server Error for url: http://**********/emby/Notifications/Admin

I think this has just started with the most recent update of Medusa. There haven't been any Emby updates for a couple of weeks. Restarting Emby - no difference.

Restated Medusa and it updated to:

Branch: master
Commit: e7c4ff3bc9a48b47c932b0e40a539d62e3a62f64
Version: v0.2.6
Database: 44.11
Python Version: | 2.7.9 (default, Aug 13 2016, 17:56:53) [GCC 4.9.2]
SSL Version: | OpenSSL 1.0.1t 3 May 2016
OS: | Linux-4.9.61+-armv7l-with-debian-8.11
Locale: | en_GB.UTF-8

But the problem persists.

Thanks for checking out.

@triage-new-issues triage-new-issues bot added the triage Untriaged issue label Jul 5, 2018
@sharkykh sharkykh self-assigned this Jul 5, 2018
@sharkykh
Copy link
Contributor

sharkykh commented Jul 5, 2018

@johnvick
Did you change the Admin username on Emby?

@sharkykh sharkykh added Support and removed triage Untriaged issue labels Jul 5, 2018
@johnvick
Copy link
Author

johnvick commented Jul 5, 2018

No, haven't changed any Emby settings (other than changing the API but this was after the problem arose - but this didn't help).

@sharkykh
Copy link
Contributor

sharkykh commented Jul 5, 2018

I need to look into this more, because I don't have Emby installed to check that.

In any case, that's just the notification test. It should still work for updating the library from Medusa.
If all the other settings for Emby are correct, of course.

@johnvick
Copy link
Author

johnvick commented Jul 5, 2018

It doesn't trigger the Emby library update as it did before when you click the Emby update button on the TV series screen. Emby is otherwise working fine as is the Emby/Kodi plugin setup over multiple devices around the house.

@sharkykh
Copy link
Contributor

sharkykh commented Jul 6, 2018

Please check the Emby logs. I can't reproduce this error.

@johnvick
Copy link
Author

johnvick commented Jul 6, 2018

This is the Emby log in response to sending the test command:
192.168.1.14 runs Medusa
192.168.1.192 runs Emby

*** Error Report ***
	Version: 3.4.1.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Unix 4.9.0.6
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Processor count: 4
	Program data path: /var/lib/emby
	Application directory: /opt/emby-server/system
	System.Runtime.Serialization.SerializationException: Type definitions should start with a '{', expecting serialized type 'AddAdminNotification', got string starting with: ImageUrl=https%3A%2F%2Fcdn.pymedusa.com%2Fimages%2
	   at ServiceStack.Text.Common.DeserializeTypeRefJson.StringToType(TypeConfig typeConfig, String strType, EmptyCtorDelegate ctorFn, Dictionary`2 typeAccessorMap)
	   at ServiceStack.Text.JsonSerializer.DeserializeFromStream(Type type, Stream stream)
	   at Emby.Server.Implementations.Services.ServiceHandler.CreateRequest(HttpListenerHost host, IRequest httpReq, RestPath restPath, Dictionary`2 requestParams)
	   at Emby.Server.Implementations.Services.ServiceHandler.<CreateRequest>d__14.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__13.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__70.MoveNext()
	System.Runtime.Serialization.SerializationException
	   at ServiceStack.Text.Common.DeserializeTypeRefJson.StringToType(TypeConfig typeConfig, String strType, EmptyCtorDelegate ctorFn, Dictionary`2 typeAccessorMap)
	   at ServiceStack.Text.JsonSerializer.DeserializeFromStream(Type type, Stream stream)
	   at Emby.Server.Implementations.Services.ServiceHandler.CreateRequest(HttpListenerHost host, IRequest httpReq, RestPath restPath, Dictionary`2 requestParams)
	   at Emby.Server.Implementations.Services.ServiceHandler.<CreateRequest>d__14.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__13.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__70.MoveNext()
	
2018-07-07 07:20:40.236 Info HttpServer: HTTP Response 500 to 192.168.1.14. Time: 9ms. http://192.168.1.192:8096/emby/Notifications/Admin 

@johnvick
Copy link
Author

johnvick commented Jul 7, 2018

I've tested this again after rebooting every relevant device - I can confirm that the library updates are now working as before, but the test notification still isn't. Probably not a problem with Medusa - thanks for looking into this and sorry if I have wasted your time.

@sharkykh
Copy link
Contributor

sharkykh commented Jul 7, 2018

The log from Emby did help me figure out what I did wrong with the test notification, so it wasn't all for nothing. Thanks :)

@sharkykh
Copy link
Contributor

sharkykh commented Jul 7, 2018

Fixed (on develop) with #4622.

@sharkykh sharkykh closed this as completed Jul 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants