Update not working, com.github.atom.ShipIt respawns all the time


#1

I was told there is an update and I had to enter my admin credentials. I selected Restart and Install Update from the menu. Atom quit yet nothing else has happened (automatic update never worked for me since the first day I downloaded Atom, but I keep trying with every new release).

I look into the Console and get the following two lines every two seconds

2014-05-29 14:06:03,758 com.apple.launchd[1]: (com.github.atom.ShipIt[1110]) Exited with code: 1
2014-05-29 14:06:03,758 com.apple.launchd[1]: (com.github.atom.ShipIt) Throttling respawn: Will start in 2 seconds

In my Library folder I found the following file:
Application Support/com.github.atom.ShipIt/ShipIt_stderr.log

and it says:

2014-05-29 14:14:41.173 ShipIt[1405:60f] Installation error: Error Domain=SQRLShipItRequestErrorDomain Code=2 "Could not read update request" UserInfo=0x7fbbf941a630 {NSLocalizedDescription=Could not read update request, NSUnderlyingError=0x7fbbf9506770 "The file “ShipItState.plist” couldn’t be opened because there is no such file."}
2014-05-29 14:14:41.174 ShipIt[1405:60f] ShipIt quitting

This also repeats every two seconds.

Just in case, the following may be relevant: All my apps in /Applications are owned by root:wheel, this is for security reasons. If they were owned by my user, any process would be able to modified the installed apps there (patch them, hack them, …) and I saw apps from the AppStore also had that ownership. Some apps have issues with that as they assume the current user can modify the installed app directly.

And in case someone has the same issue and want to stop the console spamming, try this:

sudo launchctl remove com.github.atom.ShipIt

Com.github.atom.ShipIt is using 10 GB of space
#2

Which version of Atom are you running? There was a bug in the auto-update at one point and you need to manually update to a version past that one for auto-update to work.


#3

As I said (that wasn’t meant as a joke): “automatic update never worked for me since the first day I downloaded Atom, but I keep trying with every new release”.

And the first version was 0.96, IIRC. So I had this issue with 0.96, 0.97, 0.98 and I’m currently using 0.99. Today I tried the update for 0.100 and got exactly the same issue.

Maybe also of interest:

  • I get the console spamming as soon as I type in my password, I don’t have to select Restart and Install Update first.

  • I get exactly the same issue on two different Macs (a MacBook Pro and a Mac Mini), so it is not device specific or bound to a broken setup on my Mac (the HD content of those two machines has not been cloned, both were set up from scratch).


#4

Exit Atom and try this:

$ rm -rf ~/Library/Application\ Support/com.github.atom.ShipIt

Then restart Atom and see if that fixes it.


#5

Tried that, no difference. Once there is an update, the service starts and keeps respawning all the time.


#6

There was a bug at one point that builds prior to v0.103.0, I think, wouldn’t update properly. Download the latest from the website, install manually and then try the update when the next version comes out.


#7

I did download the latest version manually not so long ago (must have been 0.105.0 or 0.106.0) , also deleting the AppSupport com.github.atom.ShipIt folder. Today I got the update for 0.107.0 and the behavior is exactly the same as before. Why can’t it find the file ShipItState.plist? This is what the whole error is all about. Where should it be and why isn’t it there?


#8

It’s right there in ~/Library/Application Support/com.github.atom.ShipIt:

$ ll ~/Library/Application\ Support/com.github.atom.ShipIt
total 40
-rw-r--r--  1 Lee  staff   261B Jun  9 18:25 ShipItState.plist
-rw-r--r--  1 Lee  staff    14K Jun  9 18:25 ShipIt_stderr.log
-rw-r--r--  1 Lee  staff     0B Apr 24 08:30 ShipIt_stdout.log

It could be that your permissions there are wrong?


#9

Right now this folder is empty, as I did delete it before installing 0.108.0 manually. Seems like starting Atom re-creates the folder but not the content. It seems the content is only re-created once there is an update, so I will have a look again as soon as 0.109.0 is released. The folder itself is drwxr-xr-x which seems fine to me.


#10

0.109 is out and the issue is back again. Again the same error message:

2014-07-08 16:30:42.849 ShipIt[2784:60f] Installation error: Error Domain=SQRLShipItRequestErrorDomain Code=2 "Could not read update request" UserInfo=0x7fc5ba428cf0 {NSLocalizedDescription=Could not read update request, NSUnderlyingError=0x7fc5ba426d80 "The file “ShipItState.plist” couldn’t be opened because there is no such file."}

taken from the file

~/Library/Application Support/com.github.atom.ShipIt/ShipIt_stderr.log

which keeps growing and growing.

The plist file is there (same folder as ShipIt_stderr.log):

-rw-r--r--  1 me  staff   251B Jul  8 16:29 ShipItState.plist

The content is:

{"launchAfterInstallation":0,"updateBundleURL":"file:\/\/\/Users\/me\/Library\/Application%20Support\/com.github.atom.ShipIt\/update.xtgTUqU\/Atom.app\/","bundleIdentifier":"com.github.atom","targetBundleURL":"file:\/\/\/Applications\/Atom.app"}

BTW update.xtgTUqU is also there, same folder and it contains a brand new Atom.app.

Running sudo launchctl list com.github.atom.ShipIt tells me:

{
    "Label" = "com.github.atom.ShipIt";
    "LimitLoadToSessionType" = "System";
    "OnDemand" = true;
    "LastExitStatus" = 256;
    "TimeOut" = 30;
    "StandardOutPath" = "/Users/me/Library/Application Support/com.github.atom.ShipIt/ShipIt_stdout.log";
    "StandardErrorPath" = "/Users/me/Library/Application Support/com.github.atom.ShipIt/ShipIt_stderr.log";
    "ProgramArguments" = (
        "/Applications/Atom.app/Contents/Frameworks/Squirrel.framework/Resources/ShipIt";
        "com.github.atom.ShipIt";
    );
    "MachServices" = {
        "com.github.atom.ShipIt" = mach-port-object;
    };
};

So please tell me: What’s the problem here?


#11

I have no idea …

@ProbablyCorey Can someone take a look at this?


#12

This issue looks similar to https://github.com/atom/atom/issues/2860. @Mecki78, if you think this problem merits a separate issue could you open one on github.com/atom/atom/issues


#13

I’ve been having this issue too, and in addition I’m pretty sure it’s causing chaos with launchd.


#14

I’m having the same issue on 10.10.2.

Service only ran for 0 seconds. Push respond out by 2 seconds.
Service exited with abnormal code: 1

This is getting fire pretty much every second in system.log.


#15

I’m still encountering this issue with version 1.0.2 on Yosemite 10.10.4.

I completely removed the app, and reinstalled from a fresh download—the log messages resumed as soon as I launched.


#16

I’m on OS X 10.10.4, and just updated 1.0.2 to 1.0.3.

I’ve had the same issue as above since I started using Atom back in the early 0.x versions. On a hunch after reading through the comments above, I changed the ownership of all of the files in Atom’s ShipIt workspace to MY_USER:staff. Atom immediately reopened with 1.0.3 properly installed. ¯\_(ツ)_/¯

Some details:

ls -alh '/Users/jmanero/Library/Application Support/com.github.atom.ShipIt/'
total 313656
drwxr-xr-x   7 jmanero  staff   238B Jul 28 22:14 .
drwx------+ 40 jmanero  staff   1.3K Jul 28 22:07 ..
-rw-r--r--   1 jmanero  staff   250B Jul 28 22:14 ShipItState.plist
-rw-r--r--   1 root     staff   306M Mar 13 11:57 ShipIt_stderr.log
-rw-r--r--   1 root     staff     0B Aug 19  2014 ShipIt_stdout.log
drwx------   3 jmanero  staff   102B Jul 28 22:08 update.P1Z4tK1
drwx------   3 jmanero  staff   102B Jul 28 22:14 update.jMboSxH

jmanero@DixieFlatline: ~/workspace/unbound-build $ sudo chown jmanero:staff '/Users/jmanero/Library/Application Support/com.github.atom.ShipIt/'*

jmanero@DixieFlatline: ~/workspace/unbound-build $ ls -alh '/Users/jmanero/Library/Application Support/com.github.atom.ShipIt/'
total 313656
drwxr-xr-x   7 jmanero  staff   238B Jul 28 22:14 .
drwx------+ 40 jmanero  staff   1.3K Jul 28 22:07 ..
-rw-r--r--   1 jmanero  staff   250B Jul 28 22:14 ShipItState.plist
-rw-r--r--   1 jmanero  staff   306M Jul 28 22:16 ShipIt_stderr.log
-rw-r--r--   1 jmanero  staff     0B Aug 19  2014 ShipIt_stdout.log
drwx------   3 jmanero  staff   102B Jul 28 22:08 update.P1Z4tK1
drwx------   3 jmanero  staff   102B Jul 28 22:14 update.jMboSxH

My guess is that the updater was unable to open its log files, and simply hung/crashed…

– cheers


#17

Thank you so much for this post. This issue was driving me nuts. Your solution worked as a charm! :smile:


#18

Thank you! After a year of no auto-update, this solved my problem :smiley:


#19

This looks ilke a solution, but my solution unfortunately was to simply remove Atom. I was spending more time faffing around broken things with Atom than spending time fixing my own broken things. I’ve since moved on to another editor, which does the job fine.


#20

We’re now in 2017, I am running macOS Sierra 10.12.3 and just installed Atom
Atom : 1.14.1
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0

I just noticed that my console was heavily polluted by that re-spawing of git.com.github.atom.ShipIt

Thank you for the service disabling tip!!