tomhoover
-
Posts
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by tomhoover
-
-
-
Please add bash-completion.
-
On 5/12/2018 at 9:54 PM, dmacias said:On 5/12/2018 at 1:48 PM, tomhoover said:I previously used the mosh server plugin at https://github.com/coppit/unraid-mosh; however, it seems to have stopped working with unRAID 6.5. Would you consider adding mosh server to NerdPack?
https://mosh.org/#getting
Thanks!I added protobuf and mosh. You will also need to install perl and utempter.
I installed protobuf and mosh on my unRAID server (I already had perl and utempter installed). When I attempt to login using mosh, I receive the following error:
mosh-server: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
Do you have any ideas?
-
3 minutes ago, dmacias said:8 hours ago, tomhoover said:I previously used the mosh server plugin at https://github.com/coppit/unraid-mosh; however, it seems to have stopped working with unRAID 6.5. Would you consider adding mosh server to NerdPack?
https://mosh.org/#getting
Thanks!I added protobuf and mosh. You will also need to install perl and utempter.
Thanks!
-
I previously used the mosh server plugin at https://github.com/coppit/unraid-mosh; however, it seems to have stopped working with unRAID 6.5. Would you consider adding mosh server to NerdPack?
https://mosh.org/#getting
Thanks!
-
As several others have reported over the past couple of days, I'm also getting a 'Call Traces found on your server' error reported by fix.common.problems. It seems unusual that several have reported identical errors since upgrading to unRAID 6.3.1. Does anyone have any ideas? (This is a server that been running unRAID for several years without issue.) I've attached diagnostics.
Thanks in advance!
-
PS. If anyone's interested in checking how big their logs are, type this in the unraid terminal and it will list the largest logs:
du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60
Thanks for the command line to locate the runaway log file. I'm new to docker, and incorrectly assumed the logs were within the docker container itself. I tried searching around inside my BitTorrent Sync container (by running the 'docker exec -it Sync bash' command), but couldn't find the problem. I'm syncing so many files with BTSync, that the log would grow to 50GB during the initial "indexing" after starting BTSync. Thanks to you, I finally figured out what was happening and modified my Sync template to include '--log-driver=none' on the startup command line. I've lost my BTSync logs for now, but I no longer have to keep growing my docker.img size to accommodate my increased use of BTSync. Thanks!
-
Please consider adding fdupes: https://github.com/adrianlopezroche/fdupes
unRAID 6 NerdPack - CLI tools (iftop, iotop, screen, kbd, etc.)
in Plugin Support
Posted
Please update docker-compose to version 1.23. Thanks!