Auto restart Windows service using zabbix

In the event that a critical application service stops unexpectedly or fails to start up for unknown reasons or your web server fails to respond and you are no where near your system, you can setup zabbix to proactively restart such services.
For the purpose of this post, I will configure zabbix to restart ‘Active Directory Domain Service‘ when service goes down.
- Log onto zabbix → click on Configuration/Actions → click Create action (top right corner) → Enter Action name and leave rest as default


- Click on Conditions tab → Leave condition label (A) → remove any other conditions and add a new Trigger condition (new condition would be ‘Trigger = <click select and select the trigger created for NTDS>) → click Add to add the new condition


- Click on Operations tab → Operation type is ‘Remote command’ → Enter new Target as ‘Current host’ → Type equals ‘Custom script’ → Execute equals ‘Zabbix agent’ → Command enter ‘cmd /c “net start “NTDS”‘ → click Add to add the new reactive action → save the configuration



- To test this, simply stop the ‘Active Directory Domain Service‘ → Wait for few seconds and check if service had restarted → To confirm this test, below is the log in the agent log file:


1600:20130723:153732.396 Processing request. 1600:20130723:153732.411 Requested [system.run["cmd /c \"net start \"NTDS\"","nowait"]] 1600:20130723:153732.411 Executing command 'cmd /c "net start "NTDS"' 1600:20130723:153732.411 zbx_execute_nowait(): executing [cmd /C "cmd /c "net start "NTDS""] 1600:20130723:153732.411 Sending back [1]

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

CLEANING UP THE ZABBIX DATABASE

My Zabbix database size increased a lot in the last few months and since my disk was running out space, I decided to clean up the old events from the database. Looking at the database tables, the biggest one was  history_uint , which holds the items history data – over 400 millions of records and over 30 Gb of disk space before the clean up. Since deleting the old records from this table directly would be a very slow process, I decided to create a new table and insert the latest records from the  history_uint  table and then just replace the old table with a new one. Since this is not an offical procedure, use it at your own risk. Environment: Zabbix v2.2 MySql 5.1 – InnoDB with  innodb_file_per_table=ON Step 1 – Stop the Zabbix server Step 2 – Open your favourite MySQL client and create a new table CREATE TABLE  history_uint_new  LIKE  history_uint; Step 3 – Insert the latest records from the  history_uint  table to the...
Đọc thêm

Configuring DHCP Relay service on the FortiGate unit

Configuring DHCP Relay service on the FortiGate unit If the clients are configured to obtain a IP address using DHCP relay, configure the FortiGate server as below: To configure DHCP relay on the FortiGate unit   1. Go to System > Network > Interfaces and select Interface want to configure DHCP relay.   2. Enable DHCP Server in the interface and choose Advanced   3. For Mode, select Relay.   4. In Type select Regular.   5. Select OK.   6. If a router is installed between the FortiGate unit and the DHCP server, define a static route to the DHCP server. Note : Sometimes it is required to specify more than one DHCP relay IP, to allow for the coverage of additional LAN subnets. Although the Web Based Manager (GUI) does not provide an option to configure this, it is possible to set up to 8 IPs from the CLI.       config system interface             edit <REQUIRED_INTERFACE_HERE>   ...
Đọc thêm

[Resolved] Amazon EC2 Redhat 7 using 6GB for the root space

Hình ảnh
I create new server with 10GB of HDD, but when i check on the command line, the root space only show 6GB. I'm using t2.micto and Redhat 7.0, disk type: XFS. - xvda1: boot partition - xvda2: root partition Fix Step: We have instance A with the volume VA. 1) Stop the current instace A 2) Snapshot the current volume VA of the instance A 3) Start the instance A 4) Create new volume with 25GB by using the snapshot of volume VA then we have new volume VB 5) Attach the new volume VB to the instance A as default (/dev/sdf) 6) From the ssh console, i use the lsblk command to list the disk. # lsblk 7) Using the xfs_repair to repair the /dev/xvdf2 ( yum install xfsprogs) # xfs_repair /dev/xvdf2 8) Continue as the image below 9) Remove the /dev/xvdf2, remember the start of this disk then we will create the new one with the same. 10) Using XFS command to repair the /dev/xvdf2 again. # xfs_repair /dev/xvdf2 11) Use the lsblk co...
Đọc thêm