More > JRiver Media Center 22 for Linux

[NEW] Docker image - MC headless server

<< < (2/6) > >>

Flyingsparks:
Hi Cassfras,

It seems the data container is coming up, bu the main container is not. This is using jriver-stable:


--- Code: ---stored passwd in file: /home/jriver/.vnc/passwd
2017-03-26 06:29:44,074 CRIT Set uid to user 999
2017-03-26 06:29:44,076 INFO supervisord started with pid 15308
2017-03-26 06:29:45,078 INFO spawned: 'Xorg' with pid 15579
2017-03-26 06:29:45,078 INFO spawned: 'x11vnc' with pid 15580
2017-03-26 06:29:45,079 INFO spawned: 'mediacenter' with pid 15581
2017-03-26 06:29:45,081 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:45,084 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:45,116 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:46,118 INFO spawned: 'Xorg' with pid 15582
2017-03-26 06:29:46,119 INFO spawned: 'x11vnc' with pid 15583
2017-03-26 06:29:46,120 INFO spawned: 'mediacenter' with pid 15584
2017-03-26 06:29:46,122 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:46,125 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:46,158 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:48,161 INFO spawned: 'Xorg' with pid 15601
2017-03-26 06:29:48,161 INFO spawned: 'x11vnc' with pid 15602
2017-03-26 06:29:48,162 INFO spawned: 'mediacenter' with pid 15603
2017-03-26 06:29:48,164 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:48,169 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:49,201 INFO success: mediacenter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-26 06:29:49,201 INFO exited: mediacenter (exit status 0; expected)
2017-03-26 06:29:50,203 INFO spawned: 'mediacenter' with pid 15605
2017-03-26 06:29:50,243 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:51,245 INFO spawned: 'Xorg' with pid 15606
2017-03-26 06:29:51,246 INFO spawned: 'x11vnc' with pid 15607
2017-03-26 06:29:51,246 INFO spawned: 'mediacenter' with pid 15608
2017-03-26 06:29:51,250 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:51,251 INFO gave up: Xorg entered FATAL state, too many start retries too quickly
2017-03-26 06:29:51,252 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:51,281 INFO gave up: x11vnc entered FATAL state, too many start retries too quickly
2017-03-26 06:29:52,283 INFO success: mediacenter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-26 06:29:52,283 INFO exited: mediacenter (exit status 0; expected)
2017-03-26 06:29:53,285 INFO spawned: 'mediacenter' with pid 15627
2017-03-26 06:29:53,322 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:54,324 INFO spawned: 'mediacenter' with pid 15637
2017-03-26 06:29:54,361 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:56,364 INFO spawned: 'mediacenter' with pid 15650
2017-03-26 06:29:56,399 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:59,403 INFO spawned: 'mediacenter' with pid 15684
2017-03-26 06:29:59,439 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:30:00,440 INFO gave up: mediacenter entered FATAL state, too many start retries too quickly

--- End code ---

Any ideas?

cassfras21:
Yes I have a couple of ideas.

It looks like the problem is coming from Xorg. Maybe it has to do with the fact I run docker on my Syno where there is no video output while you have one display on your computer running Ubuntu.

1) You could try to run the app container without DLNA support


--- Code: ---docker run -d \
--name=jrivermc22-stable \
-e UPDATE=no \
-e VNCPASS=<vnc_password> \
-h <hostname> \
-p 5900:5900 \
-p 52199:52199 \
--volumes-from jrivermc22--data-container \
-v <local_media_volume>:/mnt/media \
cassfras21/jrivermc:stable
--- End code ---

2) Or if you want to find out what's going on, please run the app container with the following command to gain shell access.
It will prevent supervisord from starting.


--- Code: ---docker run -it \
--name=jrivermc22-test \
--net=host \
--pid=host \
-e UPDATE=no \
-e VNCPASS=<vnc_password> \
--volumes-from jrivermc22--data-container \
-v <local_media_volume>:/mnt/media \
cassfras21/jrivermc:stable \
/bin/bash
--- End code ---

Then try to run Xorg manually with the command I copied from the supervisord file and look what happens


--- Code: ---Xorg :0 -noreset +extension GLX +extension RANDR +extension RENDER
--- End code ---

Maybe you should give a try with other display number like this one


--- Code: ---Xorg :1 -noreset +extension GLX +extension RANDR +extension RENDER
--- End code ---

Flyingsparks:
Yeah, that seems to be the problem. When I try to start with display :0 it doesn't run, but with display :1 it will.

Flyingsparks:
Here is the actual outputs from Xorg.


--- Code: ---Xorg :0 -noreset +extension GLX +extension RANDR +extension RENDER
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

--- End code ---


--- Code: ---Xorg :1 -noreset +extension GLX +extension RANDR +extension RENDER
libudev: udev_has_devtmpfs: name_to_handle_at on /dev: Operation not permitted

X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux Woodstock 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Build Date: 11 February 2015  12:32:02AM
xorg-server 2:1.16.4-1 (http://www.debian.org/support)
Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Sun Mar 26 12:52:11 2017
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"

--- End code ---

cassfras21:
I just built new docker images with a new environment variable MONITOR for both stable and latest repo.
The default value is :1, so in your case the command to run the container is the same as before.

This should fix your issue and allow to run the app container with other screen setup if needed.

Navigation

[0] Message Index

[#] Next page

[*] Previous page