Services auto starts then stops on Windows 2012 Server

Wowza Streaming Engine
1

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:

1040

4

0

0x80000000000000

611

Application

SERVER NAME

WowzaMediaServer362

START

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:

1008

4

0

0x80000000000000

614

Application

SERVER NAME

C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin\startup.bat

service

WowzaMediaServer362

C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin

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:

1040

4

0

0x80000000000000

615

Application

SERVER NAME

WowzaMediaServer362

STOP

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:

1011

4

0

0x80000000000000

616

Application

SERVER NAME

WowzaMediaServer362

C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server\bin\startup.bat

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:

1023

4

0

0x80000000000000

617

Application

SERVER NAME

WowzaMediaServer362

1456

259

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:

1023

4

0

0x80000000000000

618

Application

SERVER NAME

WowzaMediaServer362

1464

259

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:

1027

4

0

0x80000000000000

619

Application

SERVER NAME

1464

1456

WowzaMediaServer362

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:

1027

4

0

0x80000000000000

620

Application

SERVER NAME

1456

1456

WowzaMediaServer362

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:

1045

2

0

0x80000000000000

621

Application

SERVER NAME

WowzaMediaServer362

No process is on the other end of the pipe.

2

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

Thanks for the update.

Richard

4

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.

5

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.