1
Vote

No Java runtime present, requesting install

I previously had the takipi-service running on my Mac but now it will not start. Starting the service in the normal way (sudo launchctl load /Library/LaunchDaemons/com.takipi.service.plist) gives no output (why doesn't it write to bugtale_service.log?). I ran bin/takipi-service -l from the command line and this is the output:

zebedee:Takipi martin$ bin/takipi-service -l
ServiceConfig C: takipi.server.name = zebedee
ServiceConfig C: takipi.jvm.lib.file = /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/server/libjvm.dylib
ServiceConfig C: takipi.backend.url = https://backend.takipi.com/
Check for pending updates...
About to load JVM shared library: /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/server/libjvm.dylib
About to start Tandem JVM with args:
  -Dorg.sqlite.lib.path=/Library/Takipi/lib
  -Dorg.sqlite.lib.name=libsqlitejdbc.jnilib
  -Djava.class.path=/Library/Takipi/jars/takipi-bootstrap.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/tools.jar
  -Djava.library.path=/Library/Takipi/lib
  -Duser.dir=/Library/Takipi/work
  -Dresources.dir=/Library/Takipi/resources
  -Dtakipi.home=/Library/Takipi
  -Dtakipi.base.url=https://backend.takipi.com/
  -Dtakipi.service.id=S25276
  -Dtakipi.sparkle.enabled=true
  -Dtakipi.config.file=/Library/Takipi/collector.properties
  -Dtakipi.32library.dir=/Library/Takipi/lib32
  -Xms180m
  -Xmx180m
  -Xss1024k
  -XX:-OmitStackTraceInFastThrow
  -XX:+DisableAttachMechanism
  -Dtakipi.allow.local.bundle=y
  -Dtakipi.remote.debug=n
  -Xss2m
No Java runtime present, requesting install.

Comments 2 comments
  • Official comment

    Hi Martin,

     

    Aside from what Daniel mentioned, A few additional thoughts on this.

    1. The immediate thing that comes to mind is that the collector is not able to find the JAVA_HOME variable. Did that change?

    2. In my Mac, I often find that the collector stops working, this is because my mac goes to sleep multiple times a day which in turn pauses or kills all the background process.

    Since the collector is a deamon that auto launch's itself (in Mac), simply killing it will restart the process. That usually solves my problem.

    3. We routinely update the agent/collector. Most recently, I had an older build of the agent/collector and simply upgrading it (by installing the most recent version) did the trick.

    If the above doesnt work, I will work with Daniel to reach out to you offline.

    Karthik

  • Hi Martin,

    it appears that your path to your Java runtime is not correct, or your Java Version was upgraded so the version number or similar changed and therefore the path broke.

    As you are a customer I created a ticket for you so we can troubleshoot it together.

Please sign in to leave a comment.

Join conversation