Why can’t 80% of code farmers be architects?> > >
Dell server hardware monitoring software OpenManager, can monitor the battery, motherboard, temperature, hard disk, and so on. See installation usage
While monitoring OpenManage(OMSA) for Dell Server installation, you may encounter the following error message: Info:Memory Module 6 [DIMM7, 2048 MB] Needs attention: single-bit warning error rate Exceeded, Single-bit Failure Error rate Exceeded. Need to shut down and replug the memory bar. Due to the need to shut down service shutdown, will affect the business. But the problem will always be reported. Everyone would be upset if they got an alarm. Memory monitoring can be shielded as follows:

check_openmanage --check storage -b dimm=all

can see that the memory and Voltage are not tested. Memory will be detected without dimm=all.
is able to block the detection of relevant hardware. Such as temperature detection and so on. Such as:

/usr/local/nagios/libexec/check_openmanage --check storage -b ctrl_fw=all/ctrl_driver=all/ctrl_stdr=all/bat_charge=all/encl=all/ps=all/fan=all/temp=all/volt=all

Please quote from
Dimensional time: http://www.ttlsa.com/html/3880.html

Reproduced in: https://my.oschina.net/766/blog/211381

First, the MAC operating system is 10

When other computers SSH into a MAC server, sometimes they can log in, and the display shows no route to host
Jenkins installed on the MAC was also accessed through the browser, but the response was slow. After the following modifications, it could be used normally.
 
1. System preference setting & GT; > Sharing & gt; > Check file sharing, log in, remote management

 
It is also possible that the computer is in sleep state, so cut off the network, the following configuration, so that the computer does not go to sleep even if the monitor is turned off.
2. System preference setting & GT; > Energy-saving & gt; > When the monitor is turned off, prevent the computer from falling asleep automatically

3. Desktop and Protector & GT; > Screen saver & GT; > Idle options before starting [never]

With reference to
https://jingyan.baidu.com/article/ae97a64606acfabbfd461d9d.html
 
 
 
 
 
 
 
 
 

Reproduced in: https://www.cnblogs.com/kaerxifa/p/11382652.html

swap partition closes

is ready to adjust the utilization of the swap partition under Linux.

executing swapoff-a-v under Linux reports the following error:

swapoff: /dev/mapper/cryptswap1: swapoff failed: Cannot allocate memory

error cause analysis:

can be seen from the above information, the current Linux/dev/mapper/cryptswap1 this device as a swap partition, if the current swap partition instead of the current remaining capacity is greater than the system memory, will quote this mistake, because at the time of closing swap partition, all need to partition data written to the memory, if the memory capacity is insufficient, will cause the error.

resolved:

method 1: free memory cache

# sync ; echo 3 > /proc/sys/vm/drop_caches  #先把内存数据回写到磁盘，然后释放内存缓存

drop_caches accepted parameters are 1, 2, 3, empting pagecache, slab object, pagecahce, and slab object

, respectively

parameters explanation to this file can be found from https://github.com/torvalds/linux/blob/master/Documentation/sysctl/vm.txt:

drop_caches

Writing to this will cause the kernel to drop clean caches, as well as
reclaimable slab objects like dentries and inodes.  Once dropped, their
memory becomes free.

To free pagecache:
    echo 1 > /proc/sys/vm/drop_caches
To free reclaimable slab objects (includes dentries and inodes):
    echo 2 > /proc/sys/vm/drop_caches
To free slab objects and pagecache:
    echo 3 > /proc/sys/vm/drop_caches

dirty state memory cache will not be freed. To free as much memory cache as possible, first execute the command sync to reduce memory cache in the dirty state. If disable, the input parameter 4, note that 0 is not acceptable:

the above method may not work if you use too much swap partition.

method 2: allows memory overcommit

overcommit_memory controls “when user space requests memory, overcommit and approve:

When this flag is 0, the kernel attempts to estimate the amount
of free memory left when userspace requests more memory.

When this flag is 1, the kernel pretends there is always enough
memory until it actually runs out.

When this flag is 2, the kernel uses a "never overcommit"
policy that attempts to prevent any overcommit of memory.
Note that user_reserve_kbytes affects this policy.

2 means overcommit is not allowed. At this point, if swap is stopped, the available memory is reduced and the user space memory request may trigger overcommit to be rejected.

Reference

https://www.lijiaocn.com/%E9%97%AE%E9%A2%98/2019/02/27/linux-swap-off-fail.html

reproduced in: https://www.cnblogs.com/yjt1993/p/11163679.html

Veeam backup virtual machine error: Failed to create NFC download stream.

log is:

2017/8/13 22:06:15 :: Processing 10.1_ad02 Error: DiskLib Error: [11].

Failed to create NFC download stream. The NFC path: [NFC:// conn: 192.168.10.12 nfchost: ha – host, STG: 5942 [email protected]_ad02/10.112 _AD02. VMX].

root cause analysis: https://www.veeam.com/kb1198

1, port problems, Telnet host 902 port can be excluded;

2. Access problem, re-verify the root account when adding the host;

3. Physical host setup problem, check DNS;

final problem:

added by physical host, named Chinese caused, changed because English character backup copy is normal

reproduced in: https://blog.51cto.com/aragoon/2398864