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

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.

Related

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

SQL Server service doesn't start anymore automatically if I make a Windows restart

I have Windows 10 build 1511, where I have installed SQL Server 2014.
After installation everything is OK.
I've made several times shutdown on Windows 10, and after if I turn on my PC everything is OK.
But if I restart the system, after the restart, the SQL Server service remains stopped (startup type is Automatic). I try another restart and shutdown, but the service doesn't start automatically anymore.
I've started the service manually, and after the service is started and everything works ok. If I shut down everything, it is ok afterwards. But if I just restart, the problem that I've described above appears again.
What can I do ?
Thank you !
Update
It seems that the problem is already reported to Microsoft :
https://connect.microsoft.com/SQLServer/feedback/details/1873617/sql-server-not-coming-online-after-os-upgrade-to-windows-10-even-when-startup-type-is-automatic
If you starts services.msc and serach for the SqlServer service, in properties, set the startup as automatic delay instead of automatic.
I'm dealing with the same issue on Win 2012. and it looks like the same issue described here:
Add your windows level user in following path:
Click on Start - Run - Secpol.msc Go to Local Policies - User right assignments
Act as a part of the Operating system
bypass Traverse checking
Lock pages in memory
Log on as a service
Log on a batch job
Replace process level token
If not, please add them and try restarting your system. Your SQL Server should be starting as a service. All the best.
I had this issue on Windows 10 and SQL Server 2014 Express.
The delayed start option didn't work for me, but here's what did work - granting higher DCOM permissions to the Network Service and Local Service accounts.
Click Start, type Component and then click the Component Services
app
In Component Services, double-click Component Services, and then double- click Computers. Right-click My Computer, and then click Properties.
Click the COM Security tab.
In the Launch and Activation Permissions area, click Edit Default.
Click Add, type Network Service, and then click OK. While Network Service is selected, click to select the Allow check boxes for the following items:
Local Launch
Remote Launch
Local Activation
Remote Activation
Repeat step 4 for the Local Service account.
Reboot and SQL Server should not start automatically.
In my case, this is a development environment so I'm less concerned about the security implications of this change and more concerned about getting it to work. So be advised to check out potential security ramifications if that's important in your situation.
pay Attention in suffix too
example: if in your user Secedit.msc is as contoso\usersql, in the windows service needs to be the same, I was putting usersql#contoso.com and was having problems to start the service automatic, after change to contoso\usersql, working fine
follow the way,
SQL SERVER INSTALLATION CENTER (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2019\Configuration Tools) > Maintenance > Edition Upgrade
and restart service
Another solution worked for me:
Open SQL Server Configuration Manager
Select SQL Server Services
Select any service (double click or right click and properties)
Go to "Log On" tab (My Log On settings was "This Account")
Choose "Built-in account" and "Local Service" under it.
Then I did this steps for every other services and it worked. I have no more problem while I am connecting to SQL Server Databases.
SQL Server Services Log On Settings
I faced this issue today , as my server is dependent on SQL server connection , that was also not booting up. It was simple in my case. I saw in services screen its status is STOP. So I started there ans it started working.
windows+R--> services.msc--> right click on the service and start it.

SignalR trace to file not working

I am trying to diagnose an intermittant fault with SignalR, so I want to enable tracing. I followed this guide
http://www.asp.net/signalr/overview/testing-and-debugging/enabling-signalr-tracing
However it is not working or I cannot find the files which are being produced. The configuration in the example just lists the name of the file to log, but no path.
Is there anything else I need to do to get this working? For examples any settings on IIS or additional configuration?
If it is working where would the files be written to?
I am using SignalR 2.1.2 and running it in IIS 7.5
I had to set permissions on the folder the trace file was attempting to write to for the application pool the signalr service is running in. For example the user for the application pool is
IIS APPPOOL\<Application Pool Name>

Running Google Chrome on Ubuntu 12.04 64 bit

I have successfully installed right version of Chrome from here:
https://www.google.com/intl/en/chrome/browser/
However, when I am trying to open it via the terminal I get the following error:
labsPC:~$ google-chrome-stable
[26712:26712:0916/155253:ERROR:process_singleton_posix.cc(264)] Failed to create /home/invictuslabs/.config/google-chrome/SingletonLock: File exists
[26712:26712:0916/155253:ERROR:chrome_browser_main.cc(1155)] 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.
What should I do? Thanks.

running activator h2-browser can not successfully open H2 browser

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.