GUI dissapears after reboot and does not load about ffplayout-docker HOT 27 CLOSED

I restart docker and for 1 mon the front eng gui shows in the docker ps then it restarts and goes away

from ffplayout-docker.

Is it possible to run docker logs ffplayout-frontend?

from ffplayout-docker.

would IP address changing on server cause this? IP change is the only change on server from yesterday to today.
(how would you like me to send you the output of the command?)

from ffplayout-docker.

would IP address changing on server cause this? IP change is the only change on server from yesterday to today.

Maybe, but I can not tell you exactly.

(how would you like me to send you the output of the command?)

Normally it is ok, when you put it in a code block here. DNS and IPs you can replace. Wh it is very long, you can make a gist and send me the link.

from ffplayout-docker.

Does the setup configure to IP on setup? because that could be it. hence when machine booted with new IP it did not work.

am busy doing a clean install to test this to verify IF its the IP change that breaks it. (also testing your new easy install without docker)

from ffplayout-docker.

I can reproduce the problem, I have to look deeper in this issue. Maybe there is something wrong in the configuration.

from ffplayout-docker.

I found the problem: I need to define a more specific startup order for the containers.

from ffplayout-docker.

I found the problem: I need to define the startup order, from the containers.

awesome. let me know when pushed and i will test again from scratch.

also the new quick install seems to have an error likely related

from ffplayout-docker.

I forgot the restart parameter for the srs container...

from ffplayout-docker.

glad we found it. Pls let me know once docker updated and i will reinstall and retest.

from ffplayout-docker.

It is already updated. When you setup the container already you can run:

• docker-compose down
• git pull
• docker-compose up -d

from ffplayout-docker.

worked perfectly. rebooted with new IP and same issue showed up on Ip change though

from ffplayout-docker.

Maybe this is a docker issue. Normally production system have no IP changes, so I would just ignore this.

from ffplayout-docker.

ok so after applying the fix above and fixing the IP to static this should not reproduce?
which version you suggest is best to sue docker or the new install process for production going forwards

from ffplayout-docker.

ok so after applying the fix above and fixing the IP to static this should not reproduce?

No I don't think so.

which version you suggest is best to sue docker or the new install process for production going forwards

Personally I like the non-docker version more, it gives me more flexibility and I can change the versions and configs easier. But by us it runs in its own VM, without any other services. Usually our version is a half year or more behind the master versions from git. Most features we don't need.

Other people like more the docker version, it just run out of the box. So is up to you, what you prefer.

from ffplayout-docker.

thanks. just wanted to get better idea of which will be better supported.
how can we access your advanced ver?

from ffplayout-docker.

Which advanced version?

from ffplayout-docker.

re:"Usually our version is a half year or more behind the master versions from git"

from ffplayout-docker.

It just mean, that we use a older version. It don't have to mean that it is more stable, we just don't update so many times, because we don't need the new features. When you using the released version, they should be stable enough.

from ffplayout-docker.

rebooted server this am now on static ip and the same issue showed again. 8080 does not initilise on reboot

from ffplayout-docker.

Is port 8088...

Please provide always as much infos as possible. What says docker ps?

from ffplayout-docker.

Is port 8088...

Please provide always as much infos as possible. What says docker ps?

same as the avove it fails to show the 8080. i then have to do the:

docker-compose down
git pull
docker-compose up -d

and then it works again.

from ffplayout-docker.

To be sure, that it really use the new settings, you could remove all container and images.
this goes with:

• docker-compose down -v
• docker images
• take the ids from image list and remove the image with docker rmi $ID

And the again: docker-compose up -d

from ffplayout-docker.

To be sure, that it really use the new settings, you could remove all container and images.
this goes with:

* `docker-compose down -v`

* `docker images`

* take the ids from image list and remove the image with `docker rmi $ID`

And the again: docker-compose up -d

this will not affect the setup o ffplay just resetup docker correct?

from ffplayout-docker.

this will not affect the setup o ffplay just resetup docker correct?

Hopefully not :-)

from ffplayout-docker.

Ok will give it a try. i am testing a non docker version now to compare. i am suspecting docker somehow (not sure why but gut says it)
Will verify after testing and give feedback

from ffplayout-docker.

Hi, before the restarting on frontend give me Error: Request failed with status code 500.

from ffplayout-docker.