frakman1

Remote SMB Share Won't Mount When I add a remote SMB share, the GUI walks me through the steps and lets me search for and select the Samba share on my network by "name" (not IP address). I then select the share I want from the pull down and end up with this: However, when I hit the "MOUNT" button, I get the error below. It can't find the SMB share by the name that it gave me to use: Jul 9 15:50:20 Tower unassigned.devices: Mount SMB share '//VIDEO/ContaCam' using SMB3 protocol. Jul 9 15:50:20 Tower unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_ContaCam' '//VIDEO/ContaCam' '/mnt/disks/VIDEO_ContaCam' Jul 9 15:50:20 Tower unassigned.devices: SMB3 mount failed: mount error: could not resolve address for VIDEO: Unknown error It won't let me modify it afterwards to set the IP address. To make it work, I have to delete the share, add a new SMB share and search by IP address. Except now, the location is this ugly: /mnt/disks/192.168.xxx.xxx_ContaCam Instead of the much nicer: /mnt/disks/VIDEO_ContaCam By the way, I am running version 6.8.3 of Unraid. I just updated to the latest version of this plugin (2020.07.10) and installed the 'plus' version but the error persists: This used to work a while back. I don't know what changed other than the version of Unraid. tower-diagnostics-20200709-1641.zip

Thank you. I changed it to use: system("/usr/bin/bash /boot/config/xxxx_route.sh") and that worked.

@brunnels I did all that but when I restart the container, I see this error message in the unraid terminal: root@Tower:/boot/config# sh: /boot/config/xxx_route.sh: Permission denied Doing a "chmod +x filename" and even chmod 777 on the file doesn't change it. I even killed the no hup process to make sure it's really stopped but the changes won't stick. The script adds the route to 10.0.0.199 which is the IP address of the Unraid server so how is it adding a route to the container? That script actually runs on the server right? Not the container since it is doing a "docker inspect". Or is the "ip netns exec" command actually run inside the container?

I found a workaround for when the krusader GUI won't start. Try launching it in incognito mode. It worked for me then. It wouldn't work at all ( I mean, ever) in normal mode.

Adding an icon for PrimeOS (Android)

@SpaceInvaderOne Hi and thank you for making this script and hosting the icons on your sever and for the video instructions. Can you please add all the excellent icons on this forum to your repo? I noticed many are not on there (KDE plasma for example) I ended up manually adding a wget instruction directly in the "/boot/config/plugins/user.scripts/scripts/icon_banner downloader\script" file below the call to your "wget'. Ugly, but it works and luckily the forum location acts as a suitable location for hosting: wget $get -P $download wget https://ipsassets.unraid.net/uploads/monthly_2018_04/icon-kdeneon.png.0f710d4f92761e19ddc1a05760326f28.png -P $download wget $getbanner -P $dirbanner Just a note to everyone to insert the image directly into your post. Dropbox or Google links won't work with this method.

Does anyone know how to reduce the size of the Gitlab-CE container? Mine is about 2GB and it barely has anything in it. The docker-hub image is ~750MB so how did it get so big? I've already disabled prometheus_monitoring. Not sure what else I need to do.

Well I wanted the whole filesystem, not just my home dir. I didn't want to re-install and tweak everything from scratch. I ended up using rsync to a brand new VM with the same OS and that worked. Unfortunately, the Android VM didn't make it as it rebooted before I got to it. Yes, it absolutely did encrypt and rename the file and render it unreadable. That's why the Android VM couldn't boot.

Some nasty ransomware got me. It encrypted the vdisk1.img file of an Ubuntu VM while that VM is still up. Is there any way to recover/recreate that file from a running VM (from RAM?) before it is restarted? Same thing with my Android VM. The compromise was from a windows PC on the network with an unsecured login. It had some UNRAID folders shared through SAMBA so that's how the vdisks got encrypted. I already shut that Win PC down and have things under control. The Linux VM itself is clean and I want to maintain its contents and environment that I set up. Only the UNRAID shares were impacted. Luckily no folder was shared in the VM itself.

@MorgothCreator I ran into a similar issue when upgrading my standalone Gitlab from Gitlab 12.8.1 -> 12.10.3. The PostGres DB upgrade from 10.12 -> 11.7 failed. In my case, it pointed to a log file (pg_upgrade_server.log) that told me that it was due to low memory. Initializing the new database: OK Upgrading the data:Error upgrading the data to version 11.7 STDOUT: Performing Consistency Checks ----------------------------- Checking cluster versions ok *failure* Consult the last few lines of "pg_upgrade_server.log" for the probable cause of the failure. connection to database failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.50432"? could not connect to source postmaster started with the command: "/opt/gitlab/embedded/postgresql/10/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/opt/gitlab/postgresql/data" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/var/opt/gitlab/postgresql'" start Failure, exiting STDERR: Upgrading the data: NOT OK Traceback (most recent call last): 8: from /opt/gitlab/embedded/bin/omnibus-ctl:23:in `<main>' 7: from /opt/gitlab/embedded/bin/omnibus-ctl:23:in `load' 6: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/omnibus-ctl-0.6.0/bin/omnibus-ctl:31:in `<top (required)>' 5: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/omnibus-ctl-0.6.0/lib/omnibus-ctl.rb:746:in `run' 4: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/omnibus-ctl-0.6.0/lib/omnibus-ctl.rb:204:in `block in add_command_under_category' 3: from /opt/gitlab/embedded/service/omnibus-ctl/pg-upgrade.rb:192:in `block in load_file' 2: from /opt/gitlab/embedded/service/omnibus-ctl/pg-upgrade.rb:249:in `general_upgrade' 1: from /opt/gitlab/embedded/service/omnibus-ctl/lib/gitlab_ctl/pg_upgrade.rb:130:in `run_pg_upgrade' /opt/gitlab/embedded/service/omnibus-ctl/lib/gitlab_ctl/pg_upgrade.rb:130:in `raise': wrong number of arguments (given 4, expected 0..3) (ArgumentError) Ensuring PostgreSQL is updated: NOT OK Error ensuring PostgreSQL is updated. Please check the logs dpkg: error processing package gitlab-ce (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu11) ... Errors were encountered while processing: gitlab-ce E: Sub-process /usr/bin/dpkg returned an error code (1) root@gitlab:~# tail -n 100 /var/opt/gitlab/postgresql/pg_upgrade_server.log ----------------------------------------------------------------- pg_upgrade run on Sun May 10 12:11:15 2020 ----------------------------------------------------------------- mand: "/opt/gitlab/embedded/postgresql/10/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/opt/gitlab/postgresql/data" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/var/opt/gitlab/postgresql'" start >> "pg_upgrade_server.log" 2>&1 waiting for server to start....LOG: listening on Unix socket "/var/opt/gitlab/postgresql/.s.PGSQL.50432" FATAL: coulcomd not map anonymous shared memory: Cannot allocate memory HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 15407661056 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections. LOG: database system is shut down stopped waiting pg_ctl: could not start server Examine the log output. root@gitlab:~# free -m total used free shared buffers cached Mem: 64431 61810 2620 669 885 10965 -/+ buffers/cache: 49959 14471 Swap: 0 0 0 14,693 MB needed Luckily you can bypass upgrading the PostGres DB for now.

Well, the only thing I saw different in your Docker configuration was that my INTERFACE variable is set to eth0 and yours was br0. Try changing that:

@MarshalleqI actually just tried it after reading your post and being curious about using Mattermost. I hate how Gitlab says: oh it's just a one-line change and poof! you'll magically have a chat server. It's never that easy! haha Yes, my Gitlab starts normally after the reconfigure command. You might have a typo in that file, just a thought. When things go wrong with Gitlab, I normally look at this log file: tail -f /var/log/gitlab/gitlab-rails/production.log There are other log files in that folder that might be worth looking at depending on what's going on. Of course, there's always the docker logs as well.

How am I supposed to enable mattermost if I don't have a hostname? I'm currently using gitlab just as: http://UNRAID-IP-ADDRESS:9080 No fancy nginx reverse proxy or a hostname or anything like that. I went into /etc/gitlab/gitlab.rb and added the line: mattermost_external_url 'http://UNRAID-IP-ADDRESS:8065' (I also tried it without the port number) and ran: gitlab-ctl reconfigure and although Gitlab still comes up, going to http://IP:8065 does not work. How else is it supposed to work if you don't use URLs?

I think I just copy-pasted the contents into a new file but in general, this is how you copy a file that's in a container while you're on the host's teminal: docker cp <containerId or name>:/file/path/within/container /host/path/target for example: docker cp pihole:/etc/hosts /mnt/user/appdata/pihole/pihole/ FYI. You get the name or containerId fields from the output of: docker ps

Thank you. As a new user, I appreciate that. I appreciate that my Kodi and AppleTV and SmartTVs can just access the share on the network without any hassle. Yes, I am aware of the security implications that come with this ease.

Haha Thanks for the upside mate! (always look on the bright side of life)

Sheesh, I wish I read this first. I've used this command on other PCs with docker but I didn't think that it would complete remove forever the entries I had for them under my Docker tab in Unraid. I had a ton of apps that happened to be off at the time because I wasn't actively using them. Is there a log of what names they were somewhere? I can always re-install them from the Community App Store but I don't even know what all the ones were. Unfortunately, I closed the terminal window after running that command.

Ever since I started using PiHole, I've been having trouble logging into my Nest account. It only works if I use a VPN to login. Has anyone else noticed this?

Excuse the stupid question but if I have a openvpn .ovpn configuration file, can I use it with Wireguard or is Wireguard its own thing? I would like to have my Unraid server use my .ovpn file to connect using my own VPN provider. i.e. be a VPN client and have my VM use that interface/tunnel. I'm not looking for it to be a server. Is that possible with Wireguard?

@peter_sm @steini84 Both links on here are no longer active. I was able to get the openvpn client to work and connect. How do I then get my VM to use that new tun5 VPN interface?

I just wanted to share a trick I used to have hostnames show up in the Pihole Dashboard for my local devices instead of IP addresses. Like this: First make a copy of the /etc/hosts file in the PiHole container and place it in the app data folder on the host where you can modify it to suit your local LAN. Then I just added a volume mount via the docker template page to link the two files

you can install your favourite editor (nano, vim, emacs) apt-get update apt-get install nano

Don't. The person who wrote the message "VM manager must be Stopped to change (see Settings)" or the Network settings page should. What does your DNS server entry have to do with your drive array?

/etc/rc.d/rc.nginx restart /etc/rc.d/rc.php-fpm restart