rh535 Posted February 21, 2019 Share Posted February 21, 2019 I have been having issues with my Unraid server for a while. I keep seeing this error in my logs. Any idea on how to fix this? Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs.cfg Quote Link to comment
itimpi Posted February 21, 2019 Share Posted February 21, 2019 Where is that path configured? Back slashes in Linux are not folder separators in a path. Quote Link to comment
rh535 Posted February 21, 2019 Author Share Posted February 21, 2019 1 hour ago, itimpi said: Where is that path configured? Back slashes in Linux are not folder separators in a path. Is this what you were asking for? Could this error be from a share? I see a share that is about the plex logs. Quote Link to comment
trurl Posted February 22, 2019 Share Posted February 22, 2019 Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post. I am thinking Plex isn't really the source of that message. Quote Link to comment
trurl Posted February 22, 2019 Share Posted February 22, 2019 It is in your screenshot. You have somehow managed to create a top level folder named \appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs on one of your disks. Quote Link to comment
rh535 Posted February 22, 2019 Author Share Posted February 22, 2019 4 minutes ago, trurl said: Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post. I am thinking Plex isn't really the source of that message. Here is my logs tower-diagnostics-20190221-1813.zip Quote Link to comment
trurl Posted February 22, 2019 Share Posted February 22, 2019 It is on Disk1 according to your diagnostics. You must have somehow managed to copy that folder to that disk Quote Link to comment
rh535 Posted February 22, 2019 Author Share Posted February 22, 2019 2 minutes ago, trurl said: It is on Disk1 according to your diagnostics. You must have somehow managed to copy that folder to that disk or to your user shares. This might be a dumb question, but what is the best way to delete this share to stop the error? Quote Link to comment
trurl Posted February 22, 2019 Share Posted February 22, 2019 I really can't quite figure out how you could have done it. Since it has the \ path separator in the name it must have been from Windows. According to your diagnostics it has default settings, which means you have never gone to its page and made any, not surprising. I am just wondering whether the normal way of deleting that share is going to work. You have to delete all files and folders from the share. Then maybe you can delete it from that share's page unless the webUI chokes on that name. 1 Quote Link to comment
rh535 Posted February 22, 2019 Author Share Posted February 22, 2019 1 minute ago, trurl said: I really can't quite figure out how you could have done it. Since it has the \ path separator in the name it must have been from Windows. According to your diagnostics it has default settings, which means you have never gone to its page and made any, not surprising. I am just wondering whether the normal way of deleting that share is going to work. You have to delete all files and folders from the share. Then maybe you can delete it from that share's page unless the webUI chokes on that name. K. The folder has data and it updates the log files from plex in it. I can remember trying to get something working in Plex/ Tautulli to monitor the logs.......I wonder if this was when this happened. Quote Link to comment
trurl Posted February 22, 2019 Share Posted February 22, 2019 5 minutes ago, rh535 said: it updates the log files from plex in it. Are you saying something is currently writing files into it? Quote Link to comment
rh535 Posted February 22, 2019 Author Share Posted February 22, 2019 38 minutes ago, trurl said: Are you saying something is currently writing files into it? Sorry.... I just had a network share to that folder on my computer and thought it was my actual share - I created. I was able to delete the share and I'm not seeing the error in my log file any longer. Thank you!!!! - IM hoping this will stop my random lock-ups and crashes Quote Link to comment
rh535 Posted February 23, 2019 Author Share Posted February 23, 2019 The error is back. I have included my latest logs. Any more ideas on this??? tower-diagnostics-20190222-2328.zip Quote Link to comment
trurl Posted February 23, 2019 Share Posted February 23, 2019 36 minutes ago, rh535 said: Any more ideas on this??? You need to figure out how you are creating that share. Quote Link to comment
Squid Posted February 23, 2019 Share Posted February 23, 2019 To begin with, post the contents. of /config/plugins/dockerMan/templates-user/my-PlexMediaServer.xml on the flash drive. After that, it may be simply easiest with remove the entire plex app (along with its appdata) and do a fresh install of it. Quote Link to comment
trurl Posted February 23, 2019 Share Posted February 23, 2019 On 2/21/2019 at 7:30 PM, rh535 said: I can remember trying to get something working in Plex/ Tautulli to monitor the logs.......I wonder if this was when this happened. Do you still have this installed? Quote Link to comment
trurl Posted February 23, 2019 Share Posted February 23, 2019 Some more insight into how user shares work so you might be able to figure this out. User Shares are simply the aggregate of all top level folders on cache and array disks with the same name. When you create a user share, Unraid creates a top level folder on one or more disks as needed according the settings you make for that user share. Those top level folders will have the same name as the user share. Conversely, and this is probably what is going on here, any top level folder on cache or array disks is automatically a user share. If you don't make any settings for it (as in this case) it will have default settings. The user share will have the same name as the folder. The user shares are located at the linux path /mnt/user. Somehow, you have something creating a folder. This would be anything like these: /mnt/user/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/user0/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/cache/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/disk1/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/disk2/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/disk3/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs ... This is probably going to be something like a misconfigured docker. Maybe some host volume mapping set to any of these: /mnt/user/ /mnt/user0/ /mnt/cache/ /mnt/disk1/ /mnt/disk2/ /mnt/disk3/ ... The diagnostics don't give us enough information to tell you the answer. 1 Quote Link to comment
rh535 Posted February 23, 2019 Author Share Posted February 23, 2019 11 hours ago, Squid said: To begin with, post the contents. of /config/plugins/dockerMan/templates-user/my-PlexMediaServer.xml on the flash drive. After that, it may be simply easiest with remove the entire plex app (along with its appdata) and do a fresh install of it. Attached! my-PlexMediaServer.xml Quote Link to comment
rh535 Posted February 23, 2019 Author Share Posted February 23, 2019 10 hours ago, trurl said: Do you still have this installed? Yes. I would like to keep it if possible. I really like the service. Quote Link to comment
rh535 Posted February 23, 2019 Author Share Posted February 23, 2019 10 hours ago, trurl said: Some more insight into how user shares work so you might be able to figure this out. User Shares are simply the aggregate of all top level folders on cache and array disks with the same name. When you create a user share, Unraid creates a top level folder on one or more disks as needed according the settings you make for that user share. Those top level folders will have the same name as the user share. Conversely, and this is probably what is going on here, any top level folder on cache or array disks is automatically a user share. If you don't make any settings for it (as in this case) it will have default settings. The user share will have the same name as the folder. The user shares are located at the linux path /mnt/user. Somehow, you have something creating a folder. This would be anything like these: /mnt/user/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/user0/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/cache/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/disk1/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/disk2/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs /mnt/disk3/\appdata\PlexMediaServer\Library\Application Support\Plex Media Server\Logs ... This is probably going to be something like a misconfigured docker. Maybe some host volume mapping set to any of these: /mnt/user/ /mnt/user0/ /mnt/cache/ /mnt/disk1/ /mnt/disk2/ /mnt/disk3/ ... The diagnostics don't give us enough information to tell you the answer. I just edited the Docker for Tautulli that had something for the Plex logs (It was that same thing that is giving me the errors). I also noticed that the share I deleted earlier re-appeared. I deleted it again and will see how it acts tonight. Thanks again both of you for all your help! Quote Link to comment
trurl Posted February 24, 2019 Share Posted February 24, 2019 2 hours ago, rh535 said: I also noticed that the share I deleted earlier re-appeared. Yes I know. That's why I said this: 20 hours ago, trurl said: You need to figure out how you are creating that share. And why I explained how user shares work and can be accidentally created. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.