File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/beacons/__pycache__/service.cpython-310.pyc
Back
o ;j� � @ sJ d Z ddlZddlZddlZddlZe�e�Zi Z dZ dd� Z dd� Z dS )z% Send events covering service status � N�servicec C sd t | t�sdS tjj�| �} d| vrdS t | d t�s dS | d D ]}t | d | t�s/ dS q!dS )z+ Validate the beacon configuration )Fz0Configuration for service beacon must be a list.�services)Fz3Configuration for service beacon requires services.)FzDServices configuration item for service beacon must be a dictionary.)Fz@Configuration for service beacon must be a list of dictionaries.)TzValid beacon configuration)� isinstance�list�salt�utils�beacons� list_to_dict�dict)�configZ config_item� r �H/opt/saltstack/salt/lib/python3.10/site-packages/salt/beacons/service.py�validate s �r c C s� g }t jj�| �} | �di �D ]�}i }| d | }dtd |�i||< ||d< ||d< t�� }|s3i }d|vr;d|d< d|vrCd |d< d |vrKd|d < d |vrSd |d < d |v ro|| d so|d }tj� |�rid nd|| d < d |v r�|d d u r�|t vr�|| t |< |d s�q|d d kr�|t | d< n|� |� t | d || d kr�|| t |< |d d kr�|t | d< n|� |� dt | v r�t t |t | d ��}||d kr�t | d= |� |� q|� |� q|S )as Scan for the configured services and fire events Example Config .. code-block:: yaml beacons: service: - services: salt-master: {} mysql: {} The config above sets up beacons to check for the salt-master and mysql services. The config also supports two other parameters for each service: `onchangeonly`: when `onchangeonly` is True the beacon will fire events only when the service status changes. Otherwise, it will fire an event at each beacon interval. The default is False. `delay`: when `delay` is greater than 0 the beacon will fire events only after the service status changes, and the delay (in seconds) has passed. Applicable only when `onchangeonly` is True. The default is 0. `emitatstartup`: when `emitatstartup` is False the beacon will not fire event when the minion is reload. Applicable only when `onchangeonly` is True. The default is True. `uncleanshutdown`: If `uncleanshutdown` is present it should point to the location of a pid file for the service. Most services will not clean up this pid file if they are shutdown uncleanly (e.g. via `kill -9`) or if they are terminated through a crash such as a segmentation fault. If the file is present, then the beacon will add `uncleanshutdown: True` to the event. If not present, the field will be False. The field is only added when the service is NOT running. Omitting the configuration variable altogether will turn this feature off. Please note that some init systems can remove the pid file if the service registers as crashed. One such example is nginx on CentOS 7, where the service unit removes the pid file when the service shuts down (IE: the pid file is observed as removed when kill -9 is sent to the nginx master process). The 'uncleanshutdown' option might not be of much use there, unless the unit file is modified. Here is an example that will fire an event 30 seconds after the state of nginx changes and report an uncleanshutdown. This example is for Arch, which places nginx's pid file in `/run`. .. code-block:: yaml beacons: service: - services: nginx: onchangeonly: True delay: 30 uncleanshutdown: /run/nginx.pid r Zrunningzservice.statusZ service_name�tagZoncleanshutdownFZ emitatstartupTZ onchangeonly�delayr Zuncleanshutdown�time)r r r r �getZ__salt__r �os�path�exists� LAST_STATUS�append�int�round)r �retr Zret_dictZservice_configZcurrtime�filenameZ elapsedtimer r r �beacon0 sX = � � r ) �__doc__�loggingr r Zsalt.utils.beaconsr � getLogger�__name__�logr Z__virtualname__r r r r r r �<module> s
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings