Hi Patti.
Thank you very much for pointing me into the right direction.
It was the selinux setting. After setting it to permissive I was able to label a
new volume.
The disk group setting is not necessary with 777.
The trick with unmounting the nfs share did I try already. But anyway a sudo -u
bacula touch test already showed that it was possible to write to the nfs share.
Thanks for your help.
Stefan
> "Clark, Patti" <clarkpa AT ornl DOT gov> hat am 19. Mai 2016 um 18:55
> geschrieben:
>
> Is your bacula user a member of the disk group on your SD system?
>
> What is the state of selinux? If it’s enforcing – set it to permissive or
> disable it.
>
> And lastly, I have a disk storage area for testing. The ownership is set to
> be bacula:root with 770 perms which works. When I change it to nobody:nobody
> I get the same error below. When I change the permissions to 777, it works.
> If you can test your mount area without the nfs mount and it works, then nfs
> is your issue. NFSv4 maps users. I’m willing to bet that if you fall back to
> NFSv3 it will work (provided that firewalld is set to allow all of the ports –
> probably disable firewalld for the test). If so, then you need to either use
> NFSv3 or fix your user issues with NFSv4 which is outside the scope of this
> list.
>
> Patti
>
>
> From: Stefan Lamby <webmaster AT peter-speer DOT de mailto:webmaster AT
> peter-speer DOT de
> >
> Reply-To: Stefan Lamby <webmaster AT peter-speer DOT de
> mailto:webmaster AT peter-speer DOT de >
> Date: Thursday, May 19, 2016 at 11:25 AM
> To: "bacula-users AT lists.sourceforge DOT net
> mailto:bacula-users AT lists.sourceforge DOT net "
> <bacula-users AT lists.sourceforge DOT net mailto:bacula-users AT
> lists.sourceforge DOT net
> >
> Subject: [Bacula-users] 3910 Unable to open device ""nas2016" (/nas2016)":
> ERR=dev.c:575 Could not open: /nas2016/bkp-nas-0419, ERR=no permission
>
> Hi.
> I am searching for hours, but I am not able to figure out, why I get this
> error...
> Yes, I know, it must be a permission setting but I am too stupid to find it
> even
> after years on linux.
>
> This is my setup:
> Device {
> Name = nas2016
> Media Type = File
> Archive Device = /nas2016
> LabelMedia = yes; # lets Bacula label unlabeled media
> Random Access = Yes;
> # AutomaticMount = no; # when device opened, read it
> # RemovableMedia = no;
> AutomaticMount = yes;
> RemovableMedia = yes;
> AlwaysOpen = no;
> Maximum Volume Size = 295GB;
> Requires Mount = no;
> Mount Point = /nas2016
> #
> # nicht notwendig, NAS wird per /etc/fstab beim Booten gemountet.
> #
> # Mount Command = "/bin/mount /nas01_backup";
> # Unmount Command = "/bin/umount /nas01_backup";
> }
>
> The Mount Point looks like that:
> Notice, it is 777...
> drwxrwxrwx. 3 nobody nobody 4096 19. Mai 16:14 nas2016
>
> I am able to touch a file there using:
> sudo -u bacula touch /nas2016/test
> I can even see (when using vi instead of touch) the contents of the file
> using
> the nas gui.
>
> The nas is mounted via fstab and looks like this:
> cat /proc/mounts | grep nas
> nas2016.privat.i-concept.de:/volume1/backups /nas2016 nfs4
>
> rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.50,local_lock=none,addr=192.168.1.15
> 0 0
>
> Storage { # definition of myself
> Name = backnix05-sd
> SDPort = 9103 # Director's port
> WorkingDirectory = "/var/spool/bacula"
> Pid Directory = "/var/run"
> Maximum Concurrent Jobs = 5
> }
>
> I am on CentOS 7, running backnix05-dir Version: 5.2.13 (19 February 2013)
>
> The error is triggered when doing this:
>
> *label
> Automatically selected Catalog: IcCatalog
> Using Catalog "IcCatalog"
> The defined Storage resources are:
> 1: File
> 2: NAS01_STORAGE_BACKNIX
> Select Storage resource (1-2): 2
> Enter new Volume name: bkp-nas-0422
> Defined Pools:
> 1: Default
> 2: File
> 3: Scratch
> 4: Full-Backup-Pool
> 5: Incr-Backup-Pool
> 6: Subseq-Backup-Pool
> 7: File-Backup-Pool
> 8: USB_FRIDAY_EVEN
> 9: USB_FRIDAY_ODD
> 10: NAS01_POOL
> Select the Pool (1-10): 10
> Connecting to Storage daemon NAS01_STORAGE_BACKNIX at 192.168.1.50:9103 ...
> Sending label command for Volume "bkp-nas-0422" Slot 0 ...
> 3910 Unable to open device ""nas2016" (/nas2016)": ERR=dev.c:575 Could not
> open:
> /nas2016/bkp-nas-0422, ERR=Keine Berechtigung
>
> Label command failed for Volume bkp-nas-0422.
> Do not forget to mount the drive!!!
>
> Bacula tries to open the file, but with an ls -l I am not able to see the
> file
> /nas2016/bkp-nas-0422 either. Is it not there, because bacula is not able to
> produce and is this caused by the permission error? Or is the error triggered
> at
> a earlier point?
>
> Just in case: Yes, sd and dir are running as user bacula.
>
> ps axf | grep bacula
> 1305 ? Ssl 0:00 /usr/sbin/bacula-dir -f -c
> /etc/bacula/bacula-dir.conf -u bacula -g bacula
> 1315 ? Ssl 0:00 /usr/sbin/bacula-fd -f -c
> /etc/bacula/bacula-fd.conf
> -u root -g root
> 2999 pts/0 S+ 0:00 | \_ grep --color=auto bacula
> 2963 pts/1 S+ 0:00 | \_ vi /etc/bacula/bacula-sd.conf
> 1336 ? Ssl 0:00 /usr/sbin/bacula-sd -f -c
> /etc/bacula/bacula-sd.conf
> -u bacula -g tape
>
> Please help, my backups are not running.
>
> Thanks.
> Stefan
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net mailto:Bacula-users AT
> lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
>
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
