the http server is inaccessible.

[igeoorge 26]

We use CentOS as operating system.

Machine engineers have already searched over and over for clues in the machine logs. Unfortunately nothing was found.

Last time we talked, we did a full scan of the logs for errors and found nothing.

On the machine that the emby is on, we have 120gb of RAM.
The maximum memory that the emby has already consumed was 10gb.

We have 12 cpu on the machine.
The maximum cpu that the emby has ever used was 30%

 

"PS one last thing to check next time you see this.  When http stops responding take a look at the log file and see if any new lines are being written to the log. It's unlikely to see much as there won't be any communication with a client going on.  If you use RTM for library monitoring you might be able to have a "dummy" movie ready to go that you could move to a library path.  Within a couple of minutes if the core of Emby is still working it will try to process the file and that might show up in the log.  Something like this could help us isolate if the issue is strictly web/http related or not."

I'll follow this tip and keep an eye out:

[Carlo 4561]

10Gb of memory is a lot of memory being used.  That the kind of thing that could be useful to see in a graph.
The memory could be holding steady at 2Mb but then in a 20 minute period start climbing and climbing never going back down.

Being able to see it in a graph or table form like that could give clues to see what changed or what processes ran around the time the memory started climbing.
If would be a good data point to have.