Thanks for the update.
So far I only see three of us using AD. All 2012R2. Is anybody using other version?
Thanks for the update.
So far I only see three of us using AD. All 2012R2. Is anybody using other version?
One way to avoid the confusion of being able to select updates might be. Instead of having to select an update to read the change log make double clicking the update open the change log. Also would make reading the change logs easier.
Thanks for testing. What AD are you connecting to?
Display MoreThanks for the description, it was really easy to follow also for a non-expert like me. Loging in vs. samba is working well for domain users, also the NFS shares for my mediaplayer are working like before with OMV 5. But I encounter some problems, which are surely caused by my missing knowledge abbout that stuff.
Here are my open topics:
- Logging in via ssh for domain users iss not working (putty simply is crashing when I try that, using root user is working). I entered the following line in ssh extra options - "AllowGroups root ssh "domänen-benutzer"", because german domain.
- Logging on to FTP (using FTP rush) is not working for domain users but for root user - I always get the error "Login incorrect" when trying with a domain user. I used this already with OMV 5 integrated in a AD, which was working fine.
- I activated the "home directories" option in samba, then a folder "homes" is visible, but empty. I entred the location of my user directories in the samba extra options. Then they also visible (folder "homes" also), but not accessible (would be an ACL problem I think).
I think these problems aare causing smiles in your faces, because they are probably simple to fix, but as I wrote in the beginning I'm no expert, I think noob is beter classification for my skills with linux and OMV stuff.
Would be nice if you or someone else has the idea(s) and the time to help me in this cases.
Finally I want to say, that I really appreciate all the work which is done here and the help which is given in this forum. Please excuse, If my problems are already solved in other posts in this forum and I havn't found them.
My goal was only to connect only to AD for authentication of samba. That is why you see the above. I have not used the other services for years. That said it should not be too hard to get them working. The users and groups are showing up with getent passwd and getent group and I think that is where OMV gets them from for the web ui. So I would think you should be able to create a share and assign groups and or users to it.
Not sure why you want users ssh ing to OMV. But from the ssh settings page. Users must be assigned to the ssh group to be able to log in via SSH. So I guess you would need to create an "ssh user" in AD. Look at man sssd.conf there is some stuff about ssh service I think.
Also I didn't try to manage AD from OMV.
Please add what you learn so we can all learn also.
PS: As you search you will find that even many experienced users are noobs at AD. Learn and share.
Most looks fine. Not sure about this line.
WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients results in undefined behaviour.
Run testparm to see if there are problems with your samba config.
Is it compressing it twice? Once in OMV and again in Proxmox? Is it swapping memory to disk?
This is not my issue only trying to help the op. And maybe explain why someone may want to do this at your request. It is going to cause support issues either way. We all see that some users don't read things until there is a problem. Those we can't help until something breaks. Documenting is for those who will read it. They should be supported too. LOL
PS: You are an advanced user by many other definitions. You didn't get demoted by not ever doing this. LOL
Thanks
The user may need something like OMVip\user to tell it to auth against OMV.
Try to connect from the windows command line. You will get some errors that way. Gave up on windows and don't remember of the top of my head. But google or such knows how to do it.
Anybody picking and choosing updates is probably an advanced user. Even advanced users don't know everything and deserve some support. A warning at least and then they can research or ask here. LOL
Debian is free open source software. We use it for that reason. Restricting it is counter productive. Might as well go apple or windows if you don't mind being limited by the powers that be. Being free has a price and we have to prepare for what may happen. Being warned is good enough as far as I am concerned.
Perhaps you could use a live cd and copy the config files. Not sure which ones.
If someone posts a list it would be easy enough to write a primitive shell script to collect them.
I am not worried about me. I can usually handle whatever comes up. I agree that adding other things is at our own risk and an advanced and possibly unsupported state. But a warning is at least necessary.
So at the moment The ui and apt dist-upgrade show this.
openmediavault openmediavault-owntone openmediavault-photoprism openmediavault-s3 openmediavault-snmp
This is hypothetical but if I only want to upgrade openmediavault-owntone. I choose that. Hitting "updates" gives see attacment.
If the number selected does not match the total available. Please put an advanced tab explaining the philosophy and maybe how to get around it at your own risk. Including a warning to do a backup.
Thanks
As long as OMV can be installed on debian and other things can co exist I think it would be a good option to allow selection. This is not apple yet. Don't take that the wrong way please. Maybe add a warning if not all selected.
In my case I would worry about samba updates breaking active directory. Could be in either debian or OMV. Since I run OMV on proxmox I just run a snapshot. Then I can roll back if needed and troubleshoot in a clone.
For hardware I see some new intel nic seems not to work. I didn't follow it but if the workaround gets overridden that would not be good.
Would be nice if OMV had a rollback feature. I think that would be too much work. Maybe taking a backup would be enough. But how many do that. LOL
Not sure why you want to install one update and not the rest though.
Maybe hardware or other program would be broken by the upgrades. You could try "apt install whatever.deb". Should install just that package and maybe dependencies.
Maybe
cd /root then
cat .profile
Reinstall may be in order?
Don't know why /dev/sdg2 is recovering journal? If you are shutting down properly that is suspicious.
Try this.
root@omvad3:~# cat .profile
# ~/.profile: executed by Bourne-compatible login shells.
if [ "$BASH" ]; then
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
fi
test -t 0 && mesg n 2> /dev/null || true
root@omvad3:~#
FYI
ls -la /boot
-rw-r--r-- 1 root root 53701083 Mar 7 08:18 initrd.img-5.15.0-0.bpo.3-amd64
-rw-r--r-- 1 root root 58800550 Apr 5 08:43 initrd.img-5.16.0-0.bpo.4-amd64
Welcome to the forum.
Did you try omv-firstaid on the cli?