djotaku 3 Posted January 10, 2016 Share Posted January 10, 2016 Just updated to 3.0.5785.0 and emby-magick. Emby Server keeps crashing and I can't figure out what's causing it. Here's the last thing in my logs: 2016-01-09 18:09:13.3861 Info HttpServer: HTTP Response 200 to 192.168.1.232. Time: 1ms. http://192.168.1.7:8096/dlna/3fc15a4a46c4cf9bffaee46ba4346586/connectionmanager/connectionmanager.xml 2016-01-09 18:09:13.4088 Info HttpServer: HTTP POST http://192.168.1.7:8096/dlna/3fc15a4a46c4cf9bffaee46ba4346586/contentdirectory/control. UserAgent: UPnP/1.0 DLNADOC/1.50 2016-01-09 18:09:13.4249 Info HttpServer: HTTP Response 200 to 192.168.1.232. Time: 16ms. http://192.168.1.7:8096/dlna/3fc15a4a46c4cf9bffaee46ba4346586/contentdirectory/control 2016-01-09 18:09:13.4346 Info HttpServer: HTTP POST http://192.168.1.7:8096/dlna/3fc15a4a46c4cf9bffaee46ba4346586/connectionmanager/control. UserAgent: UPnP/1.0 DLNADOC/1.50 2016-01-09 18:09:13.4502 Info HttpServer: HTTP Response 200 to 192.168.1.232. Time: 15ms. http://192.168.1.7:8096/dlna/3fc15a4a46c4cf9bffaee46ba4346586/connectionmanager/control It's just goes on and on like that for a few pages. Nothing else I can see that might have caused it. Link to comment Share on other sites More sharing options...
Luke 37064 Posted January 10, 2016 Share Posted January 10, 2016 Please always provide the complete log file. Also, how do you define crash? Is the server process exiting? Thanks. Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 Sure, no problem. Crash is that I can't connect to it and then I do: #systemctl status emby-server which gets me : ● emby-server.service - Emby Media Server Loaded: loaded (/usr/lib/systemd/system/emby-server.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2016-01-09 19:59:06 EST; 1min 17s ago Main PID: 27201 (code=exited, status=1/FAILURE) Jan 09 19:25:12 babyluigi.mushroomkingdom systemd[1]: Started Emby Media Server. Jan 09 19:25:12 babyluigi.mushroomkingdom systemd[1]: Starting Emby Media Server... Jan 09 19:25:12 babyluigi.mushroomkingdom su[27201]: (to emby) root on none Jan 09 19:59:03 babyluigi.mushroomkingdom systemd[1]: Stopping Emby Media Server... Jan 09 19:59:05 babyluigi.mushroomkingdom systemd[1]: emby-server.service: main process exited, code=exited, status=1/FAILURE Jan 09 19:59:06 babyluigi.mushroomkingdom systemd[1]: Stopped Emby Media Server. Jan 09 19:59:06 babyluigi.mushroomkingdom systemd[1]: Unit emby-server.service entered failed state. Jan 09 19:59:06 babyluigi.mushroomkingdom systemd[1]: emby-server.service failed. Log is attached. server-63587964313.txt Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 For completion's sake, after posting this, I've updated again and now I'm using: emby-server.x86_64 0:3.0.5851.25221-553.1 Also now have ffmpeg version: ffmpeg.x86_64 0:2.6.5-1.el7.nux ffmpeg-libs.x86_64 0:2.6.5-1.el7.nux It hasn't been long enough for me to see yet if these updates fix this. But I figured I'd have the info here for as you help me. Link to comment Share on other sites More sharing options...
Luke 37064 Posted January 10, 2016 Share Posted January 10, 2016 how did you get to 5851? that is the dev channel, what you had before was the stable channel. Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 Hmm...not sure. Here's how my emby.repo looks: # cat /etc/yum.repos.d/emby.repo [home_emby] name=emby's Home Project (CentOS_7) type=rpm-md baseurl=http://download.opensuse.org/repositories/home:/emby/CentOS_7/ gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/home:/emby/CentOS_7//repodata/repomd.xml.key enabled=1 Link to comment Share on other sites More sharing options...
fc7 123 Posted January 10, 2016 Share Posted January 10, 2016 Can you run: "rpm-qa | grep emby" and post the output here? It shouldn't be possible to switch from stable to dev without first removing stable. Also if you can share the exact steps you did to upgrade will be helpful. You can consult your bash history of commands if that eould help you understand what you did. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
fc7 123 Posted January 10, 2016 Share Posted January 10, 2016 After. Checking our build system, it seems there was a problem there. Can you please remove emby-server package and re-install it? You will not loose any data and this will put you on the correct latest stable version. Thanks. Sent from my iPad using Tapatalk Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 I have removed and reinstalled emby-server. I am now at emby-server.x86_64 0:3.0.5785-554.1 It continues to crash, but I cannot figure out why. I am able to watch TV shows or movies and then eventually when no one is doing anything it decides to crash. Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 One more thing - before when I first started using Emby it kept crashing when it scanned the library. So I changed the nursery-size to 64m. Whenever I uninstall and reinstall Emby, that is lost. I had changed it back to 64m before starting this support thread, but it still crashes. At any rate, let me know if there's another log (in addition to the one I attached above) I can provide to help. Link to comment Share on other sites More sharing options...
fc7 123 Posted January 10, 2016 Share Posted January 10, 2016 One more thing - before when I first started using Emby it kept crashing when it scanned the library. So I changed the nursery-size to 64m. Whenever I uninstall and reinstall Emby, that is lost. I had changed it back to 64m before starting this support thread, but it still crashes. At any rate, let me know if there's another log (in addition to the one I attached above) I can provide to help. Which config file are you modifying? Are you removing Emby and re-installing it or upgrading the package instead? Sent from my iPad using Tapatalk Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 Editing : /etc/emby-server.conf I did a yum erase emby-server and then a yum install emby-server and the changes were removed. I think that's yum's doing as it saved the old config in /etc/ember-server.conf.rpmsave. Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 Just checked and it'd failed again. If it helps, I'm watching via Emby for Kodi. Link to comment Share on other sites More sharing options...
fc7 123 Posted January 10, 2016 Share Posted January 10, 2016 Editing : /etc/emby-server.conf I did a yum erase emby-server and then a yum install emby-server and the changes were removed. I think that's yum's doing as it saved the old config in /etc/ember-server.conf.rpmsave. This is the expected behavior. The file will be kept between regular updates but saved/removed when you unistall the package. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
fc7 123 Posted January 10, 2016 Share Posted January 10, 2016 Just checked and it'd failed again. If it helps, I'm watching via Emby for Kodi. Can you share your system specs? Why did you have to modify the nursery size of mono? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 Here are the specs: CentOS 7 1 GB RAM Movies: 1215 TV Shows: 93 This forum thread shows the nursery size change reason: http://emby.media/community/index.php?/topic/26226-library-scan-runs-out-of-memory/ Have the system required system specs increased with recent Emby versions? Link to comment Share on other sites More sharing options...
fc7 123 Posted January 10, 2016 Share Posted January 10, 2016 I don't think so but 1GB sounds scarce to me for that library size. The new default since some time ago for the nursery is 128mb anyway. I would restart emby-server leave it running until it crashes again and upload the complete log here. Maybe we will find something there. Sent from my iPad using Tapatalk Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 Restart it leaving it at 64mb or changing it back to 128mb? Link to comment Share on other sites More sharing options...
fc7 123 Posted January 10, 2016 Share Posted January 10, 2016 Go to 128mb. If it crashes again grab the log and upload it here. Then go to 64mb and if it crashes provide that full log too. Sounds like a plan? Sent from my iPad using Tapatalk Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 10, 2016 Author Share Posted January 10, 2016 Sounds good. Just as another data point - I just ran every scheduled task - from application updates to Scan media library. None of those crashed it. OK, I just commented out my 64mb change and started it up: # systemctl status emby-server ● emby-server.service - Emby Media Server Loaded: loaded (/usr/lib/systemd/system/emby-server.service; disabled; vendor preset: disabled) Active: active (running) since Sun 2016-01-10 17:38:21 EST; 4s ago Main PID: 24257 (su) CGroup: /system.slice/emby-server.service ‣ 24257 su -s /bin/sh -c exec "$0" "$@" emby -- env MONO_THREADS_PER_CPU=500 MONO_GC_PARAMS=nursery-size=128m LD_LIBRARY_PATH=/usr/lib/emby-server/lib64 /usr/bin/mono-sgen --optimize=all /usr/lib/emb... Jan 10 17:38:21 babyluigi.mushroomkingdom systemd[1]: Started Emby Media Server. Jan 10 17:38:21 babyluigi.mushroomkingdom systemd[1]: Starting Emby Media Server... Jan 10 17:38:21 babyluigi.mushroomkingdom su[24257]: (to emby) root on none Once someone tries to use Emby and it has stopped working (or later I'll come and do another status check) I'll upload the log. Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 11, 2016 Author Share Posted January 11, 2016 (edited) Ok, here we go - it died ten minutes ago. Hopefully the logs can reveal something: # systemctl status emby-server ● emby-server.service - Emby Media Server Loaded: loaded (/usr/lib/systemd/system/emby-server.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2016-01-10 20:32:25 EST; 10min ago Process: 24613 ExecStopPost=/usr/lib/emby-server/emby-server.sh clear (code=exited, status=0/SUCCESS) Process: 24257 ExecStart=/usr/lib/emby-server/emby-server.sh start (code=exited, status=134) Main PID: 24257 (code=exited, status=134) Jan 10 17:38:21 babyluigi.mushroomkingdom systemd[1]: Started Emby Media Server. Jan 10 17:38:21 babyluigi.mushroomkingdom systemd[1]: Starting Emby Media Server... Jan 10 17:38:21 babyluigi.mushroomkingdom su[24257]: (to emby) root on none Jan 10 20:32:24 babyluigi.mushroomkingdom systemd[1]: emby-server.service: main process exited, code=exited, status=134/n/a Jan 10 20:32:25 babyluigi.mushroomkingdom systemd[1]: Unit emby-server.service entered failed state. Jan 10 20:32:25 babyluigi.mushroomkingdom systemd[1]: emby-server.service failed. Last logs is attached. server-63588044301.txt Edited January 11, 2016 by djotaku Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 11, 2016 Author Share Posted January 11, 2016 As what I hope might be a workaround until we figure things out in the forum, I've changed /usr/lib/systemd/system/emby-server.service to have the following [service] section. According to a tutorial about systemd, it *should* make it just restart whenever it crashes. [Unit] Description=Emby Media Server After=network.target [Service] EnvironmentFile=/etc/emby-server.conf ExecStart=/usr/lib/emby-server/emby-server.sh start Restart=on-abort TimeoutSec=20 ExecStopPost=/usr/lib/emby-server/emby-server.sh clear [Install] WantedBy=multi-user.target [Service] Restart=always Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 11, 2016 Author Share Posted January 11, 2016 (edited) Sorry to seem to be spamming the topic, but I just noticed something else: I couldn't ever see anything in the most recent log that revealed the reason for the crash, but if I look in the penultimate log....I see this at the end (I can't attach the whole log as it's 40MB) 2016-01-10 17:37:53.8991 Info MediaEncoder: Killing ffmpeg process 2016-01-10 17:37:53.8991 Error MediaEncoder: Error sending q command to process 2016-01-10 17:37:53.8991 Error MediaEncoder: Error in WaitForExit 2016-01-10 17:37:53.8991 Error MediaEncoder: Error killing process *** Error Report *** Version: 3.0.5785.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 3.10.0.229 Processor count: 1 64-Bit OS: True 64-Bit Process: True Program data path: /var/lib/emby-server Mono: 4.2.1 (Stable 4.2.1.102/6dd2d0d Mon Dec 28 00:10:17 UTC 2015) Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe No process to kill. System.SystemException at System.Diagnostics.Process.Close (Int32 signo) <0x41494790 + 0x000ab> in <filename unknown>:0 at System.Diagnostics.Process.Kill () <0x41494760 + 0x00013> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:Kill () at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.StopProcess (MediaBrowser.MediaEncoding.Encoder.ProcessWrapper process, Int32 waitTimeMs, Boolean enableForceKill) <0x41494000 + 0x001ff> in <filename unknown>:0 2016-01-10 17:37:53.8991 Info MediaEncoder: Killing ffmpeg process 2016-01-10 17:37:53.8991 Error MediaEncoder: Error sending q command to process 2016-01-10 17:37:53.8991 Error MediaEncoder: Error in WaitForExit 2016-01-10 17:37:53.8991 Error MediaEncoder: Error killing process *** Error Report *** Version: 3.0.5785.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 3.10.0.229 Processor count: 1 64-Bit OS: True 64-Bit Process: True Program data path: /var/lib/emby-server Mono: 4.2.1 (Stable 4.2.1.102/6dd2d0d Mon Dec 28 00:10:17 UTC 2015) Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe No process to kill. System.SystemException at System.Diagnostics.Process.Close (Int32 signo) <0x41494790 + 0x000ab> in <filename unknown>:0 at System.Diagnostics.Process.Kill () <0x41494760 + 0x00013> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:Kill () at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.StopProcess (MediaBrowser.MediaEncoding.Encoder.ProcessWrapper process, Int32 waitTimeMs, Boolean enableForceKill) <0x41494000 + 0x001ff> in <filename unknown>:0 2016-01-10 17:37:53.8991 Info App: Disposing SsdpHandler 2016-01-10 17:37:53.9021 Info App: Disposing ActivityRepository 2016-01-10 17:37:53.9025 Info App: Disposing MovieDbProvider 2016-01-10 17:37:53.9025 Info App: Disposing EmbyTV 2016-01-10 17:37:53.9060 Info App: Disposing OpenSubtitleDownloader 2016-01-10 17:37:53.9066 Info App: Disposing LinuxIsoManager 2016-01-10 17:37:53.9066 Info App: Disposing LinuxMount 2016-01-10 17:37:53.9066 Info App: Disposing ApiEntryPoint 2016-01-10 17:37:53.9076 Info App: Disposing ServerEntryPoint 2016-01-10 17:37:53.9086 Info App: Disposing ActivityLogEntryPoint 2016-01-10 17:37:53.9141 Info App: Disposing AutomaticRestartEntryPoint 2016-01-10 17:37:53.9141 Info App: Disposing ExternalPortForwarding 2016-01-10 17:37:53.9177 Info App: Disposing LibraryChangedNotifier 2016-01-10 17:37:53.9181 Info App: Disposing LoadRegistrations 2016-01-10 17:37:53.9181 Info App: Disposing Notifications 2016-01-10 17:37:53.9194 Info App: Disposing WebSocketNotifier 2016-01-10 17:37:53.9194 Info App: Disposing RefreshUsersMetadata 2016-01-10 17:37:53.9194 Info App: Disposing UsageEntryPoint 2016-01-10 17:37:53.9194 Info App: Disposing ConnectEntryPoint 2016-01-10 17:37:53.9194 Info App: Disposing UdpServerEntryPoint 2016-01-10 17:37:53.9210 Info App: Disposing ServerEventNotifier 2016-01-10 17:37:53.9249 Info App: Disposing UserDataChangeNotifier 2016-01-10 17:37:53.9253 Info App: Disposing LibraryMonitorStartup 2016-01-10 17:37:53.9253 Info App: Disposing EntryPoint 2016-01-10 17:37:53.9253 Info App: Disposing HdHomerunDiscovery 2016-01-10 17:37:53.9253 Info App: Disposing NewsEntryPoint 2016-01-10 17:37:53.9253 Info App: Disposing DlnaProfileEntryPoint 2016-01-10 17:37:53.9253 Info App: Disposing DlnaEntryPoint 2016-01-10 17:37:53.9302 Info App: Disposing EntryPoint 2016-01-10 17:37:53.9302 Info App: Disposing KeepServerAwake 2016-01-10 17:37:53.9302 Info App: Disposing StartupWizard This would explain why we seem to be able to watch a movie and then it crashes. Edited January 11, 2016 by djotaku Link to comment Share on other sites More sharing options...
fc7 123 Posted January 11, 2016 Share Posted January 11, 2016 (edited) Ok, here we go - it died ten minutes ago. Hopefully the logs can reveal something: # systemctl status emby-server ● emby-server.service - Emby Media Server Loaded: loaded (/usr/lib/systemd/system/emby-server.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2016-01-10 20:32:25 EST; 10min ago Process: 24613 ExecStopPost=/usr/lib/emby-server/emby-server.sh clear (code=exited, status=0/SUCCESS) Process: 24257 ExecStart=/usr/lib/emby-server/emby-server.sh start (code=exited, status=134) Main PID: 24257 (code=exited, status=134) Jan 10 17:38:21 babyluigi.mushroomkingdom systemd[1]: Started Emby Media Server. Jan 10 17:38:21 babyluigi.mushroomkingdom systemd[1]: Starting Emby Media Server... Jan 10 17:38:21 babyluigi.mushroomkingdom su[24257]: (to emby) root on none Jan 10 20:32:24 babyluigi.mushroomkingdom systemd[1]: emby-server.service: main process exited, code=exited, status=134/n/a Jan 10 20:32:25 babyluigi.mushroomkingdom systemd[1]: Unit emby-server.service entered failed state. Jan 10 20:32:25 babyluigi.mushroomkingdom systemd[1]: emby-server.service failed. Last logs is attached. server-63588044301.txt This log seems to be incomplete or at least there is no crash logged at all. The server seems to be working fine tough. Are you sure you got the correct file and that there are no other logfile where the server continued logging information? Did you check that the date and time of the last line of the log matches exactly with the date and time the server stopped working? Edited January 11, 2016 by fc7 Link to comment Share on other sites More sharing options...
djotaku 3 Posted January 11, 2016 Author Share Posted January 11, 2016 So, I did an ls -lrot - the one on bottom is the newest one, right? So I figured that was the one to attach. Link to comment Share on other sites More sharing options...
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