Tomcat 6.0 is getting stoped after certain time automatically.. My machine is never turned off. but still this process is stopped . I am using My tomcat server in production mode.. and I really don't feel good starting my server daily.
What could be the reason because in Production mode server should never get stopped.
Check in your task scheduler;
Go To start->type in search task schduler
go to task scheduler. Check whether any task is running to stop the serverr.
or you can increase permgen space.
Server might be stop because of out of memory exception.
Related
Solr version 8.5.1
My solr is not starting anymore. I use solr start command to start the Solr. Every time I run this command I see the following error
Java HotSpot(TM) 64-Bit Server VM warning: JVM cannot use large page memory because it does not have enough privilege to lock pages in memory.
Waiting up to 30 to see Solr running on port 8983
ERROR: Solr at http://localhost:8983/solr did not come online within 30 seconds!
There is no error in the log files. But connecting to Solr is failing. This was working earlier.
Could someone please help me to troubleshoot the issue?
I found out what the issue is. Even though the message indicated that the server did not start in 30 seconds, it started after some time.
I closed the console window as the server was running in the background and it killed the server. The server is up as long as I keep the command window that I used to start the server.
I have a Release Management 2013 release that is stuck on a deployment step. I believe I know what happened, I just don't know how to get it moving forward.
There are multiple release templates that use the Servers with Agents to run PowerShell scripts. The situation came up that one of the releases, call it release Alpha, seemed to be stuck and I couldn't determine why, so I re-started the Microsoft Deployment Agent. The reason Alpha was stuck is that the Agent was actively working on a deployment step for a different release template, call it Beta. When I restarted the Agent, it picked up the first deployment step for Alpha and finished successfully. However, Beta never finished and is sitting in the In Progress status.
I would like to know if there is anyway for me to push the deployment step for Beta into any other status so that the whole process continues. I am under the gun here for timing, so I would appreciate any suggestions.
EDIT
After about 6 hours of waiting the release Beta finally failed. In the mean time I also attempted to restart the Release Management Monitor service. This resulted in disabling my Release Management Client app with a "License Expired" message. That message finally went away after I rebooted the server where the Release Managagement Monitor service was running.
I know you're over the initial problem, but for future (which is likely with the thick RM client) there's a table in the database which contains the current step status. Steps "In progress" will return with the following query (status = 2 is in progress):
FROM [ReleaseManagement].[dbo].[ReleaseV2ActivityLog]
where status = '2'
If you cannot wait for an unspecified duration for the timeout and also don't want the server restarted for fear of impact, you can change this status column to the value '3' which will mark the step as 'succeeded' and should move you on:
update [ReleaseManagement].[dbo].[ReleaseV2ActivityLog]
set Status = '3'
where Status = '2'
Obviously amend the query to target the correct "in progress" step by specifying the workflowID or something similarly unique.
On the frontend of the plesk when I go to "Tools" > "Backupmanager" the page loads some minutes and then it times just out.
On the server via ssh I saw, that the process pmmcli get one more entry for one call of the backupmanager-page. Even killing the process is not going to work except the timeout comes faster. And the pmmcli - process is keeping the machine quite busy after a few tries.
My question is, how I can get the backup manager up running again?
I am still a rookie with server and even more (or less?) with plesk. I beg for your help or some tips please :)
There is job on our SQL Server. It was started and stopped after some time. However, the job still appears to be running even if it is not.
I can see it "is running" in Job Activity Monitor and also sysjobactivity (= there is no stop_execution_date field filled, but in fact nothing happens. I do not see it running in Activity Monitor.
How to effectively kill the job without need to restart whole server? Stopping the job via SSMS GUI does not work.
I run a Matlab process from the task scheduler, on a WindowsServer 2008R2 VM running on VMWare.
The process gets data from a SQL database and does calculation. The process seems to 'hang' and not do any calculations when the servers are particularly with less activity(on weekends). But when I log in via RDP - the process seems to kick off or come alive and completes its execution.
I have done research about this and have configured the NIC to not to goto sleep when its inactive, from the OS level.
Also I have a different application writing a log file to the Win200R2 server during that period hoping to keep the NIC alive.
But none of the above fixes are working, and still the process hangs on weekends. I would love to hear what the community thinks about this ...
VM Configuration Screenshot