SuSE Linux zmd consumes 100% CPU

The recent TOP command of SuSE Linux 10 (SP3) always shows that the zmd process consumes 100% of the CPU resources, while the system-level CPU usage in the system is more than 40% and never released. After the server is restarted, the fault persists. The following describes and processes the problem.

1. The top command shows that zmd CPU usage is 100%, and the system usage is more than 40%.
Top-09:55:10 up 33 days, 4 Users, load average: 1.09, 1.12, 1.06
Task: 217 total, 2 running, 215 sleeping, 0 stopped, 0 zombie
CPU (s): 6.2% us,42.6% SY, 0.0% Ni, 48.5% ID, 1.0% wa, 0.0% hi, 1.6% Si, 0.0% St
Mem: 7527676 k total, 7475372 K used, 52304 K free, 74720 K Buffers
Swap: 2104472 k total, 1246612 K used, 857860 free, 1984724 K cached

PID user PR Ni virt res shr s % CPU % mem time + command
3633 root 34 19 110 m 21 m 9180 S 100 0.3: 822 zmd
22402 Robin 15 0 5656 1216 R 2 792. 01 top

2. zmd description
The ZENworks agent is named zmd. It is sometimes referred to as the ZENworks management daemon (zmd ).

The ZENworks agent performs software management functions on the ZENworks managed device, including updating, installing, and removing software and discovery Ming basic queries of the device's package management database. typically, these management tasks are initiated through the ZENworks control center or the rug utility, which means you shoshould not need to interact directly with the ZENworks agent.

# The main function is to manage devices, update, install and remove software, and query device package management. This ageng does not affect the operation of the entire system.
The ZENworks agent is installed to the following directory:

/Opt/Novell/ZENworks/sbin

For SuSE Linux Enterprise Server 10 (sles 10) and SuSE Linux Enterprise Desktop 10 (SLED 10) devices, the ZENworks agent is located in the following directory:

/Usr/sbin

6.1.1 ZENworks agent (zmd) cache settings
As the ZENworks agent (zmd) performs its duties, it maintains a cache that stores the content of bundles that are downloaded for installation on that managed device. you can control the age of contents in the cache and its size by using cache settings. cache cleanup is enforced on both client startup and refresh.

If the process of downloading the bundle is interrupted on the managed device, the zmd starts the download of individual packages from where it was left off.

The cleaning of cached information is always enabled. you can configure the following Settings Using the rug set command in the rug utility to manage the cache. for more information about the rug utility, see section 4.4, rug.

About zmd link: http://www.novell.com/documentation/zlm72/lm7admin? Page =/documentation/zlm72/lm7admin/data/bxltra0.html

 

3. Disable the zmd Process
Szdb:/usr/sbin # ps-Ef | grep zmd
Root 3265 1 0 may14? 00:00:01 zmd/usr/lib/zmd/zmd.exe
Root 3633 1 99 may14? 13:31:04 zmd/usr/lib/zmd/zmd.exe
Root 21841 20286 0 00:00:00 pts/2 grep zmd

--> Author: Robinson
--> Blog: http://blog.csdn.net/robinson_0612

# Run YaST at the beginning to disable zmd startup. If the execution fails, you have to kill the process and then disable it.
Szdb:/usr/sbin # Kill-9 3633 # Kill the process that occupies 100% CPU
Szdb:/usr/sbin # top again, from below system usage to below 1%

Top-10:27:39 up, 3 users, load average: 0.16, 0.09, 0.29
Task: 226 total, 1 running, 225 sleeping, 0 stopped, 0 zombie
CPU (s): 0.2% us, 0.3% Sy, 0.0% Ni, 99.3% ID, 0.2% wa, 0.0% hi, 0.0% Si, 0.0% St
Mem: 7527676 k total, 7479032 K used, 48644 K free, 75048 K Buffers
Swap: 2104472 k total, 0 K used, 2104472 K free, 6463032 K cached

PID user PR Ni virt res shr s % CPU % mem time + command
3265 root 34 19 100 M 20 m 9124 S 0 0.3. 01 zmd

# Enable YaST to disable Novell-zmd to start
YaST system services (runlevel) Novell-zmd

/Etc/init. d/Novell-zmd stop returned 0 (SUCCESS ):
Shutting down ZENworks management daemon... Done

# If you need to use Novell-zmd later, you can start it.
# After testing, If you enable Novell-zmd again, the above situation will still occur. It is estimated that it is a bug. If you are interested, you can continue to Google.

 

4. More references
Configure raw devices in SuSE Linux 10)
Rename the NIC name in SuSE Linux 10
Ulimit: open files: cannot modify limit: operation not permitted
Linux hugepage features
Configure hugepages in Linux
Job switching and Offline Management in the front and back of Linux