Running today's dnf update: ... Running scriptlet: grub2-common-1:2.06-118.fc39.noarch 32/32 Running scriptlet: armadillo-12.8.0-1.fc39.x86_64 32/32 Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
Should I worry? I don't even know what armadillo is.
On 03/12/2024 12:33 PM, Neal Becker wrote:
Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
Should I worry? I don't even know what armadillo is.
Did you look at the logs and if not, why not? Checking Wikipedia, armadillo is a C++ library for linear algebra.
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff joe@zeff.us wrote:
On 03/12/2024 12:33 PM, Neal Becker wrote:
Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
Should I worry? I don't even know what armadillo is.
Did you look at the logs and if not, why not? Checking Wikipedia, armadillo is a C++ library for linear algebra.
I didn't search, because I don't know an easy way to do it. Back when syslog was text it was easy. Let's try: journalctl -g 'Failed to start jobs:' ... Mar 13 07:17:37 nbecker0 packagekitd[723125]: Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
OK, that still tells me nothing. I need to see the lines before this, and maybe after. Any ideas?
On 3/13/24 10:10, Neal Becker wrote:
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff joe@zeff.us wrote:
On 03/12/2024 12:33 PM, Neal Becker wrote:
Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
Should I worry? I don't even know what armadillo is.
Did you look at the logs and if not, why not? Checking Wikipedia, armadillo is a C++ library for linear algebra.
I didn't search, because I don't know an easy way to do it. Back when syslog was text it was easy. Let's try: journalctl -g 'Failed to start jobs:'
-g --grep
I couldn't find any way to pass grep options to -g but grep itself has -A and -B for showing "n" number of lines After or Before the matched context.
The journalctl manpage has an option -n --lines that combined with -g MAY do something like that but I haven't tried it yet.
... Mar 13 07:17:37 nbecker0 packagekitd[723125]: Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
OK, that still tells me nothing. I need to see the lines before this, and maybe after. Any ideas?
On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has -A and -B for showing "n" number of lines After or Before the matched context.
If you need to pass options to grep, consider piping the output of journalctl through grep instead.
On 3/13/24 10:10, Neal Becker wrote:
On Tue, Mar 12, 2024 at 2:50 PM Joe Zeff <joe@zeff.us mailto:joe@zeff.us> wrote:
On 03/12/2024 12:33 PM, Neal Becker wrote: > Failed to start jobs: Failed to enqueue some jobs, see logs for details: > Invalid argument > > Should I worry? I don't even know what armadillo is. Did you look at the logs and if not, why not? Checking Wikipedia, armadillo is a C++ library for linear algebra.I didn't search, because I don't know an easy way to do it. Back when syslog was text it was easy. Let's try: journalctl -g 'Failed to start jobs:' ... Mar 13 07:17:37 nbecker0 packagekitd[723125]: Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
OK, that still tells me nothing. I need to see the lines before this, and maybe after. Any ideas?
It uses commands similar to less (maybe it's actually using less). Run "journalctl -b". Press the "/" key and type the text you want to find. Then you can see the context and use back and forward keys to move around.
You can also run "journalctl -u packagekit", although my logs show a different label for packagekit than what you have there.
Mar 12 14:04:07 fedora PackageKit[4010770]: get-updates transaction /20675_bedceece from uid 1000 finished with success after 2730ms
On 3/13/24 14:42, Joe Zeff wrote:
On 03/13/2024 12:33 PM, Mike Wright wrote:
I couldn't find any way to pass grep options to -g but grep itself has -A and -B for showing "n" number of lines After or Before the matched context.
If you need to pass options to grep, consider piping the output of journalctl through grep instead.
Or pipe the output of journalctl to 'less' and use its built-in search functions.
On 13 Mar 2024, at 17:12, Neal Becker ndbecker2@gmail.com wrote:
I need to see the lines before this, and maybe after. Any ideas?
Once I find a time of interest I have use the —since and - before to get a time bounded slice of logs.
Barry
-
Barry -
Joe Zeff -
Mike Wright -
Neal Becker -
Samuel Sieb -
Tim Evans