Technical Teams, Engineers, Product Managers
Description of Issue
Iber(qs) is interrupted by a second instance of Iber(qs) that can't be killed. Due to this, Olo is not able to communicate with the POS.
Error when attempting to kill Iber(qs) is (Access denied). This second instance of Iber(qs) is owned by "SYSTEM" (as observed in Task Manager).
Example of what can be seen in the Olo log:
2019-07-15 20:41:37.9396|2019-07-16 02:41:37.9396|INFO|Starting Iber
2019-07-15 20:41:38.4997|2019-07-16 02:41:38.4997|WARN|Found more than one instance of Iber already running
2019-07-15 20:41:38.5007|2019-07-16 02:41:38.5007|INFO|Exception when checking POS health
System.ApplicationException: Found more than one instance of Iber already running
This issue is not caused by Aloha or Olo. It is a problem in the local environment involving the TCP/IP stack. The second instance of Iber(qs) is started by System32 which restricts the instance from being stopped by Users or Administrators. The problem is not necessarily constant. It can come and go seemingly at random or at regular intervals. Once the second instance of Iber(qs) is launched, the instance that Olo relies on is interrupted and tries to restart. During this time, Olo is not able to function because the interface terminal is not up.
Clear the TCP/IP stack
- Open a Command Prompt as Administrator on the Aloha server.
- Type "netsh int ip reset" (without quotes) and hit enter.
- Wait for the Command Prompt to run through the TCP/IP reset.
- Restart the Aloha Server.
Please use these steps at your own risk. While it has been deemed a safe solution by NCR, we can't be held responsible for further issues related to troubleshooting.