Results 1 to 5 of 5

Thread: Services auto starts then stops on Windows 2012 Server

  1. #1

    Default Services auto starts then stops on Windows 2012 Server

    Services set to auto. Manually starting services works fine with no errors. After server reboot, server starts up normally, event logs show Wowza services starts up but stops right after.

    Windows 2012 Standard 64bit. Fresh install on 10 servers. Java Server 7 version 25. Fresh install. Wowza 3.6.2 fresh install. This issue is on all 10 servers. Previously running 3.5.2

    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:47 AM
    Event ID: 1040
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Service WowzaMediaServer362 received START control, which will be handled.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1040</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:47.000000000Z" />
    <EventRecordID>611</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WowzaMediaServer362</Data>
    <Data>START</Data>
    </EventData>
    </Event>

    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:49 AM
    Event ID: 1008
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Started C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin\startup.bat service for service WowzaMediaServer362 in C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1008</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:49.000000000Z" />
    <EventRecordID>614</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin\startup.bat</Data>
    <Data>service</Data>
    <Data>WowzaMediaServer362</Data>
    <Data>C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin</Data>
    </EventData>
    </Event>

    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:50 AM
    Event ID: 1040
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Service WowzaMediaServer362 received STOP control, which will be handled.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1040</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:50.000000000Z" />
    <EventRecordID>615</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WowzaMediaServer362</Data>
    <Data>STOP</Data>
    </EventData>
    </Event>

    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:50 AM
    Event ID: 1011
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Killing process C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin\startup.bat because service WowzaMediaServer362 is stopping.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1011</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:50.000000000Z" />
    <EventRecordID>616</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WowzaMediaServer362</Data>
    <Data>C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin\startup.bat</Data>
    </EventData>
    </Event>

    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:52 AM
    Event ID: 1023
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Killing process tree of process 1456 for service WowzaMediaServer362 with exit code 259
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1023</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:52.000000000Z" />
    <EventRecordID>617</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WowzaMediaServer362</Data>
    <Data>1456</Data>
    <Data>259</Data>
    </EventData>
    </Event>


    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:52 AM
    Event ID: 1023
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Killing process tree of process 1464 for service WowzaMediaServer362 with exit code 259
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1023</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:52.000000000Z" />
    <EventRecordID>618</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WowzaMediaServer362</Data>
    <Data>1464</Data>
    <Data>259</Data>
    </EventData>
    </Event>


    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:52 AM
    Event ID: 1027
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Killing PID 1464 in process tree of PID 1456 because service WowzaMediaServer362 is stopping.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1027</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:52.000000000Z" />
    <EventRecordID>619</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>1464</Data>
    <Data>1456</Data>
    <Data>WowzaMediaServer362</Data>
    </EventData>
    </Event>


    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:53 AM
    Event ID: 1027
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Killing PID 1456 in process tree of PID 1456 because service WowzaMediaServer362 is stopping.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="16384">1027</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:53.000000000Z" />
    <EventRecordID>620</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>1456</Data>
    <Data>1456</Data>
    <Data>WowzaMediaServer362</Data>
    </EventData>
    </Event>


    Log Name: Application
    Source: nssm
    Date: 8/15/2013 11:10:53 AM
    Event ID: 1045
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: SERVER NAME
    Description:
    Error attaching to console for service WowzaMediaServer362. AttachConsole() failed: No process is on the other end of the pipe.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="nssm" />
    <EventID Qualifiers="49152">1045</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-15T18:10:53.000000000Z" />
    <EventRecordID>621</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER NAME</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WowzaMediaServer362</Data>
    <Data>No process is on the other end of the pipe.
    </Data>
    </EventData>
    </Event>
    Last edited by malimar; 08-15-2013 at 12:04 PM.

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Not sure why that would be happening. Try removing or commenting out /conf/Server.xml /CommandInterface

    This part at top of Server.xml:

    		<CommandInterface>
    			<HostPort>
    				<IpAddress>*</IpAddress>
    				<Port>8083</Port>
    			</HostPort>
    		</CommandInterface>
    Richard

  3. #3

    Default

    This is a bug with Wowza because our server is booting too fast. Our Windows 2012 Server OS is on SSD, full reboot takes less than 1 minute. Wowza support verified our logs that no internet connection when services is starting to check on licensing.

    Here is the fix:
    Automatic Delayed Start

    It will still fail during the server start-up. But, setup your Recovery option on the service.

    Setup Recovery with the following settings:

    First Failure: Restart the Service
    Second Failure: Restart the Service
    Subsequent Failures: Restart the Service

    Reset fail count after: 0 days (default)
    Restart service after: 2 minutes

    2 minutes is the key to this fix. Hopefully Wowza has a fix for this because these reboots needs to be quick and just because Wowza cannot call home, at least let the services start and call home at a later time. Server now days are getting faster and faster.

  4. #4

    Default

    Restart services after 1 minute is also working after multiple server setup and reboots. Automatic Delayed Start is to workaround. We are still getting event errors of services starting and then stopping because of no internet connection during start-up.

  5. #5
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Thanks for the update.

    Richard

Similar Threads

  1. Replies: 3
    Last Post: 07-14-2015, 01:20 AM
  2. 4.0.3 Working on Windows Server 2012? Anyone get it to work?
    By Steve Guluk in forum General Forum
    Replies: 4
    Last Post: 04-07-2014, 09:13 AM
  3. Windows 2012 AMI
    By shueardm in forum Wowza Streaming Engine in the Cloud
    Replies: 2
    Last Post: 03-14-2014, 07:34 PM
  4. Wowza Service stops after logoff on Windows Server 2003 R2 x64
    By petergibbons in forum Server Administration Discussion
    Replies: 2
    Last Post: 07-11-2012, 08:45 AM
  5. Wowza Media Server 3 and Windows Media services
    By yrrab5 in forum Server Administration Discussion
    Replies: 4
    Last Post: 12-15-2011, 02:06 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •