Thanks.
I've figured it out.
Needed to update /bin/solr.in to add -Dsolr.allowPaths=D:\Solr\backup
Update solr.xml for each node with the relevant allowPaths : <str
name="allowPaths">${solr.allowPaths:D:\Solr\backup}</str>
Then update /server/etc/security.policy to add : permission
java.io.FilePermission "${solr.allowPaths}${/}-", "read,write,delete,readlink";
-----Original Message-----
From: Dave <hastings.recurs...@gmail.com>
Sent: 10 October 2022 18:03
To: users@solr.apache.org
Subject: Re: Node backup using replication
[You don't often get email from hastings.recurs...@gmail.com. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
WARNING: This email originated from outside of NHS Wales. Do not open links or
attachments unless you know the content is safe.
Exactly. In linux I would just do a 777 for such a directory anyways since no
one outside of the machine can get to it since no solr servers should have
public ip.
> On Oct 10, 2022, at 12:51 PM, Shawn Heisey <apa...@elyograg.org> wrote:
>
> On 10/10/22 09:23, Joe Jones (DHCW - Software Development) wrote:
>> java.security.AccessControlException: access denied
>> ("java.io.FilePermission" "D:\Solr\backup\node1" "read")
>
> This is saying that it failed to READ that directory. I had expected to see
> a failure to WRITE.
>
> Maybe that will be a clue that someone at your organization can use to figure
> out what's wrong.
>
> Thanks,
> Shawn
>
Rydym yn croesawu derbyn gohebiaeth yng Nghymraeg. Byddwn yn ateb y fath
ohebiaeth yng Nghymraeg ac ni fydd hyn yn arwain at oedi.
We welcome receiving correspondence in Welsh. We will reply to such
correspondence in Welsh and this will not lead to a delay.
