When i setup the couchbase community server i got the below error
“Looks like Couchbase Server doesn’t respond in time.
Please manually refresh browser and wait for the Admin Console to
fully start”
what i am doing wrong
Thank you for your help
Hi, could you tell us more? LIke when does this error appears?
Hello
Even I am getting the same error after installing Couchbase
“Looks like Couchbase Server doesn’t respond in time.
Please manually refresh browser and wait for the Admin Console to
fully start”
And, When I try to launch the localhost, it says localhost refused to connect.
http://localhost:8091/index.html
Windows 10
Couchbase 4.5
RAM 8GB
I have tried couple of times installing and unistalling the couchbase, but no luck still the same issue persists
Also, verified netstat and found port 8091 is not in use
C:\Users\12956259>netstat -an
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2738 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4369 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5683 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6087 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10031 0.0.0.0:0 LISTENING
TCP 0.0.0.0:21100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49162 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49164 0.0.0.0:0 LISTENING
TCP 0.0.0.0:50091 0.0.0.0:0 LISTENING
TCP 0.0.0.0:65515 0.0.0.0:0 LISTENING
TCP 0.0.0.0:65531 0.0.0.0:0 LISTENING
TCP 10.2.6.96:139 0.0.0.0:0 LISTENING
TCP 10.2.6.96:49677 52.1.180.171:443 ESTABLISHED
TCP 10.2.6.96:49855 132.245.59.18:443 ESTABLISHED
TCP 10.2.6.96:50408 107.152.25.197:443 CLOSE_WAIT
TCP 10.2.6.96:50700 40.97.157.50:443 ESTABLISHED
TCP 10.2.6.96:50795 40.97.155.18:443 ESTABLISHED
TCP 10.2.6.96:50998 64.71.168.201:443 ESTABLISHED
TCP 10.2.6.96:51413 72.21.206.135:443 ESTABLISHED
TCP 10.2.6.96:51414 72.21.206.135:443 ESTABLISHED
TCP 10.2.6.96:51415 72.21.206.135:443 ESTABLISHED
TCP 10.2.6.96:51416 72.21.206.135:443 ESTABLISHED
TCP 10.2.6.96:51418 72.21.206.135:443 ESTABLISHED
TCP 10.2.6.96:51424 52.216.226.123:80 CLOSE_WAIT
TCP 10.2.6.96:51459 54.231.243.162:443 ESTABLISHED
TCP 10.2.6.96:51493 74.125.29.91:443 ESTABLISHED
TCP 10.2.6.96:51501 74.125.129.188:443 ESTABLISHED
TCP 10.2.6.96:51503 40.97.124.226:443 ESTABLISHED
TCP 10.2.6.96:51506 52.77.169.20:443 ESTABLISHED
TCP 10.2.6.96:51507 52.77.169.20:443 ESTABLISHED
TCP 10.2.6.96:51510 151.101.20.249:443 ESTABLISHED
TCP 10.2.6.96:51511 94.31.29.131:443 ESTABLISHED
TCP 10.2.6.96:51512 94.31.29.131:443 ESTABLISHED
TCP 10.2.6.96:51522 172.217.4.46:443 ESTABLISHED
TCP 10.2.6.96:51525 216.58.212.227:443 ESTABLISHED
TCP 10.2.6.96:51535 172.31.2.20:135 ESTABLISHED
TCP 10.2.6.96:51536 172.31.2.20:49155 ESTABLISHED
TCP 10.2.6.96:51540 66.218.170.51:443 ESTABLISHED
TCP 10.2.6.96:51541 172.31.14.20:135 ESTABLISHED
TCP 10.2.6.96:51542 172.31.14.20:49155 ESTABLISHED
TCP 10.2.6.96:51543 172.31.2.20:445 ESTABLISHED
TCP 10.2.6.96:51688 10.5.4.56:5061 ESTABLISHED
TCP 10.2.6.96:51790 132.245.39.242:443 ESTABLISHED
TCP 10.2.6.96:51818 52.8.172.89:443 ESTABLISHED
TCP 10.2.6.96:63615 74.112.184.85:443 CLOSE_WAIT
TCP 10.2.6.96:63616 74.112.184.85:443 CLOSE_WAIT
TCP 10.2.6.96:63734 52.76.253.110:443 ESTABLISHED
TCP 10.2.6.96:63737 52.76.253.110:443 ESTABLISHED
TCP 10.2.6.96:63759 52.76.253.110:443 ESTABLISHED
TCP 10.2.6.96:63856 172.31.2.54:60432 ESTABLISHED
TCP 10.2.6.96:63858 172.31.2.54:60432 ESTABLISHED
TCP 10.2.6.96:64520 172.31.2.54:60432 ESTABLISHED
TCP 127.0.0.1:49203 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51532 127.0.0.1:4369 SYN_SENT
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:2738 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:5683 [::]:0 LISTENING
TCP [::]:5985 [::]:0 LISTENING
TCP [::]:10031 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49162 [::]:0 LISTENING
TCP [::]:49164 [::]:0 LISTENING
TCP [::]:50091 [::]:0 LISTENING
TCP [::]:65531 [::]:0 LISTENING
UDP 0.0.0.0:123 :
UDP 0.0.0.0:500 :
UDP 0.0.0.0:3702 :
UDP 0.0.0.0:3702 :
UDP 0.0.0.0:4500 :
UDP 0.0.0.0:5353 :
UDP 0.0.0.0:5353 :
UDP 0.0.0.0:6087 :
UDP 0.0.0.0:52311 :
UDP 0.0.0.0:59595 :
UDP 10.2.6.96:137 :
UDP 10.2.6.96:138 :
UDP 10.2.6.96:2177 :
UDP 127.0.0.1:8888 :
UDP 127.0.0.1:49572 :
UDP 127.0.0.1:50326 :
UDP 127.0.0.1:55037 :
UDP 127.0.0.1:56154 :
UDP 127.0.0.1:57729 :
UDP 127.0.0.1:59996 :
UDP 127.0.0.1:60129 :
UDP 127.0.0.1:60130 :
UDP 127.0.0.1:64403 :
UDP [::]:123 :
UDP [::]:500 :
UDP [::]:3702 :
UDP [::]:3702 :
UDP [::]:4500 :
UDP [::]:5353 :
UDP [::]:52311 :
UDP [::]:59596 :
UDP [::1]:61727 :
UDP [fe80::9c1a:280b:2138:517d%13]:546 :
UDP [fe80::9c1a:280b:2138:517d%13]:2177 :
Hi Sarath -
Can you verify that the Couchbase Server service is running? See https://developer.couchbase.com/documentation/server/current/install/startup-shutdown.html
Also, check the logs - if something got totally messed up, there should be something in error.log and you can post it here if it’s not self explanatory. See https://developer.couchbase.com/documentation/server/current/clustersetup/ui-logs.html
Best,
-Will
Thanks Will!
Yes, the server is running fine. I did restarted the server and verified, but the issue still persists.
Unfortunately, there are no logs recorded, the logs folder is empty.
I tried uninstall and reinstall, still the same.
If you installed it and the process can start and run at all, you should at least have a log called babysitter.log. If you don’t have that, you may be running another Erlang program that’s not letting Couchbase Server start due to some conflict.
Some things that can block successful installation on Windows:
- You’re running something else written in Erlang that prevents Couchbase Server from running. (RabbitMQ?)
- Your anti-virus might be silently preventing it from running
- Your firewall software might be preventing it from opening critical ports
I would also suggest checking the Windows Event Viewer to see if you can figure out what’s going on there.