Re: atftpd permission denied

2025-04-11 Thread Michael Stone
On Fri, Apr 11, 2025 at 05:49:28PM -0400, Timothy M Butterworth wrote: Do you know if there is a setting in VSFTPD to upload files? /etc/vsftpd.conf: write_enable=YES

Re: atftpd permission denied

2025-04-11 Thread Timothy M Butterworth
On Fri, Apr 11, 2025 at 11:30 AM Michael Stone wrote: > On Thu, Apr 10, 2025 at 06:11:31PM -0400, Timothy M Butterworth wrote: > >I am having problems writing to atftpd. I keep getting a permission denied > >error. > > It sounds like you've worked around this

Re: atftpd permission denied

2025-04-11 Thread Timothy M Butterworth
On Fri, Apr 11, 2025 at 11:30 AM Michael Stone wrote: > On Thu, Apr 10, 2025 at 06:11:31PM -0400, Timothy M Butterworth wrote: > >I am having problems writing to atftpd. I keep getting a permission denied > >error. > > It sounds like you've worked around this

Re: atftpd permission denied

2025-04-11 Thread Michael Stone
On Thu, Apr 10, 2025 at 06:11:31PM -0400, Timothy M Butterworth wrote: I am having problems writing to atftpd. I keep getting a permission denied error. It sounds like you've worked around this, but I'll note for future searchers that the reason for this is that atftpd is confi

Re: atftpd permission denied

2025-04-11 Thread Dan Ritter
Timothy M Butterworth wrote: > On Thu, Apr 10, 2025 at 7:14 PM Dan Ritter wrote: > > > Timothy M Butterworth wrote: > > > All, > > > > > > I am having problems writing to atftpd. I keep getting a permission > > denied > > > error. > &g

Re: atftpd permission denied

2025-04-11 Thread Lee
On Thu, Apr 10, 2025 at 10:12 PM Timothy M Butterworth wrote: > > On Thu, Apr 10, 2025 at 7:14 PM Dan Ritter wrote: >> >> Timothy M Butterworth wrote: >> > All, >> > >> > I am having problems writing to atftpd. I keep getting a permission denied >&g

Re: atftpd permission denied

2025-04-10 Thread Timothy M Butterworth
On Fri, Apr 11, 2025 at 2:12 AM Titus Newswanger wrote: > > On 4/10/25 18:49, Timothy M Butterworth wrote: > > > I am trying to copy a Cisco IOS image from a switch so I can push it to > another switch. > > Sounds like the type of application where I tend to use scp. Would that do > the job? Or m

Re: atftpd permission denied

2025-04-10 Thread Titus Newswanger
On 4/10/25 18:49, Timothy M Butterworth wrote: I am trying to copy a Cisco IOS image from a switch so I can push it to another switch. Sounds like the type of application where I tend to use scp. Would that do the job? Or maybe I misunderstood your question. needs ssh access on remote dev

Re: atftpd permission denied

2025-04-10 Thread Timothy M Butterworth
On Thu, Apr 10, 2025 at 7:14 PM Dan Ritter wrote: > Timothy M Butterworth wrote: > > All, > > > > I am having problems writing to atftpd. I keep getting a permission > denied > > error. > > > > Switch#$.SED.bin tftp:// > 169.254.180.65/c3550-ipservic

Re: atftpd permission denied

2025-04-10 Thread Dan Ritter
Timothy M Butterworth wrote: > All, > > I am having problems writing to atftpd. I keep getting a permission denied > error. > > Switch#$.SED.bin tftp://169.254.180.65/c3550-ipservicesk9-mz.122-25.SED.bin > > > Address or name of remote host [169.254.180.65]? &g

atftpd permission denied

2025-04-10 Thread Timothy M Butterworth
All, I am having problems writing to atftpd. I keep getting a permission denied error. Switch#$.SED.bin tftp://169.254.180.65/c3550-ipservicesk9-mz.122-25.SED.bin Address or name of remote host [169.254.180.65]? Destination filename [c3550-ipservicesk9-mz.122-25.SED.bin]? ! TFTP: error code 2

Re: Unexpected permission denied

2023-01-26 Thread Max Nikulin
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 --c

Re: Unexpected permission denied

2023-01-25 Thread Greg Wooledge
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) h

Re: Unexpected permission denied

2023-01-25 Thread Max Nikulin
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 t

Re: Unexpected permission denied

2023-01-25 Thread Jeffrey Walton
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 var/www/grammartiste.com

Re: Unexpected permission denied

2023-01-25 Thread Jeffrey Walton
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

2023-01-25 Thread Nicolas George
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 a

Re: Unexpected permission denied

2023-01-25 Thread Greg Wooledge
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

2023-01-25 Thread Yassine Chaouche
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 command

Re: Unexpected permission denied

2023-01-25 Thread Nicolas George
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

2023-01-25 Thread Yassine Chaouche
friends. You've 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

Re: Unexpected permission denied

2023-01-25 Thread Yassine Chaouche
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/ drwxr-xr-

Re: Unexpected permission denied

2023-01-25 Thread Thomas Schmitt
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 to

Re: Unexpected permission denied

2023-01-25 Thread Greg Wooledge
ends. You've 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 symlin

Re: Unexpected permission denied

2023-01-25 Thread Nicolas George
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 commands.

Re: Unexpected permission denied

2023-01-25 Thread Dan Ritter
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 p

Re: Unexpected permission denied

2023-01-25 Thread tomas
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 sign

Re: Unexpected permission denied

2023-01-24 Thread jeremy ardley
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

2023-01-24 Thread jeremy ardley
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

2023-01-24 Thread tomas
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

2023-01-24 Thread jeremy ardley
.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)

2021-12-06 Thread john doe
: 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 corre

Question on permission denied (public key)

2021-12-06 Thread Adriel Peng
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

2019-07-17 Thread Simon Bernier St-Pierre
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 lxc.apparmor.allow_in

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

2019-07-17 Thread Reco
to the 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

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

2019-07-16 Thread Simon Bernier St-Pierre
0:32:30 dl 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: Ma

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

2018-10-17 Thread Reco
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

2018-10-17 Thread mick crane
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

2018-10-17 Thread mick crane
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 indi

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

2018-10-17 Thread steve
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 s

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

2018-10-17 Thread mick crane
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

2018-10-17 Thread steve
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

2018-10-17 Thread steve
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

2018-10-17 Thread steve
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.3

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

2018-10-16 Thread Reco
: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: 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

2018-10-16 Thread Steve Kemp
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" > operatio

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

2018-10-16 Thread steve
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

2018-10-16 Thread steve
rting 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 mo

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

2018-10-16 Thread David Wright
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 option

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

2018-10-16 Thread Gene Heskett
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 will

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

2018-10-16 Thread Gene Heskett
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 will

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

2018-10-16 Thread Greg Wooledge
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 end

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

2018-10-16 Thread Gene Heskett
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. > > (I'm

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

2018-10-16 Thread Martin
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. > > (I'm

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

2018-10-16 Thread 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. (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

2018-10-16 Thread Joe
o Process: 32122 > > 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/apa

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

2018-10-16 Thread Martin
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

2018-10-16 Thread Martin
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. > oct 16 07:22:02 box apachect

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

2018-10-15 Thread Reco
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: Permission denied > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. > oct 16 07:22:02 box apache

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

2018-10-15 Thread Steve Kemp
> > 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

2018-10-15 Thread steve
ache2/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

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

2017-10-05 Thread Sven Joachim
t;core" 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:~#

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

2017-10-04 Thread Uwe Mintermann
-ccpp': 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 'ke

Re: usb permission denied

2016-09-27 Thread davidson
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 con

usb permission denied

2016-09-27 Thread Ric Moore
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 Ignoran

Re: NFS no_root_squash not working (permission denied)

2016-08-11 Thread Greg Wooledge
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 exp

Re: NFS no_root_squash not working (permission denied)

2016-08-11 Thread Ulf Volmer
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 kn

Re: NFS no_root_squash not working (permission denied)

2016-08-11 Thread Greg Wooledge
nd any > 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

Re: NFS no_root_squash not working (permission denied)

2016-08-10 Thread Greg Wooledge
nfigured. I googled "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-

Re: NFS no_root_squash not working (permission denied)

2016-08-10 Thread Erwan David
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 so

Re: NFS no_root_squash not working (permission denied)

2016-08-10 Thread Ulf Volmer
> 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)

2016-08-10 Thread Greg Wooledge
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)

2016-08-09 Thread Greg Wooledge
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 exported

NFS no_root_squash not working (permission denied)

2016-08-08 Thread Greg Wooledge
trying 10.76.142.85 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: Permissi

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

2015-12-30 Thread Steffen Nurpmeso
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 must be SETUID to a super-user that can impersonate as all

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

2015-12-30 Thread Rick Thomas
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 for mailx to do it's work? > I.e., ow

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

2015-12-30 Thread Rick Thomas
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 /usr/local/libexec/s-nail-privsep > -r-sr-xr-

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

2015-12-30 Thread Jörg-Volker Peetz
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? This works on my syste

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

2015-12-30 Thread Steffen Nurpmeso
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 14:52 /usr/lib/s-nai

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

2015-12-29 Thread Rick Thomas
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 14:

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

2015-12-28 Thread Rick Thomas
f:~$ 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, aborting operation: Permission denied >

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

2015-12-28 Thread Rick Thomas
(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, bu

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

2014-10-07 Thread Slavko
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 are

Re: webdruid and cron.daily error: Permission denied

2011-10-07 Thread Raf Czlonka
run /etc/cron.daily/webdruid I get error message: > /etc/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?

Re: webdruid and cron.daily error: Permission denied

2011-10-06 Thread Csanyi Pal
Raf Czlonka writes: > On Thu, Oct 06, 2011 at 08:18:52PM BST, Csanyi Pal wrote: >> Raf Czlonka 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? The folders has the s

Re: webdruid and cron.daily error: Permission denied

2011-10-06 Thread Raf Czlonka
On Thu, Oct 06, 2011 at 08:18:52PM BST, Csanyi Pal wrote: > Raf Czlonka 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 debian-user-req

Re: webdruid and cron.daily error: Permission denied

2011-10-06 Thread Csanyi Pal
Raf Czlonka 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 >>

Re: webdruid and cron.daily error: Permission denied

2011-10-06 Thread Raf Czlonka
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 run

webdruid and cron.daily error: Permission denied

2011-10-06 Thread Csanyi Pal
5:41 access.log.1 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? -- Regards, Pal <http://cspl.me> -- To UNSUBSCRIBE, email to debian-us

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

2011-02-23 Thread Boyd Stephen Smith Jr.
that are using this method of starting their X sessions. > > the system returns the > > error: > > "xinit: connection to X server lost" and after said "Wait for X server to > > shut > > down" and stayed with prompt flashing again. So, I tried invo

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

2011-02-22 Thread Debian_bug_report
wers or help? I'm falling here with parachute... Forwarded conversation Subject: Re: Bug#614661: exec: 58: /usr: Permission denied From: *Sandro Tosi* Date: 2011/2/22 To: Debian_bug_report , 614661-d...@bugs.debian.org go ask debian-user@lists.debian.org, reportb

Re: permission denied

2010-07-26 Thread Jordon Bedwell
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 i

permission denied

2010-07-26 Thread Jimmi Nielsen
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: Apache2 chroot /dev/null permission denied

2010-03-21 Thread Boyd Stephen Smith Jr.
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? --

Re: Apache2 chroot /dev/null permission denied

2010-03-18 Thread Knowledge Seeker
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 a

Re: Apache2 chroot /dev/null permission denied

2010-03-18 Thread Mike Bird
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

2010-03-18 Thread Wayne
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 debian-user-requ...

Re: Apache2 chroot /dev/null permission denied

2010-03-17 Thread Knowledge Seeker
ounds 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 0666 /chroot/dev/null c 1 >> 3 >> l

Re: Apache2 chroot /dev/null permission denied

2010-03-17 Thread Wayne
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

Apache2 chroot /dev/null permission denied

2010-03-17 Thread Knowledge Seeker
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

  1   2   3   4   5   >