Grafana dashboard display database name error with TDengine - tdengine

I'm using grafana dashboard 15167 with TDengine database v2.3.3.0 .
The databases are db02, db3, log, test .
But in Grafana dashboard, it's db02, db32, log, test.

Please update grafana 15167 to the latest version (revision 27), it fixed the problem.

Related

Drop database in TDengine

I'm using TDengine. I created a database named iot_data.
When I tried to drop this database:
drop database iot_data;
there is an error:
DB error: Out of memory in rpc queue
I cannot tell what the reason is.
I google 'tdengine Out of memory in rpc queue', and get nothing helped.
This is definitely a bug. You can post more details about your testing here or on GitHub TDengine site, so TDengine team or contributors can take a look.

Error in consulting All Websites in the Matomo [fechada]

I’m configure matomo server in AWS cloud with server of 4 nucleos and 16GB RAM. The database is in RDS da AWS. But when I go to all websites and select data renge, I get the folloing error message: “Oops… there was a problem during the request.” I set all recommended settings. The other options in AllWebsites return the reports.
It sounds like there is an error on the Matomo servers and that the PHP process is failing with an error.
-> Can you please get the team to check your Web server error.log for the actual error message(s) logged by the server?
Once we see the error messages we will likely be able to understand where the problem is, and help provide a solution.

Our webapplication hosted on the ec2 instance is developed in CodeIgniter

However there has been inconsistencies in the ci_session table in the installed MySQL server. Some ip addresses are being inserted repeatedly. However when we login from our system, those ipaddresses are not logged/inserted into the ci_session table. Does this mean that only certain ipaddresses are inserted in the ci_session table?
Can you able to provide guidance on this?
PHP version :7.2.15
MySQL version: 5.0.12
Codeigniter version : 3.1.3
Using session library : default system session library
Server : aws

PowerBI embedded with Direct Query gets white screen and 403

We have a PowerBI report that was connected to an on-premise SQL Server. This server was moved to Azure so we changed the report to now use Direct Query instead of import.
To do this I went into the existing PBIX and changed the data source settings so that the report dataset would now be a direct query one pointing to an azure SQL Server.
After that I've imported my PBIX to my Azure PowerBI Workspace using "powerbi import". I've then updated the dataset since it is a direct query and the credentials need to be updated with "powerbi update-connection"
All of these steps are successful.
I can then proceed get my reports "powerbi get-reports" and get access "powerbi create-embed-token". This also works.
The report loads in embedded setup but it stays white. There seems to be no data or no connection.
PowerBI generates a weird error that we don't generally see:
GET https://wabi-us-north-central-redirect.analysis.windows.net/powerbi/metadata/models/xxxxxxx/?modelOptions=Default&packageId=xxxxxxx 403 (Forbidden)
We have a lot of other reports running on direct query to other Azure SQL Server but none that are successful on this SQL Server that migrated to Azure.
I'm talking with Microsoft as soon as possible as well.
Update: Microsoft is looking at the problem. It seems my data source object got into a corrupt state due to a initial db property set (basically a bug). Will keep this post updated.
Update2: It seems PowerBi workspaces in Azure created before April/17 do not support connecting to more than one SQL Database. The solution would then be to create a different workspace but it seems PowerBi workspaces created via Azure are now deprecated. The solution is to migrate everything to the powerbi service(app.powerbi.com). A lot of rework in perspective.
I finally fixed this problem. It took a month.
the problem was 2 fold:
The PowerBi Azure workspace collection that I had been using was created before April 2017 and that meant that it couldn't support connecting to multiple SQL Server instances. This is undocumented as far as I know.
The command PowerBi CLI that I use to call PowerBi API had been modified so that my connection string's format was now deprecated. MS Product Team gave me the proper format. They did say when this changed but it did.
myversion:
powerbi update-connection -c [Workspace Collection Name] -k [Access Key] -w [Workspace Id] -d [Dataset Id] -s "Data Source=[Server];Initial Catalog [DB];User ID=[user];Password=[pwd]"
The version that works:
powerbi update-connection -c [Workspace Collection Name] -k [Access Key] -w [Workspace Id] -d [Dataset Id] -s "Data Source=[server];Initial Catalog=[db];" -u "[user]" -p "[pwd]"
That error is related to authentication. Try to modify the authentication to prompt for credentials as a workaround.
Hope this helps.

SymmetricDS missing its node_identity

I use symmetricds 3.8.0 to sync data between Oracle 12.1 and Mysql 5.5. Oracle is the Master Server. I use the demo properties to configure with modifying its db connection information.But when I execute command : bin/sym, there show the message below:
This node is configured as a registration server, but it is missing its node_identity. It probably needs configured
It only occur when the master server is Oracle, nothing with Mysql and Mssql, I try it many times but it still show this issue, Do someone meet this problem and help me?
sym_node_identity table has to be populated with one row describing the identity of the root DB on oracle

Resources