daninet

Members
  • Posts

    11
  • Joined

  • Last visited

daninet's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I'm having trouble with the setup and not sure why. I have tried to follow the instructions. The unifi web interface is not reachable. These are the steps I took: 1. backup the deprecated ls.io unifi container. 2. Install mongodb with the init script init-mongo.js db.getSiblingDB("unifi").createUser({user: "daninet", pwd: "pwd", roles: [{role: "dbOwner", db: "unifi"}]}); db.getSiblingDB("unifi_stat").createUser({user: "daninet", pwd: "pwd", roles: [{role: "dbOwner", db: "unifi_stat"}]}); docker run docker run -d --name='MongoDB' --net='bridge' -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="TEVENAS" -e HOST_CONTAINERNAME="MongoDB" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/jason-bean/docker-templates/master/jasonbean-repo/mongo.sh-600x600.png' -p '27017:27017/tcp' -v '/mnt/user/appdata/mongodb/':'/data/db':'rw' -v '/mnt/user/appdata/mongodb/mongo_init/init-mongo.js':'/docker-entrypoint-initdb.d/init-mongo.js':'rw' 'mongo' 53b1599bcd21ae9bca1461eb19327e5e4a4952ee6df196f2025fe28c26cd325a Then setup the new unifi container: docker run -d --name='unifi-network-application' --net='bridge' -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="TEVENAS" -e HOST_CONTAINERNAME="unifi-network-application" -e 'MONGO_USER'='daninet' -e 'MONGO_PASS'='pwd' -e 'MONGO_HOST'='unifi-db' -e 'MONGO_PORT'='27017' -e 'MONGO_DBNAME'='unifi' -e 'MEM_LIMIT'='1024' -e 'MEM_STARTUP'='1024' -e 'MONGO_TLS'='' -e 'MONGO_AUTHSOURCE'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://192.168.1.200:8443/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/unifi-network-application-icon.png' -p '8443:8443/tcp' -p '3478:3478/udp' -p '10001:10001/udp' -p '8080:8080/tcp' -p '1900:1900/udp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '6789:6789/tcp' -p '5514:5514/udp' -v '/mnt/user/appdata/unifi-network-application':'/config':'rw' 'lscr.io/linuxserver/unifi-network-application' aaa2d5762f3f99c50def5ef5a419972aba766006c1351c58382cfe57347f8bf5 Now the container log is telling me the following: *** Waiting for MONGO_HOST unifi-db to be reachable. *** *** Defined MONGO_HOST unifi-db is not reachable, cannot proceed. *** What is exactly unifi-db? I did not define it anywhere but the documentation says use this. They are both on the same subnet. My other DBs are working on this subnet.
  2. Hi, Thank you for your replies. I think I have cracked it and it is related to inodes and unraid's cache. The file inode changes when unraid moves the file from cache to hdd and the share unmounts. Adding noserverino flag to the smb mount resolves the problem. This is the proper config for unraid cached shares with fstab: //server_address/share_name /mount/path cifs credentials=/home/username/.smbcredentials,uid=1000,gid=1000,vers=3.0,noserverino,nounix,_netdev 0 0 Thank you for all the help it was really useful and have learnt a lot.
  3. Thank you for the detailed answer. There is a lot to unpack and I will dig myself through the settings. As for some of your questions: I initially thought xdg-desktop-portal is somehow responsible (the window that lets you pick or save a file). Very often the following happens: I download a file (any file really, pdf, image etc) from the internet, save the file to my share with the xdg-desktop-portal and when I open dolphin the share is no longer reachable. Edit: I'm really happy now, I was able to trigger it with xdg-desktop-portal and record it also. See video attached. This is an SMB mount. This also happens if I just let it be for an hour. 2024-01-16_10-54-59.mkv
  4. Hello, Thank you for your answer. First, for the SMB: As I mentioned in my original post, I have multiple windows machines and SMB shares work flawlessly. On my linux system the SMB mount works for... hours. Then suddenly it is unreachable. Then I have to umount and mount -a to make it work again. I posted above the fstab mount points I have used, I don't think I have any error in my setup on client side. It is working. Just the connection is dropping randomly for one of the share. The only settings I dont have are the global parameters you have defined, although looking on them I doubt they are responsible for this. I'm pretty much stalled why it is not working so yes, as you said I decided to move to NFS. As you see in my first post I already have those defined in fstab, the SMB is commented out, I kept it for reference. I have NFS enabled, export yes, set to private and have defined the rules for my linux system's IP address to be sys,rw Now the following is happening: I'm unable to mount the share called Private, only the other two (work and downloads), I get permission denied message in terminal. The settings are same for all 3 mounts word to word. I found no logic why one is working why the other not. So for private I have used SMB and NFS for the rest. SMB still disconnects after an hour or so, so I'm at where I started. For the record, I'm distrohopping from time to time and the same happened of Debian, Ubuntu and OpenSuse Tumbleweed (that is my current system).
  5. This forum is my last hope, please help. 🥺 I have been through ubuntu forums, then opensuse forums then multiple subreddits trying to get help but seemingly I have no grip on the problem. I was confident it is a linux problem (still might be) I have an unraid home server and avarage number of laptops and PCs around the house. Everyone is a windows user and I never had any issue with SMB shares on windows. However I'm a linux user and I'm having a lot of trouble mounting my shares. I have been through ubuntu, debian and now on opensuse tumbleweed and the issue is the same on all distro. Last year I was using windows on this PC and never had trouble mounting my shares. I have tried NFS and SMB shares mounting with the same result. (This was a very generic reply I got elsewhere why I dont use NFS, I do now, same problem) This is what happening: I'm mounting my shares with fstab (tried autofs also, same result), everything working fine then after some undefined period of time one or two of my shares are not accessible. It is always accessible on system startup. I have public and private shares, it is not related to the authentication, sometimes public is also inaccessible (on SMB). There is no specific action that results in my shares inaccessible. Sometimes I'm just browsing the web, sometimes I work from the shares. I -obviously- always notice it when I try to open a file from my share or save something there (so on linux it is either through dolphin or xdg-desktop-portal). My linux system's log has no entry on it, only when I try to open the path it throws a path unavailable error. This is how my fstab looks like (currently using NFS) #//192.168.1.200/Private /smb/Private cifs credentials=/home/daninet/.smbcredentials,uid=1000,gid=1000,vers=3.0,nounix,_netdev 0 0 #//192.168.1.200/Work /smb/Work cifs credentials=/home/daninet/.smbcredentials,uid=1000,gid=1000,vers=3.0,nounix,_netdev 0 0 #//192.168.1.200/Download /smb/Download cifs credentials=/home/daninet/.smbcredentials,uid=1000,gid=1000,vers=3.0,nounix,_netdev 0 0 192.168.1.200:/mnt/user/Private /smb/Private nfs defaults 0 0 192.168.1.200:/mnt/user/Work /smb/Work nfs defaults 0 0 192.168.1.200:/mnt/user/Download /smb/Download nfs defaults 0 0 My "Private" share is currently inaccessible, this is what I see: https://imgur.com/a/kZEMYGA To solve the problem I always have to: sudo umount /smb/Private sudo mount -a After this I can access it again: https://imgur.com/a/IoT7Nv8 As I have mentioned I have used the same fstab config on 3 different distros with the same result and always have this weird timeout error. I don't know if this is the problem with the linux kernel in general, fstab, cifs, unraid. I don't know where to look for any kind of error code and I certainly don't know why it is happening. Diagnostics attached. I'm open to any idea to resolve this. Thank you tevenas-diagnostics-20240107-1714.zip
  6. The following is happening irregularly. Watching a movie on plex then suddenly streaming stops. Unraid web interface unreachable. I'm able to connect via ssh and send etc/rc.d/rc.docker stop Suddenly the unraid interface is reachable again. I restart the server and have the docker running again. This happens ~once a month but now it has happened two times in a row. I had situations when it just woke up and after about 3-4 minutes the streaming suddenly continued. I have setup a syslog server in hopes of seeing something but it looks like logging entirely stops. If you will look on the attached logs there should be something around 21:38 just before I SSH in but nothing is there at least I don't see anything. Today I did not had to kill the docker service it restored itself. This is now a frequent issue and I'm not even sure which way to start checking. My diagnostics are attached below. Any help appreciated. tevenas-diagnostics-20230816-2246.zip
  7. First time I tought it was my kid, he regularly plays "dad working" and just slams the keyboard while I'm leaving my PC for 5 seconds. It is happening second time and I have no idea where to start. Now it is surely not my kid. I have backup, nothing is lost, it is just very annoying. Nexcloud is the only thing having access to this share across all of my things but how exactly nexcloud would wipe a share? I have home assistant VM (no access to this share), a bunch of dockers like everyone else from networking tools, databases and so on. Is there a log where you can track deletion of files? I dont even know which way to go to start with the issue.
  8. Got this figured out however I dont know what relation the problem has to the solution. I have mounted multiple folders into the docker other than the default data folder, I made data2, data3 and so on then I have these mapped inside nextcloud. For whatrever reason this broke nextcloud docker, I removed the path mapping, rerun the docker template and the system started. Then I added my mappings again and there I have it, running again and all my folders are mapped.
  9. Hello, I have this issue with my docker image. It tries to update itself but seemingly fails. I would appreciate any suggestion how to solve this.
  10. I have the same issue. I keep getting notifications from unifi controller that there are duplicate IP addresses on my network. Upon checking it it is the shim-br0 interface that is using the same IP address as unraid. I want to know if there is a way to get rid of this as disabling the notifications on this warning is not a solution for me!