-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 James,
On 8/18/17 3:48 PM, James H. H. Lampert wrote: > This is not with the Debian apt-get that I'm having trouble > figuring out where it's finding its webapp contexts. > > It's with the downloaded-from-Apache one that I've got running (on > port 7070, no HTTPS) on a CentOS 5 box, and that I haven't figured > out how to run as a service (but that's not the immediate > problem). > > It seems that the Tomcat server was apparently running fine for > several days (albeit unmonitored and without any firewall opening > allowing it to be reached from outside, up until yesterday > afternoon), up until a few hours ago. Then it started going down. > > Yesterday afternoon, I put our webapp context on it, and changed > the port forwarding in the firewall, so that the outside access > (and therefore, the Site24x7 monitor on this particular server) > pointed to it, rather than to what it replaced. > > And then I got a message from Site24x7 telling me that it had gone > down. After a brief inspection, I shut it down and restarted it. > > Less than an hour later, the same story. And a third time. > > The fourth time, I had my hands too full to go in and manually > restart it, and to my surprise, without my having restarted it, I > got a message from Site24x7 telling me it was back up. > > And it bounced up and down a few times since then. I eventually > shut it down. > > There's nothing in catalina.out between our webapp announcing that > it was running (9:14 AM), and the messages from my shutting it down > (11:46 AM). > > So far as I've been able to determine, when it's reported as down, > it's not accepting requests even from within the LAN. > > Anybody ever seen anything like this before? Do you know how the monitoring service tests the service for its "liveness"? Is there anything (else) in the log files? There may be something in the files other than catalina.out. I know that I still have trouble in a dev environment with Tomcat repeatedly detecting changes on the filesystem and re-deploying a context multiple times, even when there have been no changes after the one that caused the initial reload. Have you enabled an access log? If so, can you see the requests both before and after the service appears to go offline? You say that you aren't running it as a service. How then are you running Tomcat? Just starting catalina.sh from the CLI directly? If you run it in the background, are you running it with nohup? If not, your console closing might be killing the Java process. Hmm... but you said that Tomcat does in fact shut down when you login and stop it. Probably not a SIGHUP killing the process. If you stop Tomcat (when it's unresponsive), then re-start it, does it appear to work correctly right away, or do you need to do anything else to get it to work again? - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlmXUOYACgkQHPApP6U8 pFhrNw/+JKhveJc7Zg7gtZ4WBGrWa42jibjIXJOV62VgLRyjaCFIowltwxXpHz9F S2p91A8MYGOYnvMMHU8QHwdC+KW6gR+SoKBVHImHzz1MUJpC6Oru/Np1dcGaM4Jg 7pn4SoWXeMCWrZqt/3keQ2YvsU8ZSUgh6957AF0pYnBmXNkkYZ3LMJ+2Y1UILWZA +DBuuHRnn73YGPu0S8vLQvFr6PQwbbVUVmIe+Lp5i069G1FPHa+9zYdwlUjF5P9l gewCgVidcQE1rSoNyW2FiiNqEtQgths4sV6a34DVi2e5ez6FMGMXk4qcrcZmdP3f lOL0L+QYBvhfXXH/Vl83Bn42lQI2WMVv0nozb/NTr41kUVIbZBbERWQLRmmxqVGs irz/L/6YgGcWX/Mj+ib9mP6SJpqSXrJwBlVeudkG8V4uVkEGzFIy3PwURCNScGrJ 9xVeBz+eBEU0kcgJGP8AcGaO6MuhEnvsuVgVLpSpCAv1m2jrB68/9a1LfU+gfnfL vu6TIaDb0ivqMeD76y3XD4FLOINdAY/eKv6OSRGG+sGI7qCd/K3PQf7nj8qHnDVA QlAsmE7tA6gJb8ULDOdTYFuLDgOoEpkaCHatMP/QAOZf8CgX4uHKB73r7VA2q5Kc Kk0qIJ2stmnIah0BJVXk/sLAtYmxLOc7WzYzJf9SUK43tbZ6eM8= =fmwC -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
