Maybe solved: looking closer at the instances that worked, I realized
that their NSSM service ran a bat file that called solr.cmd with "-f". I
started solr.cmd directly from NSSM and forgot the "-f".
Changing the service to run a batch file appears to have fixed it.
Whether it was the "-f" or
Op vr 28 okt. 2022 om 17:37 schreef dmitri maziuk :
> It's a clean stand-alone install. It's not going through any proxies,
> the scripts are erroring out when run on the same server too, and it
> being python, the complete http conversation is a bit hard to get to.
Hi Dima
Whenever I need the
On 2022-10-28 10:02 AM, Shawn Heisey wrote:
If you have already checked solr.log and don't see anything, that's very
odd. Is the server in cloud mode and part of a cluster? If it is, then
the error might be logged by a different server. Can you share the
entire HTTP error responses?
It's
On 10/27/22 16:44, dmitri maziuk wrote:
has anyone gone through the exercise of replacing Data Import Handler
with scripts that POST JSON and if so, are your scripts still working
OK with 8.11.2?
I got a few that work fine with 6.5 and 8.7 but are throwing 503s and
occasional 400s all over th
> On Oct 27, 2022, at 5:44 PM, dmitri maziuk wrote:
>
> has anyone gone through the exercise of replacing Data Import Handler with
> scripts that POST JSON and if so, are your scripts still working OK with
> 8.11.2?
That's exactly what I've done a couple of years ago and they work just fine
Hi all,
has anyone gone through the exercise of replacing Data Import Handler
with scripts that POST JSON and if so, are your scripts still working OK
with 8.11.2?
I got a few that work fine with 6.5 and 8.7 but are throwing 503s and
occasional 400s all over the place with 8.11.2.
Solr isn
