Nginx重启失败/run/nginx.pid failed (2: No such file or directory)
When deploying the project, an error is reported when restarting the nginx server after configuring the open port configuration
Go to the /run directory and find that there is no nginx.pid file.
Solution: enter etc/nginx/conf/nginx.conf file and modify the location of pid as below:
Fluent error reporting record
1. invalid command [initialize-flow
. Two files are needed to calculate fluent on the cluster, *.jou and *.cas;
In *.jou, you can input and output file information and execute commands
/file/read-case *.cas
/solve/initialize/initialize-flow
/solve/iterate 10000
/file/write-data out.dat
exit
yes
Job script, take LSF as an example *.lsf：
#!/bin/sh
APP_NAME=fluent
NP=12
NP_PER_NODE=12
RUN="fluent 3d -g -i input.jou"
Error 1 after submission:
Solution: Check the format of input.jou file, type: set ff after vim, see whether the file is in dos format or unix format, the problem I encountered on my side was caused by the wrong format, and the calculation was normal after changing to unix format.
Problem description
While Compiling dyn_small_obs_avoidance, catkin_make report an error:
/home/xcs/catkin_ws_dyn/src/dyn_small_obs_avoidance/path_searching/src/kinodynamic_astar.cpp:919:61: error: ‘const class Eigen::ArrayWrapper<const Eigen::CwiseUnaryOp<Eigen::internal::scalar_multiple_op<double>, const Eigen::CwiseBinaryOp<Eigen::internal::scalar_difference_op<double>, const Eigen::Matrix<double, 3, 1>, const Eigen::Matrix<double, 3, 1> > > >’ has no member named ‘floor’
Vector3i idx = ((pt - origin_) * inv_resolution_).array().floor().cast<int>();
^~~~~
/home/xcs/catkin_ws_dyn/src/dyn_small_obs_avoidance/path_searching/src/kinodynamic_astar.cpp:919:74: error: expected primary-expression before ‘int’
Vector3i idx = ((pt - origin_) * inv_resolution_).array().floor().cast<int>();
dyn_small_obs_avoidance/path_searching/CMakeFiles/path_searching.dir/build.make:62: recipe for target 'dyn_small_obs_avoidance/path_searching/CMakeFiles/path_searching.dir/src/kinodynamic_astar.cpp.o' failed
make[2]: *** [dyn_small_obs_avoidance/path_searching/CMakeFiles/path_searching.dir/src/kinodynamic_astar.cpp.o] Error 1
CMakeFiles/Makefile2:1260: recipe for target 'dyn_small_obs_avoidance/path_searching/CMakeFiles/path_searching.dir/all' failed
make[1]: *** [dyn_small_obs_avoidance/path_searching/CMakeFiles/path_searching.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j8 -l8" failed
Cause analysis:
By modifying the location where the error occurs, it is found that the error still exists, and the judgment error has nothing to do with the code itself
referring to other posts, I found that the previously installed version of eigen is eigen3.2.1, which may be too low
try upgrading the eigen version.
Solution:
1. Uninstall the eigen
sudo updatedb
locate eigen3
sudo rm -rf /usr/include/eigen3 /usr/lib/cmake/eigen3 /usr/share/doc/libeigen3-dev /usr/share/pkgconfig/eigen3.pc /var/lib/dpkg/info/libeigen3-dev.list /var/lib/dpkg/info/libeigen3-dev.md5sums
2. Installation dependency
sudo apt-get install libopenblas-dev
sudo apt-get install --no-install-recommends libboost1.58-all-dev
sudo apt-get install libx11-dev
sudo apt-get install libgl1-mesa-dev
sudo apt-get install libglu1-mesa-dev
sudo apt-get install freeglut3-dev
sudo apt-get install doxygen
sudo apt-get install cmake
sudo wget https://nchc.dl.sourceforge.net/project/glew/glew/2.1.0/glew-2.1.0.tgz --no-check-certificate
sudo tar -xzvf glew-2.1.0.tgz
cd glew-2.1.0/
sudo make
sudo make install
sudo ldconfig -v
Some may not be installed. I will ignore them and continue with the following steps.
3. Download eigen3.3.7, and extract it to the home directory
download address: eigen3.3.7
4. Installing eigen3.3.7
mkdir build
cd build
cmake ..
make
sudo make install
sudo ldconfig -v
5. Map the path of eigen3 to the /usr/include path.
sudo cp -r /usr/local/include/eigen3 /usr/include/eigen3
sudo ln -s /usr/include/eigen3/Eigen /usr/include/Eigen
6. Re-enter dyn_small_obs_avoidance workspace catkin_make, compiled successfully.
[ 79%] Building CXX object dyn_small_obs_avoidance/path_planning/CMakeFiles/goal_transform.dir/src/goalpoint_transformer.cpp.o
[ 81%] Building CXX object dyn_small_obs_avoidance/path_planning/CMakeFiles/path_planning_node.dir/src/path_planning.cpp.o
[ 93%] Built target livox_ros_driver_node
[ 95%] Linking CXX executable /home/xcs/catkin_ws_dyn/devel/lib/path_planning/goal_transform
[ 95%] Built target goal_transform
[ 97%] Linking CXX executable /home/xcs/catkin_ws_dyn/devel/lib/path_planning/path_planning_node
[ 97%] Built target path_planning_node
[100%] Linking CXX executable /home/xcs/catkin_ws_dyn/devel/lib/fast_lio/loam_laserMappingUbuntu 18.04 installs gazebo9.0 by default and starts indoor1 of Px4 Launch will report an error:
gzserver: symbol lookup error: /usr/lib/x86_64-linux-gnu/libsdformat.so.4: undefined symbol: _ZN8igniti
The reason is that the version of gazebo 9.0 is too low and needs to be upgraded to 9.13, 9.14 or 9.15 (I can use it when upgrading to 9.19) Upgrade method:
1 Uninstall the original gazebo
sudo apt-get remove gazebo*
sudo apt-get remove libgazebo*
sudo apt-get remove ros-melodic-gazebo* #kinetic noetic Corresponding changes
2 Set up the computer to accept software from package.osrfoundation.org
sudo sh -c 'echo "deb http://packages.osrfoundation.org/gazebo/ubuntu-stable `lsb_release -cs` main" > /etc/apt/sources.list.d/gazebo-stable.list'
cat /etc/apt/sources.list.d/gazebo-stable.list
#If deb http://packages.osrfoundation.org/gazebo/ubuntu-stable xenial main appears, it means no problem
xenial should be 20.04 18.04 for bio
3 Set the key
wget https://packages.osrfoundation.org/gazebo.key -O - | sudo apt-key add -
sudo apt-get update
4 Install gazebo9.1 command.
sudo apt-get install gazebo9=9.1*
//If after executing the commands sudo apt install ros-melodic-gazebo9-* sudo apt install ros-melodic-gazebo-*, gazebo starts with an error like symbol (e.g. gzserver: symbol lookup error: /usr/lib/x86_64-linux-gnu/libsdformat.so.4: undefined symbol: _ZN8igniti). You can solve this problem by running sudo apt upgrade libignition-math2 first
5 sudo apt upgrade libignition-math2
If you type gazebo in the terminal after installation, Gazebo will open and the installation will be successful.
6 Gazebo itself is independent of ROS, so you need to install the Gazebo plugin for ROS
sudo apt install ros-melodic-gazebo9-*
sudo apt install ros-melodic-gazebo-*Error Messages:
Internal error XFS_WANT_CORRUPTED_GOTO at line 1635 of file fs/xfs/libxfs/xfs_alloc.c. Caller xfs_free_extent Internal error xfs_trans_cancel at line 990 of flie fs/xfs/xfs_trans.c. xfs_repair: /dev/mapper/cl-root contains a mounted filesystem xfs_repair: /dev/mapper/cl-root contains a mounted writable filesystem fatal error – couldn’t initialize XFS library
Reason description:
I found that most of the solutions found on the Internet do not explain why, so we don’t know why, but just follow them. Some people may actually solve the problem of the partition of the system directory mount, while some people can’t solve the problem because it’s not the directory of the system mount.
The above error is mainly due to the problem of the file in the disk partition, so it needs to be repaired. But please check which partition of the attached directory has a problem first, and then repair the corresponding disk partition.
Solution:
1. First, after reporting the following errors, please check the information in the red box
You can see that you are asked to enter the root password, and then press enter to see that you have entered the root user, and you can enter the command
First, enter the following command first. df is to view the partition of the mounted directory, and cat /etc/fstab is to view the directory information of the previously persistent mounted partition. It can be seen (in the red box) that the directory attached to /book is gone, so it can be inferred that the partition /dev/sdb1 has a problem and needs to be repaired.
df -h
cat /etc/fstab
2. Next, you can repair it. Use the following command to repair it. If you do not add the L parameter, the following error will be reported:
Function of L parameter:
Add the L parameter to complete the execution
xfs_repair -L /dev/sdb1
Finally, restart with the following command to solve the problem
init 6
Note: if you repair some partitions that are not damaged, the following error will be reported, so be sure to find the damaged partition that you need to repair, and then go to XFS_ repair
[ERROR SystemVerification]: failed to parse kernel config: unable to load kernel module: “configs“
[error systemverification]: failed to parse kernel config: unable to load kernel module: “configs”.
When installing kubernetes cluster, the above error is reported.
Solution:
Method 1: ignore the error
Add the –ignore-preflight-errors=SystemVerification option to ignore the error. It is not possible to tell if other problems will occur subsequently with this option.
Method 2: Upgrade kernel version
I installed the kubernetes cluster using kernel version 4.19.12, and the problem did not occur after upgrading the kernel to 5.13.7. I am not sure if it is a kernel version problem.
Method 3:
Manually compile the config kernel module
Description
When using git clone to clone an item on GitHub or gitee, the following error is reported:
error setting certificate verify locations:
CAfile: E:/Git/mingw64/ssl/certs/ca-bundle. crt
CApath: none
analysis
According to the error prompt, there is an error in setting the certificate verification location, that is, the certificate file path is wrong.
When cloning a remote project, the security certificate will be verified first. If the local security certificate file cannot be found, an error will be reported.
This is why this error will not be reported when cloning projects on gitlab, because gitlab is generally built on the intranet and does not need to verify the security certificate.
Path errors often occur because the local Git is installed green, that is, it is directly extracted and used.
In this way, the path of the certificate file is still the path on the original machine. If the path of the new machine is inconsistent, the path error will be caused.
Solution:
For the above analysis, there are two solutions:
Turning off certificate verification may cause security problems. It is recommended to modify the certificate file path.
Modify certificate file path
There are two ways:
The essence of these two methods is to modify the configuration file. However, some misoperations may occur when modifying the file, and the operation is more cumbersome. It is recommended to execute the configuration command.
Execute configuration command
git config --system http.sslcainfo "Git安装路径/mingw64/ssl/certs/ca-bundle.crt"Modify profile
Git’s system configuration files are located at: git installation path \etc\gitconfig
Modify the path in the file as shown in the figure to git installation path /mingw64/ssl/certs/ca-bundle.crt save again.
Turn off certificate verification
git config --system http.sslverify falseThis method may cause git security problems and is not recommended.
[root@k8s-master01 ~]# kubeadm init --config=kubeadm-config.yaml --experimental-upload-certs | tee kubeadm-init.log Flag --experimental-upload-certs has been deprecated, use --upload-certs instead [init] Using Kubernetes version: v1.15.1 [preflight] Running pre-flight checks [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.11. Latest validated version: 18.09 error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR Port-6443]: Port 6443 is in use [ERROR Port-10251]: Port 10251 is in use [ERROR Port-10252]: Port 10252 is in use [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists [ERROR Port-10250]: Port 10250 is in use [ERROR Port-2379]: Port 2379 is in use [ERROR Port-2380]: Port 2380 is in use [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
Compilation error:
/home/service/rpc/goya-rpc/src/rpc_server_impl.cc: In member function ‘void goya::rpc::RpcServerImpl::OnCallbackDone(google::protobuf::Message*, boost::shared_ptr<boost::asio::basic_stream_socket<boost::asio::ip::tcp> >)’:
/home/service/rpc/goya-rpc/src/rpc_server_impl.cc:101:44: warning: ‘int google::protobuf::MessageLite::ByteSize() const’ is deprecated (declared at /home/service/rpc/goya-rpc/thirdparty/install/include/google/protobuf/message_lite.h:430): Please use ByteSizeLong() instead [-Wdeprecated-declarations]
int serialized_size = resp_msg->ByteSize();
^
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
make[2]: *** [src/CMakeFiles/goya-rpc.dir/rpc_server_impl.cc.o] Error 4
make[1]: *** [src/CMakeFiles/goya-rpc.dir/all] Error 2
make: *** [all] Error 2The reason for the error is that the compiling machine is running out of memory, and a large number of template extensions need enough memory.
#View linux memory usage by.
1.ps aux --sort -rss
2.free -m
3.top Press [shift + M keys] to arrange them in reverse order
4.cat /proc/meminfo
Solution:
You can solve this problem by temporarily using swap partitions:
=[step 1: operate as follows]=========================================
Sudo DD if=/dev/zero of=/swapfile bs=64m count=16
\count is the size of the increased swap space. 64M is the block size, so the space size is bs*count=1024mb
sudo mkswap /swapfile \=[step 2: close release] ==================================================================================
Sudo swapoff /swapfile
sudo RM /swapfile
then continue to perform your relevant operations…Note: if you still prompt “g++: internal compiler error: killed (program cc1plus)” after creating the temporary space, it may be because the allocated space is not large enough. You can continue to allocate more space.
Grafana failed to start, and the configuration file parsing reported an error:
lvl=crit msg="failed to parse \"/etc/grafana/grafana.ini\":
open /etc/grafana/grafana.ini: no such file or directory"
The grafana.ini file is not loading properly for the following two reasons.
1, there is no grafana.ini on the host itself.
If at this point it is docker-based boot and -v goes to mount it, the result is definitely still not there.
2, -v is not used correctly, there is grafana.ini on the host, but the file is not mapped into the container
spack install failed with bootstrapping
An error occurs when spack is used for the first time,
[tools_adm@computing-host-001 ~]$ spack install python
==> Bootstrapping clingo from pre-built binaries
==> Bootstrapping clingo from sources
==> Error: cannot bootstrap the "clingo" Python module from spec "clingo-bootstrap@spack+python %gcc target=x86_64" due to the following failures:
'spack-install' raised ConflictsInSpecError: Conflicts in concretized spec "clingo-bootstrap@spack%[email protected]~docs~ipo+python~static_libstdcpp build_type=Release arch=linux-centos7-x86_64/6hb2rkn"
List of matching conflicts for spec:
clingo-bootstrap@spack%[email protected]~docs~ipo+python~static_libstdcpp build_type=Release arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected] libs=shared,static arch=linux-centos7-x86_64
^[email protected]%[email protected]+sigsegv patches=9dc5fbd0d5cb1037ab1e6d0ecc74a30df218d0a94bdd5a02759a97f62daca573,bfdffa7c2eb01021d5849b36972c069693654ad826c1a20b53534009a4ec7a89 arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected]+cpanm+shared+threads arch=linux-centos7-x86_64
^[email protected]%[email protected]+cxx~docs+stl patches=b231fcc4d5cff05e5c3a4814f6a5af0e9a966428dc2176540d2c05aff41de522 arch=linux-centos7-x86_64
^[email protected]%[email protected]~debug~pic+shared arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected]~symlinks+termlib abi=none arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected]+optimize+pic+shared arch=linux-centos7-x86_64
^[email protected]%[email protected]~doc+ncurses+openssl+ownlibs~qt build_type=Release arch=linux-centos7-x86_64
^[email protected]%[email protected]~docs certs=system arch=linux-centos7-x86_64
^[email protected]%[email protected]+bz2+ctypes+dbm~debug+libxml2+lzma~nis~optimizations+pic+pyexpat+pythoncmd+readline+shared+sqlite3+ssl~tix~tkinter~ucs4+uuid+zlib arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
1. "%gcc@:5" conflicts with "clingo-bootstrap" [C++14 support is required to bootstrap clingo]
Please run `spack -d spec zlib` for more verbose error messages
[tools_adm@computing-host-001 ~]$ spack install python
==> Bootstrapping clingo from pre-built binaries
==> Bootstrapping clingo from sources
==> Error: cannot bootstrap the "clingo" Python module from spec "clingo-bootstrap@spack+python %gcc target=x86_64" due to the following failures:
'spack-install' raised ConflictsInSpecError: Conflicts in concretized spec "clingo-bootstrap@spack%[email protected]~docs~ipo+python~static_libstdcpp build_type=Release arch=linux-centos7-x86_64/6hb2rkn"
List of matching conflicts for spec:
clingo-bootstrap@spack%[email protected]~docs~ipo+python~static_libstdcpp build_type=Release arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected] libs=shared,static arch=linux-centos7-x86_64
^[email protected]%[email protected]+sigsegv patches=9dc5fbd0d5cb1037ab1e6d0ecc74a30df218d0a94bdd5a02759a97f62daca573,bfdffa7c2eb01021d5849b36972c069693654ad826c1a20b53534009a4ec7a89 arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected]+cpanm+shared+threads arch=linux-centos7-x86_64
^[email protected]%[email protected]+cxx~docs+stl patches=b231fcc4d5cff05e5c3a4814f6a5af0e9a966428dc2176540d2c05aff41de522 arch=linux-centos7-x86_64
^[email protected]%[email protected]~debug~pic+shared arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected]~symlinks+termlib abi=none arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
^[email protected]%[email protected]+optimize+pic+shared arch=linux-centos7-x86_64
^[email protected]%[email protected]~doc+ncurses+openssl+ownlibs~qt build_type=Release arch=linux-centos7-x86_64
^[email protected]%[email protected]~docs certs=system arch=linux-centos7-x86_64
^[email protected]%[email protected]+bz2+ctypes+dbm~debug+libxml2+lzma~nis~optimizations+pic+pyexpat+pythoncmd+readline+shared+sqlite3+ssl~tix~tkinter~ucs4+uuid+zlib arch=linux-centos7-x86_64
^[email protected]%[email protected] arch=linux-centos7-x86_64
1. "%gcc@:5" conflicts with "clingo-bootstrap" [C++14 support is required to bootstrap clingo]
Please run `spack -d spec zlib` for more verbose error messages
According to the error message, I need a compiler that supports C++14. I installed a new version of gcc/11.2.0 and added its bin directory to the PATH variable.
[tools_adm@computing-host-001 ~]$ setenv PATH /tools/oss/gcc/11.2.0/bin:$PATH
[tools_adm@computing-host-001 ~]$ spack -d spec zlib %[email protected]
==> [2022-05-24-10:03:13.206293] Imported spec from built-in commands
==> [2022-05-24-10:03:13.211112] Imported spec from built-in commands
Input spec
--------------------------------
zlib%[email protected]
Concretized
--------------------------------
==> [2022-05-24-10:03:13.222579] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/config.yaml
==> [2022-05-24-10:03:13.298617] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/bootstrap.yaml
==> [2022-05-24-10:03:13.333346] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/config.yaml
==> [2022-05-24-10:03:13.387447] DATABASE LOCK TIMEOUT: 3s
==> [2022-05-24-10:03:13.387643] PACKAGE LOCK TIMEOUT: No timeout
==> [2022-05-24-10:03:13.388771] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/bootstrap.yaml
==> [2022-05-24-10:03:13.412265] DATABASE LOCK TIMEOUT: 3s
==> [2022-05-24-10:03:13.412528] PACKAGE LOCK TIMEOUT: No timeout
==> [2022-05-24-10:03:13.412772] [BOOTSTRAP CONFIG SCOPE] name=_builtin
==> [2022-05-24-10:03:13.413841] [BOOTSTRAP CONFIG SCOPE] name=defaults, path=/tools/oss/spack-0.17.2/etc/spack/defaults
==> [2022-05-24-10:03:13.413961] [BOOTSTRAP CONFIG SCOPE] name=defaults/linux, path=/tools/oss/spack-0.17.2/etc/spack/defaults/linux
==> [2022-05-24-10:03:13.414080] [BOOTSTRAP CONFIG SCOPE] name=bootstrap, path=/home/tools_adm/.spack/bootstrap/config
==> [2022-05-24-10:03:13.414180] [BOOTSTRAP CONFIG SCOPE] name=bootstrap/linux, path=/home/tools_adm/.spack/bootstrap/config/linux
==> [2022-05-24-10:03:13.416454] Reading config file /home/tools_adm/.spack/bootstrap/config/linux/compilers.yaml
==> [2022-05-24-10:03:13.504704] [BOOTSTRAP ROOT SPEC] clingo-bootstrap@spack+python %gcc target=x86_64
==> [2022-05-24-10:03:13.504904] [BOOTSTRAP MODULE clingo] Try importing from Python
==> [2022-05-24-10:03:13.505664] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/bootstrap.yaml
==> [2022-05-24-10:03:13.533487] Bootstrapping clingo from pre-built binaries
==> [2022-05-24-10:03:13.539614] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/config.yaml
==> [2022-05-24-10:03:13.602270] DATABASE LOCK TIMEOUT: 3s
==> [2022-05-24-10:03:13.602520] PACKAGE LOCK TIMEOUT: No timeout
==> [2022-05-24-10:03:13.656899] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/mirrors.yaml
==> [2022-05-24-10:03:14.404023] Cached index for https://mirror.spack.io/bootstrap/github-actions/v0.1 already up to date
==> [2022-05-24-10:03:14.477810] Imported buildcache from built-in commands
==> [2022-05-24-10:03:14.502955] Imported buildcache from built-in commands
==> [2022-05-24-10:05:40.274042] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/config.yaml
==> [2022-05-24-10:05:40.351266] Reading config file /home/tools_adm/.spack/bootstrap/config/linux/config.yaml
==> [2022-05-24-10:05:40.627291] [BOOTSTRAP MODULE clingo] The installed spec "clingo-bootstrap@spack+python %gcc target=x86_64 ^[email protected] /vcipwnf57slgoo7busvvkzjkk7vydeb5" provides the "clingo" Python module
==> [2022-05-24-10:05:40.691909] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/repos.yaml
==> [2022-05-24-10:05:40.876049] Reading config file /home/tools_adm/.spack/linux/compilers.yaml
==> [2022-05-24-10:05:40.914061] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/config.yaml
==> [2022-05-24-10:05:40.969529] Reading config file /tools/oss/spack-0.17.2/etc/spack/defaults/packages.yaml
==> [2022-05-24-10:05:41.244816] build(zlib)
[email protected]%[email protected]+optimize+pic+shared arch=linux-centos7-sandybridge
Problem-solving.
Done.
Modify prometheus.yml file and failed to start:
1. Configuring prometheus + node_exporter monitoring, the solution to the failure to start after modifying the prometheus.yml file.
2. Error message 1: err=”opening storage failed: lock DB directory: resource temporarily unavailable”
Solution: Check whether the current directory has generated files plus data/lock, need to delete the lock file: rm -rf lock
Delete and restart again
error message 2:err= “error starting web server: listen TCP 0.0.0:9090: bind: address ready in use”
installation command: yum install lsof -y
view command: lsof -i:9090
end command: kill -9 2878
restart command: ./prometheus
restart succeeded after operation 