Shawn,
Thank you for all the time you have devoted to this odd problem!
> That attachment did not come through. I saw in another message that you had
included links to screenshots on google photos. It smells like a browser issue.
I cannot replicate it with a Solr 7.7.2 or 7.7.3 download.
>
Yes I screwed the first attachment. sorry. I put the same image up on
google docs as you referenced.
About 9 months ago I upgraded our main server's OS to CentOS 7, when I did that I upgraded solr to 7.7.3. A couple months before that I installed solr 7.7.2 on my dev server. to get everything ready for the main server upgrade. Until you
pointed it out I missed that the two servers were off by a minor rev! I'm assuming this issue happened during the upgrade, but I didn't notice until a few weeks ago. The solr index gets refreshed every day via a cron job. Anyway that explains the
7.7.2 vs 7.7.3 version snafu. I will update my dev server to 7.7.3 so I'm in sync. The issue does happen on both servers.
> I wonder if there might be something in the config file loaded by the handler
that could cause something.
>
> Can you share solr.log?
>
I added the directive to the solr4j2.xml file and here is the solr.log file
after reboot.
https://drive.google.com/file/d/1L6voayOn65fd-NqpR8Pz57-390rklvtG/view?usp=sharing
> I see the same address in my debugger on Chrome. And everything works for
me. Also works in Firefox, and in Edge. I'm on Windows. What browser (and OS
for the browser) are you using to access the admin UI? Could be a browser-specific
issue.
>
I work on Linux and the server is also Linux. Though I use Mint and the
server is CentOS.
I use Firefox and Chrome on Linux, both have the issue. I just tried it on
a Windoze box with Firefox and edge and saw same issue.
thank again,
Scott
On 11/7/21 6:59 PM, Shawn Heisey wrote:
On 11/7/2021 3:44 PM, Scott Derrick wrote:
the address in the debugger is
https://xxxxxxx.org/solr/mbepp/update%2Ftei?_=1636324054429&command=show-config
The %2F between update and tei looks suspicious! 2F is the ASCII number for
the /, but why is it the only slash not uriencoded?
I see the same address in my debugger on Chrome. And everything works for me.
Also works in Firefox, and in Edge. I'm on Windows. What browser (and OS for
the browser) are you using to access the admin UI? Could be a browser-specific
issue.
I have attached a screenshot
file:///home/scott/Desktop/Screenshot%20at%202021-11-07%2014-35-48.png
If I press the Execute button I get another 404 message in the debug window and
a thick red bar at the top of the solr web page, no additional message about
what is wrong.
That attachment did not come through. I saw in another message that you had
included links to screenshots on google photos. It smells like a browser
issue. I cannot replicate it with a Solr 7.7.2 or 7.7.3 download.
One file listing you sent showed a 7.7.2 version number, but the
luceneMatchVersion in your solrconfig.xml is 7.7.3. Can you confirm the
version you're running, and the OS it's running on?
I wonder if there might be something in the config file loaded by the handler
that could cause something.
Can you share solr.log?
I wonder if you might have jars copied to other directories that cause them to
get loaded more than once. I have this advice for everyone on extra jars:
Remove all <lib> elements from solrconfig.xml. Copy all the extra jars you need to ${solr.solr.home}/lib (a directory that does not exist by default). If you have copied jars to other locations to try and get Solr to load them, remove those
copies. The goal is to make absolutely sure that each jar is loaded only once. Bad things can happen when multiple copies are loaded.
I wonder if you might engage in some debugging. In the log4j2.xml file that is actively being used by your install, there is a Loggers section near the end of the file and it defines levels for a few classes like org.apache.hadoop. Can you add a
line that looks like this to that section?:
<Logger name="org.apache.solr.core.SolrResourceLoader" level="debug"/>
(That may be shown in email as two lines, but in the file, it should be one
line. In Solr 8.10, it uses AsyncLogger instead of Logger.)
Once that's added, restart solr and look in solr.log for log lines listing all the individual jars that are loaded. If you don't see that, you may have edited the wrong log4j2.xml file. On my server (which I have not been using for tests related to
your issue) it is located here:
/var/solr/log4j2.xml.
Thanks,
Shawn
