Re: bash: solr: command not found

2020-10-15 Thread Gora Mohanty
On Thu, 15 Oct 2020 at 22:27, Ryan W  wrote:

> Hi all,
>
> I run solr like this...
>
> service solr start
>

You are probably running Solr on a Linux machine using systemd where
someone has set up the systemd files needed for Solr. This might not have
been done on your client's system. Try searching Google for "Solr systemd"
which seems to turn up likely-looking sources for the files.


> However, another user of the server can't run solr this way.  They are
> seeing...
>
> bash: solr: command not found
>

However, this seems to point to some other error; not from systemd. It
looks like the systemd files may be set up, but the user that Solr is
running as does not have the solr executable in their path. Try including
it in their path, or giving the full path to solr in the systemd file.

Regards,
Gora


Re: solr-8983.pid: Permission denied

2020-10-15 Thread Ryan W
Solved by setting a SOLR_PID_DIR path in my solr.in.sh.  And then giving
the solr user ownership of that directory.

Thanks

On Thu, Oct 15, 2020 at 11:17 AM Alexandre Rafalovitch 
wrote:

> If the .pid file is not at that location, then I would investigate
> where that file is instead (after Solr is started).
>
> If it is in a different location, then you have different environment
> expectations, somehow. This, in all honesty, would still be consistent
> with my theory that Solr was started somehow differently (perhaps just
> this once).
>
> If it is nowhere, then you may have a permission issue around creating
> that file in the first place.
>
> Basically, I am saying that maybe the issue you have is a symptom of a
> deeper discrepancy rather than the actual issue to solve directly.
>
> Regards,
>Alex.
>
> On Thu, 15 Oct 2020 at 11:03, Ryan W  wrote:
> >
> > The .pid file referenced in the "Permission denied" message does not
> exist.
> >
> > On Thu, Oct 15, 2020 at 11:01 AM Ryan W  wrote:
> >
> > > I have been starting solr like so...
> > >
> > > service solr start
> > >
> > >
> > > On Thu, Oct 15, 2020 at 10:31 AM Joe Doupnik  wrote:
> > >
> > >>  Alex has it right. In my environment I created user "solr" in
> group
> > >> "users". Then I ensured that "solr:user" owns all of Solr's files. In
> > >> addition, I do Solr start/stop with an /etc/init.d script (the Solr
> > >> distribution has the basic one which we can embellish) in which there
> is
> > >> control line RUNAS="solr". The RUNAS variable is used to properly
> start
> > >> Solr.
> > >>  Thanks,
> > >>  Joe D.
> > >>
> > >> On 15/10/2020 15:02, Alexandre Rafalovitch wrote:
> > >> > It sounds like maybe you have started the Solr in a different way
> than
> > >> > you are restarting it. E.g. maybe you started it manually (bin/solr
> > >> > start, probably as a root) but are trying to restart it via service
> > >> > script. Who owned the .pid file? I am guessing 'root', while the
> > >> > service script probably runs as a different (lower-permission) user.
> > >> >
> > >> > The practical effect of that assumption is that your environmental
> > >> > variables were set differently and various things (e.g. logs) may
> not
> > >> > be where you expect.
> > >> >
> > >> > The solution is to be consistent in using the service to
> > >> > start/restart/stop your Solr.
> > >> >
> > >> > Regards,
> > >> > Alex.
> > >> >
> > >> > On Thu, 15 Oct 2020 at 09:51, Ryan W  wrote:
> > >> >> What is my permissions problem here:
> > >> >>
> > >> >> [root@faspbsy0002 bin]# service solr restart
> > >> >> Sending stop command to Solr running on port 8983 ... waiting up
> to 180
> > >> >> seconds to allow Jetty process 38947 to stop gracefully.
> > >> >> /opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid:
> Permission
> > >> >> denied
> > >> >>
> > >> >> What is the practical effect if Solr can't write this solr-8983.pid
> > >> file?
> > >> >> What user should own the contents of /opt/solr/bin ?
> > >> >>
> > >> >> Thanks
> > >>
> > >>
>


Re: Solr 8.6.3

2020-10-15 Thread Gus Heck
Shameless self plug,.. JesterJ (which I maintain) has a stax based xml
extractor
https://github.com/nsoft/jesterj/wiki/Document-Processors#staxextractingprocessor
if you want to try it out.

On Thu, Oct 15, 2020 at 4:32 PM Alexandre Rafalovitch 
wrote:

> Why not do an XSLT transformation on it before it hits Solr.
>
> Or during if it really has to be in-Solr for some reason
>
> https://lucene.apache.org/solr/guide/8_6/uploading-data-with-index-handlers.html#using-xslt-to-transform-xml-index-updates
>
> But you have more options outside as you could use XQuery instead.
>
> As long as final XML is in Solr format, you are good to go.
>
> Regards,
> Alex
>
> On Thu., Oct. 15, 2020, 4:13 p.m. Kris Gurusamy, <
> krishnan.gurus...@xpanse.com> wrote:
>
> > I've just downloaded solr 8.6.3 and trying to create DIH for loading
> > structured XML. I found out that DIH will be deprecated soon with version
> > 9.0. What is the equivalent of DIH in new solr version? How do I import
> > structured XML data which is very custom and index in Solr new version?
> Any
> > help is appreciated.
> >
> > Regards
> >
> > Kris Gurusamy
> > Director, Engineering
> > kgurus...@xpanse.com
> > www.xpanse.com
> >
> > On 10/15/20, 1:08 PM, "Anshum Gupta (Jira)"  wrote:
> >
> >
> >  [
> >
> https://issues.apache.org/jira/browse/SOLR-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > ]
> >
> > Anshum Gupta resolved SOLR-14938.
> > -
> > Resolution: Invalid
> >
> > [~krisgurusamy] - Please ask questions regarding usage on the Solr
> > user mailing list.
> >
> > JIRA is meant for issue tracking purposes.
> >
> > > Solr 8.6.3
> > > --
> > >
> > > Key: SOLR-14938
> > > URL:
> > https://issues.apache.org/jira/browse/SOLR-14938
> > > Project: Solr
> > >  Issue Type: Bug
> > >  Security Level: Public(Default Security Level. Issues are
> > Public)
> > >  Components: contrib - DataImportHandler
> > >Reporter: Krishnan
> > >Priority: Major
> > >
> > > I've just downloaded solr 8.6.3 and trying to create DIH for
> loading
> > structured XML. I found out that DIH will be deprecated soon with version
> > 9.0. What is the equivalent of DIH in new solr version? How do I import
> > structured XML data which is very custom and index in Solr new version?
> Any
> > help is appreciated.
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.4#803005)
> >
> >
>


-- 
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)


Re: Solr 8.6.3

2020-10-15 Thread Walter Underwood
Solr does not index XML. It has an XML data format for indexing text.

If you want to index and search XML, get MarkLogic. I used to work there.
It is seriously awesome technology.

https://www.marklogic.com 

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Oct 15, 2020, at 1:10 PM, Kris Gurusamy  
> wrote:
> 
> I've just downloaded solr 8.6.3 and trying to create DIH for loading 
> structured XML. I found out that DIH will be deprecated soon with version 
> 9.0. What is the equivalent of DIH in new solr version? How do I import 
> structured XML data which is very custom and index in Solr new version? Any 
> help is appreciated.
> 
> Regards
> 
> Kris Gurusamy
> Director, Engineering
> kgurus...@xpanse.com
> www.xpanse.com
> 
> On 10/15/20, 1:08 PM, "Anshum Gupta (Jira)"  wrote:
> 
> 
> [ 
> https://issues.apache.org/jira/browse/SOLR-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
>Anshum Gupta resolved SOLR-14938.
>-
>Resolution: Invalid
> 
>[~krisgurusamy] - Please ask questions regarding usage on the Solr user 
> mailing list. 
> 
>JIRA is meant for issue tracking purposes.
> 
>> Solr 8.6.3
>> --
>> 
>>Key: SOLR-14938
>>URL: https://issues.apache.org/jira/browse/SOLR-14938
>>Project: Solr
>> Issue Type: Bug
>> Security Level: Public(Default Security Level. Issues are Public) 
>> Components: contrib - DataImportHandler
>>   Reporter: Krishnan
>>   Priority: Major
>> 
>> I've just downloaded solr 8.6.3 and trying to create DIH for loading 
>> structured XML. I found out that DIH will be deprecated soon with version 
>> 9.0. What is the equivalent of DIH in new solr version? How do I import 
>> structured XML data which is very custom and index in Solr new version? Any 
>> help is appreciated.
> 
> 
> 
>--
>This message was sent by Atlassian Jira
>(v8.3.4#803005)
> 



Re: Solr 8.6.3

2020-10-15 Thread Alexandre Rafalovitch
Why not do an XSLT transformation on it before it hits Solr.

Or during if it really has to be in-Solr for some reason
https://lucene.apache.org/solr/guide/8_6/uploading-data-with-index-handlers.html#using-xslt-to-transform-xml-index-updates

But you have more options outside as you could use XQuery instead.

As long as final XML is in Solr format, you are good to go.

Regards,
Alex

On Thu., Oct. 15, 2020, 4:13 p.m. Kris Gurusamy, <
krishnan.gurus...@xpanse.com> wrote:

> I've just downloaded solr 8.6.3 and trying to create DIH for loading
> structured XML. I found out that DIH will be deprecated soon with version
> 9.0. What is the equivalent of DIH in new solr version? How do I import
> structured XML data which is very custom and index in Solr new version? Any
> help is appreciated.
>
> Regards
>
> Kris Gurusamy
> Director, Engineering
> kgurus...@xpanse.com
> www.xpanse.com
>
> On 10/15/20, 1:08 PM, "Anshum Gupta (Jira)"  wrote:
>
>
>  [
> https://issues.apache.org/jira/browse/SOLR-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Anshum Gupta resolved SOLR-14938.
> -
> Resolution: Invalid
>
> [~krisgurusamy] - Please ask questions regarding usage on the Solr
> user mailing list.
>
> JIRA is meant for issue tracking purposes.
>
> > Solr 8.6.3
> > --
> >
> > Key: SOLR-14938
> > URL:
> https://issues.apache.org/jira/browse/SOLR-14938
> > Project: Solr
> >  Issue Type: Bug
> >  Security Level: Public(Default Security Level. Issues are
> Public)
> >  Components: contrib - DataImportHandler
> >Reporter: Krishnan
> >Priority: Major
> >
> > I've just downloaded solr 8.6.3 and trying to create DIH for loading
> structured XML. I found out that DIH will be deprecated soon with version
> 9.0. What is the equivalent of DIH in new solr version? How do I import
> structured XML data which is very custom and index in Solr new version? Any
> help is appreciated.
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>
>


Re: systemd definition for solr?

2020-10-15 Thread Ryan W
I just needed to enable the service with

systemctl enable solr.service



On Thu, Oct 15, 2020 at 4:03 PM Ryan W  wrote:

> I didn't realize that to start a systemd service, I need to do...
>
> systemctl start solr
>
> ...and not...
>
> service solr start
>
> Now the output from the status command looks a bit better, though still
> with some problems...
>
> [root@faspbsy0002 system]# systemctl status solr.service
> ? solr.service - LSB: A very fast and reliable search engine.
>Loaded: loaded (/etc/rc.d/init.d/solr; bad; vendor preset: disabled)
>Active: active (exited) since Thu 2020-10-15 15:58:23 EDT; 19s ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 34100 ExecStop=/etc/rc.d/init.d/solr stop (code=exited,
> status=1/FAILURE)
>   Process: 98871 ExecStart=/etc/rc.d/init.d/solr start (code=exited,
> status=0/SUCCESS)
>
>
>
> On Thu, Oct 15, 2020 at 3:24 PM Ryan W  wrote:
>
>> Does anyone have a simple systemd definition for a solr service?
>>
>> The things I am finding on the internet don't work.  I am not sure if
>> this is the kind of thing where there might be some boilerplate that
>> (usually) works?  Or do situations vary so much that no boilerplate is
>> possible?
>>
>> Here is what I see when I try to use one of the definitions I found on
>> the internet:
>>
>> [root@faspbsy0002 system]# systemctl status solr.service
>> ? solr.service - LSB: A very fast and reliable search engine.
>>Loaded: loaded (/etc/rc.d/init.d/solr; bad; vendor preset: disabled)
>>Active: failed (Result: exit-code) since Thu 2020-10-15 09:32:02 EDT;
>> 5h 50min ago
>>  Docs: man:systemd-sysv-generator(8)
>>   Process: 34100 ExecStop=/etc/rc.d/init.d/solr stop (code=exited,
>> status=1/FAILURE)
>>   Process: 1337 ExecStart=/etc/rc.d/init.d/solr start (code=exited,
>> status=0/SUCCESS)
>>
>> Oct 15 09:32:01 faspbsy0002 systemd[1]: Stopping LSB: A very fast and
>> reliab
>> Oct 15 09:32:01 faspbsy0002 su[34102]: (to solr) root on none
>> Oct 15 09:32:02 faspbsy0002 solr[34100]: No process found for Solr node
>> runn...3
>> Oct 15 09:32:02 faspbsy0002 systemd[1]: solr.service: control process
>> exited...1
>> Oct 15 09:32:02 faspbsy0002 systemd[1]: Stopped LSB: A very fast and
>> reliabl
>> Oct 15 09:32:02 faspbsy0002 systemd[1]: Unit solr.service entered failed
>> state.
>> Oct 15 09:32:02 faspbsy0002 systemd[1]: solr.service failed.
>> Warning: Journal has been rotated since unit was started. Log output is
>> incomplete or unavailable.
>> Hint: Some lines were ellipsized, use -l to show in full.
>>
>


Solr 8.6.3

2020-10-15 Thread Kris Gurusamy
I've just downloaded solr 8.6.3 and trying to create DIH for loading structured 
XML. I found out that DIH will be deprecated soon with version 9.0. What is the 
equivalent of DIH in new solr version? How do I import structured XML data 
which is very custom and index in Solr new version? Any help is appreciated.

Regards

Kris Gurusamy
Director, Engineering
kgurus...@xpanse.com
www.xpanse.com

On 10/15/20, 1:08 PM, "Anshum Gupta (Jira)"  wrote:


 [ 
https://issues.apache.org/jira/browse/SOLR-14938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anshum Gupta resolved SOLR-14938.
-
Resolution: Invalid

[~krisgurusamy] - Please ask questions regarding usage on the Solr user 
mailing list. 

JIRA is meant for issue tracking purposes.

> Solr 8.6.3
> --
>
> Key: SOLR-14938
> URL: https://issues.apache.org/jira/browse/SOLR-14938
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: contrib - DataImportHandler
>Reporter: Krishnan
>Priority: Major
>
> I've just downloaded solr 8.6.3 and trying to create DIH for loading 
structured XML. I found out that DIH will be deprecated soon with version 9.0. 
What is the equivalent of DIH in new solr version? How do I import structured 
XML data which is very custom and index in Solr new version? Any help is 
appreciated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)



Re: systemd definition for solr?

2020-10-15 Thread Ryan W
I didn't realize that to start a systemd service, I need to do...

systemctl start solr

...and not...

service solr start

Now the output from the status command looks a bit better, though still
with some problems...

[root@faspbsy0002 system]# systemctl status solr.service
? solr.service - LSB: A very fast and reliable search engine.
   Loaded: loaded (/etc/rc.d/init.d/solr; bad; vendor preset: disabled)
   Active: active (exited) since Thu 2020-10-15 15:58:23 EDT; 19s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 34100 ExecStop=/etc/rc.d/init.d/solr stop (code=exited,
status=1/FAILURE)
  Process: 98871 ExecStart=/etc/rc.d/init.d/solr start (code=exited,
status=0/SUCCESS)



On Thu, Oct 15, 2020 at 3:24 PM Ryan W  wrote:

> Does anyone have a simple systemd definition for a solr service?
>
> The things I am finding on the internet don't work.  I am not sure if this
> is the kind of thing where there might be some boilerplate that (usually)
> works?  Or do situations vary so much that no boilerplate is possible?
>
> Here is what I see when I try to use one of the definitions I found on the
> internet:
>
> [root@faspbsy0002 system]# systemctl status solr.service
> ? solr.service - LSB: A very fast and reliable search engine.
>Loaded: loaded (/etc/rc.d/init.d/solr; bad; vendor preset: disabled)
>Active: failed (Result: exit-code) since Thu 2020-10-15 09:32:02 EDT;
> 5h 50min ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 34100 ExecStop=/etc/rc.d/init.d/solr stop (code=exited,
> status=1/FAILURE)
>   Process: 1337 ExecStart=/etc/rc.d/init.d/solr start (code=exited,
> status=0/SUCCESS)
>
> Oct 15 09:32:01 faspbsy0002 systemd[1]: Stopping LSB: A very fast and
> reliab
> Oct 15 09:32:01 faspbsy0002 su[34102]: (to solr) root on none
> Oct 15 09:32:02 faspbsy0002 solr[34100]: No process found for Solr node
> runn...3
> Oct 15 09:32:02 faspbsy0002 systemd[1]: solr.service: control process
> exited...1
> Oct 15 09:32:02 faspbsy0002 systemd[1]: Stopped LSB: A very fast and
> reliabl
> Oct 15 09:32:02 faspbsy0002 systemd[1]: Unit solr.service entered failed
> state.
> Oct 15 09:32:02 faspbsy0002 systemd[1]: solr.service failed.
> Warning: Journal has been rotated since unit was started. Log output is
> incomplete or unavailable.
> Hint: Some lines were ellipsized, use -l to show in full.
>


systemd definition for solr?

2020-10-15 Thread Ryan W
Does anyone have a simple systemd definition for a solr service?

The things I am finding on the internet don't work.  I am not sure if this
is the kind of thing where there might be some boilerplate that (usually)
works?  Or do situations vary so much that no boilerplate is possible?

Here is what I see when I try to use one of the definitions I found on the
internet:

[root@faspbsy0002 system]# systemctl status solr.service
? solr.service - LSB: A very fast and reliable search engine.
   Loaded: loaded (/etc/rc.d/init.d/solr; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-10-15 09:32:02 EDT; 5h
50min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 34100 ExecStop=/etc/rc.d/init.d/solr stop (code=exited,
status=1/FAILURE)
  Process: 1337 ExecStart=/etc/rc.d/init.d/solr start (code=exited,
status=0/SUCCESS)

Oct 15 09:32:01 faspbsy0002 systemd[1]: Stopping LSB: A very fast and
reliab
Oct 15 09:32:01 faspbsy0002 su[34102]: (to solr) root on none
Oct 15 09:32:02 faspbsy0002 solr[34100]: No process found for Solr node
runn...3
Oct 15 09:32:02 faspbsy0002 systemd[1]: solr.service: control process
exited...1
Oct 15 09:32:02 faspbsy0002 systemd[1]: Stopped LSB: A very fast and
reliabl
Oct 15 09:32:02 faspbsy0002 systemd[1]: Unit solr.service entered failed
state.
Oct 15 09:32:02 faspbsy0002 systemd[1]: solr.service failed.
Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.


Info about legacyMode cluster property

2020-10-15 Thread yaswanth kumar
Can someone explain what are the implications when we change legacyMode=true on 
solr 8.2

We have migrated from solr 5.5 to solr 8.2 everything worked great but when we 
are trying to add a core to existing collection with core api create it’s 
asking to pass the coreNodeName or switch legacyMode to true. When we switched 
it worked fine . But we need to understand on what are the cons because seems 
like this is false by default from solr 7

Sent from my iPhone

bash: solr: command not found

2020-10-15 Thread Ryan W
Hi all,

I run solr like this...

service solr start

However, another user of the server can't run solr this way.  They are
seeing...

bash: solr: command not found

How do I enable them to run Solr as a service?

Thank you,
Ryan


Re: Strange fetch streaming expression doesn't fetch fields sometimes?

2020-10-15 Thread uyilmaz
Is it possible to duplicate its functionality using existing expressions?

In SQL, while grouping you can just say first(column) to get some one-to-many 
value if you don't care which one you get. Solr usually only has min,max,avg.. 
aggregation functions. If it had a "first" function I could just get userid and 
first(username) in an expression, I sometimes use min(username) as a trick 
while faceting to get extra fields alongside faceted results, but max,min only 
accepts numbers in streaming expressions.

On Wed, 14 Oct 2020 20:47:28 -0400
Joel Bernstein  wrote:

> Yes, the docs mention one-to-one and many-to-one fetches, but one-to-many
> is not supported currently. I've never really been happy with fetch. It
> really needs to be replaced with a standard nested loop join that handles
> all scenarios.
> 
> 
> Joel Bernstein
> http://joelsolr.blogspot.com/
> 
> 
> On Tue, Oct 13, 2020 at 6:30 PM uyilmaz  wrote:
> 
> > I think I found the reason right after asking (facepalm), but it took me
> > days to realize this.
> >
> > I think fetch performs a naive "in" query, something like:
> >
> > q="userid:(123123 123123123 12432423321323)={batchSize}"
> >
> > When userid to document relation is one-to-many, it is possible that above
> > query will result in documents consisting entirely of last two userid's
> > documents, so the first one is left out, resulting in empty username. Docs
> > state that one to many is not supported with fetch, but I didn't stumble
> > onto this issue until recently so I just assumed it would work.
> >
> > Sorry to take your time, I hope this helps somebody later.
> >
> > Have a nice day.
> >
> > On Wed, 14 Oct 2020 00:38:05 +0300
> > uyilmaz  wrote:
> >
> > >
> > > Hi all,
> > >
> > > I have a streaming expression looking like:
> > >
> > > fetch(
> > >   myAlias,
> > >   top(
> > >   n=3,
> > >   various expressions here
> > > sort="count(*) desc"
> > >   ),
> > >   fl="username", on="userid=userid", batchSize=3
> > > )
> > >
> > > which fails to fetch username field for the 1st result:
> > >
> > > {
> > >  "result-set":{
> > >   "docs":[{
> > > "userid":"123123",
> > > "count(*)":58}
> > >,{
> > > "userid":"123123123",
> > > "count(*)":32,
> > > "username":"Ayha"}
> > >,{
> > > "userid":"12432423321323",
> > > "count(*)":30,
> > > "username":"MEHM"}
> > >,{
> > > "EOF":true,
> > > "RESPONSE_TIME":34889}]}}
> > >
> > > But strangely, when I change n and batchSize both to 2 and touch nothing
> > else, fetch fetches the first username correctly:
> > >
> > > fetch(
> > >   myAlias,
> > >   top(
> > >   n=2,
> > >   various expressions here
> > > sort="count(*) desc"
> > >   ),
> > >   fl="username", on="userid=userid", batchSize=2
> > > )
> > >
> > > Result is:
> > >
> > > {
> > >  "result-set":{
> > >   "docs":[{
> > > "userid":"123123",
> > > "count(*)":58,
> > > "username":"mura"}
> > >,{
> > > "userid":"123123123",
> > > "count(*)":32,
> > > "username":"Ayha"}
> > >,{
> > > "EOF":true,
> > > "RESPONSE_TIME":34889}]}}
> > >
> > > What can be the problem?
> > >
> > > Regards
> > >
> > > ~~ufuk
> > >
> > > --
> > > uyilmaz 
> >
> >
> > --
> > uyilmaz 
> >


-- 
uyilmaz 


Error false and Error true in Solr logs

2020-10-15 Thread gnandre
Hi,

What do Error false and Error true flags mentioned against Solr errors in
Solr admin UI log mean?


Re: solr-8983.pid: Permission denied

2020-10-15 Thread Alexandre Rafalovitch
If the .pid file is not at that location, then I would investigate
where that file is instead (after Solr is started).

If it is in a different location, then you have different environment
expectations, somehow. This, in all honesty, would still be consistent
with my theory that Solr was started somehow differently (perhaps just
this once).

If it is nowhere, then you may have a permission issue around creating
that file in the first place.

Basically, I am saying that maybe the issue you have is a symptom of a
deeper discrepancy rather than the actual issue to solve directly.

Regards,
   Alex.

On Thu, 15 Oct 2020 at 11:03, Ryan W  wrote:
>
> The .pid file referenced in the "Permission denied" message does not exist.
>
> On Thu, Oct 15, 2020 at 11:01 AM Ryan W  wrote:
>
> > I have been starting solr like so...
> >
> > service solr start
> >
> >
> > On Thu, Oct 15, 2020 at 10:31 AM Joe Doupnik  wrote:
> >
> >>  Alex has it right. In my environment I created user "solr" in group
> >> "users". Then I ensured that "solr:user" owns all of Solr's files. In
> >> addition, I do Solr start/stop with an /etc/init.d script (the Solr
> >> distribution has the basic one which we can embellish) in which there is
> >> control line RUNAS="solr". The RUNAS variable is used to properly start
> >> Solr.
> >>  Thanks,
> >>  Joe D.
> >>
> >> On 15/10/2020 15:02, Alexandre Rafalovitch wrote:
> >> > It sounds like maybe you have started the Solr in a different way than
> >> > you are restarting it. E.g. maybe you started it manually (bin/solr
> >> > start, probably as a root) but are trying to restart it via service
> >> > script. Who owned the .pid file? I am guessing 'root', while the
> >> > service script probably runs as a different (lower-permission) user.
> >> >
> >> > The practical effect of that assumption is that your environmental
> >> > variables were set differently and various things (e.g. logs) may not
> >> > be where you expect.
> >> >
> >> > The solution is to be consistent in using the service to
> >> > start/restart/stop your Solr.
> >> >
> >> > Regards,
> >> > Alex.
> >> >
> >> > On Thu, 15 Oct 2020 at 09:51, Ryan W  wrote:
> >> >> What is my permissions problem here:
> >> >>
> >> >> [root@faspbsy0002 bin]# service solr restart
> >> >> Sending stop command to Solr running on port 8983 ... waiting up to 180
> >> >> seconds to allow Jetty process 38947 to stop gracefully.
> >> >> /opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission
> >> >> denied
> >> >>
> >> >> What is the practical effect if Solr can't write this solr-8983.pid
> >> file?
> >> >> What user should own the contents of /opt/solr/bin ?
> >> >>
> >> >> Thanks
> >>
> >>


Re: solr-8983.pid: Permission denied

2020-10-15 Thread Joe Doupnik
    Ah so, systemd style. I suggestion which might help. Look at the 
/etc/init.d style script in the Solr distribution and uses its commands 
as a reference when you review the systemd equivalents. In addition, a 
prerequisite is choosing the user+group for Solr files, applying 
ownership of those files, and ensuring the systemd script uses that user 
information (which the init.d script does via that RUNAS item). Solr''s 
offered /etc/init.d file is in installation directory ~/solr/bin/init.d 
as file solr.
    For systemd I control apps via commands of the form systemctl start 
solr.service.

    Thanks,
    Joe D.

On 15/10/2020 16:01, Ryan W wrote:

I have been starting solr like so...

service solr start


On Thu, Oct 15, 2020 at 10:31 AM Joe Doupnik  wrote:


  Alex has it right. In my environment I created user "solr" in group
"users". Then I ensured that "solr:user" owns all of Solr's files. In
addition, I do Solr start/stop with an /etc/init.d script (the Solr
distribution has the basic one which we can embellish) in which there is
control line RUNAS="solr". The RUNAS variable is used to properly start
Solr.
  Thanks,
  Joe D.

On 15/10/2020 15:02, Alexandre Rafalovitch wrote:

It sounds like maybe you have started the Solr in a different way than
you are restarting it. E.g. maybe you started it manually (bin/solr
start, probably as a root) but are trying to restart it via service
script. Who owned the .pid file? I am guessing 'root', while the
service script probably runs as a different (lower-permission) user.

The practical effect of that assumption is that your environmental
variables were set differently and various things (e.g. logs) may not
be where you expect.

The solution is to be consistent in using the service to
start/restart/stop your Solr.

Regards,
 Alex.

On Thu, 15 Oct 2020 at 09:51, Ryan W  wrote:

What is my permissions problem here:

[root@faspbsy0002 bin]# service solr restart
Sending stop command to Solr running on port 8983 ... waiting up to 180
seconds to allow Jetty process 38947 to stop gracefully.
/opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission
denied

What is the practical effect if Solr can't write this solr-8983.pid

file?

What user should own the contents of /opt/solr/bin ?

Thanks






Re: solr-8983.pid: Permission denied

2020-10-15 Thread Ryan W
The .pid file referenced in the "Permission denied" message does not exist.

On Thu, Oct 15, 2020 at 11:01 AM Ryan W  wrote:

> I have been starting solr like so...
>
> service solr start
>
>
> On Thu, Oct 15, 2020 at 10:31 AM Joe Doupnik  wrote:
>
>>  Alex has it right. In my environment I created user "solr" in group
>> "users". Then I ensured that "solr:user" owns all of Solr's files. In
>> addition, I do Solr start/stop with an /etc/init.d script (the Solr
>> distribution has the basic one which we can embellish) in which there is
>> control line RUNAS="solr". The RUNAS variable is used to properly start
>> Solr.
>>  Thanks,
>>  Joe D.
>>
>> On 15/10/2020 15:02, Alexandre Rafalovitch wrote:
>> > It sounds like maybe you have started the Solr in a different way than
>> > you are restarting it. E.g. maybe you started it manually (bin/solr
>> > start, probably as a root) but are trying to restart it via service
>> > script. Who owned the .pid file? I am guessing 'root', while the
>> > service script probably runs as a different (lower-permission) user.
>> >
>> > The practical effect of that assumption is that your environmental
>> > variables were set differently and various things (e.g. logs) may not
>> > be where you expect.
>> >
>> > The solution is to be consistent in using the service to
>> > start/restart/stop your Solr.
>> >
>> > Regards,
>> > Alex.
>> >
>> > On Thu, 15 Oct 2020 at 09:51, Ryan W  wrote:
>> >> What is my permissions problem here:
>> >>
>> >> [root@faspbsy0002 bin]# service solr restart
>> >> Sending stop command to Solr running on port 8983 ... waiting up to 180
>> >> seconds to allow Jetty process 38947 to stop gracefully.
>> >> /opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission
>> >> denied
>> >>
>> >> What is the practical effect if Solr can't write this solr-8983.pid
>> file?
>> >> What user should own the contents of /opt/solr/bin ?
>> >>
>> >> Thanks
>>
>>


Re: solr-8983.pid: Permission denied

2020-10-15 Thread Ryan W
I have been starting solr like so...

service solr start


On Thu, Oct 15, 2020 at 10:31 AM Joe Doupnik  wrote:

>  Alex has it right. In my environment I created user "solr" in group
> "users". Then I ensured that "solr:user" owns all of Solr's files. In
> addition, I do Solr start/stop with an /etc/init.d script (the Solr
> distribution has the basic one which we can embellish) in which there is
> control line RUNAS="solr". The RUNAS variable is used to properly start
> Solr.
>  Thanks,
>  Joe D.
>
> On 15/10/2020 15:02, Alexandre Rafalovitch wrote:
> > It sounds like maybe you have started the Solr in a different way than
> > you are restarting it. E.g. maybe you started it manually (bin/solr
> > start, probably as a root) but are trying to restart it via service
> > script. Who owned the .pid file? I am guessing 'root', while the
> > service script probably runs as a different (lower-permission) user.
> >
> > The practical effect of that assumption is that your environmental
> > variables were set differently and various things (e.g. logs) may not
> > be where you expect.
> >
> > The solution is to be consistent in using the service to
> > start/restart/stop your Solr.
> >
> > Regards,
> > Alex.
> >
> > On Thu, 15 Oct 2020 at 09:51, Ryan W  wrote:
> >> What is my permissions problem here:
> >>
> >> [root@faspbsy0002 bin]# service solr restart
> >> Sending stop command to Solr running on port 8983 ... waiting up to 180
> >> seconds to allow Jetty process 38947 to stop gracefully.
> >> /opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission
> >> denied
> >>
> >> What is the practical effect if Solr can't write this solr-8983.pid
> file?
> >> What user should own the contents of /opt/solr/bin ?
> >>
> >> Thanks
>
>


Re: Data Impor Handlert

2020-10-15 Thread DINSD | SPAutores

Hi Alexander,

Very useful the provided information.

Assinatura SPA Many thanks and best regards
**
*Rui Pimentel*


**
*DINSD - Departamento de Informática / SPA Digital*
Av. Duque de Loulé, 31 - 1069-153 Lisboa PORTUGAL
*T * (+ 351) 21 359 44 36 */* (+ 351) 21 359 44 00 *F* (+ 351) 21 353 02 57
 informat...@spautores.pt
www.SPAutores.pt
 
 


Please consider the environment before printing this email

Esta mensagem electrónica, incluindo qualquer dos seus anexos, contém 
informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e destina-se 
unicamente à pessoa e endereço electrónico acima indicados. Se não for o 
destinatário desta mensagem, agradecemos que a elimine e nos comunique 
de imediato através do telefone +351 21 359 44 00 ou por email para: 
ge...@spautores.pt 


This electronic mail transmission including any attachment hereof, 
contains information that is PRIVATE, CONFIDENTIAL and PROTECTED FROM 
DISCLOSURE, and it is only for the use of the person and the e-mail 
address above indicated. If you have received this electronic mail 
transmission in error, please destroy it and notify us immediately 
through the telephone number +351 21 359 44 00 or at the e-mail address: 
ge...@spautores.pt

Assinatura SPA
On 2020-10-15 15:33, Alexandre Rafalovitch wrote:
Solr now has package managers and DIH is one of the packages to 
reflect the fact that its development cycle is not locked to Solr's 
and to reduce core download. Tika may be heading the same way, as 
running Tika inside the Solr process could cause memory issues with 
complex PDFs.


In terms of other ways of pre-process and load data into Solr, there 
are things like:

1) Apache Camel https://camel.apache.org/
2) Apache NiFi https://nifi.apache.org/

Other commercial solutions also exist, such as StreamSets:
3) 
https://streamsets.com/documentation/datacollector/latest/help//datacollector/UserGuide/Destinations/Solr.html


And, of course, you can always roll your own with SolrJ.

Regards,
  Alex.



On Thu, 15 Oct 2020 at 10:08, DINSD | SPAutores 
 wrote:


Hi

Based on this document there are two ways to index document on the
Solr platform, https://lucidworks.com/post/indexing-with-solrj/

Quote:
"Two popular methods of indexing existing data are the Data Import
Handler (DIH) and Tika (Solr Cell)/ExtractingRequestHandler"

Now that DHI has been discontinued, only supported by a community
package, are there any other options?

Best regards
*Rui Pimentel*

**
*Rui Pimentel*


**
*DINSD - Departamento de Informática / SPA Digital*
Av. Duque de Loulé, 31 - 1069-153 Lisboa  PORTUGAL
*T * (+ 351) 21 359 44 36 */* (+ 351) 21 359 44 00 *F* (+ 351) 21
353 02 57
 informat...@spautores.pt

www.SPAutores.pt 




Please consider the environment before printing this email

Esta mensagem electrónica, incluindo qualquer dos seus anexos,
contém informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e
destina-se unicamente à pessoa e endereço electrónico acima
indicados. Se não for o destinatário desta mensagem, agradecemos
que a elimine e nos comunique de imediato através do telefone +351
21 359 44 00 ou por email para: ge...@spautores.pt


This electronic mail transmission including any attachment hereof,
contains information that is PRIVATE, CONFIDENTIAL and PROTECTED
FROM DISCLOSURE, and it is only for the use of the person and the
e-mail address above indicated. If you have received this
electronic mail transmission in error, please destroy it and
notify us immediately through the telephone number +351 21 359 44
00 or at the e-mail address: ge...@spautores.pt




Re: Data Impor Handlert

2020-10-15 Thread Alexandre Rafalovitch
Solr now has package managers and DIH is one of the packages to reflect the
fact that its development cycle is not locked to Solr's and to reduce core
download. Tika may be heading the same way, as running Tika inside the Solr
process could cause memory issues with complex PDFs.

In terms of other ways of pre-process and load data into Solr, there are
things like:
1) Apache Camel https://camel.apache.org/
2) Apache NiFi https://nifi.apache.org/

Other commercial solutions also exist, such as StreamSets:
3)
https://streamsets.com/documentation/datacollector/latest/help//datacollector/UserGuide/Destinations/Solr.html

And, of course, you can always roll your own with SolrJ.

Regards,
  Alex.



On Thu, 15 Oct 2020 at 10:08, DINSD | SPAutores
 wrote:

> Hi
>
> Based on this document there are two ways to index document on the Solr
> platform, https://lucidworks.com/post/indexing-with-solrj/
>
> Quote:
> "Two popular methods of indexing existing data are the Data Import Handler
> (DIH) and Tika (Solr Cell)/ExtractingRequestHandler"
>
> Now that DHI has been discontinued, only supported by a community package,
> are there any other options?
>
> Best regards
> *Rui Pimentel*
>
> *Rui Pimentel*
>
>
> * DINSD - Departamento de Informática / SPA Digital*
> Av. Duque de Loulé, 31 - 1069-153 Lisboa  PORTUGAL
> *T * (+ 351) 21 359 44 36 */* (+ 351) 21 359 44 00  *F* (+ 351) 21 353 02
> 57
> <%7bmailsector...@spautores.pt> informat...@spautores.pt
>  www.SPAutores.pt
> 
> 
> 
> 
> Please consider the environment before printing this email
>
> Esta mensagem electrónica, incluindo qualquer dos seus anexos, contém
> informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e destina-se
> unicamente à pessoa e endereço electrónico acima indicados. Se não for o
> destinatário desta mensagem, agradecemos que a elimine e nos comunique de
> imediato através do telefone  +351 21 359 44 00 ou por email para:
> ge...@spautores.pt
>
> This electronic mail transmission including any attachment hereof,
> contains information that is PRIVATE, CONFIDENTIAL and PROTECTED FROM
> DISCLOSURE, and it is only for the use of the person and the e-mail address
> above indicated. If you have received this electronic mail transmission in
> error, please destroy it and notify us immediately through the telephone
> number  +351 21 359 44 00 or at the e-mail address:  ge...@spautores.pt
>
>


Re: solr-8983.pid: Permission denied

2020-10-15 Thread Joe Doupnik
    Alex has it right. In my environment I created user "solr" in group 
"users". Then I ensured that "solr:user" owns all of Solr's files. In 
addition, I do Solr start/stop with an /etc/init.d script (the Solr 
distribution has the basic one which we can embellish) in which there is 
control line RUNAS="solr". The RUNAS variable is used to properly start 
Solr.

    Thanks,
    Joe D.

On 15/10/2020 15:02, Alexandre Rafalovitch wrote:

It sounds like maybe you have started the Solr in a different way than
you are restarting it. E.g. maybe you started it manually (bin/solr
start, probably as a root) but are trying to restart it via service
script. Who owned the .pid file? I am guessing 'root', while the
service script probably runs as a different (lower-permission) user.

The practical effect of that assumption is that your environmental
variables were set differently and various things (e.g. logs) may not
be where you expect.

The solution is to be consistent in using the service to
start/restart/stop your Solr.

Regards,
Alex.

On Thu, 15 Oct 2020 at 09:51, Ryan W  wrote:

What is my permissions problem here:

[root@faspbsy0002 bin]# service solr restart
Sending stop command to Solr running on port 8983 ... waiting up to 180
seconds to allow Jetty process 38947 to stop gracefully.
/opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission
denied

What is the practical effect if Solr can't write this solr-8983.pid file?
What user should own the contents of /opt/solr/bin ?

Thanks




Data Impor Handlert

2020-10-15 Thread DINSD | SPAutores

Hi

Based on this document there are two ways to index document on the Solr 
platform, https://lucidworks.com/post/indexing-with-solrj/


Quote:
"Two popular methods of indexing existing data are the Data Import 
Handler (DIH) and Tika (Solr Cell)/ExtractingRequestHandler"


Now that DHI has been discontinued, only supported by a community 
package, are there any other options?


Best regards
*Rui Pimentel*
Assinatura SPA
**
*Rui Pimentel*


**
*DINSD - Departamento de Informática / SPA Digital*
Av. Duque de Loulé, 31 - 1069-153 Lisboa PORTUGAL
*T * (+ 351) 21 359 44 36 */* (+ 351) 21 359 44 00 *F* (+ 351) 21 353 02 57
 informat...@spautores.pt
www.SPAutores.pt
 
 


Please consider the environment before printing this email

Esta mensagem electrónica, incluindo qualquer dos seus anexos, contém 
informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e destina-se 
unicamente à pessoa e endereço electrónico acima indicados. Se não for o 
destinatário desta mensagem, agradecemos que a elimine e nos comunique 
de imediato através do telefone +351 21 359 44 00 ou por email para: 
ge...@spautores.pt 


This electronic mail transmission including any attachment hereof, 
contains information that is PRIVATE, CONFIDENTIAL and PROTECTED FROM 
DISCLOSURE, and it is only for the use of the person and the e-mail 
address above indicated. If you have received this electronic mail 
transmission in error, please destroy it and notify us immediately 
through the telephone number +351 21 359 44 00 or at the e-mail address: 
ge...@spautores.pt

Assinatura SPA


Re: solr-8983.pid: Permission denied

2020-10-15 Thread Alexandre Rafalovitch
It sounds like maybe you have started the Solr in a different way than
you are restarting it. E.g. maybe you started it manually (bin/solr
start, probably as a root) but are trying to restart it via service
script. Who owned the .pid file? I am guessing 'root', while the
service script probably runs as a different (lower-permission) user.

The practical effect of that assumption is that your environmental
variables were set differently and various things (e.g. logs) may not
be where you expect.

The solution is to be consistent in using the service to
start/restart/stop your Solr.

Regards,
   Alex.

On Thu, 15 Oct 2020 at 09:51, Ryan W  wrote:
>
> What is my permissions problem here:
>
> [root@faspbsy0002 bin]# service solr restart
> Sending stop command to Solr running on port 8983 ... waiting up to 180
> seconds to allow Jetty process 38947 to stop gracefully.
> /opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission
> denied
>
> What is the practical effect if Solr can't write this solr-8983.pid file?
> What user should own the contents of /opt/solr/bin ?
>
> Thanks


solr-8983.pid: Permission denied

2020-10-15 Thread Ryan W
What is my permissions problem here:

[root@faspbsy0002 bin]# service solr restart
Sending stop command to Solr running on port 8983 ... waiting up to 180
seconds to allow Jetty process 38947 to stop gracefully.
/opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission
denied

What is the practical effect if Solr can't write this solr-8983.pid file?
What user should own the contents of /opt/solr/bin ?

Thanks


Re: Rotate Solr Logfiles

2020-10-15 Thread DINSD | SPAutores

Hi Erick,

I tried with four different browsers, whit clear caches.

Appears in any of them.

Assinatura SPA Best
**
*Rui Pimentel*


**
*DINSD - Departamento de Informática / SPA Digital*
Av. Duque de Loulé, 31 - 1069-153 Lisboa PORTUGAL
*T * (+ 351) 21 359 44 36 */* (+ 351) 21 359 44 00 *F* (+ 351) 21 353 02 57
 informat...@spautores.pt
www.SPAutores.pt
 
 


Please consider the environment before printing this email

Esta mensagem electrónica, incluindo qualquer dos seus anexos, contém 
informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e destina-se 
unicamente à pessoa e endereço electrónico acima indicados. Se não for o 
destinatário desta mensagem, agradecemos que a elimine e nos comunique 
de imediato através do telefone +351 21 359 44 00 ou por email para: 
ge...@spautores.pt 


This electronic mail transmission including any attachment hereof, 
contains information that is PRIVATE, CONFIDENTIAL and PROTECTED FROM 
DISCLOSURE, and it is only for the use of the person and the e-mail 
address above indicated. If you have received this electronic mail 
transmission in error, please destroy it and notify us immediately 
through the telephone number +351 21 359 44 00 or at the e-mail address: 
ge...@spautores.pt

Assinatura SPA
On 2020-10-15 12:57, Erick Erickson wrote:

Possibly browser caches? Try using a private window or purging your browser 
caches.

Shot in the dark…

Best,
Erick


On Oct 15, 2020, at 5:41 AM, DINSD | SPAutores 
 wrote:

Hi,

I'm currently using Solr-8.5.2 with a default log4j2.xml and trying to do the 
following :

Each time an event appears in the log file, i check, rectify if necessary and 
clean (Rotate) the logfiles.

This causes the solr.log file to run out of data, which is what we want.

However if I use the web interface, "localhost: port", and view the "Logging" 
option,
messages remain visible.

Any idea why this is happening, or other way to "force rotate"?

Best regards
Rui


Rui Pimentel



DINSD - Departamento de Informática / SPA Digital
Av. Duque de Loulé, 31 - 1069-153 Lisboa  PORTUGAL
T (+ 351) 21 359 44 36 / (+ 351) 21 359 44 00  F (+ 351) 21 353 02 57
 informat...@spautores.pt
 www.SPAutores.pt

Please consider the environment before printing this email

Esta mensagem electrónica, incluindo qualquer dos seus anexos, contém 
informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e destina-se 
unicamente à pessoa e endereço electrónico acima indicados. Se não for o 
destinatário desta mensagem, agradecemos que a elimine e nos comunique de 
imediato através do telefone  +351 21 359 44 00 ou por email para: 
ge...@spautores.pt

This electronic mail transmission including any attachment hereof, contains 
information that is PRIVATE, CONFIDENTIAL and PROTECTED FROM DISCLOSURE, and it 
is only for the use of the person and the e-mail address above indicated. If 
you have received this electronic mail transmission in error, please destroy it 
and notify us immediately through the telephone number  +351 21 359 44 00 or at 
the e-mail address:  ge...@spautores.pt
  


Re: Rotate Solr Logfiles

2020-10-15 Thread Erick Erickson
Possibly browser caches? Try using a private window or purging your browser 
caches.

Shot in the dark…

Best,
Erick

> On Oct 15, 2020, at 5:41 AM, DINSD | SPAutores 
>  wrote:
> 
> Hi,
> 
> I'm currently using Solr-8.5.2 with a default log4j2.xml and trying to do the 
> following :
> 
> Each time an event appears in the log file, i check, rectify if necessary and 
> clean (Rotate) the logfiles.
> 
> This causes the solr.log file to run out of data, which is what we want.
> 
> However if I use the web interface, "localhost: port", and view the "Logging" 
> option,
> messages remain visible.
> 
> Any idea why this is happening, or other way to "force rotate"?
> 
> Best regards
> Rui
> 
> 
> Rui Pimentel
> 
> 
> 
> DINSD - Departamento de Informática / SPA Digital
> Av. Duque de Loulé, 31 - 1069-153 Lisboa  PORTUGAL
> T (+ 351) 21 359 44 36 / (+ 351) 21 359 44 00  F (+ 351) 21 353 02 57
>  informat...@spautores.pt
>  www.SPAutores.pt
> 
> Please consider the environment before printing this email 
> 
> Esta mensagem electrónica, incluindo qualquer dos seus anexos, contém 
> informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e destina-se 
> unicamente à pessoa e endereço electrónico acima indicados. Se não for o 
> destinatário desta mensagem, agradecemos que a elimine e nos comunique de 
> imediato através do telefone  +351 21 359 44 00 ou por email para: 
> ge...@spautores.pt 
> 
> This electronic mail transmission including any attachment hereof, contains 
> information that is PRIVATE, CONFIDENTIAL and PROTECTED FROM DISCLOSURE, and 
> it is only for the use of the person and the e-mail address above indicated. 
> If you have received this electronic mail transmission in error, please 
> destroy it and notify us immediately through the telephone number  +351 21 
> 359 44 00 or at the e-mail address:  ge...@spautores.pt
>  



Rotate Solr Logfiles

2020-10-15 Thread DINSD | SPAutores

Hi,

I'm currently using Solr-8.5.2 with a default log4j2.xml and trying to 
do the following :


Each time an event appears in the log file, i check, rectify if 
necessary and clean (Rotate) the logfiles.


This causes the solr.log file to run out of data, which is what we want.

However if I use the web interface, "localhost: port", and view the 
"Logging" option,

messages remain visible.

Any idea why this is happening, or other way to "force rotate"?

Best regards
Rui

Assinatura SPA
**
*Rui Pimentel*


**
*DINSD - Departamento de Informática / SPA Digital*
Av. Duque de Loulé, 31 - 1069-153 Lisboa PORTUGAL
*T * (+ 351) 21 359 44 36 */* (+ 351) 21 359 44 00 *F* (+ 351) 21 353 02 57
 informat...@spautores.pt
www.SPAutores.pt
 
 


Please consider the environment before printing this email

Esta mensagem electrónica, incluindo qualquer dos seus anexos, contém 
informação PRIVADA, CONFIDENCIAL e de DIVULGAÇÃO PROIBIDA,e destina-se 
unicamente à pessoa e endereço electrónico acima indicados. Se não for o 
destinatário desta mensagem, agradecemos que a elimine e nos comunique 
de imediato através do telefone +351 21 359 44 00 ou por email para: 
ge...@spautores.pt 


This electronic mail transmission including any attachment hereof, 
contains information that is PRIVATE, CONFIDENTIAL and PROTECTED FROM 
DISCLOSURE, and it is only for the use of the person and the e-mail 
address above indicated. If you have received this electronic mail 
transmission in error, please destroy it and notify us immediately 
through the telephone number +351 21 359 44 00 or at the e-mail address: 
ge...@spautores.pt

Assinatura SPA