New issue
Advanced search Search tips

Issue 924417 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Today
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Goma failed to update

Project Member Reported by fergal@chromium.org, Today (100 minutes ago)

Issue description

I tried to compile but goma was not running. So I ran ensure_start and got this stack trace.

$@ ${GOMA_DIR}/goma_ctl.py ensure_start
using /run/user/10143/goma_fergal as tmpdir
new goma client found (VERSION=167).
Updating...
using /run/user/10143/goma_fergal as tmpdir
Downloaded package is already the latest version.
Extracting package to /usr/local/google/home/fergal/goma/update ...
All files verified.
Stopping compiler_proxy ...
Killing compiler proxy.
compiler proxy status:  goma is not running.
Updating package to /usr/local/google/home/fergal/goma ...
Failed to update. Rollback...
cannot access backuped file: [Errno 2] No such file or directory: '/usr/local/google/home/fergal/goma/backup/goma'Traceback (most recent call last):
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 2700, in <module>
    sys.exit(main())
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 2695, in main
    goma.Dispatch(sys.argv[1:])
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 1181, in Dispatch
    self._action_mappings.get(args[0], self._DefaultAction)()
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 845, in _Update
    self._UpdatePackage()
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 831, in _UpdatePackage
    self._UpdateManifest()
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 514, in _UpdateManifest
    self._env.WriteManifest(self._manifest)
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 1275, in WriteManifest
    with open(manifest_path, 'w') as manifest_file:
IOError: [Errno 13] Permission denied: '/usr/local/google/home/fergal/goma/MANIFEST'
Traceback (most recent call last):
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 2700, in <module>
    sys.exit(main())
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 2695, in main
    goma.Dispatch(sys.argv[1:])
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 1181, in Dispatch
    self._action_mappings.get(args[0], self._DefaultAction)()
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 687, in _EnsureStartCompilerProxy
    self._GenericStartCompilerProxy(ensure=True)
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 618, in _GenericStartCompilerProxy
    self._env.AutoUpdate()
  File "/usr/local/google/home/fergal/goma/goma_ctl.py", line 1850, in AutoUpdate
    subprocess.check_call(['python', script, 'update'])
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['python', '/usr/local/google/home/fergal/goma/goma_ctl.py', 'update']' returned non-zero exit status 1


I can see

$@ ls -l /usr/local/google/home/fergal/goma/MANIFEST
-r-------- 1 fergal primarygroup 30 Dec 31  1979 /usr/local/google/home/fergal/goma/MANIFEST


 

Comment 1 by fergal@chromium.org, Today (99 minutes ago)

Running it a second time, it worked. I'm pretty sure this is what has happened several times in the last few months. The auto-update doesn't seem to be quite auto.

Comment 2 by ukai@google.com, Today (84 minutes ago)

I believe it is fixed by https://chrome-internal-review.googlesource.com/c/715573

what version did you use before update?

Comment 3 by fergal@chromium.org, Today (70 minutes ago)

Is there an way to find out what version it was?

Comment 4 by ukai@google.com, Today (33 minutes ago)

backup/MANIFEST file?

Comment 5 by fergal@chromium.org, Today (32 minutes ago)

$@ cat /usr/local/google/home/fergal/goma/backup/MANIFEST 
VERSION=163
PLATFORM=goobuntu

Comment 6 by ukai@google.com, Today (29 minutes ago)

Status: WontFix (was: Untriaged)
I think that's buggy version.
better to re-install again if version is older than 166.

Sign in to add a comment