Tag Archives: linux

tar: Error opening archive: Failed to open ‘/Users/xxx/Library/Caches/Homebrew/downloads/348a16e

When installing brew install graphviz, there was a problem with:
tar: Error opening archive: Failed to open ‘/Users/xxx/Library/Caches/Homebrew/downloads/348a16e5fedb24cb14fe4fd5c72caa96074c7b4e21ce4d2f7a89eb4b638c830f–gd-2.3.2.arm64_big_sur.bottle.tar.gz’
Error: Failure while executing; tar --extract --no-same-owner --file /Users/xxx/Library/Caches/Homebrew/downloads/348a16e5fedb24cb14fe4fd5c72caa96074c7b4e21ce4d2f7a89eb4b638c830f--gd-2.3.2.arm64_big_sur.bottle.tar.gz --directory /private/tmp/d20210927-26485-nzi2qo exited with 1. Here’s the output:
tar: Error opening archive: Failed to open ‘/Users/xxx/Library/Caches/Homebrew/downloads/348a16e5fedb24cb14fe4fd5c72caa96074c7b4e21ce4d2f7a89eb4b638c830f–gd-2.3.2.arm64_big_sur.bottle.tar.gz

A closer look reveals that there was a problem installing the dependency at this step: the

So, the solution: install the dependency brew install gd separately

Once done, just install graphviz again, and if the same type of error occurs again during this process, continue installing the dependency where the error occurred.

[Solved] os.py“, line 725, in __getitem__ raise KeyError(key) from None KeyError: ‘PATH‘

os.py”, line 725, in getitem raise KeyError(key) from None KeyError: ‘PATH’

scenario: when I was working on the project, I encountered a problem. Everything was running normally on the Linux server, but there was a problem when I was running in the remote finalshell (the code behind the process actually ran), but it seemed that there was a problem with the environment.

Solution process:

when I instantiated a class, I was a little puzzled by this problem. When I began to find out about os.environ [“path”], I knew that Python did not load the environment (here I used the virtual environment instead of the system default Python). So I went into the virtual environment to execute this: 

import os
print(os.environ["PATH"])

It is found that there is a value here, but the bug reported is none. Therefore, at the beginning of the code, I add the value printed out just now to the code, and then I can continue to execute Python code in the virtual environment of the server on the remote shell

import os
os.environ["PATH"] = "This string copies the value printed from the above code"

So far, everything can run normally

[Solved] Git Clone Error: “error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length …

1. When git pull is used for several large projects recently, the following errors always appear: </ font>

error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

2. According to the online method, there are still problems</ font>

// set proxy
git config --global http.proxy socks5://127.0.0.1:1081
git config --global https.proxy socks5://127.0.0.1:1081
// add cache
git config --global http.postBuffer 1048576000

3. Finally, add the following operations to solve the problem

//Change this value to a larger value, the perfect solution, the default is 1500.
ifconfig eth0 mtu 14000

How to Solve Unzip Error: tar: Error is not recoverable: exiting now

Tar: error is not recoverable: exiting now

[ root@node04 soft]# tar -zxvf apache-tomcat-8.0.53-x64.tar.gz

Error message:

gzip: stdin has more than one entry–rest ignored tar: Child returned status 2 tar: Error is not recoverable: exiting now

Solution 1: remove the Z parameter and use tar – xvf to decompress

Find or report an error.

Solution 2: use the unzip command.

Problem solving.

If you cannot use the unzip command, first follow:

yum install -y unzip zip

[Solved] Error calling ICU Library: libicudata.so.51: internal error

I recently ported a front-end that depends on the icu library, and after successful compilation I got the following error
error while loading shared libraries: /usr/lib/libicudata.so.51: internal error
I thought it was a problem with icu version, and tried various versions without success.
I finally found the problem after a long day of searching, the config should add –with-data-packaging=files
The original config configurationICU_CONF_OPT = –with-cross-build=$(HOST_ICU_DIR)/source –disable-samples \
–disable-tests
New Configuration:
ICU_CONF_OPT =     –host=arm-linux-gnueabihf \
–with-cross-build=$(HOST_ICU_DIR)/source \
–prefix=$(STAGING_DIR)/usr  \
–with-data-packaging=files \
–disable-samples \
–disable-tests

file_name.sh: 3: Syntax error: “(“ unexpected [How to Solve]

An error was encountered

Execute the command $./example03. Sh error:
./example03. Sh: 3: syntax error: “(” unexpected
check the document

#!/bin/sh
#function hello
function hello(){
    echo "hello SXU."
}
#main
hello	
exit 0

Confirm again and again that there is no error.

Find the reason

Related to the actual shell version used
use the command LS - L/bin/* sh to print and view. For example:
you can see that SH is redirected to dash. Therefore, if./example.sh is executed, dash is used.

Solution:

bash example. Sh the first line of the script #/ Change bin/sh to: #/ Bin/bash, and then execute./example. Sh. The code is correct for standard bash, because Ubuntu/Debian uses dash instead of traditional bash in order to speed up startup. The solution is to cancel Dash: sudo dpkg reconfigure dash , and select no in the selection, choose one of the three methods to succeed.

The docker export container cannot be run after being imported: error response from daemon: no command specified

The docker export container cannot be run after being imported. An error is reported: error response from daemon: no command specified

According to the error message, the command can be run without specifying the command

[root@localhost ~]# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
docker.io/ubuntu    latest              fb52e22af1b0        3 weeks ago         72.8 MB

[root@localhost ~]# docker run -itd docker.io/ubuntu:latest
7ce403eba8d89127395e057eb4d6cf7eb2374e40214ce6575a29e755b707ca23

[root@localhost ~]# docker ps
CONTAINER ID        IMAGE                     COMMAND             CREATED             STATUS              PORTS               NAMES
7ce403eba8d8        docker.io/ubuntu:latest   "bash"              4 seconds ago       Up 3 seconds                            hungry_babbage
[root@localhost ~]# docker export -o test.tar 7ce403eba8d8

[root@localhost ~]# ls
anaconda-ks.cfg  test.tar

[root@localhost ~]# docker import test.tar test/ubuntu:v0.1
sha256:c3d604273769f7a74126b27f29c8cecd055fc18b10c943da0c0528dc28520a60

[root@localhost ~]# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
test/ubuntu         v0.1                c3d604273769        4 seconds ago       72.8 MB
docker.io/ubuntu    latest              fb52e22af1b0        3 weeks ago         72.8 MB

[root@localhost ~]# docker run -itd test/ubuntu:v0.1
/usr/bin/docker-current: Error response from daemon: No command specified.
See '/usr/bin/docker-current run --help'.

# add /bin/bash work
[root@localhost ~]# docker run -itd test/ubuntu:v0.1 /bin/bash
5b7dca448a1400716fa931463c2c314e0e59c7888fa77d5b182e72d911122966

[root@localhost ~]# docker ps
CONTAINER ID        IMAGE                     COMMAND             CREATED             STATUS              PORTS               NAMES
5b7dca448a14        test/ubuntu:v0.1          "/bin/bash"         3 seconds ago       Up 2 seconds                            zen_varahamihira
7ce403eba8d8        docker.io/ubuntu:latest   "bash"              5 minutes ago       Up 5 minutes                            hungry_babbage

A method to solve the error – 110 whilst initializing SD card of raspberry pie

A method to solve the error – 110 whilst initializing SD card of raspberry pie

Error – 110 whilst initializing SD card)

Recently, when playing raspberry pie 4b, it may be because the power supply is not stable enough. Suddenly, the SD card cannot be loaded when starting up. Specifically, the official 5v3a power supply is used, the green act flashes all the time, the red power light is always on, and the screen displays error – 110 whilst initializing SD card.

Changing two SD cards didn’t work, nor did updating the latest EEPROM. I had to start through the USB flash disk, but it didn’t seem to solve the problem at all.

Try the following:

    Update EEPROM. Use SD card to update EEPROM, which can be updated normally. This indicates that the SD card slot should be OK, but it still can’t solve the problem; Replace the SD card and find that it does not work, and the SD card can be read normally on the computer; Using USB flash disk to start, it is found that it can be started through USB flash disk, but it does not solve the problem of SD card startup** Try adding ‘sdhci. Debug’ to the cmdline.txt file_ Quirks2 = 4 ‘* *, solve the problem

Error when Linux executes sh script: syntax error: bad FD number

Today, when using the WCET analyzed by Chronos, there is an error:

: Syntax error: Bad fd number

This error occurs when executing the SH script and when opening the file
solution:
after consulting the data, it is possible that SH is linked to dash rather than bash, so you only need to check the link
execute command

ls -l /bin/sh

Results:

if the above results are obtained, continue to execute the command:

sudo mv /bin/sh /bin/sh.orig
sudo ln -s /bin/bash /bin/sh

Check again and you should get the correct results

configure: error: C compiler cannot create executables

An error message appears when executing ./configure :

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/jiajia/libuuid-1.0.3/libuuid-1.0.3':
configure: error: C compiler cannot create executables
See `config.log' for more details

I wonder. I’ve looked up a lot of information and summarized it:

Case 1: the export operation changes the values of cflags and LIBS
solution: clear the values of cflags and LIBS

export LIBS=
export CFLAGS=

Case 2: environment variable is modified

vi  ~/.bashrc

Check whether there is similar information at the end:

export CC=arm-linux-gcc
export AR=arm-linux-ar
export LD=arm-linux-ld
export RANLIB=arm-linux-ranlib
export STRIP=arm-linux-strip

Solution: delete or comment out the above information

Case 3: the GCC compilation environment is not configured properly
to solve the problem:

sudo apt-get install gcc libc6-dev

However, none of the above is my case, and the above operations are useless
Case 4: there is a problem with the software package, and the list information of the necessary software packages for the compiler cannot be provided
solution: reinstall the build essential software package

sudo apt purge binutils
sudo apt remove make
sudo apt autoremove
sudo apt install build-essential

The problem was finally solved and ./configure was successfully executed