Closed MattJohnsonMusic closed 2 years ago
Same on macOS both Catalina and High Sierra (10.15.7 and 10.13.6) with IPFS Desktop v0.19.3.
Quit
the app and check the process as well..ipfs
directory in IPFS_PATH
env path. (Which is the another partition)/Users/<user name>/Library/Application Support/IPFS Desktop
directory./Users/<user name>/Library/Application Support/IPFS Desktop/error.log
2022-02-19T01:42:03.466Z error: [ipfsd] start daemon SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Daemon._getConfig (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/node_modules/ipfsd-ctl/src/ipfsd-daemon.js:365:19)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Daemon.init (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/node_modules/ipfsd-ctl/src/ipfsd-daemon.js:157:9)
at async spawn (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:54:3)
at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:61:31)
at async startIpfs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:47:15)
at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:109:3)
at async run (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/index.js:83:5)
Thank you very much!! I'll give this a try. Further proof we are not islands. I appreciate your help…;-)
Unfortunately, still can’t connect. Followed clean install directions explicitly and v19.3 still cannot connect. Like I mentioned, I’m not a terminal guy…just an end-user. Any other helpful suggestions?
@KEINOS @MattJohnsonMusic
/Users/<user name>/Library/Application Support/IPFS Desktop/combined.log
AND configuration file /Users/<user name>/Library/Application Support/IPFS Desktop/config.json
? :pray: (Sorry for delay...projects and life)
I have exhausted my understanding on my side. I've deleted files, restarted multiple times. The first time I initially loaded IPFS Desktop app, everything was created as it should be. Could access app, node was created, I placed/pinned files inside, and the world was a happy place. THEN, I received the "update" dialog box, which I did, and got stuck in the initial Mac loop that was not recognized. I tried uninstalling/reinstalling, etc., but didn't work. I understand v19.3 is supposed to fix the Mac looping issue and get everything back to normal, but that's been the case. The 19.3 installs, but crashes and also can't connect to IPFS API. I don't know how to fix. I need to upload content to my node, but don't an IPFS node anywhere, nor can I cannot like I initially could.
I'm at the mercy of you…and hopefully "lidel"…to help me figure this out...pretty please? Peace, Matt
Could not attach JSON file, but here's the text: { "ipfsConfig": { "type": "go", "path": "", "flags": [ "--agent-version-suffix=desktop", "--migrate", "--enable-gc", "--routing=dhtclient" ] }, "language": "", "experiments": {}, "internal": { "migrations": { "version": "0.19.3" } }, "automaticGC": true, "openWebUIAtLaunch": true, "daemonConfigRevision": 1, "checkedCorsConfig": true }
FYI: I'm running a 2010 MacPro (monster) tower, MacOS High Sierra, v10.13.6 This is the highest MacOS I'm able to run on my machine.
…back to normal, but that's NOT been the case.
@MattJohnsonMusic happy to hear it eventually got resolved for you :+1:
I suspect the problem was introduced when you tried to manually fix 0.18 installation (which had a broken autoupdate logic), and that impacted the behavior of 0.19.3 (either via broken config or repo still being around).
Sadly can't tell much from the logs – something was killing the daemon via SIGABRT
but that could be just you exiting the app during migration or similar.
I know this is frustrating, but should be less likely to occur in the future – we removed legacy code that was specific to macOS, and use a more robust autoupdate code path in 0.19.3+ which should make future updates way safer.
NO…not corrected...don't close yet...NOT FIXED...help
I still can't connect to IPFS API through Desktop app...and do not know how to fix/correct?
/ip4/127.0.0.1/tcp/5001
as the API address and see if that helps?combined.log
I tried adding suggested API address, but Desktop app kept crashing. I see an alert to update to v20. Will download/install and hope that corrects issue.
Hello. Downloaded/installed v20. No luck. Desktop app still crashes. Seems to be a SIGABRT abort going on...don't understand what that means or how to correct issue. Attaching logs. Sorry this remains an issue, but I still need help. I don't know what I don't know…ya know? combined copy.log
Thank you @MattJohnsonMusic
Segmentation fault: 11
seems to be a popular class of problems with Mac OS X 10
.
Unfortunately, I am unable to reproduce, and we're officially supporting only macOS 11 and 12 I think.
Are you able to update to a more modern version of macOS and see if that solves the problem?
DRATS! My workhorse computer is still functional for my audio/video needs, and I don't think I can update the OS anymore. My older hardware doesn't have the latest/greatest graphic card (or something). • If I'm receiving a SIGABORT and Desktop App won't install because it's being aborted, is that on MY side, or on the Installer side? • If on my side, HOW do I correct/give permission/find the problem and manually configure? • The Desktop App IS installed, it just can't find the IPFS API. Is there some hidden file I can BBedit and fix?
• I'm REALLY wanting to run a node and keep all my assets pinned, etc. Gotta figure this out.
Thanks for your continued help, Matt
I noticed you are using macOS 10.x? I think the latest one is 11 or 12 – any chance you can update and confirm if issue occurs on the latest macOS?
I really want to upgrade my OS, but Apple won't let me, because I'm too poor to get into the Apple ecosystem. 😭
A wise man once said, "If you want to keep driving an old car, you have to learn about it and how to maintain it.
", so my older colleague said ... ... So, I did some digging. I mean a lot.
My current solution is to install and update IPFS via ipfs-update and use the go-ipfs WebUI for the user interface.
Yes, the command-line stuff. There were some issues, but once they were solved it works like a charm.
ipfs
command:
- `ipfs-update install v0.12.0`
1. Copy the backup data to `~/.ipfs/`.
1. Run the IPFS daemon in the background:
- `$ ipfs daemon --enable-gc --init --migrate &`
- Note the `&` at the end. It lets run the IPFS even closing with `ctrl+c` after the daemon is ready.
- After the daemon is ready, check the URL of the "WebUI:" section of the displayed log. It should be something like: `http://127.0.0.1:5001/webui`. When you open this URL in your browser, **you will see the same interface as the familiar IPFS desktop**.
- Note also that this command must be executed every time the operating system is restarted.
## Notes
- [IMPORTANT] If the **OS is Mojave (macOS 10.14) or later**, you need to give "full disk access" to `terminal.app`.
- In the System Preferences, open [Security and Privacy]-[Privacy]-[Full Disk Access]. After unlocking, add the `terminal` application from the "utilities" folder to the list via the `+` button.
- Do not use `brew` on older macOS. Especially on High Sierra.
- **Always backup** the IPFS data directory such as `~/.ipfs` in your home directory.
- `ls -la ~`
- This will display the directories below the user's home directory, including hidden directories.
- To make sure that the IPFS data directory is set as the default, do the following:
- `echo $IPFS_PATH`
- This will print the configured data directory path. If nothing appears then the path of the data will be `~/.ipfs`. The default path.
- If the IPFS daemon fails to boot, try:
1. Check if `IPFS_PATH` is not set. (See the above)
1. Remove the `~/.ipfs` directory and initialize by `ipfs init`.
- To check if the `ipfs daemon` is running in the background run:
- `ps aux | grep ipfs`
- This will print the current process info that contains `ipfs`. It should display 2 entries. The one with `ipfs daemon --enabl...` is the daemon running in the background. What you need is the 2nd column's number, which is the `PID`(process ID).
- To shutdown the IPFS daemon running in the background run:
- `kill Wow, thank you VERY much for all of this work. I will give this a try over the weekend and check back in. Crossing fingers. Peace, Matt
Okay...going to give all this a try today…wish me luck!
YIPPEE!!
After deleting some hidden files (thanks to above pointers), I tried installing the newest IPFS Desktop App...and it worked! At least for now. I did not have to jump through all the above hoops (yet), but REALLY appreciate the time given to help me. I can follow directions line-by-line pretty well, so thanks.
I really hope I don't have this issue again with upgrades. Thank you, thank you. Matt
I will close this as it seems to be fixed for you. For anyone reading this in the future, there seems to be a bug causing a similar error: #2000.
Seems that the Segmentation fault: 11
is back, we continue in https://github.com/ipfs/ipfs-desktop/issues/2038#issuecomment-1077186579
Trying to get out of recent Restart loop in earlier IPFS Desktop version, now version 0.19.3 crashes app. I'm not able to rejoin IPFS via Desktop app. I'm long time Mac-based End User, and not into programming or using Terminal to correct. Help, please?