Jump to content

Can't load start.jnlp on a Mac


SteveManes

Recommended Posts

Posted (edited)

It's been well over a year since I installed the ISY-994 and everything was going great until I needed to install a new Insteon device today. When I click on ISY994 Administrative Console I get a Universal Devices logo in the center of the screen and then... nothing.  No error message. It just unloads.

I checked my Java Runtime (Version 8, Update 261) which the Control Panel says is the recommended version.  My Mac was updated to 10.15.6 Catalina since I installed the ISY so I don't know if that's the issue.  I can hit the ISY994 "My Devices & Scenes" page okay. But when I click I get on Admin Console I get the screen below.

I've also downloaded and tried to run start.jnlp directly.  After the usual Mac file security warnings it let me do that but launching it gives me a UD logo and then it again crashes.

I'm a developer but not a Java guy so I don't know where the logs are to see if there's a message in there.

I saw a earlier post that I should clear the cache and did so.  But it didn't help. Any ideas?

Screen Shot 2020-09-16 at 6.01.36 PM.png

Edited by SteveManes
Posted (edited)
24 minutes ago, DennisC said:

Here is a link to the troubleshooting section of the Wiki for Macs:

https://wiki.universal-devices.com/index.php?title=Troubleshooting_Help

None of it seems to apply.  After rebooting the device I have no lights showing.

I have the Admin Console icon on my desktop.

My machine's hostname is set accordingly in the local hosts file.

I don't have any of those apps running.

I disabled my anti-virus.

This USED to work fine.  The "My Devices & Scenes" page still does. Something broke in the past year or two since I last used Admin Console.

What I'm seeing in the Mac's log is:

Sep 16 18:33:53 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.14000000-0600-0000-0000-000000000000[60854]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:33:57 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.12000000-0700-0000-0000-000000000000[60848]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:33:57 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[60835]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:00 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.1A000000-0100-0000-0000-000000000000[60846]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:02 jack com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.IDECacheDeleteAppExtension.60885): Path not allowed in target domain: type = pid, path = /Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/XPCServices/com.apple.dt.Xcode.TCPRelayService.xpc error = 147: The specified service did not ship in the requestor's bundle, origin = /Applications/Xcode.app/Contents/PlugIns/IDECacheDeleteAppExtension.appex
Sep 16 18:34:02 jack com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.IDECacheDeleteAppExtension.60885): Path not allowed in target domain: type = pid, path = /Applications/Xcode.app/Contents/Frameworks/IDEKit.framework/Versions/A/XPCServices/IDETouchBarSimulatorService.xpc error = 147: The specified service did not ship in the requestor's bundle, origin = /Applications/Xcode.app/Contents/PlugIns/IDECacheDeleteAppExtension.appex
Sep 16 18:34:03 jack com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.IDECacheDeleteAppExtension.60885): Path not allowed in target domain: type = pid, path = /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/XPCServices/RootDebuggingXPCService.xpc error = 147: The specified service did not ship in the requestor's bundle, origin = /Applications/Xcode.app/Contents/PlugIns/IDECacheDeleteAppExtension.appex
Sep 16 18:34:03 jack com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.IDECacheDeleteAppExtension.60885): Path not allowed in target domain: type = pid, path = /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Xcode/PrivatePlugIns/IDEOSXSupportCore.ideplugin/Contents/XPCServices/com.apple.dt.XcodeMacLocationSimulation.xpc error = 147: The specified service did not ship in the requestor's bundle, origin = /Applications/Xcode.app/Contents/PlugIns/IDECacheDeleteAppExtension.appex
Sep 16 18:34:09 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.15000000-0700-0000-0000-000000000000[60845]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:12 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.19000000-0500-0000-0000-000000000000[60842]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:14 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.1C000000-0400-0000-0000-000000000000[60836]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:16 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0100-0000-0000-000000000000[60849]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:18 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0000-0000-0000-000000000000[60844]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:20 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.16000000-0200-0000-0000-000000000000[60839]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:26 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0600-0000-0000-000000000000[60841]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:28 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.13000000-0300-0000-0000-000000000000[60840]): Service exited due to SIGKILL | sent by mds[323]
Sep 16 18:34:29 jack com.apple.xpc.launchd[1] (com.apple.mdworker.shared.1B000000-0600-0000-0000-000000000000[60847]): Service exited due to SIGKILL | sent by mds[323]

Edited by SteveManes
Posted
2 minutes ago, SteveManes said:

None of it seems to apply.  After rebooting the device I have no lights showing.

 

Are you saying none of the ISY front lights are on? If so, you are having a problem with your ISY. Check the power supply to start.

Posted (edited)

Yes, no lights are showing.  Yet the "My Devices & Scenes" page is working fine.  As a matter of fact, the scheduler just turned on my evening lights.

They flash when booted up but after that, no steady light.

Since I installed the ISY994 I also installed a Unifi router, cloud key and access points. I haven't had any problems with DHCP on it though.

Edited by SteveManes
Posted (edited)

I changed the power supply to another 5V/1.5a 2mm barrel power supply and same thing: the Power light never comes on. But the Unifi controller sees the ISY994.

Could this be a defective ISY994?

Is there any way to back up the data files via the telnet interface?  I really don't want to have to remove ceiling lights and chandeliers again to get at the Insteon inline modules. Or are all the devices backed up on the PLM and the codes are accessible from there?

Screen Shot 2020-09-16 at 8.01.45 PM.png

Screen Shot 2020-09-16 at 8.01.55 PM.png

Edited by SteveManes
  • 2 weeks later...
Posted

@SteveManes I had a similar problem. I'm also sharing these cross posts.

I'm running macOS 10.15.7.

I saw the "UD Loading" screen and then... nothing, the application quit.

I think it was due to an expired certificate or some type of check within the ISY jar launcher, but all of the standard options I tried didn't have any effect (including some more aggressive ones, like removing the Java apps etc.).

Finally, here is what worked for me based on some advice in other posts:

1. Run the following commands to clear the old version of Java (use caution, since these are with sudo)

sudo rm -fr /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin
sudo rm -fr /Library/PreferencePanes/JavaControlPanel.prefPane
sudo rm -fr ~/Library/Application\ Support/Oracle/Java


2. Download and install Java 251 from here https://www.oracle.com/java/technologies/javase/javase8u211-later-archive-downloads.html
(Not sure if it matters, but I also ran the uninstaller first)

3. Now, use the start.jnlp command. ISY will load properly! (Ignore the out of date Java warning for now)

4. Upgrade Java back to 261.

After these steps, everything works for me.
 

 

Posted
11 minutes ago, dxdc said:

@SteveManes I had a similar problem. I'm also sharing these cross posts.
 

That's essentially what I did: uninstall and reinstall Java.  I'm figuring that one of the Mac OS updates invalidated something.

Guest
This topic is now closed to further replies.

×
×
  • Create New...