Gateway Faulting

Ignition
1

Hi

I have recently updated Ignition (running under Mac OSX) to the latest version. Following this, the gateway fails to start (the webpage simply shows the “Gateway Faulted” message). I have been unable to find any other references on this forum to this error (java.lang.NoSuchMethodError), so hopefully I am not repeating a common issue! However, here is the last few lines of the wrapper.log file showing the failure.

INFO | jvm 1 | 2012/10/18 22:09:30 | ERROR [SRContext ] [22:09:30,477]: Error during context startup. INFO | jvm 1 | 2012/10/18 22:09:30 | java.lang.NoSuchMethodError: org.python.core.PyReflectedFunction.<init>([Ljava/lang/reflect/Method;)V INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.common.script.ScriptManager.addScriptModule(ScriptManager.java:297) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.common.script.ScriptManager.<init>(ScriptManager.java:112) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.gateway.SRContext.createScriptManager(SRContext.java:1054) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.gateway.SRContext.startupInternal(SRContext.java:949) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl.startup(RedundancyManagerImpl.java:184) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.gateway.SRContext.asyncInit(SRContext.java:766) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.gateway.SRContext.access$200(SRContext.java:191) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.gateway.SRContext$2.run(SRContext.java:557) INFO | jvm 1 | 2012/10/18 22:09:30 | at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:526) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.util.concurrent.FutureTask.run(FutureTask.java:138) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) INFO | jvm 1 | 2012/10/18 22:09:30 | at java.lang.Thread.run(Thread.java:680) INFO | jvm 1 | 2012/10/18 22:09:30 | INFO [SRContext ] [22:09:30,478]: Ignition["/main", state=STARTING] ContextState = FAULTED

Any assistance in getting this rectified would be greatly appreciated.

Cheers
James

2

This is going to be complicated to troubleshoot without support being able to dig around (GoToMeeting). It looks like there’s an older version of jython on your classpath somewhere/somehow. I can’t tell whether it’s from a botched upgrade or from another source outside Ignition…

How did you have it installed and what upgrade procedure did you follow?

3

I simply extracted the new version over top of the old version, as I could not find any other instructions for this. In short, following this procedure.

Regards
James

4

Did you shut it down completely before doing so?

5

To the best of my recollection, yes I did shut it down completely.

There is nothing dreadfully important in this project, so I am wondering if it is not a simple fix whether I simply trash the installation and start again. Is there a recommended uninstallation procedure for the OSX version?

Regards
James

6

You can copy the db folder off to your desktop if you want to save your projects and all your gateway settings.

Other than that just delete everything and then unzip it all again.

7

I have removed the old installation (I didn’t even worry about attempting to back up and restore anything), and yet upon reinstallation I get exactly the same result. Obviously this is related to something else on my machine, but I am at a loss to know where to look now. Is there any way I can run diagnostics to find out what the problem may be? Note that I have installed Ignition on another machine running the same OS version, and it runs perfectly, so I can only suspect there is some third-party that is interfering here.

Regards
James

8

You must have an older version of Jython installed or on your classpath somewhere. Does that ring any bells?

9

Unfortunately, no it doesn’t make any sense, as the only thing I did (as far as I can recall now) is install the more recent Ignition version. Is there a way I can check at all?

10

In a terminal try:

echo $PATH

This will show you all the directories on that machines path. You can then check those directories for any old copies of Jython lying around.

11

[quote=“michael.stofan”]In a terminal try:

echo $PATH

This will show you all the directories on that machines path. You can then check those directories for any old copies of Jython lying around.[/quote]

It may also be installed in one of the folders in the JRE install that are always on the classpath, like lib and lib\ext.