You are not logged in.
I had a btrfs root partition issue on my server and I restored it from tar.gz backup with
tar -zxvpf /fullbackup.tar.gz
However, now I seem to have some strange issues. For example, when I try to run snapper to configure snapshots, I get:
Failure (org.freedesktop.DBus.Error.Spawn.PermissionsInvalid).
or trying to access user's crontab, I get:
You (malina) are not allowed to access to (crontab) because of pam configuration.
Also, mounting fusemounts as user no longer work:
fusermount: mount failed: Operation not permitted
What is causing that and is there a way to fix it?
Last edited by Lockheed (2014-10-16 08:56:09)
Offline
In fact, I even get this issue when I try to switch to superuser:
$ su
Password:
su: Authentication failure
and when I am logged-in as root and try to run snapper:
[root@malina ~]# snapper -c root list
Failure (org.freedesktop.DBus.Error.Spawn.PermissionsInvalid).
Offline
This post included a solution: http://askubuntu.com/questions/201681/f … k-settings Does that help?
I know "-p" is supposed to preserve permissions, but maybe the "setuid" bit didn't get preserved properly.
Offline
Thanks. That helped with Failure (org.freedesktop.DBus.Error.Spawn.PermissionsInvalid) error.
However, all the other issues persist.
Last edited by Lockheed (2014-10-16 11:51:11)
Offline
You (malina) are not allowed to access to (crontab) because of pam configuration.
Maybe try checking the "/etc/security/access.conf" file: http://serverfault.com/questions/620157 … strictions
Maybe another setuid problem (see the comment here): http://rbsrhel.blogspot.com/2013/03/job … batch.html
fusermount: mount failed: Operation not permitted
Seems to be another setuid problem: http://forums.debian.net/viewtopic.php? … 58#p442845
That was after, like, a two minute Google search. Lockheed, are you even trying? But seriously, I don't know why you seem to be having so many setuid problems. Is there a possibility you created that tar file without the "-p" option or something?
Last edited by drcouzelis (2014-10-16 12:13:00)
Offline
I googled it out, too, and I even tried implementing that access.conf change, but it made me unable to login through ssh at all.
I reverted it back, because - after all - I never had that set up before, and things were working. So the issue must be in some other place and instead of fighting with smoke, I try to get to the fire.
Yes, the tar file was created with "-p", more precisely with "tar -cvpzf".
Offline
(Oops! Please see my edit above.)
Offline