Tag Archives: cents

[Solved] Ubuntu16.4Install vcs2016 Error: mount.vboxsf: mounting failed with the error: Invalid argument

Cause of the problem

VCS 2016 requires gcc4.8 and g++4.8, while VBoxGuestAdditions-6.1 – * * requires version 4.9+ to install (the ‘-fstack-protector-strong compilation option need to be supported).

Solution:

1. Check the version through
ls /usr/bin/gcc*. If not, install the corresponding version;

2. Then use the following command to perform version management
sudo update-alternatives –install /usr/bin/gcc gcc /usr/bin/gcc-5 100

3. Switch the new version of gcc with the following command
sudo update-alternatives –config gcc

4. Reinstall the VBoxGuestAdditions tool
cd /opt/VBoxGuestAdditions-6.1.36/init
sudo vboxadd setup

5. Finally, the problem was solved by re-hanging it in the directory

[Solved] Virtual Machine Centos7 Startup Error: Entering emergency mode

Environment

Start centos7 in VMware 15.5 on win10, and the following error is reported:

entering emergency mode Exit the shell to continue

Cause analysis

According to the CentOS file system fault, the root causes of the fault are:

  • Force shutdown of the virtual machine (skip the system and directly shut down VMWare)
  • Irregular execution of on-hook operations
  • Irregularly execute restart operation

Repair method:

Please enter the following command to repair:

xfs_repair -v -L /dev/sda3

Parameter Description:
– L: use the xfs_repair command to clear the log (even if dirty data is included, this will change the metadata information)

After modification, print the log as follows:

after that, execute reboot, restart centos7, and observe whether it can be started normally.

[Solved] vcpkg Error: Error: Could not detect vcpkg-root.

Phenomenon

When transferring vcpkg from CentOS 8 to CentOS virtual machine through SCP, the above error is always reported when running vcpkg

Root cause

The Linux environment needs to add the system variable $VCPKG_ROOT

Solution:

vim ~/. bash_profile

Add a line:

export VCPKG_ROOT=”/home/devuser1/vcpkg”

Change the directory to your directory

Close the shell, reconnect, and everything is OK

verification

[[email protected] vcpkg]# ./vcpkg list
abseil:x64-linux                                   2021-03-24#1     an open-source collection designed to augment th...
amqpcpp:x64-linux                                  4.3.11           AMQP-CPP is a C++ library for communicating with..

[Solved] Virtual machine Failed to restart network Error: Error:Failed to start LSB: Bring up/down networking

Problem description

A virtual machine that has been running normally. After a shutdown and restart, it is found that SSH cannot connect

Restart network discovery failed

service networkrestart

Solution:

[[email protected] ~]#systemctl stop NetworkManager
[[email protected] ~]#systemctl disable NetworkManager
[[email protected] ~]#systemctl restart  network
or
[[email protected] ~]#systemctl  restart NetworkManager
[[email protected] ~]#systemctl restart  network

Cause of problem

NetworkManager is a program that detects the network and automatically connects to the network.

Whether it’s wireless or wired, it makes it easy for you to manage.

For wireless networks, the network manager can automatically switch to the most reliable wireless network.

The program using the network manager can freely switch between online and offline modes.

The network manager can preferentially select wired network and support VPN.

The network manager was originally developed by RedHat and is now managed by gnome.

[Solved] Compose error “HTTP request took too long to complete“

Recently, I noticed that the following error messages often appear in docker-compose:

ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

Adding COMPOSE_HTTP_TIMEOUT seems to only delay the error. Is this a known issue? Or is there a workaround?
Tried increasing the COMPOSE_HTTP_TIMEOUT environment variable and it didn’t work.

# Increase timeout period to 120 seconds.
export COMPOSE_HTTP_TIMEOUT=120;
# Rebuild all containers using the new images.
docker-compose up -d;

# or use docker-compose --verbose up -d to check out the errors

My Solution:

sudo service docker restart
docker-compose up

Maybe I have a high inode

df -ih			#  -i, --inodes   List information about information nodes, not data block usage
Filesystem     Inodes IUsed IFree IUse% Mounted on
udev             493K   390  492K    1% /dev
tmpfs            494K   537  494K    1% /run
/dev/xvda1       1.3M  1.2M   70K   95% /
tmpfs            494K     1  494K    1% /dev/shm
tmpfs            494K     3  494K    1% /run/lock
tmpfs            494K    16  494K    1% /sys/fs/cgroup
tmpfs            494K     4  494K    1% /run/user/1000

[Solved] Centos7 xmapp Install Error: error while loading shared libraries: libc.so.6

1. Version information:

CentOS version: CentOS release 6.9 (final)

xmapp version: xampp-linux-x64-5.6.40-1-installer.run

2. Error message:

[[email protected] ~]# /opt/lampp/lampp
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

id: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/share/xampp/xampplib: line 11: test: -ne: unary operator expected
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
netstat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
netstat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/httpd: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
netstat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: /bin/sh: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
netstat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

3. Solution:

1. Open /opt/lampp/lampp

vim /opt/lampp/lampp

2. Edit
Modify this line

export LD_ASSUME_KERNEL=2.2.5

to

export LD_ASSUME_KERNEL=2.8.0

Find a word in the file [under the command line/keyword, enter to find, enter n to find the next]

Virtual machine failed to start network service error: ob for network.service failed because the control process exited with error code

About CentOS 7 virtual machine startup network service startup failure: ob for network service failed because the control process exited with error code

As shown in the following figure:

Question:

When using CentOS 7 system, after changing the static IP, it is found that the network service cannot be restarted, and after using the IP addr or ipconfig command, it is found that the changed static IP address is not displayed and mysteriously disappears. The connection to the external network is also different, and the Ping is blocked.

Error reason:

There is a conflict between NetworkManager and Network, there are two network management tools on CentOS system, NetworkManager and Network, if both of them are configured, it will cause a conflict between them. As we usually use Network to configure our virtual machine static ip address, but sometimes our improper operation will cause NetworkManager to configure automatically, so there is a conflict between the two. Possible reasons for this are: we shut down the virtual machine without shutting it down first or we don’t use the poweroff command to shut down the machine.

Solution:

Just turn off the NetworkManager service directly, that is, carry out the following steps:
solution 1:
①, service NetworkManager stop # turn off the NetworkManager service
②, chkconfig NetworkManager off # prohibit startup
③ restart the system

solution 2:
② Choose one of the following commands: (a temporary modification, a permanent modification)
systemctl stop networkmanager # temporarily close the service
systemctl disable networkmanager # permanently close the service
② restart the system

 

[Solved] CentOS Start Neo4j Database Error: Error: A JNI error has occurred, please check your installation and try again

CentOS Start Neo4j Database Error: Error: A JNI error has occurred, please check your installation and try again

This is because when installing neo4j, it comes with:

java-11-openjdk-headless-11.0.15.0.9-2.el7_9.x86_64
java-11-openjdk-11.0.15.0.9-2.el7_9.x86_64

This is caused by a conflict with the version of JDK previously installed on the server

So now you just need to uninstall all JDK versions and reinstall neo4j
check the existing JDK

rpm -qa | grep jdk

Uninstall all jdks (it’s easy to uninstall some files in CUDA, but it doesn’t affect deep learning and GPU training model)

yum -y remove(Uninstall all the packages that appear above)

Reinstall neo4j

sudo yum install neo4j

[Solved] SecureCRT Connect Error: The server has disconnected with an error…..

1. Problem environment
virtual machine: VMware 16
Windows system: Windows 10
linux system: CentOS 7.6
interactive software: SecureCRT 8.7
2. Prompt

3. Solution
click “options”, select “session options”, as shown in the figure below, click “SSH2”, then modify “username”, and click “OK”

4. reconnect

connect successfully

[Solved] Module yaml error: Unexpected key in data: static_context

Problem description

An error occurs when executing the linux command on centos8

[[email protected] ~]# dnf update epel-release
Repository epel is listed more than once in the configuration
Last metadata expiration check: 2:24:16 ago on Mon 25 Apr 2022 07:27:51 AM CST.
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Dependencies resolved.
Nothing to do.
Complete!

Solution:

It can be solved by upgrading libmodulemd (DNF upgrade libmodulemd). The problem can be fixed in libmodulemd-2.13.0-1.fc33.