If I run it as root I am getting
sysctl: error setting key 'net.ipv4.ip_forward': Read-only file system
Looking for something like this: docker run --sysctl
net.ipv4.ip_forward=1 someimage
I have been looking forward to the update of mesos offering this mvp
csi, mainly to finally be able to use ceph. But unfortunately I am still
not able to get a simple rbd image attached to a container.
I am able to use the csilvm by adding the volume like this[2], but the
cephcsi keeps
If I use the csilvm driver, I am able to use a published volume with
this task[1] with xfs fs. However when I try and ad the volume as block
device the task[3] fails to deploy the log[4] however seems ok and does
a mount and unmount. Should I change more than just accessType and
fsType? The
I hope nobody minds putting this here since the csi mailing list is on
invitation only, and Jie Yu seems to be everywhere ;)
I am having some problems understanding how the cephcsi plugin works. I
am using the csc[1] from the rexray people which I believe to have quite
some history with the
When I create this task[2], I am getting the error message:
"There was a problem with your configuration
general: App creation unsuccessful. Check your app settings and try
again."
I have the csi managed plugin running and can mount with the command
line csc[1]. What should I look at to
When I launch a task via docker with:
docker run --memory 2G --memory-swappiness 0 -v /dev/log:/dev/log -it
--network host marathon:1.11.24
This task seems to use ~400MB resident, and 2,8GB virtual.
When I launch the same task on mesos I am getting
This task seems to use ~900MB resident,
I wanted to test csi in mesos 1.11, but noticed that I am using a plugin
for marathon that does not load any more. It has this in the "build.sbt"
file:
libraryDependencies += "mesosphere.marathon" %% "plugin-interface" %
"1.6.325" % "provided"
I assume this needs to be changed to a newer
Hi James,
Sorry to bring this up again. But I have marathon constantly logging
because of using the host name from the host networking, instead of
using its own task name marathon.xxx.xxx.xxx.mesos as a host name for
which there is a certificate.
Do you have an example of setting the
I hope nobody minds that I am crossposting this to mesos, since there is
not much activity on the marathon mailing list.
Is there an option to keep marathon running, having it try to reconnect
to the mesos-master after it lost connection?
Currently I am running sort of a test cluster with
Package mesos-1.11.0-2.0.1.el7.x86_64.rpm is not signed
Is there a way to change this failover_timeout after the framework is
running? Via the api or so? I see it is changed when the leader is
changing.
-Original Message-
To: user
Cc: cf.natali; janiszt
Subject: RE: Suddenly all tasks gone, framework at completed, cannot
start framework
I have default remote syslog setup on centos all applications and server
log the same timestamp (zone), except mesos and marathon tasks. I assume
UTC times are send from them. How can I set this back to the 'hosts
default'?
is not available yet.
We are currently working on an alternative way to get external storage
into Mesos instead of using SLRP. Please watch the progress here:
https://issues.apache.org/jira/browse/MESOS-10141 . MVP support will
land in the upcoming release of Mesos.
On Mon, Sep 7, 2020 at 2:08 PM Marc Roos
Is there anyone interested in giving some paid help to get me up and
running with an slrp with ceph? I assume this serp is not available
still not?
I would like to map a ceph rbd device to a task as a static/pre-existing
volume. Is there any guide on how to do this?
Is there a recommended csi ceph plugin? I found this one[1] but I think
it is only usable for kubernetes since it requires secrets to be stored
in some kubernetes property.
[1]
https://github.com/ceph/ceph-csi
,
Tomas
On Wed, 26 Aug 2020 at 11:11, Marc Roos
wrote:
Recently I enabled the cpu and memory isolators on my test cluster.
And
since then I have been seeing the marathon containers (when
becoming
leader) increase memory usage from ~400MB until they oom at 850MB
Recently I enabled the cpu and memory isolators on my test cluster. And
since then I have been seeing the marathon containers (when becoming
leader) increase memory usage from ~400MB until they oom at 850MB
(checking vi systemd-cgtop).
Now I am testing with these settings from this page[1]
On this dcos manual[1] there is only listed how to use a profile from an
slrp. Any one know how to change this to a pre-existing (lvm) volume?
(mesos example is also welcome ;)
cat > app2.json <> data/foo && cat data/foo && sleep 5000",
"container": {
"docker": {
"image":
Message-
From: Tomek Janiszewski [mailto:jani...@gmail.com]
Sent: dinsdag 25 augustus 2020 16:55
To: user
Subject: Re: Suddenly all tasks gone, framework at completed, cannot
start framework
See: https://stackoverflow.com/a/42544023/1387612
wt., 25 sie 2020 o 15:07 Marc Roos
napisał
I assume this was because something happened with zookeeper, and it
restarted loading the wrong configuration file without the quorum=1.
Because I was testing with different zookeeper rpms (mesos rpm conf is
not standard location)
Question: Is this by design that all tasks are terminated
Today all my tasks are down and framework marathon is at completed. Any
idea how this can happen?
ed.cpp:520] Successfully authenticated with master
master@192.168.10.151:5050
I0825 13:03:27.961248 108 sched.cpp:1188] Got error 'Framework has
been removed'
I am not sure if the csi standard requires that CSI_ENDPOINT should be
set, in any case.
- csilvm does not work without specifically setting -unix-addr-env
CSI_ENDPOINT. So either document this or make it default.
- I could not test with csc on csilvm master branch only this update csi
E0815 18:43:38.774154 1073 service_manager.cpp:751] Container daemon
for
'org-apache-mesos-rp-local-storage-local_blockdevices--nfs-csi-k8s-io-cs
i_blockdevices--CONTROLLER_SERVICE-NODE_SERVICE' failed: Timed out
waiting for endpoint 'unix:///tmp/mesos-csi-iJusqh/endpoint.sock'
E0815
You should reconsider supporting cni 0.3.0, so people can use this cni
bandwidth plugin[1]
[1]
https://github.com/containernetworking/plugins/tree/master/plugins/meta/bandwidth
No one able to help? ;)
-Original Message-
To: user
Subject: How to test if slrp is working correctly
I am testing with slrp and csi drivers after watching this video[1] of
mesosphere. I would like to know how I can verify that the slrp is
properly configured and working.
1. Can
I am testing with slrp and csi drivers after watching this video[1] of
mesosphere. I would like to know how I can verify that the slrp is
properly configured and working.
1. Can I use an api endpoint to query controller/list-volumes or do a
controller/create-volume. I found this csc tool
If I disable authenticate_http_readwrite authenticate_http_readonly. My
test slrp's are indeed loaded and I see tasks running.
Launching these tasks as described on the manual page via curl[1] also
fails. The task is not running, but I see that curl commands json is
being put in the
Can anyone point me to a more practical guide on how to configure and
get csi working (preferably with ceph)
This option has no effect when
using the HTTP scheduler/executor APIs.
By default, this option is true.
(default: true)
--log_dir=VALUE Location to put log files. By
default, nothing is
I am testing with this
Failed to recover resource provider with type
'org.apache.mesos.rp.local.storage' and name 'test_slrp': Failed to get
containers: Unexpected response '401 Unauthorized' (401 Unauthorized.)
Is this because I am having authentication on, and the standalone
container
"container": {
"type": "MESOS",
"portMappings": [
{"hostPort": 0, "name": "https", "protocol": "tcp",
"networkNames": ["cni-apps"]},
{"hostPort": 0, "name": "metrics", "protocol": "tcp",
"networkNames": ["cni-apps"]}
],
-Original Message-
To: user
I was wondering if cni networks were always applied in sequence. I am
seeing the same order of eth0, eth1 etc. But is it true that the 2nd
network is only created when the first was successfully
completed/attached?
ll provide a
unix domain socket that the executor can use to connect to the agent,
instead of relying on a TCP connection.
Regards,
Qian Zhang
On Sat, Aug 8, 2020 at 4:59 PM Marc Roos
wrote:
"it is imperative that the Agent IP is reachable from the container
IP
"it is imperative that the Agent IP is reachable from the container IP
and vice versa."
Anyone know/tested if this can be an asymmetric route when you are
having multiple networks?
[1]
http://mesos.apache.org/documentation/latest/cni/
I am getting this error message. When launching a task with portMappings
and two container networks. What is the proper way to configure this?
general: networkNames must be a single item list when hostPort is
specified and more than 1 container network is defined
"networks": [
{
How can I assign random ports to a cni network and read these back from
srv. What is the equivalent of portDefinitions at network/host for
network/container?
-Original Message-
To: user
Subject: health check not working after changing host network
If I change a task from:
If I change a task from:
"networks": [
{ "mode": "host" }
],
"portDefinitions": [
{"port": 0, "name": "health", "protocol": "tcp"},
{"port": 0, "name": "metrics", "protocol": "tcp"}
],
To:
"networks": [
{ "mode": "container", "name": "cni-storage" }
],
Is native ceph support in the planning? Libvirt supports ceph with
librbd[1]. What is currently the best practice to use ceph storage?
[1]
https://docs.ceph.com/docs/master/rbd/libvirt/
Currently I am running on a testing environment with some default acl I
found[1]. I have configured mesos-credentials, and afaik everything
agents/marathon framework is authenticating. So I thought about
converting the acl to default drop/deny. However I see there are quite a
few options.
For anyone who is interested. I was surprised that nginx was not
offering srv lookups in their free version. I found a module that
offered this, however it did not work because of syntax differences in
srv lookups on mesos. I adapted this module to force sending a whole srv
domain, and tests
2nd I have the impression that SRV records are not correctly implemented
should ._tcp not be at the front (after the service) instead of in the
middle? Or do I have something incorrect in my mesos configuration that
makes these groups act as part of the task name?
[@]$ dig +short
I cannot remember seeing this before. I wondered if this is common and
is it should to be. I am having in srv lookups random string in the
group. Why is test appended with '-grxx9-s0'?
[@~]$ dig +short @192.168.10.14 server.temp.test.marathon.mesos
192.168.10.151
[@~]$ dig +short
Oops ;)
[@test2 image-synapse]$ dig +short @192.168.10.14
_metrics._synapse.dev._tcp.marathon.mesos SRV
0 1 31032 synapse.dev-nppzf-s0.marathon.mesos.
-Original Message-
To: user
Subject: getting correct metrics port from SRV records.
Is there a way to identify the correct port
Is there a way to identify the correct port via dns? I have created a
task with two ports[1]. But a dns srv query does not show anything
different than the port number. How can I identify the correct port?
Mesos-master tasks endpoint[3] shows the port names, is there a way to
get these from
n": true,
"listener": "0.0.0.0",
"SOAMname": "ns1.mesos",
"SOARname": "root.ns1.mesos",
"SOARefresh": 5,
"SOARetry": 600,
"SOAExpire": 86400,
"SOAMinttl": 5,
"IPSources&q
I am not sure if mesos-dns is discontinued. But for the ones still using
it, in some cases it does not register all tasks ip addresses.
The default[2] works, but if you have this setup[1] it will only
register one ip address 192.168.122.140 and not the 2nd. I filed issue a
year ago or so[3]
I have my test cluster of mesos on again, and I am having mesos-master
logs end up in the wrong logs. I think mesos is not logging to correct
levels/facility. (using mesos-1.10.0-2.0.1.el7.x86_64)
Eg. I have got this on level error:
Jul 24 12:25:16 m01 mesos-master[28922]: I0724
Thanks Tomek, have it running, giving it a try.
-Original Message-
To: user
Subject: Re: Advice on alternative for marathon framework
You can try https://github.com/HubSpot/Singularity
Aurora was moved to attic <https://attic.apache.org/>
śr., 15 lip 2020 o 16:29 Mar
I am having problems[1] getting marathon to run since march (can only
run 1.7) and the only emails I receive from d2iq is how to rate their
support. I wonder if this Marathon is still best to be used with mesos.
I have aurora running, but it looks to have less options.
What I like about the
I am cross posting this to mesos-users, hoping someone has came accros
this issue, and can help me resolve this issue I have. There are several
JIRA issues open with similar symptoms.
All of a sudden I having problems with marathon ui getting stuck at
'loading' and end points like
You already put these on debug?
[@ ]# cat /etc/mesos-master/logging_level
WARNING
[@ ]# cat /etc/mesos-slave/logging_level
WARNING
-Original Message-
From: Benjamin Wulff [mailto:benjamin.wulff...@ieee.org]
Sent: zaterdag 6 juni 2020 13:36
To: user@mesos.apache.org
Subject: No
* ability for an executor to communicate with an agent via Unix domain
socket instead of TCP
I think this will solve my problem with tasks running on different ip
which I was doing via a local route. But somehow this route was not
being used in mesos. While ping to the netspace were ok.
contact the marathon mailing list or slack channel.
Also, if there is a question here or some more context, please include
that so they know what you need help with.
On Wed, Mar 18, 2020 at 9:46 AM Marc Roos
wrote:
Marathon is stuck on 'loading applications
I am having these, has been reported already on Jira long time ago. How
to fix these?
der mesosphere.marathon.api.v2.PodsResource will be ignored.
(org.glassfish.jersey.internal.inject.Providers:MarathonHttpService
STARTING)
Mar 18 16:38:21 m01 marathon: [2020-03-18 16:38:21,785] WARN A
Marathon is stuck on 'loading applications'
Mar 18 14:43:48 m01 marathon: [2020-03-18 14:43:48,646] INFO Received
fake heartbeat task-status update
(mesosphere.marathon.core.heartbeat.MesosHeartbeatMonitor:Thread-30)
Mar 18 14:43:53 m01 marathon: [2020-03-18 14:43:53,321] INFO Found no
I am getting these on a test setup, where marathon and mesos-master
running on the same node and iptables is not even configured.
W0222 23:03:48.829741 1112 process.cpp:1917] Failed to send
'mesos.internal.FrameworkErrorMessage' to '192.168.10.151:35530',
connect: Failed connect, connection
it adheres to the project's quality
standards).
On Wed, Feb 5, 2020 at 8:57 AM Marc Roos
wrote:
Is this possible? I would like to start using mesos in production
to be
honest.
-Original Message-
Sent: 30 January 2020 18
practice
I do not think we plan to do it in short term.
Regards,
Qian Zhang
On Tue, Jan 28, 2020 at 1:54 AM Marc Roos
wrote:
Hi Qian,
Any idea on when this cni 0.3 is going to be implemented? I saw the
issue priority is Major, can't remember
Because the instance was not showing in the marathon gui. I have killed
a task with kill -KILL, assuming it would restart, yet it did not.
I think it has to do with these messages. Why do I have these even, when
I can just ping them?
W0202 14:46:51.215673 359364 process.cpp:1480] Failed to
.
-Original Message-
Cc: user
Subject: Re: cni iptables best practice
I do not think we plan to do it in short term.
Regards,
Qian Zhang
On Tue, Jan 28, 2020 at 1:54 AM Marc Roos
wrote:
Hi Qian,
Any idea on when this cni 0.3 is going to be implemented? I
think
there is a ticket to trace it:
https://issues.apache.org/jira/browse/MESOS-7079.
Regards,
Qian Zhang
On Sat, Dec 14, 2019 at 7:08 AM Marc Roos
wrote:
Is anyone applying iptables rules in their cni networking, and how?
I
wrote a iptables chaining plugin but cannot
think
there is a ticket to trace it:
https://issues.apache.org/jira/browse/MESOS-7079.
Regards,
Qian Zhang
On Sat, Dec 14, 2019 at 7:08 AM Marc Roos
wrote:
Is anyone applying iptables rules in their cni networking, and how?
I
wrote a iptables chaining plugin but cannot
Is anyone applying iptables rules in their cni networking, and how? I
wrote a iptables chaining plugin but cannot use it because this cni
0.3.0 is still not supported in mesos 1.9. I wondered how this done
currently
How to set iptable rules inside a container? I am getting these
Fatal: can't open lock file /run/xtables.lock: Permission denied
Fatal: can't open lock file /run/xtables.lock: Permission denied
Fatal: can't open lock file /run/xtables.lock: Permission denied
Fatal: can't open lock file
I have still with mesos 1.9 degraded performance, any help to sort this
out would be nice. Makes me also wonder if others have bothered testing
this or not? I am testing still with mesos and thus have mostly a
default setup.
Previously when I opened this thread, there was questioning about
What are my options to adding a host entry to /etc/hosts in container
running not as root?
the CNI chain support?
-Gilbert
On Wed, Jul 24, 2019 at 12:52 PM Marc Roos
wrote:
Hmm, I guess I should not get my hopes up this will be there soon?
[0]
https://issues.apache.org/jira/browse/MESOS-7178
-Original Message
Thanks Benjamin, I will bookmark these.
-Original Message-
To: user@mesos.apache.org
Subject: Re: Mesos task example json
Hi Marc,
> You also know how/where to put the capabilities? I am struggling with
> that.
Have a look at the protobufs which define this API:
* `TaskInfo`
Don't understand how to use mesos capabilities as described here[0]
1. removed caps from ping with
setcap 'cap_net_raw=-p' /usr/bin/ping
2. linux/capabilities in the isolators,
3. mesos-slave running as root,
4. did not set effective_capabilities nor bounding_capabilities
5. Running kernel
type": "SCALAR", "scalar": {"value": 128}}
],
"command": {
"value": "sleep 10"
},
"container": {
"type": "MESOS",
"mesos": {
"image": {
"type": "DOCKER",
"docker": {
"name": "busybox"
}
}
}
}
}
Regards,
Qian Zhang
On Sat, Oct 12, 2019 at 6:26 AM Marc Roos
wrote:
Is there some example json available with all options for use with
'mesos-execute --task='
Is there some example json available with all options for use with
'mesos-execute --task='
[@~]# mesos help
Usage: mesos [OPTIONS]
Available commands:
help
dns
daemon.sh
agent
start-cluster.sh
master
start-agents.sh
start-masters.sh
start-slaves.sh
stop-agents.sh
stop-cluster.sh
stop-masters.sh
stop-slaves.sh
tail
cat
I have a docker image that requires NET_ADMIN, I have found this[0] (for
the docker containerizer?), but what is the syntax for the mesos
containerizer.
[0]
{
"cpus": 0.1,
"mem": 50,
"id": "/openvpn",
"instances": 1,
"container": {
"docker": {
"image":
Are there any restrictions on a launched task that could block access to
ipsec in the kernel?
I am getting this in the launched task
Oct 8 16:05:19 c02 ipsec_starter[695921]: no netkey IPsec stack
detected
Oct 8 16:05:19 c02 ipsec_starter[695921]: no KLIPS IPsec stack detected
Oct 8
.name) \(.state) \(.slave_id)" '
-Original Message-
To: user
Subject: Re: Task list node
You can just mimic UI behaviour and use /state endpoint and filter it
with jq.
wt., 1 paź 2019 o 13:56 Marc Roos napisał(a):
Hmmm, if do something like this[0
and filter them localy with jq
http://mesos.apache.org/documentation/latest/endpoints/master/tasks/
czw., 26 wrz 2019 o 22:09 Marc Roos
napisał(a):
What would be the easiest way to list running tasks on a
node/agent/slave?
I have a few tasks that take a while before they get started. Sendmail
eg. Is not to happy you cannot set the hostname (in marathon) and then
gives a timeout of 1 minute. I think there is something similar when
starting openldap. If I enable a regular health check there, it will
fail the
Looks like my tasks that have dual networking, a gateway and cni_args
assigned ip address are not able to start anymore on mesos 1.9. During
deployment I am able to ping these assigned ip addresses. Why can't this
executor reach the task then? I guess something has changed in how the
W0929 00:45:10.676910 468993 process.cpp:1055] Failed SSL connections
will be downgraded to a non-SSL socket
W0929 00:45:10.901372 469057 state.cpp:657] Failed to find
'libprocess.pid' or 'http.marker' for container
8bf306d5-a10c-4787-9258-4198ea80bbec of executor
W0929 00:45:10.902492
What would be the easiest way to list running tasks on a
node/agent/slave?
x86_64
-Original Message-
From: Marc Roos
Sent: maandag 19 augustus 2019 21:47
To: user
Subject: "Failed to launch container" "No such file or directory"
Some temp folders gone? How to resolve this?
Failed to launch container: Failed to read man
Marc Roos
wrote:
mesos-1.8.1-2.0.1.el7.x86_64
CentOS Linux release 7.6.1810 (Core)
-Original Message-
To: user
Subject: Please some help regression testing a task
I have a task
Why do get this message? How to resolve this?
W0831 18:01:45.403295 2943686 containerizer.cpp:2375] Ignoring update
for unknown container 48d9b77c-7348-4404-9845-211be74bad1d
mesos-1.8.1-2.0.1.el7.x86_64
mesos-1.8.1-2.0.1.el7.x86_64
CentOS Linux release 7.6.1810 (Core)
-Original Message-
To: user
Subject: Please some help regression testing a task
I have a task that under performs. I am unable to discover what is
causing it. Could this be something mesos specific?
Performance
] Ignoring update for unknown container
680d3849-2b2a-4549-8842-8ef358599478
-Original Message-
From: Qian Zhang [mailto:zhq527...@gmail.com]
Sent: woensdag 28 augustus 2019 15:07
To: Marc Roos
Cc: user
Subject: Re: Large container image failing to start 'first' time
Can you please send
I am testing converting a nameserver vm to a task on mesos. If I query
just one domain (so the results comes from cache) for 30 seconds I can
do around 450.000 queries on the vm, and only 17.000 on the task.
When I look at top output on the host where task is running I see this
task only
ngs in agent logs when the container failed to start?
Regards,
Qian Zhang
On Mon, Aug 19, 2019 at 10:46 PM Marc Roos
wrote:
I have a container image of around 800MB. I am not sure if that is
a
lot. But I have noticed it is probably to big for a default setup
to
I was wondering if it is possible to export a socket of a container to
the host, so I can then share it again with another container. (Without
using pods eg. (I like to scale these applications independent from each
other))
When scaling a task from 0 to 1 with two cni networks one of them having
a gateway, I have quite a lot of failures
Step 1: deploying
Step 2: DHCPREQUEST and DHCPACK (fast)
Step 3: Right after DHCPACK this error from the agent
W0823 14:58:18.440388 2663180 containerizer.cpp:2375]
When scaling the task from 0 to 1, it takes sometimes quite a while for
it to become active. Waiting maybe 10-20 seconds on the first waiting
reported by marathon.
Step 1: deploying (fast)
Step 2: sometimes fast / sometimes 10-20 seconds
Step 3: DHCPREQUEST and DHCPACK (fast)
Step 4: Right
ogs when the container failed to start?
Regards,
Qian Zhang
On Mon, Aug 19, 2019 at 10:46 PM Marc Roos
wrote:
I have a container image of around 800MB. I am not sure if that is
a
lot. But I have noticed it is probably to big for a default setup
to get
it to lau
place to store docker layers?
-Original Message-
From: Marc Roos
Sent: maandag 19 augustus 2019 21:47
To: user
Subject: "Failed to launch container" "No such file or directory"
Some temp folders gone? How to resolve this?
Failed to launch container: Failed t
Some temp folders gone? How to resolve this?
Failed to launch container: Failed to read manifest from
'/tmp/mesos/store/docker/layers/8c49e24d4aba93c77354143366e2427e0e2e7191
cb85dbc1aa187e4e480021c1/json': No such file or directory
I have a container image of around 800MB. I am not sure if that is a
lot. But I have noticed it is probably to big for a default setup to get
it to launch. I think the only reason it launches eventually is because
data is cached and no timeout expires. The container will launch
eventually
s the sandbox is considered read only, yet
the stdout and stderr are located there???
I think the document
<http://mesos.apache.org/documentation/latest/sandbox/#using-the-sandbox>
means that sandbox is not expected to be touched by any 3rd party software or
people other than Mesos, executor and tas
-Original Message-
To: user
Subject: Re: Is chained cni networks supported in mesos 1.7
Are you interested in implementing the CNI chain support?
-Gilbert
On Wed, Jul 24, 2019 at 12:52 PM Marc Roos
wrote:
Hmm, I guess I should not get my hopes up this will be there soon
you have unanswered questions.
On Wed, Aug 7, 2019 at 4:59 PM Marc Roos
wrote:
I seem to be able to add a maintenance schedule, and get also a
report
on '{"down_machines":[{"hostname":"m02.local"}]}' but I do not see
tasks
r::Call: Expecting 'type'
to be present
Please read the "maintenace primitives" section in this doc
http://mesos.apache.org/documentation/latest/maintenance/ and let us
know if you have unanswered questions.
On Wed, Aug 7, 2019 at 4:59 PM Marc Roos
wrote:
: Expecting 'type'
to be present
Please read the "maintenace primitives" section in this doc
http://mesos.apache.org/documentation/latest/maintenance/ and let us
know if you have unanswered questions.
On Wed, Aug 7, 2019 at 4:59 PM Marc Roos
wrote:
I seem to be able to add a m
1 - 100 of 204 matches
Mail list logo
