Estou tentando entender o processo exe no meu servidor Ubuntu
sudo ls -l /proc/6293/exe
lrwxrwxrwx 1 jenkins 65533 0 апр 4 09:03 /proc/6293/exe -> /usr/local/bin/node
Quando procuro no lixo
/usr/local/bin# ls node
ls: cannot access 'node': No such file or directory
Para onde esse elo simbólico realmente aponta?
Estou tentando desabilitar o Jenins neste servidor, porque não precisamos mais dele
ps -feww | grep jenkins
mostra
jenkins 6646 6089 0 08:53 ? 00:00:00 npm start
jenkins 9180 6646 29 08:53 ? 01:19:15 next-server (v14.2.5)
jenkins 15769 12444 0 08:53 ? 00:00:02 /shared/argocd-dex rundex
jumicha 587438 544583 0 13:18 pts/0 00:00:00 grep --color=auto jenkins
Qual deve ser o próximo passo? Como descobrir o que iniciou o Jenkins?
ps -p 9180 -o pid,vsz=MEMORY -o user,group=GROUP -o comm,args=ARGS
PID MEMORY USER GROUP COMMAND ARGS
9180 21735356 jenkins 65533 next-server (v1 next-server (v14.2.5)
O que foi que deu início ao next-server?
pstree -pn 9180
next-server (v1(9180)─┬─{next-server (v1}(9189)
├─{next-server (v1}(9190)
├─{next-server (v1}(9191)
├─{next-server (v1}(9192)
├─{next-server (v1}(9193)
├─{next-server (v1}(9214)
├─{next-server (v1}(12061)
├─{next-server (v1}(12062)
├─{next-server (v1}(12063)
└─{next-server (v1}(12064)
Estou tentando entender como o systemd-journald e o rsyslog funcionam juntos. Os logs são armazenados em/var/logs? Faz
du -h /var/log/journal/
é suficiente para o que eu preciso?
Estou intrigado como o estivador e o notário trabalham juntos. não consigo assinar a imagem
docker pull nginx:latest
pegou
Error: error contacting notary server: x509: certificate signed by unknown authority
eu segui esses passos
git clone https://github.com/theupdateframework/notary
cd notary $ docker-compose build
docker-compose up -d
mkdir -p ~/.notary && cp cmd/notary/config.json cmd/notary/root-ca.crt ~/.notary
O que root-ca.crt representa? Como verificar isso? O erro significa que o cliente não reconhece o emissor do certificado e considera o certificado inválido?
nslookup -type=ns b92.net a.root-servers.net
Eu tenho esse
Server: a.root-servers.net
Address: 198.41.0.4#53
Non-authoritative answer:
*** Can't find b92.net: No answer
Authoritative answers can be found from:
net nameserver = a.gtld-servers.net.
net nameserver = b.gtld-servers.net.
net nameserver = c.gtld-servers.net.
net nameserver = d.gtld-servers.net.
net nameserver = e.gtld-servers.net.
net nameserver = f.gtld-servers.net.
net nameserver = g.gtld-servers.net.
net nameserver = h.gtld-servers.net.
net nameserver = i.gtld-servers.net.
net nameserver = j.gtld-servers.net.
net nameserver = k.gtld-servers.net.
net nameserver = l.gtld-servers.net.
net nameserver = m.gtld-servers.net.
a.gtld-servers.net internet address = 192.5.6.30
b.gtld-servers.net internet address = 192.33.14.30
c.gtld-servers.net internet address = 192.26.92.30
Se eu tentar
nslookup -type=ns b92.net
Eu tenho um endereço IP privado como saída
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
b92.net nameserver = primary.b92.net.
b92.net nameserver = ns2.b92.net.
sou novo em lookup.
Meu objetivo é receber o tipo de recurso A.
Como fazer a consulta DNS correta?
Eu tenho essa saída com dig
dig NS markovic.mydomain.com.
; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> NS markovic.mydomain.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61780
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;markovic.mydomain.com. IN NS
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 13 10:10:05 CEST 2019
;; MSG SIZE rcvd: 50
E
host -t NS markovic.mydomain.com.
Host markovic.mydomain.com. not found: 3(NXDOMAIN)
Imagem de zonas hospedadas
Sou novo na AWS, como posso decifrar se defini o domínio da maneira correta?
Estou tendo problemas para iniciar o Kong com o Postgres. Eu inspecionei o log da minha área de trabalho
root@miki:/var/log/postgresql#
2019-04-22 07:35:28.040 CEST [1181] LOG: listening on IPv4 address "127.0.0.1", port 5432
2019-04-22 07:35:28.070 CEST [1181] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-04-22 07:35:28.438 CEST [1426] LOG: database system was shut down at 2019-04-21 20:13:57 CEST
2019-04-22 07:35:28.546 CEST [1181] LOG: database system is ready to accept connections
2019-04-22 07:35:29.175 CEST [1690] [unknown]@[unknown] LOG: incomplete startup packet
O que isto significa?
Meu postgresql está rodando
/etc/init.d/postgresql status
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
Active: active (exited) since Mon 2019-04-22 07:35:30 CEST; 1h 45min ago
Process: 1939 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 1939 (code=exited, status=0/SUCCESS)
апр 22 07:35:30 miki systemd[1]: Starting PostgreSQL RDBMS...
апр 22 07:35:30 miki systemd[1]: Started PostgreSQL RDBMS.
Eu tentei clonar o repositório do github (para ver como Golang e reagir funcionam juntos)
git clone git@git.bec-systems.com:cbrake/goreact.git $GOPATH/src/github.com/cbrake/goreact
Cloning into '/home/miki/go/src/github.com/cbrake/goreact'...
The authenticity of host 'git.bec-systems.com (159.65.229.70)' can't be established.
ECDSA key fingerprint is SHA256:CzPCk6/fsCvAD1xG9GiHswVWHyOvB0/UD7da7CWzTTk.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added 'git.bec-systems.com,159.65.229.70' (ECDSA) to the list of known hosts.
git@git.bec-systems.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Há alguma repercussão para mim? O que significa que o git foi adicionado à lista de hosts conhecidos?
Depois
kubectl run -i -t load-generator --image=busybox /bin/sh
Da minha concha, estou tentando
/ # wget http://wordpress.default.svc.cluster.local
Connecting to wordpress.default.svc.cluster.local (10.102.29.45:80)
wget: can't connect to remote host (10.102.29.45): No route to host
Estes são meus serviços do kubernetes no local
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
hello-node LoadBalancer 10.104.141.138 <pending> 8080:31321/TCP 3d21h app=hello-node
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 4d <none>
tomcat-deployment LoadBalancer 10.107.218.19 <pending> 8080:32688/TCP 3d16h app=tomcat
wordpress NodePort 10.102.29.45 <none> 80:31262/TCP 2d app=wordpress,tier=frontend
wordpress-mysql ClusterIP None <none> 3306/TCP 2d app=wordpress,tier=mysql
Também wget funciona para o google
wget google.com
Connecting to google.com (216.58.214.206:80)
Connecting to www.google.com (216.58.209.164:80)
Como se conectar ao meu nó?
Eu construí meu pequeno aplicativo Python(flask). O contêiner está aqui docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4146fd976547 identidock_identidock:latest "/cmd.sh" 5 minutes ago Up 5 minutes 9090/tcp, 9191/tcp agitated_leakey
Se eu tentar
curl localhost:5000
curl: (7) Failed to connect to localhost port 5000: Connection refused
Eu verifiquei sudo netstat -an | grep -E "5000" unix 3 [ ] STREAM CONNECTED 25000
Não está listando em 5000. linha yaml com portas
ports:
- "5000:5000"
Se eu executar meu contêiner
docker exec -it agitated_leakey /bin/bash
uwsgi@4146fd976547:/app$ netstat -ln
bash: netstat: command not found
Meu Dockerfile
RUN pip install Flask==0.10.1 uWSGI==2.0.8
WORKDIR /app
COPY app /app
COPY cmd.sh /
EXPOSE 9090 9191
Por que isso acontece?
Eu quero instalar o Cassandra em 4 nós remotos. Tudo funciona bem até eu chegar ao ponto quando verifico o status
nodetool status
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID Rack
UN 127.0.0.1 103.68 KiB 256 100.0% 4e03d80f-5972-4bc7-b36d-6e536ebfa808 rack1
Eu configurei corretamente listen_address para 192.68.0.25 e sementes para 192.69.0.13
Eu tenho o mesmo no outro nó
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID Rack
UN 127.0.0.1 103.64 KiB 256 100.0% c7ad74b0-9fa1-4068-a2f8-24e45523b731 rack1
Isto é o que eu tenho quando executo o cassandra do shell de comando
OpenJDK 64-Bit Server VM warning: Cannot open file /var/log/cassandra/gc.log due to Permission denied
18:06:55,305 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.cassandra] to DEBUG
18:06:55,305 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.thinkaurelius.thrift] to ERROR
18:06:55,305 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
18:06:55,305 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@6ea12c19 - Registering current configuration as safe fallback point
INFO [main] 2018-01-25 18:06:55,399 YamlConfigurationLoader.java:89 - Configuration location: file:/etc/cassandra/cassandra.yaml
Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered during startup: Invalid yaml: file:/etc/cassandra/cassandra.yaml
Error: null; Can't construct a java object for tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create property=seed_provider for JavaBean=org.apache.cassandra.config.Config@3d36e4cd; java.lang.reflect.InvocationTargetException; in 'reader', line 10, column 1:
cluster_name: 'Test Cluster'
^
Invalid yaml: file:/etc/cassandra/cassandra.yaml
Na verdade não tenho gc.log.Este é o conteúdo da pasta
/var/log/cassandra$ ls *.log
debug.log system.log
E
/var/log$ ls -lia cassandra/
total 284
8389155 drwxr-xr-x 2 cassandra cassandra 4096 jan. 25 15:50 .
8257787 drwxrwxr-x 14 root syslog 4096 jan. 25 15:49 ..
8389157 -rw-r--r-- 1 cassandra cassandra 178071 jan. 25 17:50 debug.log
8389086 -rw-r--r-- 1 cassandra cassandra 53037 jan. 25 18:16 gc.log.0.current
8389150 -rw-r--r-- 1 cassandra cassandra 41003 jan. 25 17:50 system.log
Tentei criar um cluster com três nós do Cassandra na minha máquina. Descompactei o tar.gz e alterei listen e rpc_addresses, também JMX_PORT. Não funcionou
~/apache-cassandra-3.11.1-1/bin$ nodetool -h 127.0.0.02 -p 8081 ring
nodetool: Failed to connect to '127.0.0.02:8081' - ConnectException: 'Connection refused (Connection refused)'.
Então eu segui o conselho de ALex Ott, instalei o ccm. Então eu tenho problema novamente
ccm start
Traceback (most recent call last):
File "/home/jholmes/anaconda3/lib/python3.6/site-packages/ccm-3.1.3-py3.6.egg/ccmlib/common.py", line 513, in assert_socket_available
OSError: [Errno 98] Address already in use
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/jholmes/anaconda3/bin/ccm", line 4, in <module>
__import__('pkg_resources').run_script('ccm==3.1.3', 'ccm')
File "/home/jholmes/anaconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 750, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/home/jholmes/anaconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1534, in run_script
exec(script_code, namespace, namespace)
File "/home/jholmes/anaconda3/lib/python3.6/site-packages/ccm-3.1.3-py3.6.egg/EGG-INFO/scripts/ccm", line 105, in <module>
File "/home/jholmes/anaconda3/lib/python3.6/site-packages/ccm-3.1.3-py3.6.egg/ccmlib/cmds/cluster_cmds.py", line 490, in run
File "/home/jholmes/anaconda3/lib/python3.6/site-packages/ccm-3.1.3-py3.6.egg/ccmlib/cluster.py", line 389, in start
File "/home/jholmes/anaconda3/lib/python3.6/site-packages/ccm-3.1.3-py3.6.egg/ccmlib/common.py", line 519, in assert_socket_available
ccmlib.common.UnavailableSocketError: Inet address 127.0.0.1:7000 is not available: [Errno 98] Address already in use; a cluster may already be running or you may need to add the loopback alias
Como verificar a disponibilidade do endereço?
Eu mudei um pouco Uma introdução ao código do Terraform . Meu objetivo é implantar cluster de servidores web Meu código,main.tf
provider "aws" { region = "eu-central-1"}
resource "aws_launch_configuration" "example" {
ami = "ami-df8406b0"
image_id = "${data.aws_ami.ubuntu.id}"
instance_type = "t2.micro"
vpc_security_group_ids = ["${aws_security_group.instance.id}"]
user_data = <<-EOF
#!/bin/bash
echo "Hello, World" > index.html
nohup busybox httpd -f -p "${var.server_port}" &
EOF
lifecycle {
create_before_destroy = true
}
}
variable "server_port" {
description = "The port the server will use for HTTP requests"
default = 8080
}
resource "aws_security_group" "instance" {
name = "terraform-example-instance"
ingress {
from_port = "${var.server_port}"
to_port = "${var.server_port}"
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
}
lifecycle {
create_before_destroy = true
}
}
data "aws_ami" "ubuntu" {
most_recent = true
filter {
name = "name"
values = ["ubuntu/images/hvm-ssd/ubuntu-trusty-14.04-amd64-server-*"]
}
filter {
name = "virtualization-type"
values = ["hvm"]
}
owners = ["099720109477"] # Canonical
}
resource "aws_autoscaling_group" "example" {
launch_configuration = "${aws_launch_configuration.example.id}"
min_size = 2
max_size = 10
tag {
key = "Name"
value = "terraform-asg-example"
propagate_at_launch = true
}
}
Quando eu vou para o plano de terraform
2 error(s) occurred:
* aws_launch_configuration.example: : invalid or unknown key: ami
* aws_launch_configuration.example: : invalid or unknown key: vpc_security_group_ids
Estou um pouco confuso com dados, serve para quê? Onde está o meu erro?
Estou tentando executar o terraform.Este é meu main.tf
provider "aws" { region = "eu-central-1"}
resource "aws_instance" "example" {
ami = "ami-df8403b0"
instance_type = "t2.micro"
vpc_security_group_ids = ["${aws_security_group.instance.id}"]
user_data = <<-EOF
#!/bin/bash
echo "Hello, World" > index.html
nohup busybox httpd -f -p "${var.server_port}" &
EOF
tags {
Name = "terraform-example"
}
}
variable "server_port" {
description = "The port the server will use for HTTP requests"
default = 8080
}
resource "aws_security_group" "instance" {
name = "terraform-example-instance"
ingress {
from_port = "${var.server_port}"
to_port = "${var.server_port}"
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
}
}
Se eu quiser verificar o gráfico de dependência, é isso que eu tenho
Falha ao carregar o módulo de configuração raiz: Erro ao analisar /home/milenko/brikman/main.tf: At 41:1: heredoc não encerrado
Sou novo na AWS. Estou no processo de criação da zona hospedada do Route 53.
jholmes.my domain.com NS ns-1408.awsdns-54.org.
ns-510.awsdns-01.net.
ns-321.awsdns-43.com.
ns-1712.awsdns-35.co.uk
O próximo passo é visitar o registrador de domínio para adicionar os registros Route53 NS, diz COREOS
O que isso significa? Devo ir, por exemplo, ao GoDaddy e comprar um domínio ou o quê? Quaisquer idéias e explicações são bem-vindas.