Jennice 19 Posted November 24, 2017 Posted November 24, 2017 I also had Emby server hang on me. It seems to run, and has the tray icon. But asfter some hours of use (mostly doing nothing), it didn't respond to clients. When hovering over the tray icon, it was cleared (removed). I had to re-boot the pc. The earlier Emby releases seemed more stable in this regard. /Jennice
CBers 7450 Posted November 24, 2017 Posted November 24, 2017 Please supply logs as noted here. https://emby.media/community/index.php?/topic/790-how-to-report-a-problem/ Thanks.
Jennice 19 Posted November 24, 2017 Posted November 24, 2017 Hi, Need to find out how to attach log zip files... On the 23rd of nov, in the morning, things worked fine, but in the afternoon the user (FrBorgvej) could start, but the stream was consistently stopped very shortly after.
Jennice 19 Posted November 24, 2017 Posted November 24, 2017 (edited) I am running emby 3.2.36, but the release list has reached 3.2.40. My Emby server says it's up-to-date, and version checks are enabled on startup and every 24 hrs. something may be wrong?? Edited November 24, 2017 by Jennice
ryandavidg 30 Posted November 24, 2017 Posted November 24, 2017 I am running emby 3.2.36, but the release list has reached 3.2.40. My Emby server says it's up-to-date, and version checks are enabled on startup and every 24 hrs. something may be wrong?? See here: https://emby.media/community/index.php?/topic/53111-windows-server-update-announcement/
Jennice 19 Posted November 24, 2017 Posted November 24, 2017 Well, since the 3.2.36 was stopping randomly, I updated manually. Lets see how it goes.
Jennice 19 Posted November 24, 2017 Posted November 24, 2017 (edited) My connection issues persist, from 3.2.36 and 3.2.40. After a while of perfect streaming, it becomes impossible to connect to the server. Even after client re-boot. edit: logs attached. It seems like something with the ffmpeg? The trouble starts at around 21:20 (very roughly). edit2: I'm beginning to think if it's related to ffmpeg buffer file size or disk space. It's been streaming for more than 1 hour straight, with NO problems at all. But when it hangs, it REALLY hangs. Streaming cannot be resumed. after server re-boot, things seem to work well again. But I suppose the temporary working files are flushed when server re-starts? emby log 20171124_3-2-40.zip Edited November 24, 2017 by Jennice
Jennice 19 Posted November 24, 2017 Posted November 24, 2017 (edited) Additional info: I just checked the server. It says the C drive (system and Emby install) has 0 bytes free!? Maybe a valid reason, but what takes up the space? Where are the FFMpeg temp files located? It's default, but I can't see on Emby dashboard where default is? Edit: After re-boot, I had approx. 7 GB free. While streaming (post above) I used CPU based transcoding, with a limit of 2 mbit/s Edited November 24, 2017 by Jennice
Luke 42078 Posted November 24, 2017 Posted November 24, 2017 @@Jennice, it looks like your drive is out of space. have you looked into what folders are using the space? thanks.
Jennice 19 Posted November 25, 2017 Posted November 25, 2017 The PC was not used for anything else. So I'm wondering if the temporary working files are being deleted as they should (after a stream session ends), or if they accumulate until Emby is re-started. Where are temporary Emby files located? (The dashboard just says default, but the actual path is not showing). It'd like to do some investigating, but it's hard when I don't know where to look. Also, I cleaned up some more space from other programs, so now it's about 27 GB free on C drive).
Jennice 19 Posted November 25, 2017 Posted November 25, 2017 OK, I experimented a bit. During a transcode stream, the folder "C:\Users\HTPC\AppData\Roaming\MediaBrowser-Server\transcoding-temp" (adjust for user name), builds up a pile of small-ish files. When my disk is filled up, the transcode (and show) stops, and I now understand why. However, the files are replaced by one big *.ts file, taking up the entire space which was used for transcode (instead of deleting all the temp files). So, for next transcode stream, there is no space for the working files, and thus, streaming can't be resumed. Why is this big temp file kept?
ebr 16181 Posted November 25, 2017 Posted November 25, 2017 It isn't kept on purpose. The most likely reason it is still there is because, once the system runs out of disc space, pretty much all file operations are difficult to perform. The best thing to do is avoid running out of space. You can specify an alternate location for the transcoding temp folder so you can point it to a drive with plenty of free space.
Jennice 19 Posted November 27, 2017 Posted November 27, 2017 (edited) Hi folks, Can someone please assist me in tracking the cause of my trouble? During streaming betwen 8pm and 9pm local time, (20hrs and 21 hrs), the stream to a remote Emby Theater client failed 5 times, causing the client to hang. I'm trying to attach log files from server. Edit: file added Hopefully someone can help me find the cause of error. logs 20171127.zip Edited November 27, 2017 by Jennice
Luke 42078 Posted November 27, 2017 Posted November 27, 2017 Hi folks, Can someone please assist me in tracking the cause of my trouble? During streaming betwen 8pm and 9pm local time, (20hrs and 21 hrs), the stream to a remote Emby Theater client failed 5 times, causing the client to hang. I'm trying to attach log files from server. Edit: file added Hopefully someone can help me find the cause of error. Try further reducing the emby theater internet quality setting. try setting it to 1mbps.
Jennice 19 Posted November 27, 2017 Posted November 27, 2017 In my post above, there is something at 20:18 in the server log, about existing connection being force disconnected by external host. Talking to the person at the client, Emby Theater hangs, and the remote PC needs rebooting.
Jennice 19 Posted November 27, 2017 Posted November 27, 2017 Hi Luke, The client should have ~15 mbit download, and I have ~30 mbit upload reserved for the server. I'm on a 300/60 mbit connection. Do you see indications of the root cause being the internet bandwidth (I'd appreciate an option to set stream buffer at client and host), or if it's a matter of CPU resources? Regards, Jennice
Jennice 19 Posted November 27, 2017 Posted November 27, 2017 Can you find any reason for the Theater hanging? In other words: I'm looking for the root cause. Any ideas? Why would lower bit-rate change things? Also, picture quality suffers significantly at 1 mbit. :/ What happens (in theory) if there are peaks where the cpu or bandwidth can't keep up? The Android app seems more robust in terms of intermissions. Regards, Jennice
Jennice 19 Posted November 28, 2017 Posted November 28, 2017 I did some more experiments, but in-house. Emby Theater does indeed seem to have a decent buffer (an option to set this could be nice to have though). I found this out by disconnecting the LAN cable from my client (set to transcode into 2 mbps stream, just like the remote client that crashed). The client kept playing for a while, and usually managed to resume when the LAN cable was reconnected. Also, the server indicated that a client had disconnected/reconnected. Learning: The stream link seems to be surprisingly tolerant to data stream interruptions (at least over LAN). In my cases, I don't recall seeing this message, which leads me to think that some other issue makes the client hang (freeze). Unfortunately, I don't expect to have access to that specific client PC again until mid january, but it won't be used until then. Therefore I expect the windows10 event logs to remain as recent items (relatively speaking) on the client. Now, I wonder if the web based client behaves differently, or if the same hick-up's occur.
Jennice 19 Posted December 2, 2017 Posted December 2, 2017 A little update on ther buffer issue. It's back on my wish list: custom buffer size. Reason: I have built a new server. Intel i7-8700k (6 core, 12 thread), 16 GB 3000 MHz ram. It seems fairly relaxed at 3 mbps and 4 mbps (720p) transcode, hovering at around 18-19% CPU load. BUT at 4mbps, it stutters at regular intervals (every few seconds), not at 3 mbps. I can work aound it by pausing playback at the client for a few seconds, then resuming. I am getting the impression that the buffer size (or chunk size, or whatever it's called) for FFmpeg is not adjusted along with bit-rate. CPU load looks very stable, so it's not fluctuating as it did on my i7-870 setup. I'm testing the playback in-house, from the server to another LAN client. /Jennice
denywinarto 5 Posted December 3, 2017 Posted December 3, 2017 I'm having this issue as well. Client wont play at all (from different network) and server keeps turning off and i had to restart it. Media wont play on client, on server the timer runs briefly then restarts After a while emby would show failed to connect to local host and i had to restart it, gonna attach the logs later
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now