Yes. I tried it when I had my computer’s firewall completely off.
Try one more time. It’s probably not going to work, but I’ve got the logs to a point now where I should see your attempt.
Okay. I just tried it with the firewall off again. Did it show up?
Nope. That’s frustrating. I’ll take it up with Reprise again.
Reprise suggests using a utility called telnet to test connectivity, like this:
telnet ls75.rlmcloud.com 443
telnet ls75.rlmcloud.com 5053
Can you paste the full output of those two commands please?
Just Tried it
Trying 69.87.218.212...
Connected to ls75.rlmcloud.com.
Escape character is '^]'.
and
Trying 69.87.218.212...
Connected to ls75.rlmcloud.com.
Escape character is '^]'.
It just hang there forever unfortunately…
That’s what telnet does, it hangs until you kill it. But that does say that it has connectivity. I’m pretty stumped here. And you’re able to log in from a different machine on a different operating system?
@balep @xenon54z Another INL developer just contacted me on Slack with the same issue. We should just get you set up with an alternative licensing solution, this hosted cloud server isn’t cutting it. We can either get you a bunch of node-locked licenses, or we can give you a license server to host yourself. Which would you prefer?
yup it hangs till I push on enter 3 times. If I do, it kill the process. I tried on a machine on witch I have Coreform cubit working → same behavior.
Thanks a lot for the help we are discussing internally on what would be the best solution.
I just installed 2022.4 on macOS 12.6 (arm) and cubit crashed without notice.
From command line I got
**MacOS** % ./Coreform-Cubit-2022.4
usb support disabled
libc++abi: terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
zsh: abort ./Coreform-Cubit-2022.4
from the debugger llvm
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
* frame #0: 0x00007ff8012a300e libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x00007ff8012d91ff libsystem_pthread.dylib`pthread_kill + 263
frame #2: 0x00007ff801224d24 libsystem_c.dylib`abort + 123
frame #3: 0x00007ff801295082 libc++abi.dylib`abort_message + 241
frame #4: 0x00007ff8012861a5 libc++abi.dylib`demangling_terminate_handler() + 242
frame #5: 0x00007ff801183016 libobjc.A.dylib`_objc_terminate() + 104
frame #6: 0x00007ff8012944a7 libc++abi.dylib`std::__terminate(void (*)()) + 8
frame #7: 0x00007ff801296d05 libc++abi.dylib`__cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27
frame #8: 0x00007ff801296ccc libc++abi.dylib`__cxa_throw + 116
frame #9: 0x00007ff80129699f libc++abi.dylib`operator new(unsigned long) + 95
frame #10: 0x00000001089f9b2c libtrelis_lm.dylib`log_rlm_diagnostics(bool) + 380
frame #11: 0x00000001089f47be libtrelis_lm.dylib`trelis_rlm_init(char const*) + 4830
frame #12: 0x00000001089f1b7f libtrelis_lm.dylib`TrelisLM::get_available_features() + 79
frame #13: 0x00000001089ef81f libtrelis_lm.dylib`TrelisLM::login() + 63
frame #14: 0x00000001089eef6d libtrelis_lm.dylib`TrelisLM::login_and_activate(bool, std::__1::function<void ()>) + 45
frame #15: 0x0000000100005acb Coreform-Cubit-2022.4`main + 3419
frame #16: 0x000000020001352e dyld`start + 462
And yes,
sudo mkdir "/Library/Application Support/Reprise"
sudo chmod 777 "/Library/Application Support/Reprise"
did the job, but can’t this be handled? Either in rlm or before calling it? Just to check the directory and print a warning with hints - at least to command line?!
Hi Fabian,
We are working on the Mac packaging to make the user experience better. In the current development release the crash is at least avoided. We will add some more messaging about adding the directories as required.
The root problem is that Apple has modified some of their packaging requirements and Reprise has not adapted to the new requirements. We are attempting to work around the issues on the Mac.
Thanks,
Karl
Updated to Ventura got the same problem again…
Any suggestion?
Did you open a terminal and run the above commands?
yes I did try it before starting the code
For others who may read this thread: the problem was that the licenses had expired.