FatalError with trace, no specific information, --verbose does nothing

[jakecoble]

 △ ~ aconfmgr --verbose save                                                                                                                                                                                  
: Collecting data...
:: Compiling user configuration...
::: Using configuration in /home/jake/.config/aconfmgr
::: Sourcing /home/jake/.config/aconfmgr/00-config.sh...
::: Done (0 native packages, 0 foreign packages, 0 files).
:: Inspecting system state...
::: Querying package list...
:::: Done.
::: Enumerating owned files...
:::: Done.
::: Searching for stray files...
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:330 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:883 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:332 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:883 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]

Latest version from the AUR. Only thing in 00-config.sh is verbose=1. No other config files.

What can I do to get more information on the error?

[CyberShadow]

Could you please run aconfmgr with the -x shell flag (e.g. bash -x /usr/bin/aconfmgr), and post the output? That should, at least, allow finding the failing command.

[jakecoble]

Seems to be SIGPIPE, so one of the commands involved must be trying to write to a pipe after a command exited. That area of the code is full of nested subshells, so it's tough to track down exactly which command is failing.

[CyberShadow]

So, how can we act on this? Do you have a way to reproduce the problem?

[jakecoble]

I suspect some subtle misconfiguration of my system at play here, so I'll close this and open a new issue if I find something actually wrong with aconfmgr.

[gardar]

@jakecoble did you ever manage to trace the source of this issue? I'm facing a similar issue myself.

I've got a fresh install of aconfmgr but a not-so-fresh install of Arch 😄

:: ~ » aconfmgr --verbose save
: Collecting data...
:: Compiling user configuration...
::: Using configuration in /home/g/.config/aconfmgr
::: Done (configuration not found).
:: Inspecting system state...
::: Querying package list...
:::: Done.
::: Enumerating owned files...
:::: Done.
::: Searching for stray files...
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:346 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:900 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:348 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:900 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]

( Let me know if you want me to create a new issue for this @CyberShadow )

[CyberShadow]

It looks like the exact same issue.

Could you please run with -x, and either post the output or try to find the failing command?

[gardar]

Sure thing, here's the full output with -x:

https://gist.github.com/gardar/892d26ec4de0f7bace104deadff031d8

[CyberShadow]

Thanks. Unfortunately I can't tell what is failing from the log.

Could you please try this patch (without -x), and post the output: https://github.com/CyberShadow/aconfmgr/compare/debug-find

[jakecoble]

Forgot about this issue! IIRC it turned out that I had a file path on my system with some odd special characters in it. The script was choking on that.

[CyberShadow]

IIRC it turned out that I had a file path on my system with some odd special characters in it. The script was choking on that.

Any hints for how to recreate this problem? (I've been keeping a file with all the special characters I could think of on my real system for testing...)

[gardar]

Thanks. Unfortunately I can't tell what is failing from the log.

Could you please try this patch (without -x), and post the output: https://github.com/CyberShadow/aconfmgr/compare/debug-find

Here's the output from that branch:

: Collecting data...
:: Compiling user configuration...
::: Using configuration in /home/g/.config/aconfmgr
::: Done (configuration not found).
:: Inspecting system state...
::: Querying package list...
:::: Done.
::: Enumerating owned files...
:::: Done.
::: Searching for stray files...
:::: tee failed!
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:1673 [FatalError]
::::: /usr/lib/aconfmgr/common.bash:339 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:903 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]
:::: find failed!
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:1673 [FatalError]
::::: /usr/lib/aconfmgr/common.bash:336 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:903 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:349 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:903 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]
:::: Fatal error! Stack trace:
::::: /usr/lib/aconfmgr/common.bash:351 [AconfCompileSystem]
::::: /usr/lib/aconfmgr/common.bash:903 [AconfCompile]
::::: /usr/lib/aconfmgr/save.bash:9 [AconfSave]
::::: /usr/lib/aconfmgr/main.bash:185 [Main]
::::: /usr/lib/aconfmgr/main.bash:205 [source]
::::: /usr/bin/aconfmgr:26 [main]

Forgot about this issue! IIRC it turned out that I had a file path on my system with some odd special characters in it. The script was choking on that.

Interesting, since /home is ignored I would have thought such cases would be unlikely to occur.

The only uncommon/odd thing about my paths/filesystem that I can think of is that I'm using zfs for my root, and I have some snapshots and a few zfs volumes mounted, for containers and such. Could aconfmgr be choking on that?

[CyberShadow]

It's certainly possible, if GNU find is unequipped to deal with such special filesystem entries.

We can test that theory - run:

find / -regextype posix-extended -not '(' '(' -regex '/dev|/home|/media|/mnt|/proc|/root|/run|/sys|/tmp|/var/cache' -o -false ')' -printf I -print0 -prune ')' -printf O -print0 > /dev/null ; echo $?

It should print 0 on success.

You could also try ignoring the root of these snapshots in the aconfmgr configuration, and see if that makes any difference.