@j UddlZddlZddlZddlZddlmZmZdZdZ dZ dZ ej Z dZedZdaedzed <d ed Dd d izZdefdZdejfdZdefdZddZdeddfdZddZdedejfdZe ddededdfdZe fdededejfdZe fdedefdZ dS)N) get_log_levelinit_subprocess_loggerz4%(asctime)s - %(name)s - %(levelname)s - %(message)sz)/var/log/cloudlinux/lvectl-subprocess.logz/var/log/cloudlinux/lvectl.loglvectl)jsonzno-iopsbytes_running_commandci|] }|d|d S)z\x02x).0cs py/cllvectl/log.py r0s"<<<1aq<<< z\x7freturnct t|tS#t$rYdSwxYw)zEscape control characters so untrusted text cannot forge log records. :param message: value to render into a single-line record :return str: the text with control characters replaced by \xNN escapes z)str translate_LOG_CONTROL_CHARS Exception)messages rsanitize_for_logr3sF +7||%%&8999 +++***+s &) 77c4tjtS)zBThe logger get_synchronous_logger('lvectl') configured, if it ran.logging getLoggerLVECTL_LOGGER_NAMEr rr_lvectl_loggerr!?s  / 0 00rc, tj}n#t$rd}YnwxYw tj}n#t$rd}YnwxYwd} t d|dd5}|ddddpd}d d d n #1swxYwYt|tkr|d td z}n#t$rd}YnwxYwd |d |d |S)aDescribe this process and the one that invoked it. lvectl is rarely run by hand: cagefsctl loops over it once per user, lveutils-panel-cron drives it every 5 minutes, lvemanager and the selectors shell out to it. "Which of them ran this?" is the first question of most investigations and the answer is not recoverable from the log afterwards. Every step is guarded: this only decorates a log record, so no failure to identify the caller may propagate into the command being reported on. An unidentifiable caller degrades to '?', never to an exception. :return str: 'pid= ppid= parent=', with '?' for any part that could not be determined ?z/proc/z/cmdlinerb zutf-8replaceNz...zpid=z ppid=z parent=) osgetpidrgetppidopenreadr'decodestriplen_MAX_PARENT_CMDLINE)pidppidparentfds rdescribe_callerr5Ds  *,,  F )4)))4 0 0 ^BWWYY&&ud33::7INNTTVV]Z]F ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ v;;, , ,0001E9F  5# 5 5T 5 56 5 55sR %%= A  A C9&AC7 C9CC9 C -C99 DDcdtd|tdS)zlRecord the invocation and who made it. :param argv: the argument list as received, logged verbatim zCalled with args: %s (%s)N)r!infor5)argvs rlog_invocationr9gs/ 5t_=N=NOOOOOrcommandc |a|rVdd|D}td||dStd|dS)a\Record a command and the values it resolved its arguments to. log_invocation() says what the caller typed; this says what lvectl made of it -- the uid behind a username, the docroot and domain LVE id behind a domain name, the limits behind a --pmem=1G. Keep the context to values a troubleshooter needs in order to correlate the log with ve.cfg and /proc/lve/map: this runs once per user of a `cagefsctl --isolates-allow-all` sweep. :param str command: command name, also used to name the closing record :param context: resolved values to record, as key=repr pairs  c3*K|]\}}|d|VdS)=Nr )r keyvalues r zlog_command..s4PP*#uc--E--PPPPPPrzRunning command %s: %szRunning command %sN)r joinitemsr!r7)r:contextdetailss r log_commandrFos=((PP PPPPP6IIIII2G<<<<.sR J JSNN3'' J,/7H,H,H,H,H,H,H J Jrrz&Finished %s in %.3fs with exit code %s) r nextsysr8r!r7time monotonic _STARTED_AT) exit_coder:s r log_finishedrTs G J JCHQRRL J J J    B!4>#3#3k#A9NNNNNrnamec>tjtd|S)a8Logger for library code whose records belong in lvectl.log. lveapi and lvectllib are shared with other entry points (cllimits, lvemanager, the panel cron), so they must not open lvectl.log themselves. A child of the 'lvectl' logger inherits that logger's handler and level while lvectl is the running program, and is an inexpensive no-op under any other caller -- nothing else configures the 'lvectl' logger, and the root logger has no handlers. :param str name: child name, e.g. 'lveapi' :return logging.Logger: logger instance .r)rUs rget_lvectl_child_loggerrXs$   2;;T;; < <rvs= mmmmmmmmL!L6 dn I:;; $#*###=<d <<<gN + + + + +11111 6 6 6 6 6FPPPP==D====,NNNN$ =# ='. = = = = ?RVZ*7U8888Y`Yg88888K         r