Server keeps shutting down on its own

Register and Participate in Oracle's online communities. Learn from thousand of experts, get answers to your questions and share knowledge with peers. Error: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled.

Join the world’s largest interactive community dedicated to Oracle technologies.

Please turn JavaScript back on and reload this page. Welcome to Oracle Communities. Please enter a title. You can not post a blank message. Please type your message and try again. This discussion is archived. My reports server keeps shutting down of its own accord - then restrating when another request comes in - the problem is that it takes so long to start the user gets an error message.

Utilisation is hardly making the graphs twitch. I checked metalink - but their standard answer is insufficient memory - which is not a problem here. This content has been marked as final. Show 5 replies. Hi Andrew Get in touch with Oracle Support for assistance to resolve this issue. Regards Sripathy. Check the configuration file of the report server. The configuration file should have the same name as your reports server and should have the extension. That way no extra engine needs to start up if a report call is made.By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

The dark mode beta is finally here. Change your preferences any time. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. I have several servers where occasionally - like randomly once per week - Tomcat will just gracefully shut itself down. I've been looking at this for months and cannot find the reason. The only pattern seems to be a long period of nothing going on then the shutdown. Below is one of the events in the Catalina.

You can see it starts then does nothing exciting for several hours. Then gracefully shuts itself down as if it was told to. Tomcat does not gracefully shut down when it's "in trouble" out of memory, or anything else. Linux does not gracefully shut down processes when it's low on memory, it stops them hard with a kill -9, which leave no trace in the Tomcat log.

The answer previously said kill -3 here, which is simply causing a thread dump. So, someone, somewhere, is telling Tomcat to do this. This isn't some unknown, internal "problem". Those kind of things just kill tomcat outright, they don't ask politely.

If you get too much, you can try looking specifically at org. This may well not give you more than it already being logged, but it may tell you something. After that, if so motivated, and it continues, I'd suggest building Tomcat yourself, and interjecting some stack trace dumps. That will give you a solid stack trace to learn from whence this came.

Tomcat isn't really a nasty event storm of just random messages floating around. The shut down is pretty synchronous. So, that stack trace will give you a solid lead as to who started the party. Then you can look from there to see how that could have happened.

Fix Windows 10 Shutdown Problem [Tutorial]

There's a bunch of interfaces and abstractions in Tomcat, but really only a few implementations, so it's not impenetrable. And having a smoking stack trace will help immensely in pinning it down.

The thread is really good reading but I can summarize it for you. When you start Tomcat there is a wait state that starts waiting for the shutdown command. This is normal, but the bug in these versions is an implicit timeout on this wait of about 50 days.

When the wait state timed out, the Tomcat would shutdown. This was happening to a SOLR cluster that I maintained for more than a year before I found this bug and fixed it with an upgrade. No one ever noticed because it took so long to crash and with all that goes on it can be easy to brush past finding the root cause.

The easiest thing is to just restart Tomcat and forget it ever happened. How is your Tomcat started? If there is a parent process, a signal sent to the parent could be the cause of a clean shutdown.Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for. Search instead for. Did you mean:. Contact Email us Tell us what you think. Log In. New Discussion. Server suddenly shuts down by itself. Occasional Visitor. Suddenly the server did not respond.

server keeps shutting down on its own

When we investigated the problem, it turned out that the server was powered off. The server is located in our datacenter in a locked rack.

No one other than us have access to the rack. Obviously we did not power off the server ourselves. There is no software on the server that could have turned it off. This means that the server has suddenly shut down by it self. When we powered the server back on, the BIOS wrote that there was one new event in the error log.

The event was that there was a CMOS checksum error. What can cause the server to shut down by it self? What can cause the CMOS checksum error. All forum topics Previous Topic Next Topic. The unexpected shutdown cause the CMOS checksum error. The unexpected shutdown can be caused: by a software issue but you discard this by an enviromental problem loss power? Nothing from event viewer? There has not been any power loss. The temperature logging says that the temperature has been stable on degrees Celsius at the front of the rack and 33 degrees Celsius at the back.

You mean like if the PSU is broken?One of our Windows servers R2 is shutting down every few days, always afternoon. Different time though. No dumps are created even though the server is setup to create them.

The log under the application is always cleaned right before the restart happened so we can't see anything. In the system log says unexpected shutdown. The scheduler checked, didn't find anything. How to troubleshoot it?

Checked if Windows is activated or a thermal safety shutdown due to an internal fan failure or dysfunction not rotating fast enough?

If it is a physical what is the make on model of the server, some have settings in the BIOS that can help troubleshooting and set the power level correctly. I would look at the hardware. Heat is my first thought but there could be many things. Is the UPS holding a charge? Cleaned or the server just stopped as in power cut and no change to log. Cleaned would imply rough software doing something nasty. It is a hardware server. Running DC and small DB. The users are connecting via terminals.

Plugged into UPS. I'm planning to plug it straight into the wall just to make sure it is not loosing power. As far as rough software - the server is on software restriction policy. You can't move the mouse without the permission. Your DC should not be a TS server, users should be no where near a DC, and the fact you have it running a DB and TS as well puts me back to someone shutting it down rather than logging off, hence your clean logs.

If UPS is not the problem then I also suggest hardware problems because in my experience the hardware is to blame when servers do unexpected restarts without any BSOD's. As far as people might be shutting it down - I will create a gpo to get rid of the shut down button.

server keeps shutting down on its own

Not the best practice to have DC and TS in one place - agree.Keep in touch and stay productive with Teams and Officeeven when you're working remotely.

Learn More. Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.

Select Troubleshooting. Click on view all and select Power. Click next and follow the on-screen instructions. I would suggest you to restore default settings of power plan and check if it helps. Click on the Power Options icon. Hope this information is helpful and do let us know if you need further assistance.

We will be glad to assist. Did this solve your problem? Yes No.

Subscribe to RSS

Sorry this didn't help. I appreciate if you could answer few questions to narrow down to the issue. As an initial troubleshooting step, I suggest you to put the computer in Safe mode and check if the issue persists in Safe mode. Let us know if you need further assistance.

We will be happy to help. April 7, Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Site Feedback. Tell us about your experience with our site. AmyUrman Created on February 1, Windows 10 keeps shutting down on it's own. This thread is locked.Forum Rules. Help Register Login. Latest Threads. Results 1 to 9 of 9. Windows Server Thread, Windows Server shutting itself down! I have a home Windows Server network with a few workstations, and my domain controller Windows Server shutting itself down!

I have a home Windows Server network with a few workstations, and my domain controller keeps shutting itself down automatically every half hour.

server keeps shutting down on its own

Anyone know what's going on and a fix? Is it going through the Windows shut down process or is it like someone has switched off the power? It is going through the Windows shutdown process. Originally Posted by cameronbools. Which version of Windows Server is it?

OK, I'm going to move this thread to the correct forum. Is there anything in the logs to indicate what may be causing this? Have you checked for an update loop i. Is it server essentials? If it is, does it hold all of the FSMO foles? Last edited 9th November at PM. I believe it's 30 days, unless you install the evaluation copy, which is days. Similar Threads Windows will shut down in 1 minute?

By Hay11Mac in forum Windows 7. Windows Server rstart by itself overnight?This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.

I'm a youtuber! Server Keeps Closing itself. IllegalArgumentException: n must be positive at java. WarpManager [], SimpleSignCommands v2. Main [], WorldEdit v5.

WorldEditPlugin [], bccore v1. Vault [cereal, Sleaker, mung3r], PermissionsEx v1. PermissionsEx [[t3hk0d3, zml]], PlotMe v0. WorldGuardPlugin [], AutoBroadcaster v0. AutoBroadcasterPlus [], iConomy v7. ProtocolLibrary [Comphenix], Color4Signs v1. Color4Signs [dedomena], Essentials v2. MultiverseCore [Rigby, fernferret, lithium, main--], ScoreboardStats v0. ScoreboardStats [games], EssentialsAntiBuild v2. MultiversePortals [Rigby, fernferret], BlockHunt v0. BlockHunt [Steffion], Multiverse-Inventories v2.

MultiverseInventories [dumptruckman], SignShop v2. Rollback Post to Revision RollBack. I've seen similar errors on my server. I ended up concluding the map file was corrupted, I was having these crashes a few times a day at the time. I reset the map and all went well from then on out. If this crash happened once don't worry about it, it happens now and then.

If this is consistent I'd recommend a map reset at the least, I ended up doing a full reset of everything, changed hosts, didn't copy config files for plugins, rewrote them etc. Check that all plugins are up to date as well, especially any that interact with chunk generation.

Posting a list of all your plugins may also help.

Is there any way for me to rescue the world? It is a build I have worked on for a while and I would really like to have it back.

If you are running on a server on your pc, open the folder containing the server No I know where to find the world,but it is corrupted somehow, which is what is throwing the error.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *