Re: [CentOS] NFS Share fails to mount at boot time
Felix Natter writes: > hi Bill, > > Bill Gee writes: >> My suggestion - Add "_netdev" to the parameters list: >> >> NAS2HOST:/volume1/export/ /mnt/NAS2 nfs _netdev,rw,vers=3,soft,bg,intr 0 >> 0 > > thanks for the hint. I added this, and so far I did not see the > problem. Cannot say for sure though, as this does not occur always. For the record: I worked around the problem with the "xsystemd.automount" mount option, which triggers the mount on first access. This seems to work fine. Best Regards, Felix -- Felix Natter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Delete local user/group but not LDAP one
hello fellow linux users, thank you for your answers. Gordon Messmer writes: > On 11/25/21 21:24, Thomas Mueller wrote: >> at least it seems that save, that ansible >> * >> https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/user.py#L625 >> >> >> * >> https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/user.py#L640-L643 >> >> >> >> and puppet >> * >> https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/user/useradd.rb#L12 >> >> >> >> are using it, when you specify "local=yes" or "forcelocal=true". > > > I suppose someone should file bug reports. luserdel probably could be used > to confine actions to the local host, as long as ansible/puppet provided > their own libuser.conf and set the LIBUSER_CONF to the path of that > file... I attached the /etc/libuser.conf. Is it safe to use luserdel/lgroupdel with these settings (without affecting LDAP)? modules = files shadow -> The man page says "A list of module names to use when not creating user or group entries..." How about if I disable networking so that the LDAP Server is not reachable (pingable) before running luserdel/lgroupdel? Would that be 100% safe? Many Thanks and Best Regards! -- Felix Natter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Delete local user/group but not LDAP one
Dear fellow linux users, I have a computer with a local user X that shadows an LDAP user of the same name (and group). I know I can use: userdel X groupdel X but how do I make sure that the LDAP is not changed, and only the local user/group is deleted? This is very critical. Many Thanks and Best Regards, -- Felix Natter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] GNOME UI / gnome-shell broken
Jonathan Billings
writes:
hello Jonathan,
> On Tue, Aug 24, 2021 at 08:07:10PM +0200, Felix Natter wrote:
>>
>> hello CentOS7 users,
>>
>> I have an up-to-date Scientific Linux 7 (_very_ similar to CentOS7).
>>
>> The problem is that if one user (we have central homes) logs into any
>> machine, we only see a desktop with icons, but no window decorations or
>> top/bottom bars ("panels") (for both gnome-classic and gnome3).
>
> When you say you have "central homes", does that mean they're a
> network filesystem? What kind of filesystem? If it's NFS, do you
> have the use_nfs_home_dirs SELinux boolean enabled?
Thank you for your answer.
The NFS was mounted fine, it was some GUI configuration that was broken.
We resolved the problem by creating a new home, and copying over the
user data (not the configuration).
Cheers and Best Regards,
--
Felix Natter
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] GNOME UI / gnome-shell broken
hello CentOS7 users,
I have an up-to-date Scientific Linux 7 (_very_ similar to CentOS7).
The problem is that if one user (we have central homes) logs into any
machine, we only see a desktop with icons, but no window decorations or
top/bottom bars ("panels") (for both gnome-classic and gnome3).
I can fix the window decorations by running "metacity --replace", but
the other problem remains.
I tried to remove .gnome, .gnome2, .gconf, .metacity, .cache, .dbus,
.dmrc.
I noticed that when starting "gnome-shell --replace" from a terminal, I
get "Failed to migrate monitor configuration for ... Empty
Configuration", and when running gnome-control-center, the option
"Displays" shows "Could not get screen information" and the console
shows: 'Name "org.gnome.Mutter.DisplayConfig" does not exist'.
This happens both when logging in physically and when logging in
virtually using VNC.
How can I fix this? Do I need to reset more of GNOME's config?
Many Thanks and Best Regards!
Felix
--
Felix Natter
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS Share fails to mount at boot time
hi Bill, Bill Gee writes: > My suggestion - Add "_netdev" to the parameters list: > > NAS2HOST:/volume1/export/ /mnt/NAS2 nfs _netdev,rw,vers=3,soft,bg,intr 0 > 0 thanks for the hint. I added this, and so far I did not see the problem. Cannot say for sure though, as this does not occur always. Best Regards, Felix > > Bill Gee > > > On Tuesday, August 17, 2021 9:18:53 AM CDT Felix Natter wrote: >> hello fellow CentOS Users, >> >> on Scientific Linux 7 (_very_ similar to CentOS7), I get this when >> trying to mount NFS Shares (exported from Synology NAS) automatically at >> boot time: >> >> [root@HOST ~]# journalctl -b 0 | grep NAS[20] >> Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS0... >> Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS2... >> Jul 01 13:32:09 HOST systemd[1]: mnt-NAS0.mount mount process exited, >> code=exited status=32 >> Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS0. >> Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS0.mount entered failed >> state. >> Jul 01 13:32:09 HOST systemd[1]: mnt-NAS2.mount mount process exited, >> code=exited status=32 >> Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS2. >> Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS2.mount entered failed >> state. >> >> I read that enabling NetworkManager-wait-online.service can mitigate >> that, but it's already enabled: >> >> [root@HOST ~]# systemctl list-unit-files|grep wait >> chrony-wait.service disabled >> NetworkManager-wait-online.service enabled >> plymouth-quit-wait.service disabled >> >> /mnt/NAS2 is defined in /etc/fstab (/mnt/NAS0 is mounted analogously): >> >> NAS2HOST:/volume1/export/ /mnt/NAS2 nfs rw,vers=3,soft,bg,intr 0 0 >> >> This does not always occur, and it seems to be a race condition, because >> it did not occur a few months ago, before we moved offices (when only >> the networking changed slightly). >> >> Of course, once the computer is booted, I can always mount the shares >> without problems. >> >> Does someone have an idea? >> >> Many Thanks and Best Regards, >> -- Felix Natter debian/rules! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] NFS Share fails to mount at boot time
hello fellow CentOS Users, on Scientific Linux 7 (_very_ similar to CentOS7), I get this when trying to mount NFS Shares (exported from Synology NAS) automatically at boot time: [root@HOST ~]# journalctl -b 0 | grep NAS[20] Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS0... Jul 01 13:32:09 HOST systemd[1]: Mounting /mnt/NAS2... Jul 01 13:32:09 HOST systemd[1]: mnt-NAS0.mount mount process exited, code=exited status=32 Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS0. Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS0.mount entered failed state. Jul 01 13:32:09 HOST systemd[1]: mnt-NAS2.mount mount process exited, code=exited status=32 Jul 01 13:32:09 HOST systemd[1]: Failed to mount /mnt/NAS2. Jul 01 13:32:09 HOST systemd[1]: Unit mnt-NAS2.mount entered failed state. I read that enabling NetworkManager-wait-online.service can mitigate that, but it's already enabled: [root@HOST ~]# systemctl list-unit-files|grep wait chrony-wait.service disabled NetworkManager-wait-online.serviceenabled plymouth-quit-wait.servicedisabled /mnt/NAS2 is defined in /etc/fstab (/mnt/NAS0 is mounted analogously): NAS2HOST:/volume1/export/ /mnt/NAS2 nfs rw,vers=3,soft,bg,intr 0 0 This does not always occur, and it seems to be a race condition, because it did not occur a few months ago, before we moved offices (when only the networking changed slightly). Of course, once the computer is booted, I can always mount the shares without problems. Does someone have an idea? Many Thanks and Best Regards, -- Felix Natter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
