search

kelinger / OmniStream

Deployment and management tools for an entire streaming platform that can reside on a server (local, remote, hosted, VPS) with media files stored on cloud services like Google Drive or Dropbox.
MIT License
30 stars 8 forks source link

ERROR: for Container is unhealthy. ERROR: Encountered errors while bringing up the project. #38

Closed Abu3safeer closed 1 year ago

Abu3safeer commented 1 year ago

Hello, I did get this when selecting any streaming component:

ERROR: for ... Container "..." is unhealthy.
ERROR: Encountered errors while bringing up the project.

I tried it with multiple components image

Abu3safeer commented 1 year ago

this is status image

Abu3safeer commented 1 year ago

this is stats image

TechPerplexed commented 1 year ago

Sounds like the Mount container isn't set up properly. What do you get when you type omni home followed by ls mnt ?

Abu3safeer commented 1 year ago

cloud uploadcache

Abu3safeer commented 1 year ago

i tried installing nextcloud, it requires mariadb and radis, both if maria and radis installed succefully, but nexcloud didn't

image
TechPerplexed commented 1 year ago

Well, let's first sort your mount issue. Did you follow all the steps to set up Rclone? When you type rclone configs followed be ls OmniMount, do you see the file rclone.conf? Is it filled with the correct Rclone information?

Abu3safeer commented 1 year ago

I can see the rclone config, i can use omni menu then select setups menus then redefine media directory i can see the file from google drive, to make sure it is correct, I created a folder in google drive then check redefine media directory and i can see the newly created folder with no issues.

Abu3safeer commented 1 year ago

by the way ls OmniMount didn't show anything, I am in main user folder

TechPerplexed commented 1 year ago

Sorry multitasking here... apologies. I meant what do you see when you type omni configs followed by ls omnimount?

Abu3safeer commented 1 year ago

I see rclone.conf

TechPerplexed commented 1 year ago

And does it contain the same information as your original Rclone config file? What is the mount named?

Abu3safeer commented 1 year ago

yes the original information, the maont name is gd

TechPerplexed commented 1 year ago

So far, so good :) Let's try a system cleanup, see if that sorts it... try omni refresh followed omni down, then omni up. Does that bring back your mounts?

Abu3safeer commented 1 year ago

image

TechPerplexed commented 1 year ago

Thanks, I'm out of ideas for the time being, but will hand you over to @kelinger who I'm sure will be able to sort you out :)

Abu3safeer commented 1 year ago

I use oracle vps, it does require openning ports manually, does plex container need ports to be open to be healthy?

kelinger commented 1 year ago

There are a lot of things to discuss here so I'm going to take them apart and then recommend a process for finding what is preventing your startup.

Oracle: For the most containers, the only ports you need to open on an Oracle VPS will be the ssh port (which you obviously already have) and ports 80 and 443 for Traefik. You do not need to open anything special for most containers with the exception of things like Torrent engines which need to go directly to the container (while the web interface will still go through the reverse web proxy).

It looks like, from your last screenshot, that you are getting the core components loaded. Before we try any other containers, let's make sure that is the case.

omni down
omni components

When you're editing the components, make sure that all you have enabled is one version of Traefik (either the CloudFlare-aware version, traefik-cf, or the standard version, traefik) and OmniMount. Everything else is just a distraction at this point.

Now, try to bring OmniStream back online:

omni up

Does it work? Any errors? If it doesn't report errors, then see if you can browse your cloud mount.

omni mounts

This command should make your current directory the one just above all the mounts. You should see (if the default options were used) Cache, cloud, UploadCache, and the name you gave your cloud mount (eg, Google, gd, etc.).

If you can cd into the one named after your rclone service (let's say "Google" for the sake of this discussion) and see files, then things are looking good. Go back to omni mounts and verify you can see the same files--and possibly more--in the directory called "cloud." If so, this means that OmniMount is working and that you have the directory you will use for most things up. This is the "Google" mounted drive overlain with local files pending upload as well as cached files like those you're downloading.

If the above is not working, there's no need to continue. This needs to be resolved before we try to get NextCloud, Plex, or anything else up. Let us know the results of the above and then we can proceed.

Abu3safeer commented 1 year ago

Ok, first I have enabled just those two components image

then bring it back online

image

I only see those two

image

kelinger commented 1 year ago

Thanks for that update.

What do you see with: omni logs omnimount ? (control-c to exit)

Abu3safeer commented 1 year ago

Thank you @kelinger @TechPerplexed for helping me, I created a new fresh vps instance so I make sure it won't conflict with my other docker images.

first thing I do is installing OmniStream, everything was fine until the last step, I see this message image

is it good for now?

Abu3safeer commented 1 year ago

Looks like docker compose is not installed

image

Abu3safeer commented 1 year ago

As I see here https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-compose-on-ubuntu-22-04

docker-compose become docker compose, this might the cause of corrupted installation.

kelinger commented 1 year ago

Try running update-compose