Page 1 of 1

Cannot create snapshot repository

Posted: Mon Oct 29, 2018 3:30 am
by tomasvalenta
Hello,
I prepared Samba based repository for snapshots, mounted it and configured permissions. I tested to create file in this repository under nagios account from Nagios LogServer and the result is OK. But when I tried to attach this repository from UI by button Create Repository I got error message The snapshot repository in directory /lsbackup could not be created. Possibly due to permissions. Make sure the nagios user can write to the location. But I see in Samba log there was connection from LogServer and successfully created and deleted several test files.
Thanks for any hint or help.
Tomas

Re: Cannot create snapshot repository

Posted: Mon Oct 29, 2018 11:29 am
by ssax
What version of Log Server are you running? You can grab it from the bottom left hand side of the web interface.

Please post the output of these commands as well:

Code: Select all

ls -ld /lsbackup
ls -l /lsbackup

Re: Cannot create snapshot repository

Posted: Tue Oct 30, 2018 5:35 am
by tomasvalenta
latest version 2.0.5
ls -ld /lsbackup/
drwxrwx--- 2 nagios nagios 0 Oct 29 15:12 /lsbackup/
ls -l /lsbackup/
total 0

Re: Cannot create snapshot repository

Posted: Tue Oct 30, 2018 1:47 pm
by ssax
I labbed it up with those exact settings/version and it's working on mine.

What is the output of these commands:

Code: Select all

grep nag /etc/group
grep "User \|Group " /etc/httpd/conf/httpd.conf
Are you using lsbackup as the name and /lsbackup as the location when adding through the web UI?

Please try to add it again and then PM me a copy of your profile from Admin > System Status so that I can take a look at your logs.

Re: Cannot create snapshot repository

Posted: Thu Nov 01, 2018 4:15 am
by tomasvalenta
Good news, it is working now. After restart of both servers in the cluster it is fixed.
Thanks for your help.
Tomas

Re: Cannot create snapshot repository

Posted: Thu Nov 01, 2018 8:35 am
by scottwilkerson
tomasvalenta wrote:Good news, it is working now. After restart of both servers in the cluster it is fixed.
Thanks for your help.
Tomas
Glad to hear it is resolved!

Locking thread