jemgold
commented
9 years ago I've been having some problems getting paz-web running locally recently - I think it might be linked. Will look into it and get back to you - thanks.
Closed thecatwasnot closed 9 years ago
jemgold
commented
9 years ago I've been having some problems getting paz-web running locally recently - I think it might be linked. Will look into it and get back to you - thanks.
thecatwasnot
commented
9 years ago Thanks.
lukebond
commented
9 years ago Hey @thecatwasnot, thanks so much for such a detailed issue posting, it's really really helpful.
I concur with @jongold that the "something went wrong :(" is most likely an instance of paz-sh/paz-web#3 (fix incoming). But your logs helpfully highlight a few other issues:
./integration.sh Starting Paz integration test script ./integration.sh: line 18: checkRequiredEnvVars: command not found
^ my bad during 2cdec8fa6c4015834e5eecdf4c10e5f986e3a939. Created #38.
Regarding waiting a long time for the service to announce itself, that also is an issue. Do you know if it actually worked but the script failed to detect that it had, or if the service never came up, and if so why?
thecatwasnot
commented
9 years ago It appears demo-api is not up:
core@core-01 ~ $ fleetctl list-units
UNIT MACHINE ACTIVE SUB
demo-api-1-1.service 84797605.../172.17.8.102 inactive dead
demo-api-1-2.service 3897eec3.../172.17.8.103 inactive dead
demo-api-1-3.service 457ac316.../172.17.8.101 inactive dead
demo-api-announce-1-1.service 84797605.../172.17.8.102 inactive dead
demo-api-announce-1-2.service 457ac316.../172.17.8.101 inactive dead
demo-api-announce-1-3.service 3897eec3.../172.17.8.103 inactive dead
paz-orchestrator-announce.service 3897eec3.../172.17.8.103 active running
paz-orchestrator.service 3897eec3.../172.17.8.103 active running
paz-scheduler-announce.service 457ac316.../172.17.8.101 active running
paz-scheduler.service 457ac316.../172.17.8.101 active running
paz-service-directory-announce.service 84797605.../172.17.8.102 active running
paz-service-directory.service 84797605.../172.17.8.102 active running
paz-web-announce.service 3897eec3.../172.17.8.103 active running
paz-web.service 3897eec3.../172.17.8.103 active running
core@core-01 ~ $ fleetctl status demo-api-1-2.service
● demo-api-1-2.service - Very simple HTTP Hello World server (2)
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Mar 11 01:48:01 core-01 systemd[1]: [/run/fleet/units/demo-api-1-2.service:8] Executable path is not absolute, ignoring: "/usr/bin/docker run --name=demo-api-1-2 -P lukebond/demo-api"
Mar 11 01:48:01 core-01 systemd[1]: demo-api-1-2.service has no ExecStart= setting, which is only allowed for RemainAfterExit=yes services. Refusing.
Mar 11 01:48:02 core-01 systemd[1]: [/run/fleet/units/demo-api-1-2.service:8] Executable path is not absolute, ignoring: "/usr/bin/docker run --name=demo-api-1-2 -P lukebond/demo-api"
Mar 11 01:48:02 core-01 systemd[1]: demo-api-1-2.service has no ExecStart= setting, which is only allowed for RemainAfterExit=yes services. Refusing.
Mar 11 01:48:03 core-01 systemd[1]: [/run/fleet/units/demo-api-1-2.service:8] Executable path is not absolute, ignoring: "/usr/bin/docker run --name=demo-api-1-2 -P lukebond/demo-api"
Mar 11 01:48:03 core-01 systemd[1]: demo-api-1-2.service has no ExecStart= setting, which is only allowed for RemainAfterExit=yes services. Refusing.
Mar 11 01:48:04 core-01 systemd[1]: [/run/fleet/units/demo-api-1-2.service:8] Executable path is not absolute, ignoring: "/usr/bin/docker run --name=demo-api-1-2 -P lukebond/demo-api"
Mar 11 01:48:04 core-01 systemd[1]: demo-api-1-2.service has no ExecStart= setting, which is only allowed for RemainAfterExit=yes services. Refusing.
Mar 11 01:48:04 core-01 systemd[1]: [/run/fleet/units/demo-api-1-2.service:8] Executable path is not absolute, ignoring: "/usr/bin/docker run --name=demo-api-1-2 -P lukebond/demo-api"
Mar 11 01:48:04 core-01 systemd[1]: demo-api-1-2.service has no ExecStart= setting, which is only allowed for RemainAfterExit=yes services. Refusing.
core@core-01 ~ $ fleetctl status demo-api-announce-1-3.service
● demo-api-announce-1-3.service - Very simple HTTP Hello World server announce (3)
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Mar 11 01:51:06 core-01 systemd[1]: [/run/fleet/units/demo-api-announce-1-3.service:7] Executable path is not absolute, ignoring: "/bin/sh -c \"until docker inspect -f '{{range $p, $conf := .NetworkSettings.Ports}} {{$p}} -> {{(index $conf 0).HostPort}} {{end}}' demo-api-1-3 >/dev/null 2>&1
Mar 11 01:51:06 core-01 systemd[1]: demo-api-announce-1-3.service lacks both ExecStart= and ExecStop= setting. Refusing.
Mar 11 01:51:07 core-01 systemd[1]: [/run/fleet/units/demo-api-announce-1-3.service:7] Executable path is not absolute, ignoring: "/bin/sh -c \"until docker inspect -f '{{range $p, $conf := .NetworkSettings.Ports}} {{$p}} -> {{(index $conf 0).HostPort}} {{end}}' demo-api-1-3 >/dev/null 2>&1
Mar 11 01:51:07 core-01 systemd[1]: demo-api-announce-1-3.service lacks both ExecStart= and ExecStop= setting. Refusing.
Mar 11 01:51:08 core-01 systemd[1]: [/run/fleet/units/demo-api-announce-1-3.service:7] Executable path is not absolute, ignoring: "/bin/sh -c \"until docker inspect -f '{{range $p, $conf := .NetworkSettings.Ports}} {{$p}} -> {{(index $conf 0).HostPort}} {{end}}' demo-api-1-3 >/dev/null 2>&1
Mar 11 01:51:08 core-01 systemd[1]: demo-api-announce-1-3.service lacks both ExecStart= and ExecStop= setting. Refusing.
Mar 11 01:51:09 core-01 systemd[1]: [/run/fleet/units/demo-api-announce-1-3.service:7] Executable path is not absolute, ignoring: "/bin/sh -c \"until docker inspect -f '{{range $p, $conf := .NetworkSettings.Ports}} {{$p}} -> {{(index $conf 0).HostPort}} {{end}}' demo-api-1-3 >/dev/null 2>&1
Mar 11 01:51:09 core-01 systemd[1]: demo-api-announce-1-3.service lacks both ExecStart= and ExecStop= setting. Refusing.
Mar 11 01:51:10 core-01 systemd[1]: [/run/fleet/units/demo-api-announce-1-3.service:7] Executable path is not absolute, ignoring: "/bin/sh -c \"until docker inspect -f '{{range $p, $conf := .NetworkSettings.Ports}} {{$p}} -> {{(index $conf 0).HostPort}} {{end}}' demo-api-1-3 >/dev/null 2>&1
Mar 11 01:51:10 core-01 systemd[1]: demo-api-announce-1-3.service lacks both ExecStart= and ExecStop= setting. Refusing.@thecatwasnot could you please post the output of fleetctl cat demo-api-1-1.service?
thecatwasnot
commented
9 years ago fleetctl cat demo-api-1-1.service
[Unit]
Requires=docker.service
After=docker.service
Description=Very simple HTTP Hello World server (1)
[Service]
ExecStartPre=/bin/bash -c "docker pull lukebond/demo-api && docker inspect demo-api-1-1 >/dev/null 2>&1 && docker rm -f demo-api-1-1 || true"
ExecStart="/usr/bin/docker run --name=demo-api-1-1 -P lukebond/demo-api"
ExecStop=/usr/bin/docker stop -t 3 demo-api-1-1
TimeoutStartSec=30m
[X-Fleet]
X-Conflicts=demo-api-1*.serviceThanks agagin @thecatwasnot. Created scheduler issue paz-sh/paz-scheduler#3
thecatwasnot
commented
9 years ago Awesome, will close this then.
Hi guys, I attempted to bring up a vagrant cluster last night and the paz-web.paz dashboard failed with the above message. I know very little about javascript/ember so I'm not sure how much more debugging I can do, I'm not even sure where to start at this point.
I started it up with:
I did edit /etc/hosts fleet reports everything OK:
This morning I tried running the integration test:
Which hung for hours (was still waiting when I returned 8 hours later) I've now also tried changing my version of etcdctl to match the one on coreos and no joy.