"Starting Reasoning service: Loading rules and configuration" is a normal startup step that could take some time. When you see this, you can quickly check that reasoning is doing something by tailing the log (tail -f /usr/tideway/log/tw_svc_reasoning.log). You should be able to see the progress of rules loading.

"omniORB: (0) 2018-12-06 14:40:21.984745: Failed to bind to address :: port 25035. Address in use?" usually means you try to start reasoning service but a process is still present that you need to manually kill to solve the problem. As suggested by Brian, a reboot also cleans this up.

This means that an old reasoning service has failed to shutdown correctly. Kill all the old reasoning processes. E.g. run ps axw | grep reasoning to get the pids and kill them.

If you still get it after reboot then this means that something is dying a reasoning is starting and it tries to unsuccessfully restart. In that case what is reported in tw_svc_reasoning.out and tw_svc_reasoning.log

I'll defer to Andrew, but if this is a brand new standalone appliance - no data - how about just doing a tw_model_wipe (with appropriate options) to clear all the data and reload the base taxonomy and TKU

Okay - for some reason the system cannot load the code generated for the IBM.InfomixDynamicServer pattern. The tw_svc_eca_engine.log may tell you why. Given the message is has a TKU. Something else must have been done because otherwise everybody would have problems with 11.3.

In order to get the system working again.

* On the command line run tw_svc_reasoning --deactivate-patterns

* Once the "tw_svc_reasoning started" message appears Ctrl+C out of it