Closed Bug 1344550 Opened 8 years ago Closed 8 years ago

Failed to start script 'lineman run' while building the balrog-ui container

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: anjul.ten, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce: -> Ran 'docker-compose up' Actual results: Balrog Admin UI doesn't work at port: 8080. The port 9090 is working however This is the log """ info start balrog-ui@0.0.1 7 verbose unsafe-perm in lifecycle true 8 info balrog-ui@0.0.1 Failed to exec start script 9 verbose stack Error: balrog-ui@0.0.1 start: `lineman run` 9 verbose stack spawn ENOENT 9 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:17:16) 9 verbose stack at ChildProcess.emit (events.js:98:17) 9 verbose stack at maybeClose (child_process.js:766:16) 9 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:833:5) 10 verbose pkgid balrog-ui@0.0.1 11 verbose cwd /app 12 error Linux 3.13.0-108-generic 13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 14 error node v0.10.48 15 error npm v2.15.1 16 error file sh 17 error code ELIFECYCLE 18 error errno ENOENT 19 error syscall spawn 20 error balrog-ui@0.0.1 start: `lineman run` 20 error spawn ENOENT 21 error Failed at the balrog-ui@0.0.1 start script 'lineman run'. 21 error This is most likely a problem with the balrog-ui package, 21 error not with npm itself. 21 error Tell the author that this fails on your system: 21 error lineman run 21 error You can get information on how to open an issue for this project with: 21 error npm bugs balrog-ui 21 error Or if that isn't available, you can get their info via: 21 error 21 error npm owner ls balrog-ui 21 error There is likely additional logging output above. 22 verbose exit [ 1, true ] """
The complete log looks like this: balrogui_1 | npm WARN unmet dependency /app/node_modules/lineman/node_modules/express requires commander@'1.2.0' but will load balrogui_1 | npm WARN unmet dependency /app/node_modules/lineman/node_modules/commander, balrogui_1 | npm WARN unmet dependency which is version 1.3.2 balrogui_1 | npm WARN unmet dependency /app/node_modules/lineman/node_modules/fetcher requires coffee-script@'^1.7.1' but will load balrogui_1 | npm WARN unmet dependency /app/node_modules/lineman/node_modules/coffee-script, balrogui_1 | npm WARN unmet dependency which is version 1.6.3 balrogui_1 | balrogui_1 | > balrog-ui@0.0.1 start /app balrogui_1 | > lineman run balrogui_1 | balrogui_1 | sh: 1: lineman: not found balrogui_1 | balrogui_1 | npm ERR! Linux 3.13.0-108-generic balrogui_1 | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" balrogui_1 | npm ERR! node v0.10.48 balrogui_1 | npm ERR! npm v2.15.1 balrogui_1 | npm ERR! file sh balrogui_1 | npm ERR! code ELIFECYCLE balrogui_1 | npm ERR! errno ENOENT balrogui_1 | npm ERR! syscall spawn balrogui_1 | npm ERR! balrog-ui@0.0.1 start: `lineman run` balrogui_1 | npm ERR! spawn ENOENT balrogui_1 | npm ERR! balrogui_1 | npm ERR! Failed at the balrog-ui@0.0.1 start script 'lineman run'. balrogui_1 | npm ERR! This is most likely a problem with the balrog-ui package, balrogui_1 | npm ERR! not with npm itself. balrogui_1 | npm ERR! Tell the author that this fails on your system: balrogui_1 | npm ERR! lineman run balrogui_1 | npm ERR! You can get information on how to open an issue for this project with: balrogui_1 | npm ERR! npm bugs balrog-ui balrogui_1 | npm ERR! Or if that isn't available, you can get their info via: balrogui_1 | npm ERR! balrogui_1 | npm ERR! npm owner ls balrog-ui balrogui_1 | npm ERR! There is likely additional logging output above. balrogui_1 | balrogui_1 | npm ERR! Please include the following file with any support request: balrogui_1 | npm ERR! /app/npm-debug.log balrog_balrogui_1 exited with code 1 balrogagent_1 | 2017-03-05 14:26:32,352 - DEBUG - root.run_agent#25: Looking for active scheduled changes for endpoint rules... balrogagent_1 | 2017-03-05 14:26:32,352 - DEBUG - root.request#31: Sending GET request to http://balrogadmin:7070/api/scheduled_changes/rules balrogagent_1 | 2017-03-05 14:26:32,358 - ERROR - root.run_agent#66: Encountered exception: balrogagent_1 | Traceback (most recent call last): balrogagent_1 | File "/usr/local/lib/python3.5/site-packages/aiohttp/connector.py", line 607, in _create_connection balrogagent_1 | local_addr=self._local_addr) balrogagent_1 | File "/usr/local/lib/python3.5/asyncio/base_events.py", line 775, in create_connection balrogagent_1 | raise exceptions[0] balrogagent_1 | File "/usr/local/lib/python3.5/asyncio/base_events.py", line 762, in create_connection balrogagent_1 | yield from self.sock_connect(sock, address) balrogagent_1 | File "/usr/local/lib/python3.5/asyncio/selector_events.py", line 451, in sock_connect balrogagent_1 | return (yield from fut) balrogagent_1 | File "/usr/local/lib/python3.5/asyncio/futures.py", line 380, in __iter__ balrogagent_1 | yield self # This tells Task to wait for completion. balrogagent_1 | File "/usr/local/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup balrogagent_1 | future.result() balrogagent_1 | File "/usr/local/lib/python3.5/asyncio/futures.py", line 293, in result balrogagent_1 | raise self._exception balrogagent_1 | File "/usr/local/lib/python3.5/asyncio/selector_events.py", line 481, in _sock_connect_cb balrogagent_1 | raise OSError(err, 'Connect call failed %s' % (address,)) balrogagent_1 | ConnectionRefusedError: [Errno 111] Connect call failed ('172.17.0.4', 7070) balrogagent_1 | balrogagent_1 | The above exception was the direct cause of the following exception: balrogagent_1 | balrogagent_1 | Traceback (most recent call last): balrogagent_1 | File "/usr/local/lib/python3.5/site-packages/aiohttp/connector.py", line 321, in connect balrogagent_1 | yield from self._create_connection(req) balrogagent_1 | File "/usr/local/lib/python3.5/site-packages/aiohttp/connector.py", line 630, in _create_connection balrogagent_1 | (req.host, req.port, exc.strerror)) from exc balrogagent_1 | aiohttp.errors.ClientOSError: [Errno 111] Can not connect to balrogadmin:7070 [Connect call failed ('172.17.0.4', 7070)] balrogagent_1 | balrogagent_1 | The above exception was the direct cause of the following exception: balrogagent_1 | balrogagent_1 | Traceback (most recent call last): balrogagent_1 | File "/app/balrogagent/cmd.py", line 28, in run_agent balrogagent_1 | auth=auth, loop=loop) balrogagent_1 | File "/app/balrogagent/client.py", line 32, in request balrogagent_1 | resp = await aiohttp.request(method, url, data=json.dumps(data), headers=headers, auth=auth, loop=loop) balrogagent_1 | File "/usr/local/lib/python3.5/site-packages/aiohttp/client.py", line 585, in __await__ balrogagent_1 | return (yield from self._coro) balrogagent_1 | File "/usr/local/lib/python3.5/site-packages/aiohttp/client.py", line 186, in _request balrogagent_1 | conn = yield from self._connector.connect(req) balrogagent_1 | File "/usr/local/lib/python3.5/site-packages/aiohttp/connector.py", line 331, in connect balrogagent_1 | .format(key, exc.strerror)) from exc balrogagent_1 | aiohttp.errors.ClientOSError: [Errno 111] Cannot connect to host balrogadmin:7070 ssl:False [Can not connect to balrogadmin:7070 [Connect call failed ('172.17.0.4', 7070)]]
Also, I don't have any usr/local/lib/python3.5 directory in my pc. I installed python3.5 to work alongside python3.4 and I run python3.5 with the command py3.5. How can I make balrog use python3.4 instead of python3.5?
(In reply to Anjul Tyagi from comment #2) > Also, I don't have any usr/local/lib/python3.5 directory in my pc. I > installed python3.5 to work alongside python3.4 and I run python3.5 with the > command py3.5. How can I make balrog use python3.4 instead of python3.5? You don't need any particular Python version locally, everything runs in Docker containers. It looks to me like the root problem here is that "lineman" is not getting installed when the balrog-ui container starts up. Could you try removing ui/node_modules, and running "docker-compose up" again?
Flags: needinfo?(anjul.ten)
it worked, thanks !! However, I'm still getting that other exception related to "balrogagent" service. It seems that this exception is frequent while building Balrog, as today it was also mentioned in Bug: 1343255.
Flags: needinfo?(anjul.ten) → needinfo?(bhearsum)
(In reply to Anjul Tyagi from comment #4) > it worked, thanks !! However, I'm still getting that other exception related > to "balrogagent" service. It seems that this exception is frequent while > building Balrog, as today it was also mentioned in Bug: 1343255. That exception is totally normal while the containers are still starting up. If you can access https://localhost:8080 within a few minutes of running "docker-compose up", everything is fine.
Flags: needinfo?(bhearsum)
yes, I figured that out later when I was trying to run "localhost:8080/api" and it showed connection error but later it worked. Thanks.
Okay, let's close this bug out then!
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.