Do Active Runbooks Restart Automatically on Server Reboot

We have been developing Runbooks in combination with our Service Manager implementation. We have a Runbook server that has 30 or so active Runbooks. We have yet to reboot the server since the automation was brought on-line (my fault).
We will need to patch the server at some point in the near future. So my question is, when the server is rebooted, do I have to manually restart all of the active jobs or do they restart themselves automatically. I don't have anyway to test this
since the system is operating in a production capacity and I don't want to cause service disruptions.

Hello,
if a Runbook Server is stopped the other(s) or the Runbook Server itself (if its the only and up again) will restart the active Runbooks from begining.
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

Similar Messages

How clusterware restarts on automatically after server reboot in 11g R2

Hi,
I would like to know how the cluster restarts on automatically after the server reboot in 11g R2 RAC . The oracle restart feature in 11g R2 help to restart the components like databases, ASM in case of abnormal failure. But how the clusterware starts on own after the server reboot? can you share any documents or notes is really appreciated.
Thanks,
Robin.

At Grid Infrastructure installation time system configuration is modified so that UNIX init daemon restarts OHASD: http://docs.oracle.com/cd/E11882_01/rac.112/e16794/intro.htm#BABIDEFI. For example with Oracle Linux 5 and Oracle RAC 11.2.0.1 you have following line in /etc/inittab:
h1:35:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1 </dev/nulland:
[root@rac1 ~]# head /etc/init.d/init.ohasd
#!/bin/sh
# Copyright (c) 2001, 2009, Oracle and/or its affiliates. All rights reserved.
# init.ohasd - Control script for the Oracle HA services daemon
# This script is invoked by the init system
ORA_CRS_HOME=/u01/app/11.2.0/grid
export ORA_CRS_HOMEEdited by: P. Forstmann on 11 févr. 2013 18:45

SSRS 2008 R2 Services not restarting automatically after reboot

SSRS 2008 R2 Reporting instance not restarting automatically after patches install. Is there a way to resolve the issue
Windows 2008 R2 Server
16 GB RAM

Hi,
Follow this article to resolve the issue:
Reporting Services service doesn't start after the installation of MS12-070 security patch
http://blogs.msdn.com/b/mariae/archive/2012/11/12/reporting-services-service-doesn-t-start-after-the-installation-of-ms12-070-security-patch.aspx
Workaround 1:
Modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds, follow these steps:
1. Click Start, click Run, type regedit,and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
3. In the right pane, locate the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you must créate it. To do this, follow these steps:
a.On the Edit menu, point to New, and then click DWORD Value.
b.Type ServicesPipeTimeout, and then press ENTER.
c.Right-click ServicesPipeTimeout, and then click Modify.
d.Click Decimal, type 60000, and then click OK.
This value represents the time in milliseconds before
Restart the computer for the changes to take effect. Check that SSRS services can be started now.
You cannot start SQL Server Reporting Services after you apply the update that is discussed in KB 2677070
http://support.microsoft.com/kb/2745448/en-us
Thanks.
Tracy Cai
TechNet Community Support

PI 7.0 Production server restarts automatically

Hi guys,
We have installed and configured correctly a PI 7.0 system on Windows 2003 Standard Edition X64-bit with SQL Server 2005. We are on SP12. Everything, SLD, RFC connections work properly.
The problem is that 4-5 days after the installation the Windows Server restarts automatically in unexpected time during the day (unexpected shutdown), even when anybody doesn't do anything in the system. In the Event Viewer we get the following message/error "System Error: Category 102 EventID 1003". There are no other messages/errors.
This is a production system and we are supposed to go live within the next days! So I need your help ASAP.
Any ideas?
Thank you.
Best Regards.
Evaggelos

1) update your network card drivers to the latest and for all devices including your motherboard chipset drivers.
2) Are you using ethernet instead of USB?
3) This URL might help you
http://www.pcreview.co.uk/forums/thread-1885463.php
Regards
Sangeetha

Automatically start VMs after server reboot

Hello,
I use a OVM server (3.0.3) without clustering, and I'm doing failure simulations before going to production.
When the server reboots after a electrical failure, all VM are in "offline" state, and I need to acknowledge all events before be able to start them (thanks the forum for this information).
I would like to automatically boot the VM after the reboot, is there a way to do this ?
Thanks,
TM

Have you tried to put a symlink to the vm.cfg in /etc/xen/auto? That works independent of VM Manager. I beleive VM Manager will update the machine to running in that situation. If not, at least your machines are running while you sort out the problems with VM Manager.
ln -s /OVS/Repository/<repositoryUUID>/VirtualMachines/<vmUUID>/vm.cfg /etc/xen/auto/<simplename>
Where repositoryUUID (hopefully the only one because the manager doesn't display it)
vmUUID shows as ID on the Info page for the VM
simplename is any name you like. I chose the name that shows as Name on the machine's Info page.
Let us know if the Manager figures it out OK or if you have to jump through some hoops to get it to show "running" for these VMs.

Notify when managed server restarts automatically after a crash.

I am trying to see if there is some way I can be notified (by email) when a managed server a cluster restarts automatically. I am running Weblogic 9.2 on Solaris Sparc 5.10.
I can certainly compare the PIDs of the last and the new JVM but am looking for a slick way to do it especially at the Node Manager level.
Thanks.

Hi,
*The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
*The resource adaptor was started properly.
*We are using file store. But will it make a difference?
Thanks!

After restart Oracle Report Server some reports start automatically to run.

When our report server is restarted always a number of reports are started automatically.
I don't know why these are started automatically?
Is there a avoid starting these reports?

Hello,
If you are storing the jobs on the database then please check:
Using the Reports Server Queue PL/SQL Table and API - RW_SERVER_JOB_QUEUE (Doc ID 72531.1)
otherwise just rename the report server .dat files
1- Go to $ORACLE_HOME/reports/server directory
2- Rename Reports Server dat file.
Unix example :
mv reports_server_name.dat reports_server_name.dat.old
3- Try again to start Reports Server
Possible causes of the issue are:
1.scheduled jobs
or
2.restart of report server while some jobs were waiting in the queue
Regards,
Alex
If someone's answer is correct or helpful please mark it accordingly.
Edited by: AlexDiniasi on 02.08.2012 18:49

Production server restarted automatically

Hi ,
I am new to the production enviorment .
Our production server restarted automatically ,i am unable to find out the reason.
Where we can see the log for cause of restart .
IN SAP SERVER/OPERATING SYSTEM LEVEL .
Ths is on very urgent basis
Hoping earliest response.
Thanks in advance .
RohitK
<b></b>
Message was edited by:
Rohit Kawankar

Hi Manoj,
Thanks for your reply ,
My current configuration is ecc 5 ,oracle 9i ,win2k3 .
I had checked in sm21 ,but i did not found anything related to restart of server .
What are all checks where i can find the log to analysis the problem.
Thanx & Regards
RohitK

Secure server instance restarts automatically

Hi All,
I am using iPlanet Web Server 6.0 SP1 with weblogic app server ( no LDAP ) to host a website on Windows 2000 machine. I have two virtual server instances of iPlanet. The one that is configured for SSL, gets restarted automatically. I get following error in event log of system or error log of that instance.
ncorrect Parameter security ( 3780): for host 202.68.143.70 trying to HEAD /index.html, acl-state reports: access of D:/iPlanet/Servers/docs/web/index.html denied by ACL path=d:/iplanet/servers/docs/web/ directive 1
The ACL entries are OK.
Could anybody please help me out?

The error message states that the server denied access to a client who was trying to access D:/iPlanet/Servers/docs/web/index.html. It denied access as it was instructed to by the first access control directive configured on the path d:/iplanet/servers/docs/web/. If you don't want to deny access to D:/iPlanet/Servers/docs/web/index.html, you should review your ACL file configuration.
The Service Pack Release Notes document the issues addressed by that Service Pack. You can view the Release Notes on docs.sun.com at http://docs.sun.com/db/prod/s1websrv#hic

Outlook 2010 doesn't automatically re-connect after Exchange Server reboot - help

We have recently upgraded from Exch 2003 to Exch 2010. We also upgraded our users Outlook client from 2003 to 2010. Now when an Exch 2010 server is rebooted Outlook does not re-connect automatically. You have to close Outlook and re-open
it and it starts working again. Others have reported the same issue. Outlooks shows the status in the status bar area as password is required. I have read an article in the forums about it being an authentication problem. What
changes can I make in Outlook or to Exchange 2010 to make Outlook automatically reconnect after an Exchange server reboot. thanks

They connect internally in the LAN with their domain credentials.
I haven't noticed any errors in the Exchange server related to this issue but I have not really looked in the logs right after this happens.
I guess I just don't understand how when we were running Exch2003 with Outlook2003 we did not have this problem. Now that we have spent all this money and upgraded to bigger, better, smarter software we are having a problem like this. It seems like
if Outlook senses the lost connection and transfers to Offline that it would keep periodically to see if the email server is back up and reconnect.
Sorry for the delay response.
I would suggestyou create a new Windows profile and test it again. Some times the windows profile curropted and woithout being able to provide credentials.
Hope it is helpful.
Fiona Liao
TechNet Community Support

How to get Mavericks server that is connected to a UPS to restart automatically after a power outage.

This is driving me crazy. Is there anyone running Mavericks as a mission critical server on Backup Power Supplies that has a way to get the servers to restart automatically after a power outage. The UPS vendors all have software for Windows, but not Macs, and the setting in System Preferences, doesn't work with the UPS's Iv'e tried (2 different APC models (Smart and Back-UPs), one Triplite (Smart) and one CyberPower, (all claiming to be Mac compatible))

APC do apparently still do a command-line daemon (PowerChute Network Shutdown) which monitors over the network the UPS and will cleanly shutdown the Mac. For lower-end UPS devices these are typically connected via a USB cable and the built-in Apple System Preferences let you control the options - if it is a model supported. There is however a big limitation of using a USB connection which is that you can only connect a single computer to a UPS via USB and of course most companies have multiple servers.
It maybe that what is happening even if you use APC's software is the following -
Power failure detected by UPS
Signal sent to Mac
Computer does a clean shutdown
Power restored
UPS has no way to tell Mac because it is shutdown and Mac does not support 'Wake on LAN' if fully shutdown
The Mac does have an option to 'Startup automatically after a power failure'. However this might only take place if the Mac is not cleanly shutdown, it could be that if the Mac is cleanly shutdown it does not count this as a power failure. If this is correct then there is nothing that can be done as users to resolve this, the only way it could be resolved would be if Apple provided a way for a tool like APCs software to both do a clean shutdown and set a flag as this being due to a power failure so that when the Mac does detect the power being restored it triggers the Mac in to booting.
In the dim and distant past when Macs used ADB to connect keyboards and mice the ADB interface did support an external power-on signal. This does not exist for USB.
Personally I have regarded the APC software (PowerChute Network Shutdown 3.0.1) to be so badly supported and so old as to be too risky to use. It lists 10.7 and 10.8 but not 10.9 and uses Java 1.6 which itself is unsupported. There is a third-party tool you might want to look at called NUT (Network Ups Tools) see http://www.networkupstools.org
NUT is free and lets you do clever things like -
Connect a single computer via serial or USB to the UPS
Act as a 'server' over the network to other computers sharing the UPS
When power failure is detected the NUT 'server' sends a signal to the NUT 'clients' so all of them know that there is a power failure and can do their own clean shutdowns
This gets round only being able to connect a single computer via USB.

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

ADFS 2.0 service does not automatically start after reboot

Hello,
We have two ADFS 2.0 servers in a farm. Any time these servers reboot, the ADFS service does not automatically start, even though the service is set to auto start. If I manually start the service it starts within 10 seconds.
The error in the logs show:
A timeout was reached (30000 milliseconds) while waiting for the AD FS 2.0 Windows Service service to connect.
The AD FS 2.0 Windows Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
But after the reboot is completed, I can manually start the service with no problems. Again, this ONLY happens on restart. I've searched the forums and found potential solutions for people who have consistent issues with starting ADFS every time.
Any ideas?

UPDATE - I built a 3rd ADFS server and was unable to reproduce the problem, until...
I went in to the service properties of ADFS and saw that even though I specified a Log On As account during the ADFS wizard, it changed itself back to "Network Service". I re-entered our ADFS service account username and password, it was
accepted, and I rebooted. On the next reboot, the service did not start automatically (with the same errors as the other ADFS servers), but I was able to manually start it.
I then went to the original ADFS server having the problem, switched it to use "Network Service", rebooted, and the service started up properly on reboot. I then changed it back to the named domain service account, and the issue came right
back. There are no other errors in the System Log indicating a problem with anything else.
So my guess is that something is happening to prevent the service from starting with the named Domain account on server reboot. But what?

IPlanet 6 restarts automatically

Hi.
I am using iPlanet 6.0. When I try to access a certain screen, sometimes the web server restarts automatically, sometimes it just crashes, and sometimes it works properly. I can't find any error msg logged in the server error log or access log.
Does any one have any ideas as to what might be causing my web server to restart/crash?
Thanks.

These are the only messages I can find in the error and access log:
[25/Jun/2004:18:14:20] info ( 2792):      /listing/ls1200ha.jsp: init
[25/Jun/2004:18:14:32] info ( 336):      Installing a new configuration
[25/Jun/2004:18:14:32] info ( 336):      [LS ls1] <server>, port 8563 ready to accept requests
[25/Jun/2004:18:14:32] info ( 336):      A new configuration was successfully installed
[25/Jun/2004:18:14:32] info ( 336):      Using the Java HotSpot(TM) Server VM v1.3.1_03 from Sun Microsystems Inc.
[25/Jun/2004:18:14:32] info ( 336):      Java VM classpath: c:\ph2c\bin3\class;c:\ph2c\bin3\conf;c:\ph2c\bin3\xml;c:\ph2c\bin3\class\lib\activation.jar;c:\ph2c\bin3\class\lib\classes12.zip;c:\ph2c\bin3\class\lib\jdbc2_0-stdext.jar;c:\ph2c\bin3\class\lib\crimson.jar;c:\ph2c\bin3\class\lib\jaxp.jar;c:\ph2c\bin3\class\lib\xalan.jar;c:\ph2c\bin3\class\lib\jce.zip;c:\ph2c\bin3\class\lib\jce1_2_1.jar;c:\ph2c\bin3\class\lib\local_policy.jar;c:\ph2c\bin3\class\lib\sunjce_provider.jar;c:\ph2c\bin3\class\lib\US_export_policy.jar;c:\ph2c\bin3\class\lib\servlets.jar;c:\ph2c\bin3\class\lib\jndi.jar;c:\ph2c\bin3\class\lib\icu4j.jar;c:\ph2c\bin3\class\lib\mail.jar;c:\ph2c\bin3\class\lib\oromatcher.jar;c:\ph2c\bin3\class\iText;c:\ph2c\bin3\class\webdms;c:\ph2c\bin3\class\ISWeb;C:/iPlanet/Servers/bin/https/jar/NSServletLayer.jar;C:/iPlanet/Servers/bin/https/jar/NSJavaUtil.jar;C:/iPlanet/Servers/bin/https/jar/NSJavaMiscUtil.jar;C:/iPlanet/Servers/bin/https/jar/servlet.jar;C:/iPlanet/Servers/bin/https/jar/servlet-2.3-filters-api.jar;C:/iPlanet/Servers/bin/https/jar/jsp092.jar;C:/iPlanet/Servers/bin/https/jar/jaxp.jar;C:/iPlanet/Servers/bin/https/jar/crimson.jar;C:/iPlanet/Servers/bin/https/jar/xalan.jar;C:/iPlanet/Servers/bin/https/jar/jspengine.jar;
[25/Jun/2004:18:14:32] info ( 336):      Loading IWSSessionManager by default.
[25/Jun/2004:18:14:32] info ( 336):      IWSSessionManager: Maximum number of sessions is 1000
[25/Jun/2004:18:14:33] info ( 336):      Successfully initialized web application environment (web-apps.xml) for virtual server (https-ph2c_com3)
[25/Jun/2004:18:14:33] info ( 336):      Internal Info: loading servlet /listing/ls1200ha.jsp
[25/Jun/2004:18:14:33] info ( 336):      /listing/ls1200ha.jsp: init
[25/Jun/2004:18:14:33] info ( 336):      Internal Info: loading servlet /base/error.jsp
[25/Jun/2004:18:14:33] info ( 336):      /base/error.jsp: init
[25/Jun/2004:18:14:35] info ( 336):      Internal Info: loading servlet /base/error_db.jsp
[25/Jun/2004:18:14:35] info ( 336):      /base/error_db.jsp: init
[25/Jun/2004:18:14:15 +0800] "GET /listing/ls0160.jsp?SRC=%2Flisting%2Fls0510ha.jsp%3FAPP_ID%3D1366830&CM_APP_COMP_NO=3 HTTP/1.0" 200 16300
[25/Jun/2004:18:14:15 +0800] "GET /include/styles.css HTTP/1.0" 304 -
[25/Jun/2004:18:14:15 +0800] "GET /include/modal_ns4.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:15 +0800] "GET /include/strings.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:15 +0800] "GET /include/utils.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:15 +0800] "GET /include/number.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:16 +0800] "GET /include/messages.jsp HTTP/1.0" 200 3482
[25/Jun/2004:18:14:16 +0800] "GET /include/lbjs02.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:16 +0800] "GET /include/action.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:17 +0800] "GET /images/print.gif HTTP/1.0" 200 927
[25/Jun/2004:18:14:17 +0800] "GET /images/radio_y.gif HTTP/1.0" 200 95
[25/Jun/2004:18:14:17 +0800] "GET /images/radio_n.gif HTTP/1.0" 200 87
[25/Jun/2004:18:14:33 +0800] "GET /listing/ls1200ha.jsp?PROF_TYPE=C&CM_APP_COMP_NO=3&CTP_DOC_TYPE=CODE%20OF%20ETHICS&SUB_MEAN=P HTTP/1.0" 200 966
[25/Jun/2004:18:14:34 +0800] "GET /include/action.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:34 +0800] "GET /base/error_db.jsp?_ACTION=&SCREEN_ID=&MSG=AZ-000503%3A+Session+timed+out.+Please+logout+from+the+system+by+clicking+the+Logout+button+and+login+again.++Thank+you. HTTP/1.0" 200 2200
[25/Jun/2004:18:14:34 +0800] "GET /include/styles.css HTTP/1.0" 304 -
[25/Jun/2004:18:14:35 +0800] "GET /include/action.js HTTP/1.0" 304 -
[25/Jun/2004:18:14:35 +0800] "GET /images/line.gif HTTP/1.0" 200 1818
Is there any way for me to know the cause of the crash?
Thanks.

Auto start CLS on server reboot?

I've found that while I leave CLS running with the AlwaysOn scenario it won't resume operation after a server reboot, say for maintenance or other action. Besides setting up some kind of Powershell scheduled task that runs on boot is there a way to enable
CLS to run automatically when the server starts up? That way we can reliably have logging enabled on the server during all of its uptime.

Hi,
Which startup type did you set for Lync Server Centralized Logging Service Agent? If you set to Automatic you can try to change to Automatic (Delayed Start) restart server and wait minutes to have a test.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Do Active Runbooks Restart Automatically on Server Reboot

Similar Messages

Maybe you are looking for