[
https://issues.apache.org/jira/browse/AURORA-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176946#comment-14176946
]
Mark Chu-Carroll commented on AURORA-847:
-----------------------------------------
Trying to get more info for this: wiped all of my vagrant images and started
fresh. In the latest run, I extracted the stderr from the thermos workspace of
the instance:
{noformat}
vagrant@192:/var/lib/mesos/slaves/20141020-141831-119646400-5050-14106-0/frameworks/20141020-141831-119646400-5050-14106-0000/executors/thermos-1413815692462-vagrant-test-http_example-0-49ebd095-a0d0-4f95-88c1-98442a078883/runs/latest$
more stderr
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1020 14:34:52.525929 16059 fetcher.cpp:76] Fetching URI '/home/vagrant/aurora/d
ist/thermos_executor.sh'
I1020 14:34:52.526244 16059 fetcher.cpp:179] Copying resource from '/home/vagran
t/aurora/dist/thermos_executor.sh' to '/var/lib/mesos/slaves/20141020-141831-119
646400-5050-14106-0/frameworks/20141020-141831-119646400-5050-14106-0000/executo
rs/thermos-1413815692462-vagrant-test-http_example-0-49ebd095-a0d0-4f95-88c1-984
42a078883/runs/13649197-b3e3-47a9-969a-f152186431e4'
./thermos_executor.sh: line 2: /home/vagrant/aurora/dist/thermos_executor.pex: P
ermission denied
./thermos_executor.sh: line 2: exec: /home/vagrant/aurora/dist/thermos_executor.
pex: cannot execute: Permission denied
vagrant@192:/var/lib/mesos/slaves/20141020-141831-119646400-5050-14106-0/frameworks/20141020-141831-119646400-5050-14106-0000/executors/thermos-1413815692462-vagrant-test-http_example-0-49ebd095-a0d0-4f95-88c1-98442a078883/runs/latest$
vagrant@192:/var/lib/mesos/slaves/20141020-141831-119646400-5050-14106-0/frameworks/20141020-141831-119646400-5050-14106-0000/executors/thermos-1413815692462-vagrant-test-http_example-0-49ebd095-a0d0-4f95-88c1-98442a078883/runs/latest$
{noformat}
Looking at thermos_executor.pex in the virtual machine, it's mode 644. Manually
chmod'ing thermos_executor.pex to make it executable isn't sufficient; it
results in a new error:
{noformat}
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1020 14:45:57.017156 17237 fetcher.cpp:76] Fetching URI
'/home/vagrant/aurora/dist/thermos_executor.sh'
I1020 14:45:57.017457 17237 fetcher.cpp:179] Copying resource from
'/home/vagrant/aurora/dist/thermos_executor.sh' to
'/var/lib/mesos/slaves/20141020-141831-119646400-5050-14106-0/frameworks/20141020-141831-119646400-5050-14106-0000/executors/thermos-1413816350358-vagrant-test-http_example-1-89bbd100-31e7-4014-9725-c81fda69b43c/runs/1930ea4f-fa34-491c-beff-db6077ee0188'
./thermos_executor.sh: line 2: /home/vagrant/aurora/dist/thermos_executor.pex:
cannot execute binary file: Exec format error
./thermos_executor.sh: line 2: /home/vagrant/aurora/dist/thermos_executor.pex:
Success
{noformat}
Has anyone actually successfully run anything on the vagrant cluster lately?
Unless I'm missing something, this means that the vagrant provisioning script
is completely botching the setup, and it's impossible to run anything under
thermos using it.
> Executor error causing end-to-end task failures
> -----------------------------------------------
>
> Key: AURORA-847
> URL: https://issues.apache.org/jira/browse/AURORA-847
> Project: Aurora
> Issue Type: Bug
> Components: Executor, Testing
> Reporter: Mark Chu-Carroll
>
> When running the end-to-end tests, both restart and update commands fail,
> with no useful information returned from the server.
> Checking the status of the job shows many repetitions of:
> {noformat}
> Task:
> cpus: 0.5, ram: 32 MB, disk: 64 MB
> ports: {'http': 31734}
> failure count: 0 (max 1)
> events:
> 2014-10-16 15:48:58 PENDING: None
> 2014-10-16 15:49:00 ASSIGNED: None
> 2014-10-16 15:49:02 LOST: Executor terminated
> {noformat}
> Trying to check the logs produces nothing: there are no logs in /var/log
> about any events in aurora or mesos relating to the executor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
