ERROR: Failed building wheel for osgeo
Problem: When Installing pip3 install osgeo report an error: ERROR: Failed building wheel for osgeo
Solution:
Method 1
conda install gdal
Method 2:
1. According to the python version, download the corresponding GDAL installation file
for example: Python 3.8 download GDAL‑3.4.3‑cp38‑cp38‑win_amd64.whl
Cp38 stands for python3.8 version and windows64 bit
2. install:
pip3 install gdal-3.4.3-cp38-cp38-win_amd64.whl
Error: failed building wheel for pycryptodome PIP installation error solution
1. Questions
PIP install pycryptodome build wheel error error error stack display reference OpenSSL error
ERROR: Failed building wheel for pycryptodome
2. Solutions
# ①. install brew
# ②. install openssl@1
# ③ link to openssl
env LDFLAGS="-L$(brew --prefix openssl)/lib" CFLAGS="-I$(brew --prefix openssl)/include"
3. Other collected information
For devices using apple silicon, you can try this (because the default homebrew bin directory is different)
export LDFLAGS="-L/opt/homebrew/opt/[email protected]/lib"
export CPPFLAGS="-I/opt/homebrew/opt/[email protected]/include"
You can enter the view command yourself
brew info openssl
If you want to install an older version of cryptography (such as 2.9.x), you must link [email protected] instead of openssl@3
brew install openssl will prompt you to export
Failed to remove multipath map 320b508ca45022b80
1. Project scenario
Host os:kylin-server-10-sp1-release-build02-20210518-arm64
docker:docker-ce-18.09.7
cloud: openstack queens
storage: same acs5000
VM os: kylin-server-10-sp1-release-build02-20210518-arm64
2. Problem description and cause analysis
2.1 problem description
The volume-based virtual machine can be created normally, but the error after restarting the virtual machine, checking the logs of nova-compute, found that it reports ProcessExecutionError:unexpected error while running command. command: multipah -f 320b508ca45022b80 failed, map in use, failed to remove multipath map 320b508ca45022b80.
I manually executed multipah -f 320b508ca45022b80, and it did report the status of in use, so I suspect that there are processes using the volume, and I found that the same volume group name was activated through lvdisplay, vgdisplay and lsblk, so I suspect that the virtual machine and the physical machine used the same volume group name, and the volume group name was activated after the virtual machine started. The VM has been activated, and the process of reactivating all logical volumes in the volume group failed, resulting in multipath -f failure. Therefore, we need to configure lvm to activate only the logical volumes of the system, check the system volumes by lsblk, and then configure accordingly, edit /etc/lvm/lvm.conf and modify the following content
devices {
filter = [ "a/sda/", "r/.*/" ]
}
allocation {
volume_list = ["klas"]
auto_activation_volume_list = ["klas"]
}
Restart service:
systemctl restart lvm2-lvmetad.service lvm2-lvmetad.socket
Re create the virtual machine and restart it. It is also recommended that the virtual machine adopt other volume group names
2.2 storage configuration
2.2.1 drive
Use the same driver version zeus-driver-3.1.2.000106, copy the driver to the cinder_volume container /usr/lib/python2.7/site-packages/cinder/volume/drivers/ directory and the cinder_backup container /usr/lib/python2.7/site-packages/cinder/backup/drivers/ directory, and restart the related services.
2.2.2 configure cinder volume
vim /etc/kolla/cinder-volume/cinder.conf
[DEFAULT]
enabled_backends=toyou_ssd
[toyou_ssd]
volume_driver = cinder.volume.drivers.zeus.Acs5000_iscsi.Acs5000ISCSIDriver
san_ip = x.x.x.x
use_mutipath_for_image_xfer = True
image_volume_cache_enabled = True
san_login = cliuser
san_password = ******
acs5000_volpool_name = toyou_ssd
acs5000_target = 0
volume_backend_name = toyou_ssd
Restart the cinder-volume service. For others, please refer to the “reference scheme”
3. Solutions
View the adopted system disk through lsblk, and then edit /etc/lvm/lvm.conf to modify the following contents
devices {
filter = [ "a/sda/", "r/.*/" ]
}
allocation {
volume_list = ["klas"]
auto_activation_volume_list = ["klas"]
}
Restart service:
systemctl restart lvm2-lvmetad.service lvm2-lvmetad.socket
Note that it is mainly the filter. The drive letter in the filter is determined by the system disk recognized by lsblk, which may be SDB or nvme, etc
2021-12-31:
The project works fine on Windows, but when it is moved to a Mac system, an error appears!
According to the error message, the initialization of “logback-spring.xml” failed, and the configuration of “Logback” was detected as an error and an illegal exception was declared,
Failed to create a parent directory for “[/apps/logs/sns_error.log]”…
The main reason is that the initialization of the configuration file failed, and then the following error was reported.
First, let’s take a look at the input location of the log file defined in the configuration file, as shown below.
The specific error information is as follows:
Logging system failed to initialize using configuration from ‘classpath:logback/logback-spring.xml’ java.lang.IllegalStateException: Logback configuration error detected: ERROR in ch.qos.logback.core.rolling.RollingFileAppender[ERROR] - Failed to create parent directories for [/apps/logs/sns_error.log] ERROR in ch.qos.logback.core.rolling.RollingFileAppender[ERROR] - openFile(/apps/logs/sns_error.log,true) call failed. java.io.FileNotFoundException: /apps/logs/sns_error.log (No such file or directory) ERROR in ch.qos.logback.core.rolling.RollingFileAppender[WARN] - Failed to create parent directories for [/apps/logs/sns_warn.log] ERROR in ch.qos.logback.core.rolling.RollingFileAppender[WARN] - openFile(/apps/logs/sns_warn.log,true) call failed. java.io.FileNotFoundException: /apps/logs/sns_warn.log (No such file or directory) ERROR in ch.qos.logback.core.rolling.RollingFileAppender[INFO] - Failed to create parent directories for [/apps/logs/sns_info.log] ERROR in ch.qos.logback.core.rolling.RollingFileAppender[INFO] - openFile(/apps/logs/sns_info.log,true) call failed. java.io.FileNotFoundException: /apps/logs/sns_info.log (No such file or directory) ERROR in ch.qos.logback.core.rolling.RollingFileAppender[DEBUG] - Failed to create parent directories for [/apps/logs/sns_debug.log] ERROR in ch.qos.logback.core.rolling.RollingFileAppender[DEBUG] - openFile(/apps/logs/sns_debug.log,true) call failed. java.io.FileNotFoundException: /apps/logs/sns_debug.log (No such file or directory) ERROR in ch.qos.logback.core.rolling.RollingFileAppender[TRACE] - Failed to create parent directories for [/apps/logs/sns_trace.log] ERROR in ch.qos.logback.core.rolling.RollingFileAppender[TRACE] - openFile(/apps/logs/sns_trace.log,true) call failed. java.io.FileNotFoundException: /apps/logs/sns_trace.log (No such file or directory)
Let’s continue with the above
It should be that I don’t know its features very well when I just use Mac, and I don’t know whether it’s caused by different computer environments (I can’t create this directory on MAC)
Follow up: 2021-12-31 PM
Background Note: On Windows my project is in a folder on the D: drive, and today I found the “/apps/logs” directory on the D: drive, just like the path in the configuration below.
When I change the input location of the configuration file to “/apps/logs/sns”, the folder of “SNS” appears on disk D.
As shown in the following figure:
This shows that when the value in this configuration is “relative path”, it will be created in the root directory of the disk where the project is located (for example, if the project is on disk d: then the path is “d:+ relative path”).
Follow up: December 31, 2021
After opening the folder, I found that the following log was created, and then I looked at the error message. It can completely explain the reason for the error: the folder path cannot be created, and then the log file cannot be created, and the log file failed to be opened.
Then reported an error!!
The created log file is shown in the following figure:
The error information is shown in the following figure: 
The solution must start with why the file path is not created on the Mac.
There is no concept of disk partition on Mac. Is it because of this reason that you can’t create a path.
Finally, I found the Solution:
On Mac when I remove the backslash at the top of “/apps/logs/sns” and change it to “apps/logs/sns”, it runs successfully
=====There is no error prompt in ZK here. Look for the logs. There is a logs directory on the upper layer of the bin directory. Check the logs===
Main error log information:
2022-07-28 15:31:50,793 [myid:] - ERROR [main:QuorumPeerMain@98] - Invalid config, exiting abnormally========Solution information========
cd apache-zookeeper-3.6.2-bin/conf/
View the VIM zoo configuration file, view the dataDir directory defined by yourself, and view the ID information of zkServer.
CD to the dataDir directory,
echo “serverid” > myid
Go to the bin directory and start again, sh zkServer.sh start
check ZK application status: sh zkServer.sh status, (if the startup is successful and the status is wrong, you can wait until the cluster machine starts completely).
========================End=====================
When Installing nextcloud+onlyoffice, onlyoffice failed to start and report an error:
enter the container to see the error information of out.log
[root@nextcloud ~]# docker ps -a
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a7c97fb93556 docker.io/onlyoffice/documentserver:latest 30 hours ago Up 30 hours ago 0.0.0.0:8080->80/tcp, 0.0.0.0:9000->443/tcp onlyoffice
[root@nextcloud ~]# docker exec -it a7c97fb93556 /bin/bash
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
root@a7c97fb93556:/# cd /var/log/onlyoffice/documentserver/converter/
root@a7c97fb93556:/var/log/onlyoffice/documentserver/converter# ls
err.log out.log-20220729
root@a7c97fb93556:/var/log/onlyoffice/documentserver/converter#
Disabling Document Server Access Authentication
Next, disable access authentication for Document Server, which by default rejects unauthenticated requests (i.e., self-signed HTTPS requests).
I am now running Document Server with Docker, using the docker exec command to log into the container.
There seems to be only the nano editor in the container, but that’s enough.
Open /etc/onlyoffice/documentserver/default.json, go down and find the rejectUnauthorized field and change its value to false.
Restart the container.
Modify default.json
root@a7c97fb93556:/var/log/onlyoffice/documentserver/converter# cd /etc/onlyoffice/
root@a7c97fb93556:/etc/onlyoffice# ls
documentserver documentserver-example
root@a7c97fb93556:/etc/onlyoffice# cd documentserver
root@a7c97fb93556:/etc/onlyoffice/documentserver# ls
default.json local.json production-linux.json
development-linux.json log4js production-windows.json
development-mac.json logrotate supervisor
development-windows.json nginx
root@a7c97fb93556:/etc/onlyoffice/documentserver# pwd
/etc/onlyoffice/documentserver
root@a7c97fb93556:/etc/onlyoffice/documentserver#
Modify as follows: “rejectunauthorized”: false
"requestDefaults": {
"headers": {
"User-Agent": "Node.js/6.13",
"Connection": "Keep-Alive"
},
"gzip": true,
"rejectUnauthorized": false
},
Restart container
root@a7c97fb93556:/etc/onlyoffice/documentserver# exit
exit
[root@nextcloud ~]# docker stop a7c97fb93556
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: given PIDs did not die within timeout
[root@nextcloud ~]# docker start a7c97fb93556
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: unable to start container "a7c97fb93556650c83dd763f9578705a82f34b2673f9759e8d0ce62afc63e77c": container a7c97fb93556650c83dd763f9578705a82f34b2673f9759e8d0ce62afc63e77c must be in Created or Stopped state to be started: container state improper
[root@nextcloud ~]# reboot
Restart nextcloud
login as: root
[email protected]'s password:
Activate the web console with: systemctl enable --now cockpit.socket
Last login: Fri Jul 29 15:59:59 2022 from 192.168.182.1
[root@nextcloud ~]# setenforce 0
[root@nextcloud ~]# systemctl start https
Failed to start https.service: Unit https.service not found.
[root@nextcloud ~]# systemctl start httpd
Enter TLS private key passphrase for localhost:443 (RSA) : ******
[root@nextcloud ~]# docker ps -a
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a7c97fb93556 docker.io/onlyoffice/documentserver:latest 31 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:9000->443/tcp onlyoffice
[root@nextcloud ~]# docker start a7c97fb93556
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
a7c97fb93556
[root@nextcloud ~]#
Start onlyoffice
run as prompted
[root@nextcloud ~]# sudo docker exec a7c97fb93556 sudo supervisorctl start ds:example
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
sudo: unable to send audit message: Operation not permitted
ds:example: started
Successfully opened word document 
When using HttpPost to call the https interface, report an error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to the requested target,
Here is a solution below:
/**
* HttpClient error: ”SSLPeerUnverifiedException: peer not authenticated”
* You don't need to import SSL
*
* @param base
* @return
*/
public static HttpClient wrapClient(HttpClient base) {
try {
SSLContext ctx = SSLContext.getInstance("TLS");
X509TrustManager tm = new X509TrustManager() {
@Override
public void checkClientTrusted(java.security.cert.X509Certificate[] arg0, String arg1)
throws java.security.cert.CertificateException {
// TODO Auto-generated method stub
}
@Override
public void checkServerTrusted(java.security.cert.X509Certificate[] arg0, String arg1)
throws java.security.cert.CertificateException {
// TODO Auto-generated method stub
}
@Override
public java.security.cert.X509Certificate[] getAcceptedIssuers() {
// TODO Auto-generated method stub
return null;
}
};
ctx.init(null, new TrustManager[]{tm}, null);
SSLConnectionSocketFactory ssf = new SSLConnectionSocketFactory(ctx, NoopHostnameVerifier.INSTANCE);
CloseableHttpClient httpclient = HttpClients.custom().setSSLSocketFactory(ssf).build();
return httpclient;
} catch (Exception ex) {
ex.printStackTrace();
return HttpClients.createDefault();
}
}
Calling wrapclient method to generate httpclient can avoid problems.
@Inject(target = "/infoResourcesManageRest/custom/getAllDataNum", type = InjectTypeExt.CUSTOM_URL)
public synchronized WSResult getAllDataNum(JSONObject json) throws Exception {
Integer talentNum = 0;
Integer companyNum = 0;
Integer organizationNum = 0;
CloseableHttpClient httpClient = HttpClients.createDefault();
httpClient = (CloseableHttpClient) wrapClient(httpClient);
CloseableHttpResponse response = null;
/**
* 1. Little data
* **/
String[] zx = new String[]{"qyjbxx", "dwjbxx"};
for (String s : zx) {
JSONObject jsonObject1 = JSONObject.fromObject("{\n" +
" \"size\": 1,\n" +
" \"page\": 1,\n" +
" \"params\": {\n" +
" \"englishName\": \"" + s + "\"\n" +
" },\n" +
" \"filter\": {}\n" +
"}");
String jsonString = JSON.toJSONString(jsonObject1);
HttpPost httpPost = new HttpPost("https://www.baidu.com");
StringEntity entity = new StringEntity(jsonString, "UTF-8");
httpPost.setEntity(entity);
httpPost.setHeader("Content-Type", "application/json;charset=utf8");
response = httpClient.execute(httpPost);
JSONObject jsonObject = JSONObject.fromObject(EntityUtils.toString(response.getEntity(), "utf-8"));
JSONObject result = (JSONObject) jsonObject.get("result");
if (result != null) {
Integer totalElements = (Integer) result.get("totalElements");
if (s.equals("qyjbxx")) {
companyNum = companyNum + totalElements;
} else if (s.equals("dwjbxx")) {
organizationNum = organizationNum + totalElements;
}
}
}
}In the MAC environment, during the development of HarmonyOS, the project runs to the simulator and reports the following errors:
Failure[INSTALL_PARSE_FAILED_USESDK_ERROR]
compileSdkVersion and releaseType of the app do not match the apiVersion and releaseType on the device.
Operation steps.
I. If the HDC tool environment variables are not configured, configure them as follows, and skip this step if they have been configured.
1. Open Mac terminal and enter the following command to open the bash_profile file.
open .bash_profile
2. In the bash_profile file, configure the environment variables, here the PATH path, refer to your own sdk path, version 3.0.0.1 is the version corresponding to Toolschains under API Version7 in my own SDK, the value is 3.0.0.1.
export PATH=$PATH:/Users/tangkun/Library/HarmonyOS/Sdk/toolchains/{3.0.0.1}
export CLASSPATH
HDC_SERVER_PORT=7035
launchctl setenv HDC_SERVER_PORT $HDC_SERVER_PORT
export HDC_SERVER_PORT
3. Save the configured environment variables and enter the following command in the open terminal.
source .bash_profile
4. Restart the development tool DevEco-Studio.
Second, the following is the operation of configured HDC environment variables:
In the terminal terminal of DevEco-Studio, enter the following command:
. /hdc shell
(Windows environment does not need the previous . /hdc shell)
Next, enter the following command in the terminal, but this time you do not need to enter . /, in terminal my Huawei emulator output 6.
getprop hw_sc.build.os.apiversion
This apiversion version number 6 is smaller than the version number 7 in my project’s build.gradle and project’s build.gradle, so it causes my project to run on this apiversion version 6 emulator with the following direct error.
The version numbers of entry and application in the build.gradle: compileSdkVersion 7 and compatibleSdkVersion 7
Solution:
1. lower the compileSdkVersion and compatibleSdkVersion version numbers in the build.gradle file of entry and application to 6.
2. Use an emulator with Api 7 for debugging.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
> Using insecure protocols with repositories, without explicit opt-in, is unsupported. Switch Maven repository 'maven(http://storage.flutter-io.cn/download.flutter.io)' to redirect to a secure protocol (like HTTPS) or allow insecure protocols. See https://docs.gradle.org/7.4/dsl/org.gradle.api.artifacts.repositories.UrlArtifactRepository.html#org.gradle.api.artifacts.repositories.UrlArtifactRepository:allowInsecureProtocol for more details.
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 50s
Exception: Gradle task assembleDebug failed with exit code 1
Solution:
Although there are many tutorials online, but there is no solution to this solution, the early my attention are in the first sentence, only to know that the original focus is the latter sentence, the main error is in the http and https protocol, Just modify HTTP to HTTPS of the system variable FLUTTER_STORAGE_BASE_URL variable value.
Question:
As shown in the figure, execute brew install redis and report an error: Command failed with exit 128:git
Solution:
After entering brew -v, you will be prompted to execute two configuration commands. It is OK to copy and execute directly!
git config --global --add safe.directory /opt/homebrew/Library/Taps/homebrew/homebrew-cask
Homebrew/homebrew-cask
git config --global --add safe.directory /opt/homebrew/Library/Taps/homebrew/homebrew-core
Homebrew/homebrew-core
See the following figure for details
The following problems were encountered when running Caffe Code:
Problem Description:
E0727 11:22:09.213124 6200 io.cpp:89] Could not open or find file D:/.../
F0727 11:22:09.213124 6200 image_data_layer.cpp:129] Check failed: cv_img.data Could not load D:/.../
*** Check failure stack trace: ***
Solution:
Check the train or test file for the presence of empty lines (usually the last line) and delete them.
After upgrading Android Sdk to 33 recently, packing Android generates the following problems:
AndroidManifest.xml Error: Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details. See http://g.co/androidstudio/manifest-merger for more information about the manifest merger. Execution failed for task ':launcher:processDebugMainManifest'. > Manifest merger failed with multiple errors, see logs
1. Tried to add android:exported as instructed, but the problem remains. So I used the 2nd solution, drop the sdk version.
2. Drop Android sdk version
1. Set the SDK version of Android project as shown in the following figure:
2. After setting, modify the relevant SDK in all build.gradle configuration files in the project to be consistent with the version number configured in the above figure.
compileSdkVersion 30 buildToolsVersion '30.0.2' targetSdkVersion 30