Environment
OES2015SP1 with iPrint for OES2015 SP1
OES2018SP2 with iPrint Advanced
Situation
In a cluster setup, post upgrade from iPrint for OES2015 SP1 to OES2018 SP2 with iPrint Advanced installed, you are not able to login to IPCON due to an OrientDB issue.
Resolution
This issue happens randomly, and only in a cluster upgrade situation. The workaround is to:
- Stop the orientdb service
- Delete the /var/opt/novell/orientdb/databases/OSystem directory
- Start the orientdb service
- Restart mobile server service
systemctl stop orientdb;rm -rf /var/opt/novell/orientdb/databases/OSystem;systemctl start orientdb;rcnovell-iprint-mobile restart
Additional Information
The /var/opt/novell/log/iprintmobile/iprint_mobile0.log file will show:
at com.orientechnologies.orient.core.db.OrientDBEmbedded.openNoAuthenticate(OrientDBEmbedded.java:215)at com.orientechnologies.orient.core.db.OrientDBEmbedded.openNoAuthenticate(OrientDBEmbedded.java:60)at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:936)at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:913)at com.orientechnologies.orient.server.OConnectionBinaryExecutor.executeDatabaseOpen37(OConnectionBinaryExecutor.java:1200)at com.orientechnologies.orient.client.remote.message.OOpen37Request.execute(OOpen37Request.java:77)at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:304)at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:206)at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:69)