Comments
-
Hello, sure, you can. Make sure the postgresql database is at least version 14(the newer the better) and timescaledb extension is newer than 2.9.1. Most of our lab and what we provide are versions 2.14.2 and newer so that is what we recommend as of now. this official documentation should guide you through the installation…
-
please send us logs UI --> settings --> Logs --> support logs: follow the form Send us generated file via https://upload.xormon.com
-
Hello, uknown status for databases we cannot connect to is expected, health status for SQLServer is more of a connection status => if we connect OK otherwise NOK. I suppose the message should be "no current health status information". In the future version you will be able to see separate tables for Connection and Data…
-
1. In the Overview section of each SQL Server instance the graph that should contain information about deadlocks does not contain any values (I guess it should report 0 if no deadlocks where found). If there isn't a 0 the metric wasn't returned at all 2. In the Instances/<DB name>/Capacity section of each database the tab…
-
Hello Jesper, when connecting we specify that intent is read only, but unfortunately that seems to not be enough With this patch the script will not crash and will pool data as expected (changes from yesterday are included and will be included in versions going forward)…
-
Hello Jesper, no, that wasn'ŧ a known issue, thanks for letting us know and testing so thoroughly. 1.Here is a patch: https://download.xormon.com/patch/1.5-26-g08e21/sqlserver-service.pl.gz Gunzip it and copy to this path in your Xormon application directory (755, xormon owner): server-nest/microservices/sqlserver/…
-
Hello, you can find more specific info about most of the metrics here: https://www.ibm.com/docs/en/db2/11.5?topic=functions-mon-get-database-get-database-metrics ROWS_MODIFIED he number of rows inserted, updated, or deleted.This monitor element is an alias of the rows_written monitor element. This monitor element includes…
-
Hello, are you sure you have granted the permissions? https://lpar2rrd.com/OracleDB-performance-monitoring-install.php#OracleDB section: Create DB user for LPAR2RRD Solution: Either re-grant them or you can check their status like so("/as sysdba"): SELECT grantee, table_name, privilege FROM DBA_TAB_PRIVS WHERE grantee LIKE…
-
Hello, apply these 2 patches. 1. https://download.stor2rrd.com/patch/7.60-1-6-g116a9/infortrendperf.pl.gz Gunzip it and copy to /home/stor2rrd/stor2rrd/bin (755, stor2rrd owner) -rwxrwxr-x 1 stor2rrd stor2rrd 30378 Feb 20 09:59 infortrendperf.pl If your web browser gunzips it automatically then just rename it: mv…
-
send us output of these commands please cd /home/lpar2rrd/lpar2rrd # or where your LPAR2RRD work dir is tail -1 etc/version.txt ls -l etc/web_config/hosts.json cat etc/web_config/hosts.json | grep DB2
-
Hello, have you upgraded to v7.60 or is it on virtual appliance with v7.60 already preinstalled?
-
It uses the first section for sure. I believe that the issue has been found, download these 2 patches, apply them and try the connection test again, if it goes ok then the data should start collecting as well https://download.lpar2rrd.com/patch/7.43-2-1-g4983/sqlserver-apitest.pl.gz…
-
Hello, 1.check which driver the script is using: cd /home/lpar2rrd/lpar2rrd # or where your LPAR2RRD work dir is cat data/SQLServer/sqlserver_driver.txt {ODBC Driver 13 for SQL Server} 2.and then check file "/etc/odbcinst.ini" to make sure there isn't specified port under the used driver example: [ODBC Driver 13 for SQL…
-
Try this patch, wait for at least 15 minutes, check a few graphs and send us output of the command below. command: tail /home/lpar2rrd/lpar2rrd/logs/error.log-sqlserver patch: https://download.lpar2rrd.com/patch/7.40-2-3-ged4e/sqlserver-db2json.pl.gz Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755, lpar2rrd owner)…
-
Try to apply the patch below and let it run for a while. The affected Instance should collect data, but keep an eye on other SQL Server Instances also and make sure they did not stop collecting data. If they stop and you need them more than this one then reapply the backup. let us know how it went, this will help us…
-
Hello, run these queries, and send us the output select to_char(action_time,'yyyy-mm-dd') "DATE",<br> action,<br> namespace,<br> version,id,<br> …
-
Hello Greg, so after you set up listener.ora and sqlnet.ora the connection test started working, is that correct?
-
We looked at this closely and are you sure the IP address is correct? connection test you sent us output of was done to 172.30.174.96:1433 and the one entered into web form is 172.130.174.96:1433
-
Does this happen every time you test connection or does it sometimes go through?
-
These changes will be accounted for in the upcoming LPAR2RRD version 7.40 In the meantime you can use these patches. This patch is for connection test: https://download.lpar2rrd.com/patch/7.34-5-16-gedc59/sqlserver-apitest.pl.gz Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755, lpar2rrd owner) -rw-rw-r-- 1 lpar2rrd…
-
Hello, run these commands. su - lpar2rrd cd /home/lpar2rrd/lpar2rrd/ #or where your LPAR2RRD work dir is . etc/lpar2rrd.cfg echo $ORACLE_HOME $ORACLE_HOME/sqlplus
-
Hello, please contact us at support@lpar2rrd.com for further testing
-
Hello, please apply this patch and then try connection test that is in the configuration form where you set up the monitoring and send us a screenshot of the output. Just to see if this small change fixes that. https://download.lpar2rrd.com/patch/7.34-2-3-g518c/sqlserver-apitest.pl.gz Gunzip it and copy to…
-
Hello, we recently encountered the same issue in our test labs. This is what helped: Upgrade libpq on the application end and try again. If you don't need scram-sha-256 authentication, you can revert to md5: * set password_encryption = md5 in postgresql.conf * change the authentication method to md5 in…
-
Hello, can you please try connection test that is in the configuration form where you set up the monitoring and send us a screeshot of the output?
-
ok, I see now, the seemingly simple solution can be to open /etc/odbcinst.ini and manually rename [MSSQL] to for example [ODBC Driver 13 for SQL Server] as our script looks for this naming scheme [ODBC Driver * for SQL Server], can you try and do that?
-
Hello, have you gone through the installation process and installed the ODBC driver? install documentation: https://www.lpar2rrd.com/Microsoft_SQL_Server-performance-monitoring-install.php#MSSQLServer Driver to install:…
-
Hello Greg, could you try connection test on the SSL only available DB with the patch below? 1. backup your current /home/lpar2rrd/lpar2rrd/bin/oracledb-test-api.pl file. 2. Apply this patch: https://download.lpar2rrd.com/patch/7.30-1-4-g6e97f/oracledb-test-api.pl.gz Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755,…
-
This patch should help with getting the capacity data for SQL Server instances with versions lesser than 2016. Would you mind testing it? https://download.lpar2rrd.com/patch/7.30-1-4-g6e97f/sqlserver-db2json.pl.gz Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755, lpar2rrd owner) -rw-rw-r-- 1 lpar2rrd lpar2rrd 23629…
-
seems like we will have to find a workaround for earlier versions, we will look into it
Howdy, Stranger!