Although I wasn't able to figure out the underlying problem, I have finally found a fix;
Instead of setting the nssm to run "solr.cmd" with "start -f" as arguments, I set it to run java.exe with exact command line arguments generated by the solr.cmd command. I haven't experienced an unexpected shutdown ever since. Best Regards, Alexandre Rafalovitch <arafa...@gmail.com>, 28 Oca 2025 Sal, 21:35 tarihinde şunu yazdı: > > Port clash? Possibly with "kill -9" to free that port thrown in. > > Regards, > Alex > > On Tue, Jan 28, 2025, 7:05 a.m. Yaşar Arabacı <yasar11...@gmail.com> wrote: > > > I was able to get procmon and wireshark records today. It looks like a > > windows service (installed by one of the programs we are using) starts > > gbak.exe at the exact time solr is shutting down. Attempts to restart > > solr are also failed while that program is running. > > > > Google search reveals gbak.exe is a backup utility for firebird sql > > server (which was also installed by the same program we are using). I > > found the earlier backups created by the same program and they match > > the earlier shutdown times. > > > > I don't know how and why that program interacts with solr but it gives > > me some peace of mind knowing what is causing the problem. > > > > Best Regards, > > > > Alexandre Rafalovitch <arafa...@gmail.com>, 27 Oca 2025 Pzt, 06:51 > > tarihinde şunu yazdı: > > > > > > Network setup? Has a firewall appliance? It may drop the connection if > > > there is no traffic for a while. E.g. between the nodes. That may cause > > all > > > sorts of fun events. > > > > > > And if you were watching it and maybe doing some test requests, that > > resets > > > the timeout value. > > > > > > Something like wireshark may catch this kind of situations. Both actively > > > by examining the live connection and seeing the device IDs participating > > in > > > it (because firewall will be a piggy in a middle) and by checking if > > > connection was aborted just as Solr shutdown trying to use it. The > > timeout > > > itself will be silent, it is attempt to use connection after will get TCP > > > Fin (or some such). > > > > > > JDBC pools used to get this issue a lot. So if all else fails, check this > > > option. > > > > > > Regards, > > > Alex > > > > > > On Mon, Jan 27, 2025, 2:48 a.m. Yaşar Arabacı <yasar11...@gmail.com> > > wrote: > > > > > > > Checking the task scheduler and system event logs didn't reveal > > > > anything interesting. I also ran procmon during the time it was > > > > supposed to shutdown, but it didn't shut down this time. I think this > > > > is one of those quantum bugs that only exists when not observed. > > > > > > > > I will run procmon again tomorrow and post updates if anything > > > > interesting comes up. > > > > > > > > Best Regards, > > > > > > > > Dmitri Maziuk <dmitri.maz...@gmail.com>, 25 Oca 2025 Cmt, 22:25 > > > > tarihinde şunu yazdı: > > > > > > > > > > On 1/25/25 12:15, Yaşar Arabacı wrote: > > > > > > Hi, > > > > > > > > > > > > I am facing a weird problem where solr shuts down everyday at > > exactly > > > > > > the same time for no apparent reason. I don't know how to begin to > > > > > > debug this. I am sharing some system info and log entries below. I > > > > > > would appreciate any tips and insights into understanding this > > issue. > > > > > > > > > > Did you check the task scheduler? And system event logs? > > > > > > > > > > Dima > > > > > > > > > > >
