I am connecting to a CentOS booted from a persistent disk created from here. The instance is a n1-standard instance but I'm having some serious performance issues.
I can SSH into the instance just fine, however commands take a long time to run. I tried to just run a simple ping command to google.com and it took 2 minutes and 36 seconds to start the command. The CPU usage is next to none as there isn't really anything going on within the instance except an Apache installation that isn't doing anything yet. My internet connection is just fine, and other instances work just fine. I've even deleted the instance and started over from scratch.
Is there something wrong with the image CentOS is being created from or is this just a problem I'm having? What steps can I take to narrow down the problems?
Related
Redis n00b here.
I'm using Redis locally on Windows to test code before pushing to my server.
I used this tutorial to set it up:
https://dingyuliang.me/redis-3-2-create-cluster-windows/
Before "Map slave node to master node" I ran the "cluster reset hard" command for all nodes because for some reason, all my nodeIDs were the same.
The test then ran exactly as it in the example. However, when I restart my PC nothing works anymore. Tells me that Could not connect to Redis at :0: The requested address is not valid in its context. This is how it looks in the console when checking their state:
Everything except one master has no IP, port and is disconnected. What is going on and how can I fix this? The way to fix it was to completely wipe everything and start over so far. All Redis Services are running. My conf file is like on the tutorial.
Well I followed the official tutorial which turned out to be better (for Linux):
https://redis.io/topics/cluster-tutorial
The fact that I hard to give them a hard reset on the other one showed something did not work as planned and they all ran on the same redis.conf which probably made it weird as hell. Since the Windows Redis is only at V3, you will need an old redis-trib.rb (like here https://github.com/beebol/redis-trib.rb/blob/master/redis-trib.rb) to install the clusters. Bottom line, if you can really try to do this on Linux instead, if not what I did is hopefully good enough for the local dev environment.
I have created a new t2.small instance where I setup tomcat8 with java 8. But this tomcat is causing issue when I shut it down and start, it sometimes starts properly, most of the times it either gets stuck at activating or deactivating and it take forever to start the tomcat. I don't understand why my other instances which were created a long time back work with no trouble but this gives me such a headache as both of them share similar configuration.
Please any solutions.
I built my app with docker-compose , one container is database use mariadb image ,one php to run Laravel (I installed php-memcached or php-redis extension for my app), one cache container built on redis docker image .
at first everything goes on well , but after running 2 or 3 days , I got the php exception : Connection timed out [tcp://redis:6379];
I monitor the cpu and memory and network use zabbix installed by myself on host server , but I got these error :
monitor CPU
monitor memory
I changed cache container to memcached and 2 or 3 days same thing happen,
the only way I found to solve this problem is to restart system , and it can run another 2 or 3 days before getting the same error. you know it's not possible to restart system on production, so any one can suggest me where to solve the problem other than restarting system ?
Thanks!
I think you are facing problem with redis docker container. This type of error comes when memory is exhausted. You need to set max memory parameter of redis server.
Advice: Please try to use another image of redis.
I have install DC/OS (3master and 7slave server - all Centos7)
I saw problem - when one of slave server shut down - mesos/marathon start killed instance of application after 5 minutes.
For example - I run in mesos/marathon 8 instance simple web application. When I shut down or deactivate network interface of one slave server marathon show that some instancje are killed. From this moment mesos/marathon wait 5 minutes and start killed instance to another online slave server.
My question is - how can I change this time? 5 minutes is to long. I read documentation of DC/OS but I can't find variable responsible for this.
I will be very thankful for your help.
You can have a at the Marathon command-line flags. Based on your description, I guess the default for either task_launch_timeout or scale_apps_interval could be responsible for this.
I'm unsure though if this can be configured on the fly, or during installation in DC/OS. I saw that there's a quite recent enhancement request to Make Marathon flags passable via environment variables.
I have an EBS-backed EC2 instance. According to docs, it should be 'paused' if I stop (ec2stop) it. However, I noticed that server is indeed restarted after I start the instance back. Uptime counts from 0 after start, and tmux session is detached.
For comparison, everything above mentioned is really paused when I 'savestate' VirtualBox machine, so I can attach to existing tmux session after starting VBox machine back.
Could you please explain what is the difference? What really happens when I stop the EC2 instance?
Thanks,
Robusta
I entered your question into Google.
The first hits contained the answer to your question:
AWS FAQ
RightScale FAQ
Amazon says:
[...]The instance performs a normal shutdown and stops running (the
status goes to stopping and then stopped).[...]