Paramon Cluster Monitoring front-end Installation Problems and usage

Problems encountered when installing the paramon Cluster Monitoring Software on the Ubuntu front-end and the solution software package composer

Problems with installing the paramon Cluster Monitoring Software on the Ubuntu front-end and Their Solutions

Software Pack http://www.paratera.com/paramon/&FrontColumns_navigation01-1399971723306FirstColumnId=3.html

After downloading and decompressing the package, enter sudo dpkg-I paramon. XXX. deb.

• Installation Problems

1. Dynamic library loss occurs after dpkg installs paramon

Error message:

Paramon: error while loading shared libraries: libcrypto. so.0.9.8: cannot open shared object file: No such file or directory

Solution:

Sudo apt-get install libssl0.9.8

2. The dpkg application is occupied

Error message:

E: unable to obtain the lock/var/lib/dpkg/lock-open (11: The resource is temporarily unavailable)
E: The management directory (/var/lib/dpkg/) cannot be locked. Is there any other process occupying it?

Solution:

1. Enter ps-aux on the terminal, list the processes, find the processes containing apt-get, and solve the problem directly by using sudo kill PID.
2. Force unlock -- command:
Sudo rm/var/cache/apt/archives/lock
Sudo rm/var/lib/dpkg/lock

3. The dpkg is interrupted.

Error message:

E: dpkg is interrupted. You must manually run sudo dpkg -- configure-a to solve this problem.

Solution:

Sudo dpkg -- configure-

4. paramon died when the software center was canceled.

Error image: always stop at the page shown in

As a result, all software cannot be installed and the following error occurs:

Www.linuxidc.com@www.linuxidc.com :~ $ Sudo apt-get update
E: unable to obtain the lock/var/lib/apt/lists/lock-open (11: The resource is temporarily unavailable)
E: the directory/var/lib/apt/lists/cannot be locked.

I personally understand that this is the lock mechanism of apt-get. The current resource is being occupied, that is, the apt process is not over yet. There are two solutions to this problem: one is to delete the lock file as above.

 

Another type of apt process is killed.

1. Ps-aux | grep apt-get: locate the apt process number and kill it.
2. Sudo fuser-vki/var/lib/dpkg/lock

Follow the prompts and run the fuser command to check which process is using this folder. The command is "sudo fuser-vki/var/lib/lists/lock ". Sure enough, the apt-get process is using this file and kill the process directly (fuser can display the pid of this process). apt-get can be used normally.

Fuser: displays the ID of the process using the specified file and sockets. The "-k" parameter can kill the process using this file; the "-I" parameter is used to ask the user whether to kill the process before kill the process. The "-v" parameter displays detailed information.

• Usage

Enter paramon on the terminal to go To the GUI and select the. pmon configuration file.

Shows the main features of cluster hardware.

Eight computing nodes, and node 6 goes down

Sudo fuser-vki/var/lib/dpkg/lock

For more information about Ubuntu, see Ubuntu special page http://www.linuxidc.com/topicnews.aspx? Tid = 2

This article permanently updates the link address: Http://www.linuxidc.com/Linux/2015-02/113170.htm