Difference between revisions of "smart reporter"
(Created page with " rmdstop -server to stop category:loggin") |
(→tables) |
||
(7 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
+ | ==databases and versions== | ||
+ | |||
+ | SmartReporter Database Management | ||
+ | This release can use one of these SQL databases: | ||
+ | |||
+ | • MySQL - When you upgrade from R75.40 or earlier to R77, SmartReporter continues to use the legacy | ||
+ | • MySQL database. In some cases, upgrading from R75.20 or R75.40 can also use MySQL. | ||
+ | |||
+ | PostgreSQL - All new installations of SmartReporter, from R75.40VS and higher, use the PostgreSQL | ||
+ | database. | ||
+ | You do database management operations in these ways: | ||
+ | |||
+ | • With the SmartReporter Database Maintenance view | ||
+ | • With CLI commands. MySQL and PostgreSQL have different commands and procedures | ||
+ | • Changing SmartReporter configuration files | ||
+ | |||
+ | '''To see which SQL database is installed, run:''' | ||
+ | grep DefaultDatabase $CPDIR/registry/HKLM_registry.data | ||
+ | |||
+ | If the command returns the string PostgreSQL, the database is PostgreSQL. If the command returns | ||
+ | another result, the database is MySQL. | ||
+ | |||
+ | ==mysql database== | ||
+ | |||
+ | username for mysql connections: RMSERVER | ||
+ | password can me set in smartreporter gui under management > database maintenance > change database password | ||
+ | |||
+ | mysql binary location: $RTDIR/Database/bin/mysql | ||
+ | socket file: use as defined in $RTDIR/Database/conf/my.cnf | ||
+ | |||
+ | example command to connect to local database | ||
+ | $RTDIR/Database/bin/mysql -u RMSERVER -h localhost -p --socket=/opt/CPrt-R75.40/Database/mysql.sock | ||
+ | |||
+ | ==postgresql== | ||
+ | connecting to postgresql database | ||
+ | $CPDIR/database/postgresql/bin/psql -U cp_postgres -p 18272 rt_database | ||
+ | |||
+ | ==logging and session status== | ||
+ | log consolidation session log: $RTDIR/log_consolidator_engine/log/<Session_ID>/lc_rt.log | ||
+ | |||
+ | example of successful log consolidation entry... | ||
+ | |||
+ | Last processed file: 2017-03-01_235900.log | ||
+ | <br>The Engine has finished scanning the requested log files. | ||
+ | |||
+ | ==service stop and start== | ||
rmdstop -server to stop | rmdstop -server to stop | ||
+ | |||
+ | ==tables== | ||
+ | |||
+ | == fwaction == | ||
+ | |||
+ | fw_action_code | fw_action_name | ||
+ | <br> -1 | | ||
+ | 0 | consolidated | ||
+ | 1 | encrypt | ||
+ | 2 | approved | ||
+ | 3 | accept | ||
+ | 4 | blocked | ||
+ | 5 | drop | ||
+ | 6 | reject | ||
+ | ... and more... | ||
+ | |||
+ | |||
+ | |||
[[category:loggin]] | [[category:loggin]] |
Latest revision as of 02:27, 6 May 2017
Contents |
databases and versions
SmartReporter Database Management This release can use one of these SQL databases:
• MySQL - When you upgrade from R75.40 or earlier to R77, SmartReporter continues to use the legacy • MySQL database. In some cases, upgrading from R75.20 or R75.40 can also use MySQL.
PostgreSQL - All new installations of SmartReporter, from R75.40VS and higher, use the PostgreSQL database. You do database management operations in these ways:
• With the SmartReporter Database Maintenance view • With CLI commands. MySQL and PostgreSQL have different commands and procedures • Changing SmartReporter configuration files
To see which SQL database is installed, run:
grep DefaultDatabase $CPDIR/registry/HKLM_registry.data
If the command returns the string PostgreSQL, the database is PostgreSQL. If the command returns another result, the database is MySQL.
mysql database
username for mysql connections: RMSERVER password can me set in smartreporter gui under management > database maintenance > change database password
mysql binary location: $RTDIR/Database/bin/mysql socket file: use as defined in $RTDIR/Database/conf/my.cnf
example command to connect to local database
$RTDIR/Database/bin/mysql -u RMSERVER -h localhost -p --socket=/opt/CPrt-R75.40/Database/mysql.sock
postgresql
connecting to postgresql database
$CPDIR/database/postgresql/bin/psql -U cp_postgres -p 18272 rt_database
logging and session status
log consolidation session log: $RTDIR/log_consolidator_engine/log/<Session_ID>/lc_rt.log
example of successful log consolidation entry...
Last processed file: 2017-03-01_235900.log
The Engine has finished scanning the requested log files.
service stop and start
rmdstop -server to stop
tables
fwaction
fw_action_code | fw_action_name
-1 | 0 | consolidated 1 | encrypt 2 | approved 3 | accept 4 | blocked 5 | drop 6 | reject
... and more...