Deploy Script fails

[pixel5919]

Just tested the deploy script on a clean install of Ubuntu 14.04.4 LTS

+ systemctl enable docker
deploy.sh: line 69: systemctl: command not found

Do we need anything pre-installed? If so, we should create/update the wiki

[kabilans]

Is this on CentOS? Tag Ian on this. I think systemctl might not be installed on your image.

On Mon, May 16, 2016 at 3:54 PM, pixel5919 notifications@github.com wrote:

Assigned #28 https://github.com/iankronquist/beeswax/issues/28 to @kabilans https://github.com/kabilans.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/iankronquist/beeswax/issues/28#event-662284187

Sempon Sibi Kabilan

[kabilans]

Also, the system should work fine regardless. It'll just start docker up the first time you run the honeypot.

On Mon, May 16, 2016 at 4:04 PM, Sibi Kabilan ibisnopmes@gmail.com wrote:

Is this on CentOS? Tag Ian on this. I think systemctl might not be installed on your image.

On Mon, May 16, 2016 at 3:54 PM, pixel5919 notifications@github.com wrote:

Assigned #28 https://github.com/iankronquist/beeswax/issues/28 to @kabilans https://github.com/kabilans.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/iankronquist/beeswax/issues/28#event-662284187

Sempon Sibi Kabilan

Sempon Sibi Kabilan

[pixel5919]

It looks like as if honeypot_config.json never gets populated. And it's on Ubuntu 14.04, you should have the credentials.

[kabilans]

http://159.203.253.60/ui/sensors/

Find your sensor on their. But I just tested the script on Ubuntu and it worked fine.

[pixel5919]

Did you verify that honeypot_config.json gets repopulated with the UUID changing? I had to manually enter mine.

[kabilans]

Mine did repopulate fine. I have no idea what went wrong for you.

On Mon, May 16, 2016 at 6:59 PM, pixel5919 notifications@github.com wrote:

Did you verify that honeypot_config.json gets repopulated with the UUID changing? I had to manually enter mine.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/iankronquist/beeswax/issues/28#issuecomment-219600065

Sempon Sibi Kabilan

[iankronquist]

@pixel5919 the deploy script only works with MHN, and MHN depends on supervisor. Is MHN installed on the droplet?

[iankronquist]

Fixed by #31.

[iankronquist]

@kabilans FYI: systemctl is part of the systemd init system and should be installed on every modern Linux distro. It can run, restart, and monitor daemons as services. supervisor is a python daemon which watches programs and restarts them if they fail. I think you meant to say supervisorctl.

[kabilans]

Thats what I thought but the droplet Zach has this on doesn't have systemd. The command systemctl doesn't work on his droplet.

[pixel5919]

@kabilans Testing on new Ubuntu droplet fails:

+ cp /opt/beeswax_gopath/src/github.com/iankronquist//senior-project-experiment/beeswax_supervisor.conf /etc/supervisor/conf.d/beeswax.conf
cp: cannot stat ‘/opt/beeswax_gopath/src/github.com/iankronquist//senior-project-experiment/beeswax_supervisor.conf’: No such file or directory

• Need to update since we've change file locations and names
• Sidenote: honeypot_config.json populates but the UUID and secret need to be contained within quotes

[pixel5919]

Fixed some of the issues in https://github.com/kabilans/mhn/pull/1

[pixel5919]

I'm having issues with the honeypot_config.json never getting populated and systemctl not working on Ubuntu 14

• [x] It looks as if the HPF_* variables never get exported back into deploy_beeswax.sh
• [ ] CentOS and Ubuntu use different system init services: https://docs.docker.com/engine/admin/configuring/