![]() ![]() etc/apparmor.d/-confine.real $ file /var/lib/snapd/apparmor/snap-confine/nfs-support & cat /etc/apparmor.d/. Mai 06 06:10:06 jammy systemd: Started Snap Daemon. ![]() Mai 06 06:10:01 jammy snapd: backend.go:133: snapd enabled NFS support, additional implicit network permissions granted Mai 06 06:10:01 jammy snapd: daemon.go:340: adjusting startup timeout by 1m30s (pessimistic estimate of 30s plus 5s per snap) Mai 06 06:10:01 jammy snapd: patch.go:63: Patching system state level 6 to sublevel 3. ![]() Mai 06 06:10:01 jammy snapd: patch.go:63: Patching system state level 6 to sublevel 2. Mai 06 06:10:01 jammy snapd: patch.go:63: Patching system state level 6 to sublevel 1. Mai 06 06:10:01 jammy snapd: overlord.go:268: Acquired state lock file Mai 06 06:10:01 jammy snapd: overlord.go:263: Acquiring state lock file Mai 06 06:10:01 jammy snapd: AppArmor status: apparmor is enabled and all features are available ![]() Mai 06 06:10:01 jammy systemd: Starting Snap Daemon. Mai 06 06:09:57 jammy systemd: rvice: Consumed 24.749s CPU time. Mai 06 06:09:57 jammy systemd: Stopped Snap Daemon. Mai 06 06:09:57 jammy systemd: rvice: Deactivated successfully. 1 myuser myuser 524 May 11 23:09 flutter drwxr-xr-x. when I run ls -la in /opt I get this: drwxr-xr-x. I don't want to install the snap package. Mai 06 06:09:57 jammy snapd: overlord.go:504: Released state lock file when I run flutter -version in the terminal I get zsh: permission denied: flutter. Mai 06 06:09:57 jammy systemd: Stopping Snap Daemon. Mai 06 06:09:57 jammy snapd: main.go:155: Exiting on terminated signal. Mai 06 05:54:01 jammy snapd: storehelpers.go:721: cannot refresh snap "gtk-common-themes": snap has no updates available Mai 06 05:53:53 jammy snapd: storehelpers.go:721: cannot refresh: snap has no updates available: "bare", "cmake", "core", "core20", "dust", "firefox", "gnome-3-38-2004", "pdftk", "snap-store", "snapd", "snapd-desktop-integration" Mai 05 21:39:16 jammy snapd: storehelpers.go:721: cannot refresh snap "firefox": snap has no updates available Mai 05 21:38:54 jammy snapd: storehelpers.go:721: cannot refresh: snap has no updates available: "bare", "cmake", "core", "core20", "dust", "gnome-3-38-2004", "gtk-common-themes", "pdftk", "snap-store", "snapd", "snapd-desktop-int> Mai 05 14:48:53 jammy systemd: Started Snap Daemon. Mai 05 14:48:53 jammy snapd: daemon.go:340: adjusting startup timeout by 1m30s (pessimistic estimate of 30s plus 5s per snap) Mai 05 14:48:52 jammy snapd: overlord.go:268: Acquired state lock file Mai 05 14:48:52 jammy snapd: overlord.go:263: Acquiring state lock file Mai 05 14:48:52 jammy snapd: AppArmor status: apparmor is enabled and all features are available Yes the line can be found mai 05 14:48:51 jammy systemd: Starting Snap Daemon. This is what I do in sssd config $ grep ldap_user_name /etc/sssd/nf My account is “ but my home directory is “p000000xxxxx”. Maybe the problem is related to the fact that our home directories are not map on the uid field ? Now that we know SELinux is the problem, what can we do about it? There are four possible solutions at this point to get Postgres working again:įirst, we can simply edit the PGDATA assignment within the /etc/init.d/postgresql file to point to the actual data dir, and bypass the symlink.So, asked to the NFS guy for the export line, waiting for his answer. SELinux did not like the fact that the postmaster process was trying to read across that symlink. tmp symlink, not the permissions of the /private/tmp directory that the symlink points to. Here we see that although the postgres user owns the symlink, owns the data directory at /var/lib/pgsql/data, and owns the file in question, /var/lib/pgsql/data/nf, the conf file is no longer really on /var/lib/pgsql, but is on /mnt/newpgdisk. couldnt create error file for command: permission denied. 1 postgres postgres 16816 23:57 /var/lib/pgsql 2 postgres postgres 4096 23:56 /var/lib/pgsql/data 1 postgres postgres 18 23:55 /var/lib/pgsql -> /mnt/newpgdiskĭrwx. # ls -ld /var/lib/pgsql /var/lib/pgsql/data /var/lib/pgsql/data/nf ![]()
0 Comments
Leave a Reply. |