August 26, 201510 yr That's not a bug, it's a feature! It doubles as ram % usage when docker is disabled [emoji3] Are you sure? As RAM usage is already in the row right above and show different value. And even IF that is the case, then the text would have to be adapted, as it still shows "flash : log : docker" even if there is no docker enabled and no docker image file present. I think you've missed the joke, I'm sure they'll fix it for the next release.
August 26, 201510 yr I think you've missed the joke, I'm sure they'll fix it for the next release. Arrghh ... yeah, obviously I overlooked the smiley ;-)
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000]
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000] Question though: did you update any of your containers recently? If so, that could be why you didn't see this in earlier RCs of 6.1. Maybe the container update has a bad build of python of something else causing it.
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000] Question though: did you update any of your containers recently? If so, that could be why you didn't see this in earlier RCs of 6.1. Maybe the container update has a bad build of python of something else causing it. I did not update them after upgrading to rc6 and prior to seeing these messages. I did force an update on a few to see if it would help but it did not. I just can't remember if I updated any of them just prior to the RC upgrade. John
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000] Question though: did you update any of your containers recently? If so, that could be why you didn't see this in earlier RCs of 6.1. Maybe the container update has a bad build of python of something else causing it. I did not update them after upgrading to rc6 and prior to seeing these messages. I did force an update on a few to see if it would help but it did not. I just can't remember if I updated any of them just prior to the RC upgrade. John Well regardless, I can guarantee these are not the result of the host OS. Python is not baked into the OS itself. Some plugins add it because they use it and some containers use it. Either could cause issues.
August 28, 201510 yr Here is another message I have not seen before: Aug 28 06:31:12 unRAID kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 Looks like others are/were seeing the same: https://lime-technology.com/forum/index.php?topic=41963.0 John
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000] Question though: did you update any of your containers recently? If so, that could be why you didn't see this in earlier RCs of 6.1. Maybe the container update has a bad build of python of something else causing it. I did not update them after upgrading to rc6 and prior to seeing these messages. I did force an update on a few to see if it would help but it did not. I just can't remember if I updated any of them just prior to the RC upgrade. John Well regardless, I can guarantee these are not the result of the host OS. Python is not baked into the OS itself. Some plugins add it because they use it and some containers use it. Either could cause issues. That's fair. I have my CP container stopped to see if the messages continue. So far none. John
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000] Question though: did you update any of your containers recently? If so, that could be why you didn't see this in earlier RCs of 6.1. Maybe the container update has a bad build of python of something else causing it. I did not update them after upgrading to rc6 and prior to seeing these messages. I did force an update on a few to see if it would help but it did not. I just can't remember if I updated any of them just prior to the RC upgrade. John Well regardless, I can guarantee these are not the result of the host OS. Python is not baked into the OS itself. Some plugins add it because they use it and some containers use it. Either could cause issues. That's fair. I have my CP container stopped to see if the messages continue. So far none. John Is that CP as in couch or crashplan? Who's variant? Maybe see if anyone else in the support thread for it are experiencing this?
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000] Question though: did you update any of your containers recently? If so, that could be why you didn't see this in earlier RCs of 6.1. Maybe the container update has a bad build of python of something else causing it. I did not update them after upgrading to rc6 and prior to seeing these messages. I did force an update on a few to see if it would help but it did not. I just can't remember if I updated any of them just prior to the RC upgrade. John Well regardless, I can guarantee these are not the result of the host OS. Python is not baked into the OS itself. Some plugins add it because they use it and some containers use it. Either could cause issues. That's fair. I have my CP container stopped to see if the messages continue. So far none. John Is that CP as in couch or crashplan? Who's variant? Maybe see if anyone else in the support thread for it are experiencing this? hurricane/docker-couchpotato:latest I'll sit on it for a day. If no messages, I'll fire it back up and if I get a message, off to the appropriate thread I go. John
August 28, 201510 yr EDIT: Just found this post by jonp: https://lime-technology.com/forum/index.php?topic=40255.msg378322#msg378322 I am going to shutdown my containers one at a time until I find the culprit but I suspect CouchPotato. --------------- I'm seeing these segfaults again in rc6 but haven't seen them in previous 6.1 RCs. I know that we have seen these before but I can't remember if it was determined that it was container related or not. Aug 27 19:45:15 unRAID kernel: python[30161]: segfault at 58 ip 000000000052c8d8 sp 00002b15874116e0 error 4 in python2.7[400000+2bd000] Aug 27 19:57:12 unRAID kernel: python[24089]: segfault at 58 ip 000000000052c8d8 sp 00002aacfa42f220 error 4 in python2.7[400000+2bd000] Aug 27 20:39:12 unRAID kernel: python[20220]: segfault at 58 ip 000000000052c8d8 sp 00002b53cc3ff480 error 4 in python2.7[400000+2bd000] Aug 27 22:25:58 unRAID kernel: python[30826]: segfault at 58 ip 000000000052c8d8 sp 00002b75c0c03920 error 4 in python2.7[400000+2bd000] Aug 28 01:08:25 unRAID kernel: python[1602]: segfault at 58 ip 000000000052c8d8 sp 00002b7123fe4950 error 4 in python2.7[400000+2bd000] Question though: did you update any of your containers recently? If so, that could be why you didn't see this in earlier RCs of 6.1. Maybe the container update has a bad build of python of something else causing it. I did not update them after upgrading to rc6 and prior to seeing these messages. I did force an update on a few to see if it would help but it did not. I just can't remember if I updated any of them just prior to the RC upgrade. John Well regardless, I can guarantee these are not the result of the host OS. Python is not baked into the OS itself. Some plugins add it because they use it and some containers use it. Either could cause issues. That's fair. I have my CP container stopped to see if the messages continue. So far none. John Is that CP as in couch or crashplan? Who's variant? Maybe see if anyone else in the support thread for it are experiencing this? hurricane/docker-couchpotato:latest I'll sit on it for a day. If no messages, I'll fire it back up and if I get a message, off to the appropriate thread I go. John Sounds like a good plan to me!
August 28, 201510 yr Those segfaults remind me of the old days of "dependency hell", when various plugins demanded their own version of some library or module, and dependency conflicts arose, and segfaults like the above were a prime symptom. So much has changed since then, to eliminate the problem (Dockers!), but I can think of 2 ways that they could still occur, perhaps there are others too. One is in the core - the PhAzE plugins use his own baked-in version of python, and the NerdPack uses a little different version, so someone that loads both *could* have a conflict. The second is in a Docker where more than one application is combined, something like Deluge and Sonarr, CouchPotato and something else, etc. If one of the apps is updated and that update in some way involves an updated library that the other also uses, there could be a potential conflict there. Or an updated app demands a version of something that's different than the base of the container includes. But I could be all wrong, as I don't know enough about how Docker components are updated.
August 28, 201510 yr Those segfaults remind me of the old days of "dependency hell", when various plugins demanded their own version of some library or module, and dependency conflicts arose, and segfaults like the above were a prime symptom. So much has changed since then, to eliminate the problem (Dockers!), but I can think of 2 ways that they could still occur, perhaps there are others too. One is in the core - the PhAzE plugins use his own baked-in version of python, and the NerdPack uses a little different version, so someone that loads both *could* have a conflict. The second is in a Docker where more than one application is combined, something like Deluge and Sonarr, CouchPotato and something else, etc. If one of the apps is updated and that update in some way involves an updated library that the other also uses, there could be a potential conflict there. Or an updated app demands a version of something that's different than the base of the container includes. But I could be all wrong, as I don't know enough about how Docker components are updated. Rob, you are definitely on the right track. Container authors need to be aware of these issues when compiling their builds and it's another good reason to avoid combining too many different apps into a single container. With plugins, sadly there is no simple answer. Even if we baked Python into unRAID OS again (which we are not even considering at this time), you could still see an issue where certain apps break because of a mismatched python version. The simple answer here is that if you are using a Plugin that requires python, maybe it's time to consider switching to a Docker container. If you're using a Docker container that uses python and is causing these errors, notify the container author and in the meantime, perhaps try an alternative variant. First step though is to narrow down the root cause to the specific plugin/container.
August 29, 201510 yr Sorry if I missed this in an announcement somewhere... Was the newperms script renamed or removed? root@unRAID:/# newperms -bash: newperms: command not found I used to be able to run it from any path. John
August 29, 201510 yr Sorry if I missed this in an announcement somewhere... Was the newperms script renamed or removed? root@unRAID:/# newperms -bash: newperms: command not found I used to be able to run it from any path. John Script was moved: /usr/local/emhttp/webGui/scripts/newperms
August 29, 201510 yr Sorry if I missed this in an announcement somewhere... Was the newperms script renamed or removed? root@unRAID:/# newperms -bash: newperms: command not found I used to be able to run it from any path. John Script was moved: /usr/local/emhttp/webGui/scripts/newperms Thanks. Is it possible to have the ability again to be able to call it from any path? John
August 29, 201510 yr Sorry if I missed this in an announcement somewhere... Was the newperms script renamed or removed? root@unRAID:/# newperms -bash: newperms: command not found I used to be able to run it from any path. John Script was moved: /usr/local/emhttp/webGui/scripts/newperms Thanks. Is it possible to have the ability again to be able to call it from any path? John I added the following to my go file to achieve this: ln -s /usr/local/emhttp/webGui/scripts/newperms /usr/local/sbin/newperms
August 29, 201510 yr Sorry if I missed this in an announcement somewhere... Was the newperms script renamed or removed? root@unRAID:/# newperms -bash: newperms: command not found I used to be able to run it from any path. John Script was moved: /usr/local/emhttp/webGui/scripts/newperms Thanks. Is it possible to have the ability again to be able to call it from any path? John I added the following to my go file to achieve this: ln -s /usr/local/emhttp/webGui/scripts/newperms /usr/local/sbin/newperms Thanks guys. I'll modify my go file if things will remain they way they are now (not being able to call newperms from any path). However, do we expect that this will be corrected in a future release? If so, I'll just wait for that. I'd rather keep my go file clean if possible. John
August 29, 201510 yr Is there a specific reason why you run newperms from CLI and not GUI ? Via the CLI you can provide a path parameter to limit the scope. This is useful if you know just a few files need their permissions adjusting. As far as I know you cannot do this from the GUI.
August 29, 201510 yr Is there a specific reason why you run newperms from CLI and not GUI ? Via the CLI you can provide a path parameter to limit the scope. This is useful if you know just a few files need their permissions adjusting. As far as I know you cannot do this from the GUI. Exactly.
August 29, 201510 yr Is there a specific reason why you run newperms from CLI and not GUI ? Via the CLI you can provide a path parameter to limit the scope. This is useful if you know just a few files need their permissions adjusting. As far as I know you cannot do this from the GUI. From the GUI you can select an individual disk. What kind of scope are you using/looking for ?
August 29, 201510 yr Is there a specific reason why you run newperms from CLI and not GUI ? Via the CLI you can provide a path parameter to limit the scope. This is useful if you know just a few files need their permissions adjusting. As far as I know you cannot do this from the GUI. From the GUI you can select an individual disk. What kind of scope are you using/looking for ? I often limit it to a particular folder on a particular disk.
August 29, 201510 yr Is there a specific reason why you run newperms from CLI and not GUI ? Via the CLI you can provide a path parameter to limit the scope. This is useful if you know just a few files need their permissions adjusting. As far as I know you cannot do this from the GUI. From the GUI you can select an individual disk. What kind of scope are you using/looking for ? I often limit it to a particular folder on a particular disk. I do exactly the same thing. I typically run it on exactly the new movie or show or show season subdirectory like such: newperms /mnt/disk2/Media/TV/Narcos\ \(2015\) newperms /mnt/disk2/Media/TV/From\ Dusk\ Til\ Dawn\ \(2014\)/Season\ 2
Archived
This topic is now archived and is closed to further replies.