Can't start kodi via kodi.service supplied by kodi-standalone-service

rbellamy · 2015-01-22 01:41:15

I got past the same issue found here. Now I'm flummoxed by a failure to start kodi.

Journal looks something like this:

Jan 19 16:22:58 lamassu systemd[1]: Starting user-420.slice.
Jan 19 16:22:58 lamassu systemd[1]: Created slice user-420.slice.
Jan 19 16:22:58 lamassu systemd[1]: Starting Session c1 of user kodi.
Jan 19 16:22:58 lamassu systemd[1]: Started Session c1 of user kodi.
Jan 19 16:22:58 lamassu systemd[1]: Starting User Manager for UID 420...
Jan 19 16:22:58 lamassu systemd[373]: pam_unix(systemd-user:session): session opened for user kodi by (uid=0)
Jan 19 16:22:58 lamassu systemd[373]: Starting Timers.
Jan 19 16:22:58 lamassu systemd[373]: Reached target Timers.
Jan 19 16:22:58 lamassu systemd[373]: Starting Paths.
Jan 19 16:22:58 lamassu systemd[373]: Reached target Paths.
Jan 19 16:22:58 lamassu systemd[373]: Starting Sockets.
Jan 19 16:22:58 lamassu systemd[373]: Reached target Sockets.
Jan 19 16:22:58 lamassu systemd[373]: Starting Basic System.
Jan 19 16:22:58 lamassu systemd[373]: Reached target Basic System.
Jan 19 16:22:58 lamassu systemd[373]: Starting Default.
Jan 19 16:22:58 lamassu systemd[373]: Reached target Default.
Jan 19 16:22:58 lamassu systemd[373]: Startup finished in 8ms.
Jan 19 16:22:58 lamassu systemd[1]: Started User Manager for UID 420.
Jan 19 16:22:58 lamassu systemd[1]: Started Samba NetBIOS name server.
Jan 19 16:22:58 lamassu systemd[1]: Starting Samba SMB/CIFS server...
Jan 19 16:22:58 lamassu systemd[1]: Started Samba SMB/CIFS server.
Jan 19 16:22:58 lamassu systemd[1]: Starting Multi-User System.
Jan 19 16:22:58 lamassu systemd[1]: Reached target Multi-User System.
Jan 19 16:22:58 lamassu systemd[1]: Starting Graphical Interface.
Jan 19 16:22:58 lamassu systemd[1]: Reached target Graphical Interface.
Jan 19 16:22:58 lamassu systemd[1]: Startup finished in 1.539s (kernel) + 6.979s (userspace) = 23.149s.
Jan 19 16:22:58 lamassu systemd[1]: Starting Avahi mDNS/DNS-SD Stack Activation Socket.
Jan 19 16:22:58 lamassu systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Jan 19 16:22:58 lamassu systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Jan 19 16:22:58 lamassu systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jan 19 16:23:13 lamassu systemd[1]: kodi.service: main process exited, code=exited, status=1/FAILURE
Jan 19 16:23:13 lamassu systemd[1]: Unit kodi.service entered failed state.
Jan 19 16:23:13 lamassu systemd[1]: kodi.service failed.
Jan 19 16:23:13 lamassu systemd[1]: Stopping User Manager for UID 420...
Jan 19 16:23:13 lamassu systemd[373]: Stopping Default.
Jan 19 16:23:13 lamassu systemd[373]: Stopped target Default.
Jan 19 16:23:13 lamassu systemd[373]: Starting Shutdown.
Jan 19 16:23:13 lamassu systemd[373]: Reached target Shutdown.
Jan 19 16:23:13 lamassu systemd[373]: Stopping Basic System.
Jan 19 16:23:13 lamassu systemd[373]: Stopped target Basic System.
Jan 19 16:23:13 lamassu systemd[373]: Starting Exit the Session...
Jan 19 16:23:13 lamassu systemd[373]: Stopping Paths.
Jan 19 16:23:13 lamassu systemd[373]: Stopped target Paths.
Jan 19 16:23:13 lamassu systemd[373]: Stopping Sockets.
Jan 19 16:23:13 lamassu systemd[373]: Stopped target Sockets.
Jan 19 16:23:13 lamassu systemd[373]: Stopping Timers.
Jan 19 16:23:13 lamassu systemd[373]: Stopped target Timers.
Jan 19 16:23:13 lamassu systemd[373]: Received SIGRTMIN+24 from PID 387 (kill).
Jan 19 16:23:13 lamassu systemd[1]: Stopped User Manager for UID 420.
Jan 19 16:23:13 lamassu systemd[1]: Stopping user-420.slice.
Jan 19 16:23:13 lamassu systemd[1]: Removed slice user-420.slice.

So you can see systemd starting up the user session (here its PID 373).

Kodi doesn't log anything to /var/lib/kodi/.local/share/xorg/Xorg.0.log or to /var/lib/kodi/.kodi/temp/*.log or to the journal indicating why it dies with "kodi.service: main process exited, code=exited, status=1/FAILURE".

I cannot find anything in the logs indicating what PID 387 is, or why it's issuing a SIGTRMIN.

graysky · 2015-01-22 09:56:21

Permissions (recursive) on /var/log/kodi correct? Anything unsusal about your setup? Is Arch or an Arch clone like Arch ARM?

rbellamy · 2015-01-22 23:57:00

Thanks @graysky. Specifically for your help here, and more generally for the work you've done for the community with XBMC and now Kodi. I really believe we wouldn't be here without you...

From your readme.install, I'm guessing you meant "/var/lib/kodi" rather than "/var/log/kodi"? And yes, I had bad permissions on "/var/lib/kodi/.kodi", however, the service still won't start as expected, but now I'm getting an Xorg.0.log...

The only thing that might be unusual is that I originally ran through numerous custom builds of XBMC + VDPAU libs to try and get HW Acceleration working (still doesn't work) on my Sapphire Radeon HD 7750. I'm running on Gigabyte H87M-D3H Motherboard with an Intel Core i3-4130T CPU.

I made sure to clear all the cruft from those custom builds BEFORE I attempted the upgrade, as I'd been running the vanilla build of XBMC for about three months.

My Xorg.0.log can be found here.

The pertinent portion (I think, you tell me?) is:

....
[233791.567] (II) LoadModule: "ramdac"
[233791.567] (II) Module "ramdac" already built-in
[233791.567] (--) Depth 24 pixmap format is 32 bpp
[233791.567] Unable to retrieve master
[233791.567] (EE) 
Fatal server error:
[233791.567] (EE) AddScreen/ScreenInit failed for driver 0
...

graysky · 2015-01-23 00:39:10

Not sure about your error, but the readme.install doesn't say log at all... are you using 1.8-1?

Knute · 2015-01-23 00:56:23

If you log in normally, and then try to start kodi manually, not with the standalone service, does it start?

I'm thinking that maybe the service is fine, but something with kodi is messed up?

rbellamy · 2015-01-23 01:58:11

graysky wrote:

Permissions (recursive) on /var/log/kodi correct? Anything unsusal about your setup? Is Arch or an Arch clone like Arch ARM?

And, yes, I'm using 1.8-1.

I'm going to try kodi, by itself, again. Maybe this time, now that I've fixed the bad permissions, I can better see what's going on...

graysky · 2015-01-23 09:53:14

The permissions only affect the kodi user, not any other user since any system user can run /usr/bin/kodi from X. If you log in to your DE and just run it as yo ur user, does it load? If so, I don't see what is keeping the kodi user and standalone service from working again assuming you have the correct permissions on the homedir and files within.

rbellamy · 2015-01-28 01:47:18

I can start kodi-standalone via the command line as root.

Knute · 2015-01-28 01:49:40

What errors do you get when you try to run it as the kodi user?

rbellamy · 2015-01-28 02:38:51

I've compared Xorg logs from my success, and one from a failure:

58 [427808.133] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 9 p»|   55 [698283.773] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 8 »
59 [427808.133] (II) xfree86: Adding drm device (/dev/dri/card0)            |   56 [698283.773] (EE) Error systemd-logind returned paused fd for drm node  
60 [427808.133] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 »|   57 [698283.773] (II) systemd-logind: releasing fd for 226:1

On the left is the one from a successful launch of kodi-standalone as root, and on the right is comparable lines of a failed launch via systemd via PAMName login (logind).

2015-01-27 18:20:56
root@lamassu i /var/log # ls -alh /dev/dri/
total 0
drwxr-xr-x   2 root root       160 Jan 19 16:22 .
drwxr-xr-x  20 root root      3.3K Jan 22 09:11 ..
crw-rw----+  1 root video 226,   0 Jan 19 16:22 card0
crw-rw----+  1 root video 226,   1 Jan 19 16:22 card1
crw-rw----   1 root video 226,  64 Jan 19 16:22 controlD64
crw-rw----   1 root video 226,  65 Jan 19 16:22 controlD65
crw-rw----+  1 root video 226, 128 Jan 19 16:22 renderD128
crw-rw----+  1 root video 226, 129 Jan 19 16:22 renderD129
2015-01-27 18:25:20
root@lamassu i /var/log # groups kodi
network video audio optical kodi

And there are the permissions and group memberships for the kodi user. I'm reading that to mean that kodi should have the rights necessary to get and hold a rw fd on /dev/dri/card1...

rbellamy · 2015-01-28 02:43:12

I added "needs_root_rights=yes" to Xwrapper.config and it starts right up.

Now I guess the question is why I need that - presumably that was obviated by the recent changes.

graysky · 2015-01-28 09:51:46

rbellamy wrote:

I can start kodi-standalone via the command line as root.

I think you misunderstand. This is a systemd service. Only root can start it. You should not try running it as any other user since the systemd service knows to run as the di user. You should not need the Xwrapper with version 18-1 of this package. Please try running the service via 'sudo systemctl start kodi' or starting it at boot by enabling the service, and report back.

rbellamy · 2015-01-28 23:18:07

I guess I'm just being unclear. I understand systemd and how to enable and start a service.

I start the kodi.service unit via systemctl, as root. I get the errors I've shown when I do that.

I've enabled the service. It won't start unless I've got the "needs_root_rights=yes" in Xwrapper.config.

I've got the newest version of the package, which is 18-1.

I was asked to see if kodi could even start at all. Hence my starting kodi-standalone via xinit as root - this proves that all things being equal kodi CAN run on the system. That lends credence to the idea that the issue is one of permission, not missing deps or hardware problems or something similar.

I show the side-by-side Xorg.0.log, one on the left created by a successful launch of kodi-standalone as root via xinit at the command line, the one on the right created when starting kodi via the systemd service unit. This is to further troubleshoot the difference in running conditions between success and failure.

I wonder why kodi, running as the systemd service unit, can't get a file descriptor to /dev/dri/card1 (226,1)???

I know I "shouldn't" need the "needs_root_rights=yes" but that is what I did to make things work.

graysky · 2015-01-28 23:46:22

Sorry, I must have gotten confused when I read your reply. In any case, glad you found a solution. I don't understand what is going wrong on your system that requires it.

Last edited by graysky (2015-01-28 23:47:50)

rbellamy · 2015-01-29 23:27:41

graysky wrote:

Sorry, I must have gotten confused when I read your reply. In any case, glad you found a solution. I don't understand what is going wrong on your system that requires it.

No worries, I'm just happy to have you take a critical look at what I'm doing. I was serious about the thanks + kudos earlier.

I'm still baffled by the need for the Xwrapper.config, but it's working so I'm going to mark this as solved.

caotic · 2015-07-18 17:13:27

rbellamy wrote:

I added "needs_root_rights=yes" to Xwrapper.config and it starts right up.

Hey I am having a very similar problem and have been unable to find that file can you maybe post location and its contents ? I would really appreciate it.

Knute · 2015-07-18 17:25:37

https://wiki.archlinux.org/index.php/Xo … 28v1.16.29

Arch Linux

#1 2015-01-22 01:41:15

Can't start kodi via kodi.service supplied by kodi-standalone-service

#2 2015-01-22 09:56:21

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#3 2015-01-22 23:57:00

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#4 2015-01-23 00:39:10

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#5 2015-01-23 00:56:23

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#6 2015-01-23 01:58:11

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#7 2015-01-23 09:53:14

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#8 2015-01-28 01:47:18

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#9 2015-01-28 01:49:40

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#10 2015-01-28 02:38:51

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#11 2015-01-28 02:43:12

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#12 2015-01-28 09:51:46

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#13 2015-01-28 23:18:07

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#14 2015-01-28 23:46:22

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#15 2015-01-29 23:27:41

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#16 2015-07-18 17:13:27

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

#17 2015-07-18 17:25:37

Re: Can't start kodi via kodi.service supplied by kodi-standalone-service

Board footer