Re: Unexpected permission denied

On 26/01/2023 11:04, Greg Wooledge wrote: On Thu, Jan 26, 2023 at 10:26:34AM +0700, Max Nikulin wrote: Greg, I agree with your warnings. Just out of curiosity, is there a reason why the following variant may still be unsafe? runas() { local who=$1; shift; su --login "$who" --shell=/bin/bash

Re: Unexpected permission denied

On Thu, Jan 26, 2023 at 10:26:34AM +0700, Max Nikulin wrote: > Greg, I agree with your warnings. Just out of curiosity, is there a reason > why the following variant may still be unsafe? > > runas() { local who=$1; shift; su --login "$who" --shell=/bin/bash > --command='"$0" "$@"' -- "$@"; } 1)

Re: Unexpected permission denied

On 25/01/2023 21:52, Greg Wooledge wrote: On Wed, Jan 25, 2023 at 03:36:33PM +0100, Yassine Chaouche wrote: runas_wwwdata () { echo su - www-data -s /bin/bash -c "$*"; su - www-data -s /bin/bash -c "$*" } ... su(1) is pretty much the WORST possible choice for this, as it forces you

Re: Unexpected permission denied

On Wed, Jan 25, 2023 at 2:54 AM jeremy ardley wrote: > > [...] > Rechecked, thanks. The vendor directory didn't have x permissions. > Fixed. Now to track down all the other files similarly afflicted in the > screaming pile of manure called drupal. > > root@gram01:/# ls -ld

Re: Unexpected permission denied

On Wed, Jan 25, 2023 at 2:34 AM wrote: > > On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: > > [...] > > > 0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", > > 0x7fffdc580970) = -1 EACCES (Permission deni

Re: Unexpected permission denied

Greg Wooledge (12023-01-25): > When investigating permissions, there's really no reason to do the > investigation as a non-root user. When investigating permissions, doing your tests as root instead of the user who is having the permissions issues, is a sure way for hiding the issue. Nothing to

Re: Unexpected permission denied

On Wed, Jan 25, 2023 at 03:36:33PM +0100, Yassine Chaouche wrote: > Le 1/25/23 à 3:22 PM, Nicolas George a écrit : > > For the current problem: > > > > sudo -u www-data namei /var/www/nextcloud/3rdparty/autoload.php > > > > … will cause the command to be executed in an environment closer to the

Re: Unexpected permission denied

Le 1/25/23 à 3:22 PM, Nicolas George a écrit : For the current problem: sudo -u www-data namei /var/www/nextcloud/3rdparty/autoload.php … will cause the command to be executed in an environment closer to the one that causes the problem, and therefore is more likely to reveal it. Use any

Re: Unexpected permission denied

Yassine Chaouche (12023-01-25): > I prefer to use namei -l. namei is good indeed. > root@cloud[10.10.10.84/24] 15:15:43 ~ # namei -l > /var/www/nextcloud/3rdparty/autoload.php For the current problem: sudo -u www-data namei /var/www/nextcloud/3rdparty/autoload.php … will cause the command to

Re: Unexpected permission denied

e got ACLs, getfacl(1) and friends. You've got AppArmor, which can cause Permission denied errors on files outside of a program's designated working areas. This usually crops up when someone tries to move stuff to a different location in the file system(s) with a symlink to the new location.

Re: Unexpected permission denied

Le 1/25/23 à 8:44 AM, jeremy ardley a écrit : Anyway tree permissions: root@gram01:/# ls -ld var drwxr-xr-x 12 root root 4096 Nov  7 23:30 var root@gram01:/# ls -ld var/www drwxr-xr-x 5 www-data www-data 4096 Jan 23 16:33 var/www root@gram01:/# ls -ld var/www/grammartiste.com/

Re: Unexpected permission denied

Hi, jeremy ardley wrote: > > > I have vague memories there are more file flags in newer Linux file > > > systems? Dan Ritter wrote: > > There are extended attributes, [...] > > lsattr and chattr are the relevant commands. Nicolas George wrote: > What you describe are file attributes specific

Re: Unexpected permission denied

ot ACLs, getfacl(1) and friends. You've got AppArmor, which can cause Permission denied errors on files outside of a program's designated working areas. This usually crops up when someone tries to move stuff to a different location in the file system(s) with a symlink to the new location. You

Re: Unexpected permission denied

Dan Ritter (12023-01-25): > There are extended attributes, of which the only one you are > likely to encounter is i, immutable. It is occasionally useful > to nail down the state of a file even when something properly > has write permissions for it. > > lsattr and chattr are the relevant

Re: Unexpected permission denied

jeremy ardley wrote: > I have vague memories there are more file flags in newer Linux file systems? There are extended attributes, of which the only one you are likely to encounter is i, immutable. It is occasionally useful to nail down the state of a file even when something properly has write

Re: Unexpected permission denied

On Wed, Jan 25, 2023 at 03:53:50PM +0800, jeremy ardley wrote: [...] > Rechecked, thanks. The vendor directory didn't have x permissions. Fixed. > Now to track down all the other files similarly afflicted in the screaming > pile of manure called drupal. uh-oh ;-) Cheers & good luck -- t

Re: Unexpected permission denied

On 25/1/23 15:44, jeremy ardley wrote: On 25/1/23 15:33, to...@tuxteam.de wrote: On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: [...]   0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", 0x7fffdc580970) = -1 EACCES (Permission denied)

Re: Unexpected permission denied

On 25/1/23 15:33, to...@tuxteam.de wrote: On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: [...] 0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", 0x7fffdc580970) = -1 EACCES (Permission denied) 0.34 lstat("/var/www/grammartiste

Re: Unexpected permission denied

On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: [...] > 0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", > 0x7fffdc580970) = -1 EACCES (Permission denied) > 0.34 lstat("/var/www/grammartiste.com/web/vendor/autoload.php&q

Unexpected permission denied

.29 stat("/var/www/grammartiste.com/web/index.php", {st_mode=S_IFREG|0755, st_size=549, ...}) = 0 0.34 getcwd("/var/www/grammartiste.com/web", 4096) = 30 0.30 stat("/var/www/grammartiste.com/web/autoload.php", {st_mode=S_IFREG|0755, st_size=312

Re: Question on permission denied (public key)

: git config --global user.email "n...@mail.com" git config --global user.name "new-username" After doing those when I run git pull it always gets: $ git pull Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the c

Question on permission denied (public key)

uot;n...@mail.com" git config --global user.name "new-username" After doing those when I run git pull it always gets: $ git pull Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository ex

Re: Re: Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

Thanks a ton! I'm running this container on my private network behind a NAT, so I'm not too worried about disabling apparmor. I ended up just giving as loose of a configuration I could and it did the trick. lxc.apparmor.profile = unconfined lxc.apparmor.allow_nesting = 1

Re: Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

e problem. > This is the journalctl log for the openvpn service: ... > Jul 16 20:32:30 dl systemd[70]: openvpn-client@pia.service: Failed to > set up mount namespacing: Permission denied And that is too. As usual with this kind of problems, journalctl log is useless. What you need is a

Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

systemd[70]: openvpn-client@pia.service: Failed to set up mount namespacing: Permission denied Jul 16 20:32:30 dl systemd[70]: openvpn-client@pia.service: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied Jul 16 20:32:30 dl systemd[1]: openvpn-client@pia.service: Main process

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Hi. On Thu, Oct 18, 2018 at 06:11:13AM +0200, steve wrote: > Le 17-10-2018, à 09:52:06 +0300, Reco a écrit : > > > > > And, finally, /var/log/audit/audit.log if you have auditd installed > > > > (hint - install it if you don't). > > > > > > grep apache /var/log/audit/audit.log > > > >

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On 2018-10-18 07:15, steve wrote: Le 18-10-2018, à 07:07:34 +0100, mick crane a écrit : On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On 2018-10-18 07:07, mick crane wrote: On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected ? Ah, OK I see you tried that. Would that not

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Le 18-10-2018, à 07:07:34 +0100, mick crane a écrit : On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected ? Yes I did and apache failed to

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected ? mick -- Key ID4BFEBB31

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Le 17-10-2018, à 09:52:06 +0300, Reco a écrit : > And, finally, /var/log/audit/audit.log if you have auditd installed > (hint - install it if you don't). grep apache /var/log/audit/audit.log type=AVC msg=audit(1539750555.347:76): apparmor="DENIED" operation="open" profile="/usr/sbin/apache2"

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Thanks Reco for your input. I'll have to go trough it, but don't have time right now. Steve

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Le 17-10-2018, à 05:38:11 +, Steve Kemp a écrit : To recap you reported the original error: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied Now you've provided more details, from your audit-log: type=AVC msg=audit(1539750555.347:77

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

1 box systemd[1]: Starting The Apache HTTP Server... > > > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open > > > configuration file /etc/apache2/apache2.conf: Permission denied > > > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. > > >

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

To recap you reported the original error: > apache2: Could not open configuration file /etc/apache2/apache2.conf: > Permission denied Now you've provided more details, from your audit-log: > type=AVC msg=audit(1539750555.347:77): apparmor="DENIED" > operation=&qu

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Le 16-10-2018, à 06:39:01 +, Steve Kemp a écrit : ls -l /etc/apache2/apache2.conf -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf Getting nuts. Probably the permissions on /etc/apache2, or /etc are broken for the user www-data. ls -l /etc drwxr-xr-x 213 root root

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

The Apache HTTP Server... oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. oct 16 07:22:02 box apachectl[32122]: The Apache error log may have more information

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On Tue 16 Oct 2018 at 12:24:49 (-0400), Gene Heskett wrote: > On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote: > > > On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > > > Since leaving a sudo -i laying about is considered a security > > > breach, I'm amazed that the -i

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote: > On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > > Since leaving a sudo -i laying about is considered a security > > breach, I'm amazed that the -i option doesn't accept a timeout. Say > > in seconds, as if you think it

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote: > On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > > Since leaving a sudo -i laying about is considered a security > > breach, I'm amazed that the -i option doesn't accept a timeout. Say > > in seconds, as if you think it

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > Since leaving a sudo -i laying about is considered a security breach, I'm > amazed that the -i option doesn't accept a timeout. Say in seconds, as > if you think it will take 5 minutes to do the job as root, sudo -i300, > at the

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On Tuesday 16 October 2018 05:56:31 Jonathan Dowland wrote: > On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote: > >> sudo su - www-data -s /bin/sh > > > >Don't use sudo with su. It is evil. > >You want to use 'sudo -i' in this case. > > Fascism is evil. This is just unnecessary. > >

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Am 16.10.18 um 11:56 schrieb Jonathan Dowland: > On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote: >>>     sudo su - www-data -s /bin/sh >> >> Don't use sudo with su. It is evil. >> You want to use 'sudo -i' in this case. > > Fascism is evil. This is just unnecessary. Good point. > >

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote: sudo su - www-data -s /bin/sh Don't use sudo with su. It is evil. You want to use 'sudo -i' in this case. Fascism is evil. This is just unnecessary. (I'm guilty of still typing "sudo su -" via muscle memory even after your messages

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2 > > ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE) > > > > oct 16 07:22:01 box systemd[1]: Starting The Apache HTTP Server... > > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open > > configuration file /etc/apache2/apache2.conf: Perm

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

Am 16.10.18 um 08:39 schrieb Steve Kemp: >> >> ls -l /etc/apache2/apache2.conf >> -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf [...] > sudo su - www-data -s /bin/sh Don't use sudo with su. It is evil. You want to use 'sudo -i' in this case. [...]

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

: Starting The Apache HTTP Server... > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration > file /etc/apache2/apache2.conf: Permission denied > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. > oct 16 07:22:02 box apachectl[32122]: The Apache erro

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

x systemd[1]: Starting The Apache HTTP Server... > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration > file /etc/apache2/apache2.conf: Permission denied > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. > oct 16 07:22:02 box apachectl[32122]: The

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

> > ls -l /etc/apache2/apache2.conf > -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf > > > Getting nuts. Probably the permissions on /etc/apache2, or /etc are broken for the user www-data. Assuming you have sudo installed you can become "www-data", and test: sudo

apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

/apache2.conf: Permission denied oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. oct 16 07:22:02 box apachectl[32122]: The Apache error log may have more information. oct 16 07:22:02 box systemd[1]: apache2.service: Control process exited, code=exited status=1 oct 16 07:22:02 box

Re: '/proc/sys/kernel/core_pattern': Permission denied

t; as root (no sudo). > > root:~# sysctl -w kernel.core_pattern=core > sysctl: permission denied on key 'kernel.core_pattern' > > > root:~# echo "core" > /proc/sys/kernel/core_pattern > bash: /proc/sys/kernel/core_pattern: Permission denied > > root:~# rm /proc/sys/kernel/

'/proc/sys/kernel/core_pattern': Permission denied

': No such file or directory Ok problem is clear. abrt should handle segment faults but abrt is not installed. So I am trying to change the sysctl kernel.core_pattern to "core" as root (no sudo). root:~# sysctl -w kernel.core_pattern=core sysctl: permission denied on key 'kernel.core_patte

Re: usb permission denied

On Tue, 27 Sep 2016, Ric Moore wrote: libusb requires write access to USB device nodes. libusb couldn't open USB device /dev/bus/usb/001/006: Permission denied. If anyone can assist, I'd love to fix this. Ric You know the drill. For posterity's sake, can you provide more context? What

usb permission denied

libusb requires write access to USB device nodes. libusb couldn't open USB device /dev/bus/usb/001/006: Permission denied. If anyone can assist, I'd love to fix this. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and th

Re: NFS no_root_squash not working (permission denied)

On Thu, Aug 11, 2016 at 05:43:12PM +0200, Ulf Volmer wrote: > /etc/exports is > > /export/backup-n40l bob.clients(rw,no_subtree_check) > virt(rw,no_root_squash,no_subtree_check) I changed my /etc/exports from what I had to: /home arc1(ro,no_root_squash,sync,no_subtree_check) Ran

Re: NFS no_root_squash not working (permission denied)

On 08/10/2016 11:17 PM, Greg Wooledge wrote: > Any suggestions on what I can try to change? Could you post your jessie > server's /etc/exports and /etc/default/nfs-kernel-server configs, or at > least the parts relevant to the working no_root_squash mount? And any > other configs that I don't

Re: NFS no_root_squash not working (permission denied)

y > other configs that I don't know about > > Which kernel version? Just in case this is a kernel issue. Additional information: installing and rebooting into the jessie-backports kernel (linux-image-4.6.0-0.bpo.1-amd64) did not change anything. Still permission denied. I am still o

Re: NFS no_root_squash not working (permission denied)

ogled "debian disable nfsv4". It came up with http://unix.stackexchange.com/questions/205403/disable-nfsv4-server-on-debian-allow-nfsv3 I edited /etc/default/nfs-kernel-server as indicated in the answers, adding "--no-nfs-version 4" to *TWO* places. Restarted nfs-kernel-serve

Re: NFS no_root_squash not working (permission denied)

Le 10/08/2016 à 22:38, Ulf Volmer a écrit : >> Is there ANYONE using NFS with no_root_squash on jessie amd64 successfully? >> If so, please tell me how you did it! > NFS run here with jessie amd64 and no_root_squash fine w/o any problems. > > Server is jessie, client is centos/fedora. There must

Re: NFS no_root_squash not working (permission denied)

> Is there ANYONE using NFS with no_root_squash on jessie amd64 successfully? > If so, please tell me how you did it! NFS run here with jessie amd64 and no_root_squash fine w/o any problems. Server is jessie, client is centos/fedora. There must something wrong on your setup. best regards Ulf

Re: NFS no_root_squash not working (permission denied)

On Tue, Aug 09, 2016 at 09:14:56AM -0400, Greg Wooledge wrote: > On Mon, Aug 08, 2016 at 11:14:36AM -0400, Greg Wooledge wrote: > > It appears that no_root_squash is being ignored. Opened bug #833925. :(

Re: NFS no_root_squash not working (permission denied)

On Mon, Aug 08, 2016 at 11:14:36AM -0400, Greg Wooledge wrote: > It appears that no_root_squash is being ignored. > > 1) NFS server: svr4 (jessie) > > /home -no_subtree_check arc1(ro,no_root_squash,sync) Nobody? :( Additional information: * It's not limited to /home. Other

NFS no_root_squash not working (permission denied)

prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 10.76.142.85 prog 15 vers 3 prot UDP port 58163 svr4:/home on /mnt type nfs (rw) arc1:~# ls /mnt/wooledg/Maildir ls: cannot open directory /mnt/wooledg/Maildir: Permission denied arc1:~# su

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

On Dec 30, 2015, at 3:36 AM, Steffen Nurpmeso wrote: > Hello! > > Rick Thomas wrote: > |Hi Steffan, > > (My name is Steffen) Ooops! Sorry! > Well, just as already shown in this thread, on my local box it is > > ?0[sdaoden@wales nail.git]$ ll

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

Steffen Nurpmeso wrote on 12/30/15 12:36: > Hello! > > Rick Thomas wrote: > |-rwxr-sr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-nail/s-nail-privsep Wouldn't these be enough rights for mailx to do it's work? I.e., owner: root, group: mail, sticky bit for the group?

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

On Dec 30, 2015, at 9:51 AM, Jörg-Volker Peetz wrote: > Steffen Nurpmeso wrote on 12/30/15 12:36: >> Hello! >> >> Rick Thomas wrote: > > >> |-rwxr-sr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-nail/s-nail-privsep > > Wouldn't these be enough rights

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

Rick Thomas wrote: |On Dec 30, 2015, at 3:36 AM, Steffen Nurpmeso wrote: |> Rick Thomas wrote: |>|Hi Steffan, |> |> (My name is Steffen) | |Ooops! Sorry! Don't worry, i had so many typos myself in what followed.. .. |> It

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

Hello! Rick Thomas wrote: |Hi Steffan, (My name is Steffen) |So what, exactly, are the correct permissions for s-nail-privsep? | |Should it be: |-rwxr-sr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-nail/s-nail-privsep |or: |-rwsr-xr-x 1 root mail 10104 Dec 4

Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

Hi Steffan, So what, exactly, are the correct permissions for s-nail-privsep? Should it be: -rwxr-sr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-nail/s-nail-privsep or: -rwsr-xr-x 1 root mail 10104 Dec 4 14:52 /usr/lib/s-nail/s-nail-privsep or: -rwsr-sr-x 1 root mail 10104 Dec 4

s-nail fails with "Unable to (dot) lock mailbox, aborting operation: Permission denied"

(dot) lock mailbox, aborting operation: Permission denied > Creating dotlock for "/var/mail/rbthomas" . > Unable to (dot) lock mailbox, aborting operation: Permission denied > rbthomas@half:~$ I don’t know if this is deliberate, or even whether this is the right fix,

Re: s-nail fails with "Unable to (dot) lock mailbox, aborting operation: Permission denied"

gt; >> rbthomas@half:~$ mail >> Creating dotlock for "/var/mail/rbthomas" . >> Unable to (dot) lock mailbox, aborting operation: Permission denied >> Creating dotlock for "/var/mail/rbthomas" . >> Unable to (dot) lock mailbox, abort

GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied

Hi, after today update of my Debian testing i cannot hibernate, nor suspend, not reboot, nor halt the system from the regular user XFCE session with the message: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied Please, how i can these thing get back? Which permissions

Re: webdruid and cron.daily error: Permission denied

/cron.daily# ./webdruid ./webdruid: 19: /var/log/apache2/csplbubba/access.log.1: Permission denied No wonder, you're trying to run the log file - I should have spotted that earlier. How can I solve this problem? Stop copying things blatantly without understanding what they do ;^) Regards, -- Raf

webdruid and cron.daily error: Permission denied

/cron.daily# ./webdruid ./webdruid: 19: /var/log/apache2/csplbubba/access.log.1: Permission denied How can I solve this problem? -- Regards, Pal http://cspl.me -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Re: webdruid and cron.daily error: Permission denied

On Thu, Oct 06, 2011 at 03:30:33PM BST, Csanyi Pal wrote: When I run /etc/cron.daily/webdruid I get error message: /etc/cron.daily# ./webdruid ./webdruid: 19: /var/log/apache2/csplbubba/access.log.1: Permission denied How can I solve this problem? Who are you running the script

Re: webdruid and cron.daily error: Permission denied

Raf Czlonka r...@linuxstuff.pl writes: On Thu, Oct 06, 2011 at 03:30:33PM BST, Csanyi Pal wrote: When I run /etc/cron.daily/webdruid I get error message: /etc/cron.daily# ./webdruid ./webdruid: 19: /var/log/apache2/csplbubba/access.log.1: Permission denied How can I solve this problem

Re: webdruid and cron.daily error: Permission denied

On Thu, Oct 06, 2011 at 08:18:52PM BST, Csanyi Pal wrote: Raf Czlonka r...@linuxstuff.pl writes: Who are you running the script as? I'm running the script as root. What about the permissions of the folders themselves, you only sent file permissions? -- Raf -- To UNSUBSCRIBE, email to

Re: webdruid and cron.daily error: Permission denied

Raf Czlonka r...@linuxstuff.pl writes: On Thu, Oct 06, 2011 at 08:18:52PM BST, Csanyi Pal wrote: Raf Czlonka r...@linuxstuff.pl writes: Who are you running the script as? I'm running the script as root. What about the permissions of the folders themselves, you only sent file

apache 2 log : creation of executable memory area failed: Permission denied

/www/users/guy/tmp/temp10.xls creation of executable memory area failed: Permission denied Il s'agit de la même config et même api sur les deux ververs. le document xls est bien construit. J'ai fouillé pendant plus de 5 heures sans trouver réellement de solutions. Qqun a déjà rencontré cette

Re: apache 2 log : creation of executable memory area failed: Permission denied

/var/www/wt/gddbcore/gdods/DocumentConverter.py /var/www/users/guy/tmp/temp9.ods /var/www/users/guy/tmp/temp10.xls creation of executable memory area failed: Permission denied Il s'agit de la même config et même api sur les deux ververs. le document xls est bien construit. J'ai

Re: apache 2 log : creation of executable memory area failed: Permission denied

Bonjour, Le dimanche 27 février 2011 à 14:40 +0100, Bernard Schoenacker a écrit : Le Sun, 27 Feb 2011 12:14:21 +0100, Guy Deleeuw g.de_le...@eurofer.be a écrit : bonjour, aller encore une fois, comme c'est dimanche guy a abusé du pekèt ... Jaloux va ! est il possible

Re: Fwd: Bug#614661: exec: 58: /usr: Permission denied

for invisiblemanguard at Ter Fev 22 16:36:02 BRT 2011 exec: 58: /usr: Permission denied Like the /usr couldn't be acess by a user... only root can... Output of (ls -ld /usr) might be helpful here, but I think you might be misinterpreting the error message. but I not change any priority

Fwd: Bug#614661: exec: 58: /usr: Permission denied

with parachute... Forwarded conversation Subject: Re: Bug#614661: exec: 58: /usr: Permission denied From: *Sandro Tosi* mo...@debian.org Date: 2011/2/22 To: Debian_bug_report invisiblemanguard-debianbugrep...@yahoo.com.br, 614661-d...@bugs.debian.org go ask debian-user

permission denied

Hello. i have a small problems with my debian server. alle files are permission 644/600 or something, so i can't change anything on it. how can i change it back with root login. i have try but it say Permission denied i try to login with SSH but it say permission denied how can i change this.

Re: permission denied

On 7/26/10 4:35 PM, Jimmi Nielsen wrote: Hello. i have a small problems with my debian server. alle files are permission 644/600 or something, so i can't change anything on it. how can i change it back with root login. i have try but it say Permission denied i try to login with SSH but it say

Re: Apache2 chroot /dev/null permission denied

On Wednesday 17 March 2010 17:46:34 Knowledge Seeker wrote: Even outside of the chroot when I try to echo something and redirect to this device I get the same message: -su: null: Permission Denied Something mounted with the nodev option? -- Boyd Stephen Smith Jr

Re: Apache2 chroot /dev/null permission denied

Knowledge Seeker wrote: That is the problem. The permission is set to 666 and the group is root. But it still don't work. I don't know know what else to suggest. Maybe it is time to upgrade to lenny? Sorry I could not be of more help. Wayne -- To UNSUBSCRIBE, email to

Re: Apache2 chroot /dev/null permission denied

On Wed March 17 2010 19:00:35 Knowledge Seeker wrote: That is the problem. The permission is set to 666 and the group is root. But it still don't work. Please post the exact complete error message, and also the results of the following three commands run as root as soon as possible after the

Re: Apache2 chroot /dev/null permission denied

Thanks for the help. Doing what was asked I figured out and solved the problem. Another administrator added the option nodev to the partition of the chroot. Probably He did not umounted and mounted the partition after that and the service did not stopped, when we restart the machine, the problem

Apache2 chroot /dev/null permission denied

Hi, I have an old Debian Etch box, running Apache2 on chroot jail. Yesterday, (it sounds like joke) I turned off the machine and when I started it again the web server did not come to life again. The problem was a Permission Denied on the /dev/null. I created my device with the command: mknod -m

Re: Apache2 chroot /dev/null permission denied

Knowledge Seeker wrote: Hi, I have an old Debian Etch box, running Apache2 on chroot jail. Yesterday, (it sounds like joke) I turned off the machine and when I started it again the web server did not come to life again. The problem was a Permission Denied on the /dev/null. I created my device

Re: Apache2 chroot /dev/null permission denied

turned off the machine and when I started it again the web server did not come to life again. The problem was a Permission Denied on the /dev/null. I created my device with the command: mknod -m 0666 /chroot/dev/null c 1 3 listing the permissions: crw-rw-rw- 1 root root 1, 3 2010-03-16 18

[SOLVED] Permission denied when changing fan speed on T23 (Lenny)

I forgot to mark my previous reply to this thread solved, silly me :) I've also written a little script for the benefit of those who may have a similiar problem in the future and find this via the archives or by google. Due to the triviality of this script, I'm declaring it to be public domain.

Permission denied when tweaking various /proc knobs (Lenny)

I am attempting to adjust brightness via '/proc/acpi/ibm/brightness', but I get permission denied if I do it via sudo -- I have to su to root in order to do the adjustments. Log at [1]. [1] bry...@esterhazy:~$ sudo echo up /proc/acpi/ibm/brightness bash: /proc/acpi/ibm/brightness: Permission

Re: Permission denied when tweaking various /proc knobs (Lenny)

On Sat, Dec 05, 2009 at 11:22:37PM -0600, Brian Ryans wrote: bry...@esterhazy:~$ sudo echo up /proc/acpi/ibm/brightness bash: /proc/acpi/ibm/brightness: Permission denied The redirection is set up by the current shell, i.e. with non-elevated privileges. Try this instead: sudo sh -c 'echo up

Re: Permission denied when tweaking various /proc knobs (Lenny)

On 2009-12-06 06:22 +0100, Brian Ryans wrote: I am attempting to adjust brightness via '/proc/acpi/ibm/brightness', but I get permission denied if I do it via sudo -- I have to su to root in order to do the adjustments. Log at [1]. [1] bry...@esterhazy:~$ sudo echo up /proc/acpi/ibm

Re: Permission denied when tweaking various /proc knobs (Lenny)

Thanks, I wasn't paying attention to the 'bash' part, only to the 'permission denied' part. : PEBKAC on my part. -- _ ASCII Ribbon Campaign Against ( ) Brian Ryans HTML E-mail and V-cards Xbrianlry...@gmail.com www.asciiribbon.org

Re: passwd: Permission denied ?

On Mon, Sep 21, 2009 at 03:37:01PM +0200, Sven Joachim wrote: No, they are not. It's /etc/passwd, not /usr/bin/passwd. Oops! (red with embarrassment) signature.asc Description: Digital signature

Re: passwd: Permission denied ?

On Fri, Sep 18, 2009 at 11:39:28AM +0200, Frank Bonnet wrote: -rw-r--r-- 1 root root 1358 2009-09-18 09:21 /etc/passwd These permissions are wrong. The missing suid bit (as someone else pointed out) will prevent anyone but root using it. The missing e(x)ecute bit will prevent even root.

Re: passwd: Permission denied ?

On 2009-09-21 15:27 +0200, Jon Dowland wrote: On Fri, Sep 18, 2009 at 11:39:28AM +0200, Frank Bonnet wrote: -rw-r--r-- 1 root root 1358 2009-09-18 09:21 /etc/passwd These permissions are wrong. No, they are not. It's /etc/passwd, not /usr/bin/passwd. Sven -- To UNSUBSCRIBE, email to

  1   2   3   4   5   6   7   >