socket_vmnet icon indicating copy to clipboard operation
socket_vmnet copied to clipboard

Exceeded max notifications for socket_vmnet

Open nirs opened this issue 1 year ago • 0 comments

I see this error in the Console.app right after installing the luanchd service:

default	00:46:22.719379+0200	logger	Installing executables for socket_vmnet v1.1.7-10-g04497d2 in //opt/socket_vmnet/bin
default	00:46:22.813225+0200	logger	Installing launchd service for socket_vmnet v1.1.7-10-g04497d2 in /Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.plist
default	00:46:22.829787+0200	kernel	AMFI: '/opt/socket_vmnet/bin/socket_vmnet' has no CMS blob?
default	00:46:22.829797+0200	kernel	AMFI: '/opt/socket_vmnet/bin/socket_vmnet': Unrecoverable CT signature issue, bailing out.
default	00:46:22.900100+0200	backgroundtaskmanagementd	registerLaunchItem: found existing item: uuid=598DDC91-531D-402F-8AB2-FEFA7059D507, name=socket_vmnet, type=legacy daemon, disposition=[enabled, allowed, visible, not notified], identifier=16.io.github.lima-vm.socket_vmnet, url=file:///Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.plist
default	00:46:22.900156+0200	backgroundtaskmanagementd	registerLaunchItem: checking for an updated legacy agent or daemon item: uuid=598DDC91-531D-402F-8AB2-FEFA7059D507, name=socket_vmnet, type=legacy daemon, disposition=[enabled, allowed, visible, not notified], identifier=16.io.github.lima-vm.socket_vmnet, url=file:///Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.plist
default	00:46:22.913316+0200	backgroundtaskmanagementd	registerLaunchItem: updated item: uuid=102B2D63-FF4B-4EC8-ACBD-2B0CCB244FD0, name=socket_vmnet, type=legacy daemon, disposition=[enabled, allowed, visible, not notified], identifier=16.io.github.lima-vm.socket_vmnet, url=file:///Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.plist
default	00:46:22.913794+0200	backgroundtaskmanagementd	effectiveItemDisposition: appURL=(null), type=legacy daemon, url=file:///Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.plist, config={
    BTMConfigArguments =     (
        "/opt/socket_vmnet/bin/socket_vmnet",
        "--vmnet-gateway=192.168.105.1",
        "/var/run/socket_vmnet"
    );
    BTMConfigBundleIdentifiers =     (
    );
    BTMConfigExecutablePath = "/opt/socket_vmnet/bin/socket_vmnet";
    BTMConfigLabel = "io.github.lima-vm.socket_vmnet";
}
default	00:46:23.232265+0200	syspolicyd	GK evaluateScanResult: 2, PST: (path: 1cc082597f2c11c6), (team: (null)), (id: socket_vmnet), (bundle_id: NOT_A_BUNDLE), 0, 0, 1, 0, 0, 0, 0
default	00:46:23.234448+0200	tccd	AUTHREQ_ATTRIBUTION: msgID=487.16, attribution={accessing={TCCDProcess: identifier=socket_vmnet, pid=29735, auid=0, euid=0, binary_path=/opt/socket_vmnet/bin/socket_vmnet}, requesting={TCCDProcess: identifier=com.apple.syspolicyd, pid=487, auid=0, euid=0, binary_path=/usr/libexec/syspolicyd}, },
default	00:46:23.237502+0200	tccd	AUTHREQ_SUBJECT: msgID=487.16, subject=/opt/socket_vmnet/bin/socket_vmnet,
default	00:46:23.238260+0200	tccd	-[TCCDAccessIdentity staticCode]: static code for: identifier /opt/socket_vmnet/bin/socket_vmnet, type: 1: 0x652251500 at /opt/socket_vmnet/bin/socket_vmnet
default	00:46:33.278543+0200	socket_vmnet	[0x600003838000] activating connection: mach=true listener=false peer=false name=com.apple.NetworkSharing
default	00:46:33.278732+0200	socket_vmnet	[0x155004080] activating connection: mach=false listener=true peer=false name=(anonymous)
default	00:46:33.278778+0200	socket_vmnet	[0x155004080] Channel could not return listener port.
default	00:46:33.602171+0200	InternetSharing	socket_vmnet: com.apple.NetworkSharing.broadcast-0 has been started
error	00:46:33.885705+0200	backgroundtaskmanagementd	Exceeded max notifications for socket_vmnet. Please file a Feedback report or contact the developer. item=uuid=102B2D63-FF4B-4EC8-ACBD-2B0CCB244FD0, name=socket_vmnet, type=legacy daemon, disposition=[enabled, allowed, visible, not notified], identifier=16.io.github.lima-vm.socket_vmnet, url=file:///Library/LaunchDaemons/io.github.lima-vm.socket_vmnet.plist

Searching does not return anything meaningful about this error. Maybe we need to configure launchd differently?

With systemd well behaved daemon need to notify systemd when it is ready, I expect launchd to have similar feature.

I could not find anything about the notifications here: https://www.launchd.info/

nirs avatar Nov 09 '24 23:11 nirs