running activator h2-browser can not successfully open H2 browser - playframework-2.3

I'm running activator h2-browser command in a ubuntu 14.04 system in a directory containing associated files of a play framework project. when that command is executed my web application is running on localhost:9000. after running activator h2-browser in the root directory of my project I get the following message in terminal:
[info] Loading project definition from /XXXX/project
[info] Set current project to XXXX (in build file:/XXX/)
TCP server running at tcp://127.0.1.1:9092 (only local connections)
PG server running at pg://127.0.1.1:5435 (only local connections)
Web Console server running at http://127.0.1.1:8082 (only local connections)
after executing that command 127.0.1.1:8082 is opened. I expect to see the h2-browser but actually I get The connection was reset on firefox.
how can I possibly fix it?

Mine worked just as said in documention:
You can browse the contents of your database by typing h2-browser at the play console. An SQL browser will run in your web browser.
To get into play console, I tried activator first and then at the prompt, entered h2-browser.

Running activator h2-browser
has the same effect for me as for the OP. I also tried following the statement on the documentation, so I tried to get into play console by typing "activator", but that seems to start the application and leaves me with three [info]s, the last being
a.e.s.Slf4jLogger - Slf4jLogger started
and no way to enter h2-browser.
Edit: The answer was already posted here! Continuous mode did it for me.

Related

Azure MySQL in App: The server is not responding

I have an Application hosted in a Windows WebApp with MySQL in APP enabled.
After realizing the application wasn't responding I could see in the logs errors about MySQL not responding.
So when I try to access the PHPMyAdmin from the console (clicking on the manage button) I got this error:
I already tried to restart my application, and also stop/start but nothing works.
I already looked for other posts here and no one help me, unfortunately.
As per your screenshot error, it is expected when we are using the Free F1 tier as you can see in my below Screenshot when i tried to reproduce the same.
Later when I changed to Standard S1 SKU and tried to access the PHPMyAdmin from the console, got the expected response from server.
Create an App service.
Go to create a web app. Left-hand side menu search MySQL. and click MySQL.
Click MySQL in App and convert off to on. and click the Save button.
Then Manage Enable and click on the Manage link. phpMyAdmin open.
Solved fixing the database port.
After checking the application's logs I realized a loop of tries to connect to the database and it got all memory and cpu of the server, doing the phpMyAdmin out of the connection. So after scaling the instance and restarting the application, I realized the MySql port had changed. So the problem was because in some time the MySQL port changed generating an infinite loop in the application and in the end making phpMyAdmin out because there was no memory available in the server.

Rabbitmq web manager failed to login in as a administrator and error in console

I`ve created a new user and set that as an administrator but still failed to log in after times of trial. However, I find some information in console, but can not solve it after enable-disable plugins and multiple times of re-installation of rabbitmq-server.
BTW I am using CentOS 7.9.
Solved the question by changing browser from chrome to IE, edge also works.

VS Code 2017 "Localhost refused to connect" HTML file

This is a simple index.Html file, when i click on run i get the attached screen.
I have included the Json configuration.
The previous posts did not resolve my issue, and i did restart the machine as well as running VS Code as an admin. VS Code Error
installed Extensions
This happening because of your firewall setting restriction. please
Try Live Server Extension AND check for Firewall Settings.
Plain HTML/CSS can be opened as a file, no need to run them through a web server.
And if these procedures didn't work tell me about your browser.

Chromium ProcessSingleton

I just got a question recently about how to run chrome or chromium on our school machine (Ubuntu 16.04).
The machine is configured to mount user home folder via samba server with 700 permission. (I think it causes the problem of executing chrome)
When I execute the chromium-browser from terminal
chromium-browser
[26686:26686:1023/143803.603878:ERROR:process_singleton_posix.cc(278)] Failed to create /home/NETID/kharam/.config/chromium/SingletonLock: Operation not supported (95)
[26686:26686:1023/143803.603961:ERROR:chrome_browser_main.cc(1639)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.
I've tried to run chromium on the local account, and it ran.
Is there possible solution??????????
Thank you

"Fail to execute ES search request" popup alert in SonarQube web UI after upgrading from 4.5.1 to 5.1

when I click on an issue in SonarQube web UI to see details, I get this red popup:
Fail to execute ES search request
'{"size":1000,"query":{"bool":{"must":[{"term":{"fileUuid":"9c1ae181-f5c3-47da-8fad-3716aca54b6d"}},{"range":{"line":{"from":1,"to":1000,"include_lower":true,"include_upper":true}}}]}},"sort":[{"line":{"order":"asc"}}]}'
on indices '[sourcelines]' on types '[sourceline]'
and the source code or issue details are not shown.
we started getting this after upgrading from Sonar 4.5.1 to 5.1
I stopped the sonar server, deleted SONAR_QUBE/data/es folder, restarted the process and I see these messages in log:
es[o.e.c.r.a.decider] [sonar-1431655214631] low disk watermark
[15%] exceeded on [1rprlr2pTS2zotdYv71GkQ][sonar-1431655214631] free:
534.3mb[13.2%], replicas will not be assigned to this node
I suppose this may be related, but not sure if these "replicas" have anything to do with "indices"...
I solved this by rebuilding Elastic Search indices:
Stop your SonarQube server
Remove the contents of the $SQ_HOME/data/es directory
Start the server
SonarQube will recreate indices on startup.