Problem after upgrading to 24.11-RC
-
Remote access for your tech staff is offered (again).
I am pretty positive one of the devs (wizards) could trace into the failing "pkg info" command, and tell us whats up in 90 seconds flat :-)
In any case .. I am stuck as of now.
-
A thought has struck me ..
Remember at the beginning of this thread, that I tested the offending command without the "2>&1" redirect,
and it complets with NO errors, and correctly generates the expected list directly to the console ..But it fails when the redirect is present ..
Suppose this problem is not sourcing the list, but rather that target denies "entry" ?
A priviledge-issue, insufficient rights to some ressource (the redirect target) ?Tried this in CLI:
pkg clean -y
pkg upgrade -fNo change .. :-)
-
@m-d-frederiksen said in Problem after upgrading to 24.11-RC:
Remote access for your tech staff is offered (again).
Yes, thank you. I believe they plan to do so on Monday if you're able to do that.
-
BRILLIANT !
Please instruct me on what environment you need / expect ?
Do you need a workstation running specific host-software on LAN, .. and so on.
Thanks in advance.
-
@m-d-frederiksen said in Problem after upgrading to 24.11-RC:
Suppose this problem is not sourcing the list, but rather that target denies "entry" ?
A priviledge-issue, insufficient rights to some ressource (the redirect target) ?Are you not logged in as admin/root when you tried this?
The redirect is not expected to work at the CLI directly but it should work fine when called by repoc.
-
Yes, in my simple attempt to fathom the issue, I claim that the "2>&1" is the part that is the culprit.
The recieving end is unable to parse the generated list.
The same list that looks perfectly valid when NOT redirected, - in the console.And yes, I am root ..
-
UPDATE:
Zeek has left the equation .. apparently felt the heat.
Now pfBlockerNG alone is keeping up the shenanigans. -
@m-d-frederiksen send me an email cmcdonald<at>netgate.com so we can setup a remote access session. Thanks
-
Mail has been sent. Thank you.
-
We've worked it out, root cause identified and a fix proposed. Unsure yet how this will impact the 24.11-RELEASE.
If you are impacted by this, make sure to uninstall any packages that you are not actively using.
-
The fix will land in 24.11 after all :)
