March 16, 20188 yr Since the last update I have a really weird bug. All my shares disappear after some time, the shares Tab just shows the There are no exportable user shares Message as if i didn't add any. Whenever I reboot the Shares reappear but are gone by the next evening. I didn't get any errors whatsoever. I did attach the Diagnostics though, as I hope you guys can make something from them. Any tips on what I can do? I don't really want to muck about in my Unraid Box at the Moment, since I don't have enough external space to save all the data to. Thanks in advance for your help. mainframe-diagnostics-20180317-0013.zip Edited April 14, 20188 yr by ChromeMystic Solved: I had an error on my cachedrive.
March 17, 20188 yr Community Expert SHFS segfaulted, no idea why though: Mar 16 03:40:01 MAINFRAME kernel: shfs[5189]: segfault at 0 ip 0000000000402627 sp 000014f9569848f0 error 4 in shfs[400000+f000] Mar 16 03:40:01 MAINFRAME emhttpd: error: get_filesystem_status, 6432: Transport endpoint is not connected (107): scandir See if the same happens if you lose them again.
March 17, 20188 yr I've had this issue at various times on a test server for quite a while. It appears after working with Dockers a lot. This is the server where I do my Docker testing. I've not made an issue of it because I sometimes do stuff on the test server that I thought might cause this problem. It appears now that others are having this same issue.
March 19, 20188 yr Author I checked the Logs this evening and had an error again: Mar 19 03:40:01 MAINFRAME kernel: shfs[6275]: segfault at 0 ip 0000000000402667 sp 00001537fd9418f0 error 4 in shfs[400000+f000] Mar 19 03:40:01 MAINFRAME emhttpd: error: get_filesystem_status, 6447: Transport endpoint is not connected (107): scandir Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656748875.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1 error: Software caused connection abort Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656755200.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656839632.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656841600.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656894455.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656895498.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656928000.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63656957641.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/logs/server-63657014400.txt Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/logs error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/news.json Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/00ef52c1b2efbbf9b17e9a6c7c02becb Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/f70ca6622474da8168a3b6c06f651a16 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/e2ab45883bcfbae02934100719d983a7 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/0749146507c313f127b2e01d7ffff862 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/75a15dcd708db4e16663dc2fb3d404de Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/2e755b3954b9fdd55ad5274cc05ccb94 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/fd731b3fdfb62f86594fc6b98cba9099 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/fafabf3146b539ba8afdf43e2d8387f2 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/9afe611dc51b62212f25654dbc716f7f Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/0261bfb53f2cc2fd47cc4b30094d5499 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/8e50fc73dc8679eab48a65063934cb82 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Mar 19 03:40:02 MAINFRAME root: move: file /mnt/disk1/Apps/EmbyServer/cache/httpclient/9b818c2b98b82b1f4444470441f5aa39 Mar 19 03:40:02 MAINFRAME root: move: create_parent: /mnt/disk1/Apps/EmbyServer/cache/httpclient error: Transport endpoint is not connected Again the Segfault errors. Any Idea what I could do? It sems the Error appears after about 18 hours of uptime or so. Edit: I tried updating to 6.5 from 6.4.1 but that didn't help. Forgot to mention that Edited March 19, 20188 yr by ChromeMystic
March 19, 20188 yr Community Expert Try running without any docker for some time, if the error doesn't occur then try re-enabling dockers one by one.
March 19, 20188 yr Author 1 minute ago, johnnie.black said: Try running without any docker for some time, if the error doesn't occur then try re-enabling dockers one by one. Will it by ok if I just deactivate them or do I need to uninstall?
March 20, 20188 yr Author I just came home and my server lost its shares again. Docker is disabled and I get the same segfault errors I posted yesterday
March 20, 20188 yr Community Expert Try booting in safe mode to rule out a plugin, if it still happens in safe mode it could be hardware related.
March 20, 20188 yr Author 3 hours ago, johnnie.black said: Try booting in safe mode to rule out a plugin, if it still happens in safe mode it could be hardware related. I tried searching the Wikis, but I didn't find the entry, could you point me towards the how to boot into safe mode?
March 20, 20188 yr Community Expert 1 hour ago, ChromeMystic said: how to boot into safe mode? On the boot menu. Do you have a monitor and keyboard attached?
March 30, 20188 yr Author On 21/03/2018 at 12:44 AM, trurl said: On the boot menu. Do you have a monitor and keyboard attached? I finally got around to plugging my headless box into a screen and keyboard. Booted in safe today. Will keep you posted. Thanks for all your help so far.
April 1, 20188 yr Author Still getting the error in Safe Mode (with GUI for that matter) Any other Tips? What hardware could it be? mainframe-diagnostics-20180401-2312.zip Edited April 1, 20188 yr by ChromeMystic Added Diagnostics
April 9, 20188 yr Author I ran several SMART Tests this weekend, my Disks seem to be fine as well. I don't have the slightest idea what to do next...
April 9, 20188 yr Community Expert It's still segfaulting, try installing 6.5.1-rc5, but it can be hardware related.
April 9, 20188 yr Author 1 minute ago, johnnie.black said: It's still segfaulting, try installing 6.5.1-rc5, but it can be hardware related. I will give that a try, any Ideas what to test for hardware? I don't have a spare board around for testing the entire OS with
April 9, 20188 yr Community Expert 1 minute ago, ChromeMystic said: I will give that a try, any Ideas what to test for hardware? Not really, you'd need to start swapping parts to rule them out, if you have more than 1 DIMM try with just one at a time and in different slots, for the rest you'd need spare parts, like different board, PSU, etc.
April 9, 20188 yr Author 6 minutes ago, johnnie.black said: Not really, you'd need to start swapping parts to rule them out, if you have more than 1 DIMM try with just one at a time and in different slots, for the rest you'd need spare parts, like different board, PSU, etc. RAM I do have :D. Lets hope the newest release helps though. Thanks
April 10, 20188 yr Author I just switched out the 16gigs of Ram in my box for the other 2 slots I salvaged from my old gaming pc. If it persists, i will ad the old 8 gigs I had in there earlier.
April 12, 20188 yr Author I rechecked my Logs: MAINFRAME emhttpd: /mnt/cache mount error: Unsupported partition layout I fixed this by reformatting my cache drive and the server has been running for 24 hours now without losing any shares. I am starting to become hopeful
April 13, 20188 yr Author My shares are still visible after 2 days and 4 hours uptime. Re enabling docker and Emby to see what happens if i have more jobs running.
April 14, 20188 yr Author The System has been Online for 3 days now without a hitch. I think it is OK again
Archived
This topic is now archived and is closed to further replies.