Craig,
I'm sorry but I know absolutely nothing about that "systemd socket" mechanism.
I am an old hat
that grew up with init and hates systemd.
Maybe I have inadvertently broken something, I only know what I have written
before and that it does
not work for me without forcing the service to
On Fri, 2 Feb 2024 at 08:54, Rob Janssen wrote:
> I am using systemd.
>
Where are you seeing this error? The systemd socket is the thing that opens
up the socket, so shouldn't matter what the snmptrapd process is running as.
When I reboot, I get this:
$ sudo ss -unlp | grep 162
UNCONN 0 0
On 2024-02-01 22:09, Craig Small wrote:
> On Sat, 30 Dec 2023 at 06:15, Rob Janssen wrote:
>
> After the upgrade, the snmptrapd service no longer starts.
> The error message is: couldn't open udp:162 -- errno 13 ("Permission
> denied")
>
> Could you tell me how you start snmptrapd?
>
On Sat, 30 Dec 2023 at 06:15, Rob Janssen wrote:
> After the upgrade, the snmptrapd service no longer starts.
> The error message is: couldn't open udp:162 -- errno 13 ("Permission
> denied")
>
Could you tell me how you start snmptrapd?
There are two ways:
The default systemd way. The socket is
Package: snmptrapd
Version: 5.9.3+dfsg-2
I upgraded a system from bullseye to bookworm.
It had snmptrapd installed.
Before the upgrade, all was OK.
After the upgrade, the snmptrapd service no longer starts.
The error message is: couldn't open udp:162 -- errno 13 ("Permission denied")
It appears
5 matches
Mail list logo
