16 Commits (jsonvalidator)

Author	SHA1	Message	Date
Stéphane Lesimple	8cafbc854c	fix: allow ssh-as in connect.pl	2 years ago
Stéphane Lesimple	fa842c94d8	fix: connect.pl: don't look for error messages when sysret==0	2 years ago
Stéphane Lesimple	867410a16d	enh: plugins: better signal handling to avoid dangling children processes	2 years ago
Stéphane Lesimple	4fb5e17166	chore: connect.pl: more readable indentation	3 years ago
Stéphane Lesimple	ce9cf3213c	enh: connect.pl: report empty ttyrec as ttyrec_empty instead of ttyrec_error	3 years ago
Stéphane Lesimple	4508b6b6a8	enh: more precise matching of ssh client error messages	3 years ago
Stéphane Lesimple	e040afb074	chore: new perltidy rules	4 years ago
Stéphane Lesimple	1725130a15	fix: avoid double-close log messages on HUP	4 years ago
Stéphane Lesimple	f1e875ca4b	fix: erroneous message in connect.pl	5 years ago
Stéphane Lesimple	7da3ef3e25	fix: connect.pl: decode 2K bytes of the ttyrec instead of 1K to not miss messages	5 years ago
Stéphane Lesimple	1d9018ef7f	fix: strict check failure was no longer detected to print a help message ... Fixes #155	5 years ago
Stéphane Lesimple	e8d60810f1	Merge pull request #111 from ovh/perluseall ... chore: perl-use-all: dynamically find required modules	5 years ago
Stéphane Lesimple	8e7fc9b949	chore: perl-use-all: dynamically find required modules	5 years ago
Stéphane Lesimple	a479810d83	feat: revamp logs ... All connections and plugin executions emit two logs, an 'open' and a 'close' log. We now add all the details of the connection to the 'close' logs, those that were previously only available in the corresponding 'open' log. This way, it is no longer required to correlate both logs with their uniqid to have all the data: the 'close' log should suffice. The 'open' log is still there if for some reason the 'close' log can't be emitted (kill -9, system crash, etc.), or if the 'open' and the 'close' log are several hours, days or months appart. An additional field "duration" has been added to the 'close' logs, this represents the number of seconds (with millisecond precision) the connection lasted. Two new fields "globalsql" and "accountsql" have been added to the 'open'-type logs. These will contain either "ok" if we successfully logged to the corresponding log database, "no" if it is disabled, or "error $aDetailedMessage" if we got an error trying to insert the row. The 'close'-type log also has the new "accountsql_close" field, but misses the "globalsql_close" field as we never update the global database on this event. On the 'close' log, we can also have the value "missing", indicating that we couldn't update the access log row in the database, as the corresponding 'open' log couldn't insert it. The "ttyrecsize" log field for the 'close'-type logs has been removed, as it was never completely implemented, and contains bogus data if ttyrec log rotation occurs. It has also been removed from the sqlite log databases. The 'open' and 'close' events are now pushed to our own log files, in addition to syslog, if logging to those files is enabled (see ``enableGlobalAccesssLog`` and ``enableAccountAccessLog``), previously the 'close' events were only pushed to syslog. The /home/osh.log is no longer used for ``enableGlobalAccessLog``, the global log is instead written to /home/logkeeper/global-log-YYYYMM.log. The global sql file, enabled with ``enableGlobalSqlLog``, is now split by year-month instead of by year, to /home/logkeeper/global-log-YYYYMM.sqlite.	5 years ago
Stéphane Lesimple	cb02fd2a33	fixes after review	6 years ago
Stéphane Lesimple	fde20136ef	Initial commit	6 years ago