obfuscurity / obfuscurity/backstop

Backstop on Debian Wheezy 7.7

Open
#23 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
296
Forks
33
PR merge metrics
No merged PRs in 30d

Description

Hi Guys,

When I try to install backstop, I get the following errors with event machine and thin:

Installing eventmachine (0.12.10) with native extensions
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
....
make
compiling rubymain.cpp
rubymain.cpp: In function ‘VALUE t_connect_server(VALUE, VALUE, VALUE)’:
rubymain.cpp:468:42: error: format not a string literal and no format arguments [-Werror=format-security
rubymain.cpp: In function ‘VALUE t_bind_connect_server(VALUE, VALUE, VALUE, VALUE, VALUE)’:
rubymain.cpp:488:42: error: format not a string literal and no format arguments [-Werror=format-security]
cc1plus: some warnings being treated as errors
make: *** [rubymain.o] Error 1

After some research it seems it's because of a Debian desicion to make -Werror=format-securoty a default compile flag. Changing the Gem.lock file to use eventmachine 1.0.3 and thin 1.6.3 lets backstop compile. However, after I export my carbon location and a test prefix, I use netstat to see if anything is listening on port 80 and nothing..... the foreman start command appears to hang as well.
bkvm4:root# export CARBON_URLS="carbon://carbon.example.com:2003"
bkvm4:root# export PREFIXES=test
bkvm4:root# foreman start
16:09:35 web.1 | started with pid 4741
16:09:35 web.1 | Ignoring ruby directive. This is a feature added to Bundler 1.2.0
16:09:35 web.1 | and higher. Please upgrade if you would like to use it.
16:09:35 web.1 |

^ hangs here, not sure if it's supposed to daemonize or not....

bkosick@bkvm4:~/puppet/modules/salesforce/manifests$ sudo netstat -l | grep http retuens nothing.

Any help would be appreciated.
Thanks,
Brian

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported Gem.lock changes for eventmachine and thin, then inspect the foreman start output and the netstat check on Debian Wheezy 7.7. Reproduce the installation and startup behavior with the stated CARBON_URLS and PREFIXES values; done means the service builds successfully and its expected listener is confirmed.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.