Loading Profile...
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
Krugle basic client "service unavailable"
Krugle basic client doesn't show up. After booting the vmware and succesfully indexing several projects the client interface (port 80) doesn't show up, it permanently shows a message saying it's unavailable.
Official
Response
-
You might need to restart krugle, since it does take a little time to start all the services. Can you get to the Admin Console of Krugle? ip_Address:8080
If you check the status page you can see a service health check at the bottom, the Admin Console runs differently then the Krugle Basic Search Engine.
Another thing to note that if your host machine is slow or has a small amount of RAM, then it will take time for Krugle Basic to run all it's processes.
EMPLOYEE
-
You might need to restart krugle, since it does take a little time to start all the services. Can you get to the Admin Console of Krugle? ip_Address:8080
If you check the status page you can see a service health check at the bottom, the Admin Console runs differently then the Krugle Basic Search Engine.
Another thing to note that if your host machine is slow or has a small amount of RAM, then it will take time for Krugle Basic to run all it's processes.Comment -
-
Yes we're able to access the admin console on port 8080, it seems that's booting correctly (a couple of linux warnings/errors when booting, such as PCI 0:0:7 not found or it couldn't sink with the time server) but it ends booting and shows up a console screen telling us we're able to login to admin and client console on ports 8080 and 80 respectively.
At the admin console there seems to be no problem, there are a couple of warnings telling that couldn't access the Krugle Entreprise API and another one similar, with something about Enterprise version not available or such.
Otherwise we successfully build and indexed one of our projects, at least it seems to succesfully checkout the project and index its contents (as of the projects tab in the admin interface)
By the way, we're running krugle in and vmware fusion under macosx dual core 2 64 bits 4Gb ram so don't think it's a matter of hardware (prehaps might be because the machine connects only via wifi to internet).
Other vmware images of windows and linux run perfectly under the same machine and vmware. -
-
The Krugle Api will not allow the Krugle Basic Search will not be accessible. It should start right up, I am not sure why this service is crashing when the system starts. In the Krugle Basic Admin Console, can click the restart button and see if this will restart the service. If it still doesn't come up I can help you manual start it.
-
-
Well, i just started it again and this time seems to work fine.I've been able to try the client interface straight ahead with our projects. The sole thing that has changed is that the network mode from bridged to nat after being unable to start in bridged mode by a vmware complaint. The admin console show now
Krugle Enterprise website: N/A - Public Search Disabled
Krugle Enterprise webserver: OK
Krugle Enterprise API: OK
Database: OK
Before a 404 Not found message was shown on the "Krugle Enterprise API" status label.
I may dispose the log files if you need them in order to reproduce the problem, just let me know.
Thanks -
-
-
