Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesnt work as it should #8

Open
petrovicboban opened this issue Apr 20, 2017 · 0 comments
Open

Doesnt work as it should #8

petrovicboban opened this issue Apr 20, 2017 · 0 comments

Comments

@petrovicboban
Copy link

Hi,
I created graphite container with this image graphite-statsd
After that, I started collectd-mesos-tasks as:
docker run -d -e GRAPHITE_HOST=172.17.0.3 -e MESOS_HOST=x.x.x.x bobrik/collectd-mesos-tasks
where 172.17.0.3 is ip of graphite container (collectd-mesos-tasks can ping that ip) and x.x.x.x is my mesos slave.

root@server1:~# docker ps -a
CONTAINER ID        IMAGE                                      COMMAND                  CREATED             STATUS                   PORTS                                                                                                                                    NAMES
aaeba32b6fa3        bobrik/collectd-mesos-tasks                "/run.sh"                17 minutes ago      Up 17 minutes                                                                                                                                                     cranky_carson
2216a6ed5d41        hopsoft/graphite-statsd                    "/sbin/my_init"          20 hours ago        Up 20 hours              0.0.0.0:80->80/tcp, 0.0.0.0:2003-2004->2003-2004/tcp, 0.0.0.0:2023-2024->2023-2024/tcp, 0.0.0.0:8126->8126/tcp, 0.0.0.0:8125->8125/udp   graphite
root@server1:~# docker logs cranky_carson 
Initialization complete, entering read-loop.
mesos-tasks plugin: Task gsm_continuous-gsm_continuous_deploy_0-1492653911302-1-BOUNCE-1492653908595 found in metrics, but missing in state
mesos-tasks plugin: Task enet_parser-enet_parser_deploy_3-1492621370051-1-NEW_DEPLOY-1492621369675 found in metrics, but missing in state
mesos-tasks plugin: Task a3et_basketball_parser-a3et_basketball_parser_deploy_1-1490880271584-1-DECOMISSIONED_SLAVE_OR_RACK-1490880270912 found in metrics, but missing in state
mesos-tasks plugin: Task gsm_continuous-gsm_continuous_deploy_0-1492653911302-1-BOUNCE-1492653908595 found in metrics, but missing in state
mesos-tasks plugin: Task enet_parser-enet_parser_deploy_3-1492621370051-1-NEW_DEPLOY-1492621369675 found in metrics, but missing in state
mesos-tasks plugin: Task a3et_basketball_parser-a3et_basketball_parser_deploy_1-1490880271584-1-DECOMISSIONED_SLAVE_OR_RACK-1490880270912 found in metrics, but missing in state

I use singularity framework for deploying, and my deploy looks like this:

{
    "containerInfo": {
        "type": "MESOS"
    },
    "customExecutorCmd": "/usr/local/bin/singularity-executor",
    "executorData": {
        "cmd": " something to do",
        "embeddedArtifacts": [],
        "externalArtifacts": [],
        "extraCmdLineArgs": [],
        "loggingExtraFields": {},
        "s3Artifacts": [],
        "sigKillProcessesAfterMillis": 120000,
        "successfulExitCodes": [],
        "user": "admin"
    },
    "healthcheckProtocol": "HTTP",
    "id": "enet_parser_deploy_3",
    "labels": {
        "collectd_app": "enet_parser"
    },
    "mesosLabels": [
        {
            "key": "collectd_app",
            "value": "enet_parser"
        }
    ],
    "requestId": "enet_parser",
    "resources": {
        "cpus": 0.1,
        "diskMb": 0.0,
        "memoryMb": 256.0,
        "numPorts": 0
    },
    "shell": true
}

However, this conetainer doesn't send anything to graphite.
What am I doing wrong here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant