Ignition Service fails to start - 7.6.3 Server 2008 R2 upgrades to Server 2012 R2

Ignition
1

Ignition Service fails to start - v7.6.3 on Server 2008 R2 that was upgraded to Server 2012 R2

Was upgraded to the latest java 8 prior to in place upgrade to Server 2012 R2
Updated the java location in the ignition conf and confirmed fully operational prior to upgrading to 2012 R2

Wrapper log only has errors regarding the service not responding in a timely fashion.
Java is running
The Ignition conf has the correct Java location

This isn't mission critical, I just wanted to attempt upgrading from Server 2008 since it's no longer supported my MS.

Any thoughts as what to check? What could cause the service to not start and only log the service not responding in a timely fashion in the wrapper log?

Thanks,
Casey

2

Can you share the wrapper log anyway?

Ignition 7.6 (and 7.7, 7.8, 7.9, 8.0...) aren't supported any more either...

3

Oh, one thing to check: since you upgraded Java, the location may have changed, and your ignition.conf may no longer be pointing to the right place.

4

Kevin, Sure can: attached

wrapper.log (3.6 MB)

Thanks,
Casey

5

Hmm, yeah, how about ignition.conf?

6

Here is the ignition.conf in a zip file. I triple checked just now the java location and it is the same as in the config: C:\Program Files\Java\jdk1.8.0_192\bin\java.exe

ignition.zip (2.9 KB)

Thanks,
Casey

7

Hmm. I'm kind of out of ideas. Maybe try running uninstall_ignition.bat, reboot, install_ignition.bat, then start_ignition.bat?

(were those even the file names back in 7.6?)

1 Like
8

Also this seems odd, because 8u192 isn't the latest Java 8 release. Did they just get installed side-by-side and Ignition is just ignoring the new version?

9

I'll give that a shot tonight. Those are the names just dashes instead of underscores.

Thanks,
Casey

10

I'll verify that too. That is odd then. Yeah I see that, when I navigate with my PC I get 8 u371 as the download choice (Windows 11). I had used the server to navigate there in server 2008. Oversight by me, I should have checked closer after the upgrade.

Thanks,
Casey

11

Kevin,
That worked! Running those batch files to uninstall, reboot, install and start the service resolved it for me.
Thanks,
Casey