关于【error-handling】的问题- 第1页

raylight

Asked: 2022-05-05 19:35:18 +0800 CST

如何检查管道上的第一个命令是否出错？

0

假设我在终端上执行以下命令：

this-command-doesnt-exist-and-closes-with-code-127 | jq ''

如果我执行echo $?，我会得到0结果，因为它正在检查jq. 我想知道管道上第一个命令的退出代码。我想过像这样重定向标准错误：

this-command-doesnt-exist-and-closes-with-1 2>&1 | jq ''
if [ $? != 0 ]; then
    echo "I got an error"
fi

就这样我发送了一条没有意义的消息jq。它可以解决问题，但看起来不是正确的解决方案。如何管理获取管道上命令的错误代码？

DGesto

Asked: 2019-07-26 01:27:26 +0800 CST

程序崩溃并出现错误“ld.so 检测到不一致：dl-lookup.c:111”（linux 初学者）

3

这是我第一次发帖，所以对于格式化或暴露问题的任何错误，我深表歉意。我也是Linux初学者。

我正在尝试运行一个名为 Caver Analyst 的生物信息学程序。每当我在终端上调用它时，我都会得到以下输出：

dgesto@jarvis ~: caver_analyst

Jul 24, 2019 5:24:39 PM cz.caver.Main main
INFO: Using default userdir: /home/dgesto/.caver_analyst/2.0b2
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.netbeans.ProxyURLStreamHandlerFactory (file:/usr/local/lib/caver_analyst2/platform/lib/boot.jar) to field java.net.URL.handler
WARNING: Please consider reporting this to the maintainers of org.netbeans.ProxyURLStreamHandlerFactory
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed!

我正在使用 OpenJDK 版本 11.0.3 运行 Linux Mint 19.1 (Tessa)。我认为它可能与java有关，并尝试降级到版本8但没有运气。

如果您需要有关我的系统的更多信息，请告诉我。

Dmitry Pavlushin

Asked: 2019-04-29 08:08:23 +0800 CST

处理 bash 中的特定错误

0

作为我脚本的一部分，我想将包发布到 nuget 提要：

dotnet nuget push package.1.2.3.nupkg --source "mysource" --api-key "mykey"

该命令可能会打印error: 409 already contains version 1.2.3并退出代码 1。这在我的上下文中非常好，但它会使整个脚本失败。我想用一些东西包装这个命令，如果特定错误出现在标准输出中，它将吞下非零退出代码，但如果它没有出现，则冒泡非零退出代码。我可以用什么来完成我的任务？

Gqqnbig

Asked: 2019-04-17 17:19:48 +0800 CST

ls 先报告不存在的文件，忽略指定的顺序

0

$ ls -lU a.txt test.sh badtest
ls: cannot access 'badtest': No such file or directory
-rw-r--r-- 1 gqqnbig gqqnbig 11 Apr 15 17:17 a.txt
-rw-r--r-- 1 gqqnbig gqqnbig 11 Apr 16 17:22 test.sh

虽然参数的顺序是a.txt test.sh badtest，但 lsbadtest先报告。

ls 是否可以遵守文件的顺序？IE。输出像

$ ls -lU a.txt test.sh badtest
-rw-r--r-- 1 gqqnbig gqqnbig 11 Apr 15 17:17 a.txt
-rw-r--r-- 1 gqqnbig gqqnbig 11 Apr 16 17:22 test.sh
ls: cannot access 'badtest': No such file or directory

Erel Segal-Halevi

Asked: 2019-03-20 07:13:25 +0800 CST

这三个额外的字符是什么？为什么它们会导致如此奇怪的错误？[复制]

3

看看这两个文件：

在我看来它们完全一样，但文件 1 有 41 个字节，文件 2 有 44 个字节。

现在，我不会关心 3 个额外的字符，但是，我认为这些字符也会导致一个奇怪的错误：当我克隆并运行这些文件时，文件 1 运行正常，而文件 2 在第 3 行返回错误：“./ BasicCheck.sh：第 3 行：cd：case0：没有这样的文件或目录”。

那么：这些额外的字符是什么？为什么它们会导致错误？我应该怎么做才能修复这些错误？

我的猜测是它们是换行符——也许文件 1 有基于 Linux 的换行符，而文件 2 有基于 Windows 的换行符。这是对的吗？为什么它会导致这样的错误？

Brendan Darrer

Asked: 2019-01-26 04:10:00 +0800 CST

铿锵声：错误：没有这样的文件或目录：'_REENTRANT'

0

我正在尝试为图形可视化浏览器安装UDUNITS-2包：ncview。我需要了解以下错误消息：

clang: error: no such file or directory: '_REENTRANT'

这里给出了一个类似的问题---> Xcode 7.2 - clang: error: no such file or directory:

我的./configure输出：

brendan-darrer:Downloads brendandarrer$ cd src/
brendan-darrer:src brendandarrer$ ls
COPYRIGHT   INSTALL     NOTEBOOK    README      VERSION     admin       configure.in    perl        udunits
CUSTOMIZE   Makefile.in ORIGIN      RELEASE_NOTES   aclocal.m4  configure   lib     port
brendan-darrer:src brendandarrer$ ./configure
creating cache ./config.cache
configure: warning: reading configuration customizations
checking type of operating system... darwin
checking for c89... c89
checking for dependency generation mechanism... c89 -M
checking how to run the C preprocessor... c89 -E
checking the C preprocessor... works
checking for C const... yes
checking for C volatile... yes
checking for C signed... yes
checking for C function prototypes... yes
checking for standard C variadic functions... yes
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c89: illegal option -- M
usage: c89 [-cEgs] [-D name[=value]] [-I directory] ... [-L directory] ...
       [-o outfile] [-O optlevel] [-U name]... operand ...
checking for standard C string generation... yes
checking for standard C token pasting... yes
checking C void pointer... yes
checking type of machine... x86_64
checking for ar... ar
checking for tar flags... -chof
checking for ranlib... ranlib
checking binary distribution directory... /home/ftp/pub/binary/x86_64-darwin
checking the installation prefix... /Users/brendandarrer/Downloads
checking the installation exec-prefix... /Users/brendandarrer/Downloads/bin
checking for neqn... neqn
checking for tbl... tbl
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c89: illegal option -- M
usage: c89 [-cEgs] [-D name[=value]] [-I directory] ... [-L directory] ...
       [-o outfile] [-O optlevel] [-U name]... operand ...
checking C header file <stddef.h> for typedef size_t... declared
checking for ar... (cached) ar
checking for float.h... yes
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c89: illegal option -- M
usage: c89 [-cEgs] [-D name[=value]] [-I directory] ... [-L directory] ...
       [-o outfile] [-O optlevel] [-U name]... operand ...
checking C header file <stdlib.h> for typedef size_t... declared
checking for atexit... yes
checking C header file <stdlib.h> for function atexit()... declared
checking for getenv... yes
checking C header file <stdlib.h> for function getenv()... declared
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c89: illegal option -- M
usage: c89 [-cEgs] [-D name[=value]] [-I directory] ... [-L directory] ...
       [-o outfile] [-O optlevel] [-U name]... operand ...
checking C header file <string.h> for typedef size_t... declared
checking for strerror... yes
checking C header file <string.h> for function strerror()... declared
checking for strstr... yes
checking C header file <string.h> for function strstr()... declared
checking for memmove... yes
checking C header file <string.h> for function memmove()... declared
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c89: illegal option -- M
usage: c89 [-cEgs] [-D name[=value]] [-I directory] ... [-L directory] ...
       [-o outfile] [-O optlevel] [-U name]... operand ...
checking C header file <time.h> for typedef time_t... declared
checking C header file <time.h> for typedef size_t... declared
checking for difftime... yes
checking C header file <time.h> for function difftime()... declared
checking for strftime... yes
checking C header file <time.h> for function strftime()... declared
checking for perl... perl
checking for type of perl executable to create... dynamic
checking for position-independent compilation flags... ''
updating cache ./config.cache
creating ./config.status
creating Makefile
creating lib/Makefile
creating udunits/Makefile
creating perl/Makefile.PL
creating port/master.mk
creating port/Makefile
creating port/misc/Makefile
creating port/fortc/Makefile
creating port/misc/udposix.h
creating port/misc/stdarg.h
creating port/misc/stddef.h
creating port/misc/stdlib.h
creating port/misc/string.h
creating port/misc/time.h
expanding `include's in file `Makefile'
expanding `include's in file `lib/Makefile'
expanding `include's in file `udunits/Makefile'
expanding `include's in file `perl/Makefile.PL'
expanding `include's in file `port/master.mk'
expanding `include's in file `port/Makefile'
expanding `include's in file `port/misc/Makefile'
expanding `include's in file `port/fortc/Makefile'
brendan-darrer:src brendandarrer$ make
Makefile:279: warning: overriding commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:276: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:384: warning: overriding commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:381: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:418: warning: overriding commands for target `/Users/brendandarrer/Downloads/include'
Makefile:415: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/include'
Makefile:448: warning: overriding commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:445: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:503: warning: overriding commands for target `/Users/brendandarrer/Downloads/man'
Makefile:491: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/man'
Makefile:541: warning: overriding commands for target `/Users/brendandarrer/Downloads/info'
Makefile:538: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/info'

making `all' in directory /Users/brendandarrer/Downloads/src/port

Makefile:263: warning: overriding commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:260: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:368: warning: overriding commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:365: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:402: warning: overriding commands for target `/Users/brendandarrer/Downloads/include'
Makefile:399: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/include'
Makefile:432: warning: overriding commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:429: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:487: warning: overriding commands for target `/Users/brendandarrer/Downloads/man'
Makefile:475: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/man'
Makefile:525: warning: overriding commands for target `/Users/brendandarrer/Downloads/info'
Makefile:522: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/info'
Makefile:263: warning: overriding commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:260: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:368: warning: overriding commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:365: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:402: warning: overriding commands for target `/Users/brendandarrer/Downloads/include'
Makefile:399: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/include'
Makefile:432: warning: overriding commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:429: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:487: warning: overriding commands for target `/Users/brendandarrer/Downloads/man'
Makefile:475: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/man'
Makefile:525: warning: overriding commands for target `/Users/brendandarrer/Downloads/info'
Makefile:522: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/info'

making `all' in directory /Users/brendandarrer/Downloads/src/port/misc

Makefile:285: warning: overriding commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:282: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/lib'
Makefile:390: warning: overriding commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:387: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/bin'
Makefile:424: warning: overriding commands for target `/Users/brendandarrer/Downloads/include'
Makefile:421: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/include'
Makefile:454: warning: overriding commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:451: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/etc'
Makefile:509: warning: overriding commands for target `/Users/brendandarrer/Downloads/man'
Makefile:497: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/man'
Makefile:547: warning: overriding commands for target `/Users/brendandarrer/Downloads/info'
Makefile:544: warning: ignoring old commands for target `/Users/brendandarrer/Downloads/info'
c89 -c -g -I.  -D_REENTRANT  uddummy.c
clang: error: no such file or directory: '_REENTRANT'
make[3]: *** [uddummy.o] Error 1
make[2]: *** [misc/all] Error 1
make[1]: *** [subdirs/all] Error 2
make: *** [port/all] Error 1
brendan-darrer:src brendandarrer$

Jeremy

Asked: 2018-12-21 10:13:51 +0800 CST

在 && 表达式左侧调用的函数内部发生错误时失败

3

我正在开发一个具有多个功能的 Bash 脚本。如果任何命令返回非零退出代码，我想退出脚本，除非在明确处理该代码的上下文中（例如在if条件中或在||替代之前）。为了使这更容易，我从脚本中删除了所有子 shell 的使用，并启用了我能找到的每个错误处理选项。

不幸的是，我仍然遇到一种常见的错误被抑制的模式。

如果函数中的命令返回非零退出代码，但不是函数中的最后一个命令，并且函数作为&&表达式的第一部分被调用，则退出代码将被忽略。

#!/bin/bash

trap 'echo "Error occurred." && exit' ERR
set -o errexit;  # -e
set -o errtrace; # -E
set -o pipefail;

first-step-fails() {
    # These should be redundant, but are repeated to be certain and clear.
    trap 'echo "Error occurred." && exit' ERR
    set -o errexit;  # -e
    set -o errtrace; # -E
    set -o pipefail;

    false; # exit code 1 (failure)
    true;  # exit code 0 (success)

    echo "A is executed.";
}

first-step-fails && echo "B is executed.";

A is executed.
B is executed.

我没想到任何一个echos 都会在调用false.

如果未在&&表达式中调用该函数，则会捕获错误：

#!/bin/bash

trap 'echo "Error occurred." && exit' ERR
set -o errexit;  # -e
set -o errtrace; # -E
set -o pipefail;

first-step-fails() {
    # These should be redundant, but are repeated to be certain and clear.
    trap 'echo "Error occurred." && exit' ERR
    set -o errexit;  # -e
    set -o errtrace; # -E
    set -o pipefail;

    false; # exit code 1 (failure)
    true;  # exit code 0 (success)
    echo "A is executed.";
}

first-step-fails ### && echo "B is executed.";

Error occurred.

如果失败是函数的最后一步，则错误不会被捕获，但函数当然会传递其非零退出状态并抑制外部echo.

#!/bin/bash

trap 'echo "Error occurred." && exit' ERR
set -o errexit;  # -e
set -o errtrace; # -E
set -o pipefail;

first-step-fails() {
    # These should be redundant, but are repeated to be certain and clear.
    trap 'echo "Error occurred." && exit' ERR
    set -o errexit;  # -e
    set -o errtrace; # -E
    set -o pipefail;

    false; # exit code 1 (failure)
    ### true;  # exit code 0 (success)
    ### echo "A is executed.";
}

first-step-fails && echo "B is executed.";

(no output)

当在表达式左侧调用的函数内部调用的命令返回非零退出状态时，如何让我的 bash 脚本退出&&？

我一直在 macOS（内置 GNU Bash 4.4.23）上进行测试，但需要一个也适用于 Alpine Linux（打包 GNU Bash 4.4.19）的解决方案。

user149572

Asked: 2018-12-21 06:32:28 +0800 CST

只有在剧本没有问题的情况下，如何运行 Ansible 剧本？

0

我已经了解了ansible-playbook example.yml --check可以告诉我剧本中的某些内容是否有问题的命令（据 Ansible 可以识别）。

我想我应该把这个命令和ansible-playbook example.ymlso 结合起来，只有在前一个测试听没有错误的情况下才能执行我的剧本。

我想到了这个，但我不确定它是否正确：

ansible-playbook example.yml --check && ansible-playbook example.yml

我认为这&&将确保只有在检查正常（未发现错误）时才会发生第二个命令（实际执行剧本）。

是这样吗？如果不是，那么确保当且仅当剧本没有错误时才能播放剧本的正确方法是什么？

elbarna

Asked: 2018-10-08 10:01:25 +0800 CST

使用“set -e”退出的 Slackbuild 脚本……没有错误！

0

有了这个松弛构建：

#!/bin/sh

PRGNAM=libnfsidmap
VERSION=${VERSION:-0.25}
BUILD=${BUILD:-3}
TAG=${TAG:-_mg}

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
        i?86) ARCH=i486 ;;
        arm*) ARCH=arm ;;
           *) ARCH=$( uname -m ) ;;
  esac
fi


CWD=$(pwd)
TMP=${TMP:-/tmp/txz}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}

if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
fi

set -e

SOURCE="http://www.citi.umich.edu/projects/nfsv4/linux/libnfsidmap/libnfsidmap-$VERSION.tar.gz"

if [ ! -e $PRGNAM-$VERSION.tar.gz ];
then
    wget -c $SOURCE
else
    echo "already download"
fi


rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xzvf $CWD/$PRGNAM-$VERSION.tar.gz
cd $PRGNAM-$VERSION

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --sysconfdir=/etc \
  --localstatedir=/var \
  --mandir=/usr/man \
  --build=$ARCH-slackware-linux

make
make install DESTDIR=$PKG
mkdir $PKG/etc
install -m 644 $CWD/idmapd.conf $PKG/etc

( cd $PKG
  find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | \
    xargs strip --strip-unneeded 2> /dev/null || true
  find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | \
    xargs strip --strip-unneeded 2> /dev/null
)

( cd $PKG/usr/man
  find . -type f -exec gzip -9 {} \;
  for i in $( find . -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
)

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a \
  $TMP/$PRGNAM-$VERSION/README $TMP/$PRGNAM-$VERSION/AUTHORS $TMP/$PRGNAM-$VERSION/COPYING \
    $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
chown -R root:root $PKG/usr/doc
find $PKG/usr/doc -type f -exec chmod 0644 {} \;

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

cd $PKG
/sbin/makepkg -l y -c n $CWD/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.txz

我编译

sudo sh *ld

并且......它在 make 之后退出，即使在该行之后没有错误（！）

make install DESTDIR=$PKG

如果我删除 set -e，继续并正确创建我的包。为什么用 set -e 退出？据我所知，set -e 的意思是“如果发生错误，则退出脚本”。Distro 是 slackware 14.2，bash 是 4.3.48，我也尝试 bash script.sh..但还是一样。

hkoosha

Asked: 2018-08-10 02:46:13 +0800 CST

如何在 bash shell 中静默处理“bash: /xyz: Is a directory”错误？

1

在 zsh 中，执行目录路径会 cd 进入它。我想让 bash shell 表现相同。这个想法是检查并查看错误是否bash: /xyz: Is a directory和 cd 进入 '/xyz' 并使错误消息静音。为此，我需要一个自定义错误处理程序。trap捕获信号，并且提到的错误不会产生信号（或者是吗？）。

这与 bash 脚本无关，而是每天使用的实际 bash shell。可能吗？

如何检查管道上的第一个命令是否出错？

程序崩溃并出现错误“ld.so 检测到不一致：dl-lookup.c:111”（linux 初学者）

处理 bash 中的特定错误

ls 先报告不存在的文件，忽略指定的顺序

这三个额外的字符是什么？为什么它们会导致如此奇怪的错误？[复制]

铿锵声：错误：没有这样的文件或目录：'_REENTRANT'

在 && 表达式左侧调用的函数内部发生错误时失败

只有在剧本没有问题的情况下，如何运行 Ansible 剧本？

使用“set -e”退出的 Slackbuild 脚本……没有错误！

如何在 bash shell 中静默处理“bash: /xyz: Is a directory”错误？

模块 i915 可能缺少固件 /lib/firmware/i915/*

无法获取 jessie backports 存储库

如何将 GPG 私钥和公钥导出到文件

我们如何运行存储在变量中的命令？

如何配置 systemd-resolved 和 systemd-networkd 以使用本地 DNS 服务器来解析本地域和远程 DNS 服务器来解析远程域？

dist-upgrade 后 Kali Linux 中的 apt-get update 错误 [重复]

如何从 systemctl 服务日志中查看最新的 x 行

Nano - 跳转到文件末尾

grub 错误：你需要先加载内核

如何下载软件包而不是使用 apt-get 命令安装它？

问题[error-handling](unix)