Version 8.1.20 on Windows Server 2022 Standard. Service is set for Automatic start. Delayed start doesn't help. Not sure where to go next. Wrapper.log snip attached.
wrapper_log_042523.txt (32.8 KB)
It looks like ports 8060 and 8088 are already in use by the system. Do you have a second instance of Ignition running?
1 Like
Negative. It is a redundant server system, if that lends any additional clues.
We can start the service manually.
As long as the gateways are on separate machines, then redundancy wouldn't cause the ports to be reported as already in use.
Do you have an updated log file that shows a failed startup and a successful one?
1 Like
running this command in powershell "netstat -anb" or using Tcpview (TCPView for Windows - Sysinternals | Microsoft Learn) should help you check ports already in use, and what is using it
1 Like
Just to be clear, there isn't any indication of a "failed" start attempt of the Ignition service. It simply isn't running, but does start manually.
Attached is yesterday's log file with two annotations that show a server restart after Windows updates, then the manual Ignition service start. This is all I have at the moment, but can get more tomorrow. This isn't a production server (yet) but we want to iron this out while in testing.
wrapper_log_042423.txt (72.5 KB)
After you start it manually what port do you access it on? What's the URL of the gateway when started manually
You can see in this portion of the logs on failed startup that some of the logs are duplicated. To me it looks like it's starting two instances at once.
STATUS | wrapper | 2023/04/24 12:13:30 | --> Wrapper Started as Service
STATUS | wrapper | 2023/04/24 12:13:35 | Java Service Wrapper Standard Edition 64-bit 3.5.42
STATUS | wrapper | 2023/04/24 12:13:35 | Java Service Wrapper Standard Edition 64-bit 3.5.42
STATUS | wrapper | 2023/04/24 12:13:35 | Copyright (C) 1999-2020 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2023/04/24 12:13:35 | Copyright (C) 1999-2020 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2023/04/24 12:13:35 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2023/04/24 12:13:35 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2023/04/24 12:13:35 |
STATUS | wrapper | 2023/04/24 12:13:35 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2023/04/24 12:13:35 |
STATUS | wrapper | 2023/04/24 12:13:39 | Launching a JVM...
STATUS | wrapper | 2023/04/24 12:13:39 | Launching a JVM...
For comparison, this is the successful startup.
STATUS | wrapper | 2023/04/24 12:15:38 | --> Wrapper Started as Service
STATUS | wrapper | 2023/04/24 12:15:38 | Java Service Wrapper Standard Edition 64-bit 3.5.42
STATUS | wrapper | 2023/04/24 12:15:38 | Copyright (C) 1999-2020 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2023/04/24 12:15:38 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2023/04/24 12:15:38 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2023/04/24 12:15:38 |
STATUS | wrapper | 2023/04/24 12:15:38 | Launching a JVM...
1 Like
Are you certain there aren't two Ignition services that are set to start automatically? I know I've seen this before and both services had the path to executable pointing to the same installation of Ignition.
Could you upload a copy of your ignition.conf file? I'm curious to see what the service name is set to in there. And also what's the name of the service that you manually start?
Well, if there are two Ignition services attempting to run, it wasn't done intentionally. If true, how do we resolve? Uninstall/re-install?
The service is named simply "Ignition". Without it running we aren't able to run Designer.
Ignition.conf attached as zip.
ignition.zip (2.8 KB)
You would have to delete the second service. This can be done from the command prompt with sc delete ServiceName. Uninstalling would only remove the service that is used in the ignition.conf file which is currently pointing to the default name of "Ignition".
I don't see a way to locate a service based on the path to executable unfortunately. You could try sorting the services based on the description and see if there are two with "Ignition Gateway" as the description. If you can't find a second service then it may be best to reach out to support.
1 Like
Yes! I found the second "Ignition Gateway" service. I suspect it has to do with a botched attempt at uninstall several months ago. At that time we re-installed anyway and obviously used a different naming for the Gateway.
I successfully removed the offending service and am rebooting now to test....thanks for the help!
2 Likes