Quote from: SlappinTOYSsilly on August 13, 2018, 12:28:18 AM

nodecore CLI wont connect to 127.0.0.1:10501

client just repeats messages like this one:
Aug 12, 2018 8:26:24 PM io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference cleanQueue
SEVERE: *~*~*~ Channel ManagedChannelImpl{logId=1111, target=127.0.0.1:10501} was not shutdown properly!!! ~*~*~*
Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.
java.lang.RuntimeException: ManagedChannel allocation site
at io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference.(ManagedChannelOrphanWrapper.java:103)
at io.grpc.internal.ManagedChannelOrphanWrapper.(ManagedChannelOrphanWrapper.java:53)
at io.grpc.internal.ManagedChannelOrphanWrapper.(ManagedChannelOrphanWrapper.java:44)
at io.grpc.internal.AbstractManagedChannelImplBuilder.build(AbstractManagedChannelImplBuilder.java:410)
at nodecore.cli.services.AdminServiceClient.(AdminServiceClient.java:63)
at nodecore.cli.DefaultShell.connect(DefaultShell.java:70)
at nodecore.cli.DefaultShell.access$100(DefaultShell.java:25)
at nodecore.cli.DefaultShell$1.bound(DefaultShell.java:510)
at nodecore.cli.DefaultShell$1.run(DefaultShell.java:479)
at java.lang.Thread.run(Unknown Source)

anyone have a similar issue or a solution??

Other than being annoying, it doesn't seem to prevent the CLI or nodecore from working.
Once nodecore has synced, you can quit the CLI and restart it, if you want to.
It's not a new issue: https://github.com/VeriBlock/nodecore-releases/issues/11