![daemon sync failed daemon sync failed](https://support.gfi.com/hc/article_attachments/360004542959/42.png)
A few weeks ago, I erased the free space on my Mac, but the Monero wallet should not have been considered free space. A user on telegram instructed me to enter this terminal command: monerod -db-sync-mode safe:sync, and I got the message: -bash: monerod command not found. I made sure to allow permission for Daemon to run despite it being an "app from an unauthorized developer" by Mac. My Monero wallet won't sync with Daemon or start. I'm running my own node (at least I was able to run it successfully in the past). I have 1TB of space and I'm only using about 200mb.
![daemon sync failed daemon sync failed](https://i.ytimg.com/vi/ta_92bxBalg/maxresdefault.jpg)
Daemon sync failed mac os#
Could it be caused by the Mac OS version? (macOS Big Sur v11.6.1)I'm using MAC OS, 10.13.6. Not sure why “execute daemon shutdown request”. Pid file deleted, daemon will be shut down NOW. Pid file ‘/Users/meijun/code/farm-ffa-tech.git/subgit/daemon.pid’ deleted. Daemon info pid=39324 port=57521 address=127:0:0:1 user=root from file ‘/Users/meijun/code/farm-ffa-tech.git/subgit/daemon.pid’ Succeeded attempt to obtain file lock on ‘/Users/meijun/code/farm-ffa-tech.git/subgit/daemon.lock’ Trying to obtain file lock on ‘/Users/meijun/code/farm-ffa-tech.git/subgit/daemon.lock’. Executing daemon shutdown request, the reason is UNKNOWN. Sync started for git location ‘default’, mirror mode: REMOTE_MIRROR, recovery mode: FAIL_HARD, fail-safe mode: AUTO Additional repository sync for location ‘default’ Operations will be allowed as soon as SubGit installation is completed.’, warning=true, git enabled=false, svn enabled=false] Updated installation report:ĮrrorReport[description=‘Operation rejected: SubGit installation is in progress. I noticed that deamon.pid briefly appeared in finder. I think it means pid created successfully. ‘/Users/meijun/code/farm-ffa-tech.git/subgit/’ renamed to ‘/Users/meijun/code/farm-ffa-tech.git/subgit/daemon.pid’ I tried setting “launchTimeout=60” before and it still didn’t work. Translating Subversion revisions to Git commits…Įrror: Failed to launch background translation process: timeout waiting for pid file ‘/Users/meijun/code/farm-ffa-tech.git/subgit/daemon.pid’.Įrror: Unexpected error has occurred please report along with the logs (’/Users/meijun/code/subgit-install-20220620-141637.zip’) SubGit version 3.3.14 (‘Bobique’) build #4433Ībout to shut down background translation process.īackground translation process is not running. I cleaned the logs and re-run the subgit install.
Daemon sync failed install#
This is not the first time to install as the logs are huge. To resolve it make sure that the user on whose behalf you start the installation is able to create the file. The default value is 5 try to increase it to, say, 60 seconds.Īnother possible reason is that the daemon started but couldn’t write to the pid file due to a permissions issue, for example. To resolve it increase the daemon launch timeout in SubGit configuration file: One of the possible reasons is that the daemon was too slow to start. In your case, the daemon was not able create the pid file within the given period of time. Then it connects to the daemon using this port and sends a command to it. If, on the other hand, that was just another subgit install invoked to start SubGit daemon, then it indicates the Git and SVN repositories are in sync.Īnother issue is that the daemon didn’t start in the end of the install process due to timeout waiting for pid file error: during the installation, SubGit starts the daemon and waits until the daemon creates a pid file with the port number the daemon listens (the daemon listens random unoccupied port). I’m not sure if that was an initial import or just another subgit install to start SubGit daemon, however: if that was the very first subgit install and initial import, then that means SubGit imported nothing and the most probable cause is incorrect mapping, the ffa/client_root/Client path probably points at nowhere in the SVN repository. Judging from the log, the installation went well, SubGit managed to translate all the revisions from the repository up to the bare latest r23320: Revisions: