I've checked where XPages OpenLog Logger gets the log database. It specifically goes to the current server, using getSession().getServerName(). As far as I can tell I've never added functionality to log to a different server. So, it doesn't look like it's the XPages code.
It's key to identify if it's the LS, Java or XPages version that's trying to go to the wrong place. XPages OpenLog Logger's debugPrint() method prefixes console messages with “OpenLogItem error: “, but the Java SL may also do that (that was the original source for the code). If you're not getting that, it would suggest it's an LS error being thrown. Also, the particular stack trace may help identify whether it's failing on getting the log database or trying to access a document to add a link, or something else. For XPages OpenLog Logger, xsp.openlog.debugLevel=2 will output the stack trace as well, prefixed with “OpenLogItem error trace:” as a separate logging message.