OP25 Logs - Database Error (Code {{ code }})
{{ file }}
File not found.
{{ file }}
Attributes do not conform.
{{ file }}
Database structure is good, but no data was found.
0 rows in table 'data_store'.
{{ file }}
Database might be locked or in use by another process (OP25).
Source: {{ source }}
Traceback
{{ err }}
../op25/gr-op25_repeater/apps/README
Setup SQL Log Database (Optional)
This addition provides a permanent server-side log of control channel activity via logging to an SQL database. See the next section for details on installing and using the log viewer.
1. Make sure that sqlite3 is installed in python
2. Initialize DB (any existing DB data will be destroyed)
WARNING: OP25 MUST NOT BE RUNNING DURING THIS STEP
op25/.../apps$ python sql_dbi.py reset_db
3. Import talkgroups tags file
op25/.../apps$ python sql_dbi.py import_tgid tags.tsv
also, import the radio ID tags file (optional)
op25/.../apps$ python sql_dbi.py import_unit radio-tags.tsv
import the System ID tags file (see below)
op25/.../apps$ python sql_dbi.py import_sysid sysid-tags.tsv
The sysid tags must be a TSV file containing two columns column 1 is the P25 trunked sysid (int, decimal) colunn 2 is the System Name (text) (Note: there is no header row line in this TSV file).
4. Run op25 as usual. Logfile data should be inserted into DB in real time and you should be able to view activity via the OP25 http console (once the flask/datatables app has been set up; see next section).