Opening macOS Console and looking at the System Log i ran into this error message that keeps repeating itself indefinitely:
com.apple.xpc.launchd[1] (com.macpaw.CleanMyMac4.HealthMonitor[21558]): Service exited with abnormal code: 78
com.apple.xpc.launchd[1] (com.macpaw.CleanMyMac4.HealthMonitor): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
com.apple.xpc.launchd[1] (com.macpaw.CleanMyMac4.HealthMonitor[21559]): Could not find and/or execute program specified by service: 149: Could not find a bundle of the given identifier through LaunchServices: com.macpaw.CleanMyMac4.HealthMonitor
I also tried to search inside
home/Library/LaunchAgents
but cannot find anything about CleanMyMacX.
A few days ago I deleted the "HealthMonitor" application because it was always running in background. I think that some service is trying to keep the application alive, but how can I stop it?
If you're not seeing it there, it's likely a launch daemon, not an agent. That means the binary is located in the /Library/PrivilegedHelperTools/ directory and its registration file is located in the /Library/LaunchDaemons/ directory.
Related
I've been attempting to setup a Windows agent for our Jenkins on Linux to use. Mostly using the instructions from https://www.gdcorner.com/2019/12/30/JenkinsHomeLab-P3-WindowsAgents.html
Only mostly, as those (like EVERY OTHER SET I've found) don't match the current Jenkins screens.)
I got to the point where I ran the curl/java -jar commands on the Agent machine in an Administrator Command window.
It worked, and connected to Jenkins, showed up as running. Though this means it was still running as a normal program in a command window.
While attempting to figure out what was meant by "Click the Launch agent from browser. " - which showed a small window that should then be displayed - which would allow you to install it as a service, I closed the Command window.
I never figured out how to "click the launch agent from browser", so I opened a new admin command window and re-ran the commands. They no longer work. It gets this error every time: (note that "WinDInstaller" is really "Win%2DInstaller")
Sep 28, 2022 10:15:40 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using C:\Enterprise\Agent\remoting as a remoting work directory
Sep 28, 2022 10:15:40 AM org.jenkinsci.remoting.engine.WorkDirManager setupLogging
INFO: Both error and output logs will be printed to C:\Enterprise\Agent\remoting
Failed to obtain http://metrixbld1:8080/computer/WinDInstaller/jenkins-agent.jnlp?encrypt=true
java.io.IOException: Failed to load http://metrixbld1:8080/computer/WinDInstaller/jenkins-agent.jnlp?encrypt=true: 404 Not Found
at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:514)
at hudson.remoting.Launcher.run(Launcher.java:346)
at hudson.remoting.Launcher.main(Launcher.java:297)
Waiting 10 seconds before retry
It seems like it should be possible to get an Agent running on windows as a Service - but so far I've not found a set of instructions that work.
EDIT: Since that agent definition no longer worked, I created a new one and had it just copy the settings from the old one.
Then ran the new java/agent command - and it worked.
Apparently you can only launch a new agent once. If it ever stops you have to re-create it????
I've been running a few containers (approximately a dozen) for awhile now. I've approached whatever the hard limit is on container/image sizes in the past, and had to clean these up to keep it from barfing all over everything, and recently the same has happened again.
I have identified several containers and images I can safely remove to reduce its footprint. But just as I was getting ready to do so, Docker crashed on me. And when I attempt to restart it, it crashes with the error message:
Fatal Error
Docker daemon failed to start
[timestamp] dockerd failed to start daemon: error initializing graphdriver: driver not supported
Thus, I can't use any of the command-line tools to remove these images/containers.
As there are running containers that I don't dare delete at this point, this makes it a little difficult to resolve. Is there a way to start Docker (on the mac) that doesn't actually start any of the containers so that maybe I can avoid this error?
Is the error message even related to my problem? I'm on Docker 2.3.0.4 if it matters.
You could switch to overlay2 driver instead of graph driver
You can follow the document below to switch
https://docs.docker.com/storage/storagedriver/overlayfs-driver/
macOS Majoave 10.14.4
My Mac is set to go to sleep after 5 minutes of no activity. I used Jiggler to prevent this. I set up a crontab that will automatically start Jiggler 8am in the morning.
0 8 * * * open -a Jiggler
It worked fine before but stopped working a few days ago. From the log I can see something like below:
com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.0): Could not import service from caller: caller = open.79537, service = com.stick.app.jiggler.13728, error = 134: Service cannot load in requested session
What could be the issue and how to fix it?
The issue is because it is trying to run Jiggle with the root user, and not your MacOS user. But this app cannot run as root [and should never run as root anyway].
This message is telling this:
com.apple.xpc.launchd.domain.user.0
Is says the failed session was a user domain session, for the UID 0 [which is root]
Was your MacOS user logged in at 8h00 AM on the Graphical interface? when that error occurred?
To fix it you must adjust your cron job to run under your username, and because this is a graphical application, your user need to have an active session (logged in graphically) for this job correctly be executed.
We have just uninstalled Docker Community Edition and installed Enterprise Edition on a Windows Server 2016 System as per these steps.
On reaching the last step which is to test a hello-world container we are receiving the following error:
C:\Program Files\Docker\docker.exe: failed to register layer: re-exec
error: exit status 1: output: ProcessUtilityVMImage
\?\C:\ProgramData\Docker\windowsfilter\e345ad40cc8f7d073f62501b7445d42d677889c04b2c6fe0963ea6e092b52f95\UtilityVM:
The process cannot access the file because it is being used by another
process.
We are seeing lots of examples on SO related to other types of applications giving this error but not Docker.
How might we fix this?
This turned out to be an issue related to Symantec Endpoint Protection(SEP) clashing with Docker.
SEP needs to be upgraded to version 14 RU1 and several files need execution privileges.
Symantec posted a fix here: https://support.symantec.com/en_US/article.TECH246815.html which we have tried and worked.
Following error is encountered when trying to start Oracle Weblogic Server:
<Info> <Management> <BEA-141297> <Could not get the server file lock. Ensure that another server is not running in the same directory. Retrying for another 60 seconds.>
How do I overcome this error and start the server?
The error means that there is a file lock that could not be released, as the server was previously not shut down correctly.
In this case you must follow the next steps:
Navigate to tmp folder in your $DOMAIN_HOME directory. (for example: C:\Oracle\Middleware\Oracle_Home\user_projects\domains\mydomain\servers\AdminServer\tmp)
Delete the lock file for the server instance, AdminServer.lok
Check if there are any java.exe processes are running, which should not be there. If there are any, they would have to be killed.
Restart your server