root@gitlab:/# gitlab-psql
psql (12.7)
Type "help" for help.

gitlabhq_production=# UPDATE projects SET runners_token = null, runners_token_encrypted = null;
UPDATE 346
gitlabhq_production=# UPDATE namespaces SET runners_token = null, runners_token_encrypted = null;
UPDATE 129
gitlabhq_production=# UPDATE application_settings SET runners_registration_token_encrypted = null;
UPDATE 1
gitlabhq_production=# UPDATE application_settings SET encrypted_ci_jwt_signing_key = null;
UPDATE 1
gitlabhq_production=# UPDATE ci_runners SET token = null, token_encrypted = null;
UPDATE 3
gitlabhq_production=# UPDATE ci_builds SET token_encrypted = null;
UPDATE 4039

 

Mysql 8 버전 기준

 

CREATE USER 'josungwoo'@'%' IDENTIFIED BY '패스워드';

GRANT ALL PRIVILEGES ON `sungwoodb`.* TO 'josungwoo'@'%';

flush privileges;

 

 

읽기 권한만 주고싶다..

 

CREATE USER 'josungwoo'@'%' IDENTIFIED BY '패스워드';
GRANTSELECT ON `sungwoodb`.* TO 'josungwoo'@'%';
flush privileges;

 

 

RDS Aurora로 생성하고 파라미터 그룹 생성하고 편집에서 

 

charater set 과 time zone 세팅

admin@josungwoo-MBP eks % eksctl delete cluster --name eks-tutorial
2024-02-07 09:54:57 [ℹ]  deleting EKS cluster "eks-tutorial"
2024-02-07 09:54:57 [ℹ]  will drain 1 unmanaged nodegroup(s) in cluster "eks-tutorial"
2024-02-07 09:54:57 [ℹ]  starting parallel draining, max in-flight of 1


2024-02-07 09:55:58 [!]  1 pods are unevictable from node ip-192-168-9-219.ap-northeast-2.compute.internal
2024-02-07 09:56:58 [!]  1 pods are unevictable from node ip-192-168-9-219.ap-northeast-2.compute.internal

 

계속 펜딩 상태...

 

아래 옵션을 주어서 삭제

eksctl delete cluster --name eks-tutorial --disable-nodegroup-eviction

 

 

admin@josungwoo-MBP eks % eksctl delete cluster --name eks-tutorial --disable-nodegroup-eviction
2024-02-07 09:59:45 [ℹ]  deleting EKS cluster "eks-tutorial"
2024-02-07 09:59:45 [ℹ]  will drain 1 unmanaged nodegroup(s) in cluster "eks-tutorial"
2024-02-07 09:59:45 [ℹ]  starting parallel draining, max in-flight of 1
2024-02-07 10:00:01 [✔]  drained all nodes: [ip-192-168-85-198.ap-northeast-2.compute.internal ip-192-168-22-84.ap-northeast-2.compute.internal ip-192-168-9-219.ap-northeast-2.compute.internal]
2024-02-07 10:00:02 [ℹ]  deleted 0 Fargate profile(s)
2024-02-07 10:00:02 [✔]  kubeconfig has been updated
2024-02-07 10:00:02 [ℹ]  cleaning up AWS load balancers created by Kubernetes objects of Kind Service or Ingress
2024-02-07 10:00:04 [ℹ]
2 sequential tasks: { delete nodegroup "ng-1", delete cluster control plane "eks-tutorial" [async]
}
2024-02-07 10:00:04 [ℹ]  will delete stack "eksctl-eks-tutorial-nodegroup-ng-1"
2024-02-07 10:00:04 [ℹ]  waiting for stack "eksctl-eks-tutorial-nodegroup-ng-1" to get deleted
2024-02-07 10:00:04 [ℹ]  waiting for CloudFormation stack "eksctl-eks-tutorial-nodegroup-ng-1"
2024-02-07 10:00:34 [ℹ]  waiting for CloudFormation stack "eksctl-eks-tutorial-nodegroup-ng-1"
2024-02-07 10:01:32 [ℹ]  waiting for CloudFormation stack "eksctl-eks-tutorial-nodegroup-ng-1"

2024-02-07 10:03:11 [ℹ]  waiting for CloudFormation stack "eksctl-eks-tutorial-nodegroup-ng-1"
2024-02-07 10:03:11 [ℹ]  will delete stack "eksctl-eks-tutorial-cluster"
2024-02-07 10:03:11 [✔]  all cluster resources were deleted

https://github.com/eksctl-io/eksctl/issues/6287

https://www.arthurkoziel.com/setting-up-vim-for-yaml/

 

Setting up Vim for YAML editing

Setting up Vim for YAML editing March 23, 2020 In this blog post I'm going to show how to set up Vim for easier YAML editing. You can scroll down to the end for a summary of all installed plugins and config file changes. There's not much to do here. VIM ha

www.arthurkoziel.com

 

YAML 파일을 VI, VIM 으로 다루다 보니, Tab 이 들어가면서 나오는 에러,

error: error parsing deployment.yml: error converting YAML to JSON: yaml: line 10: found character that cannot start any token

 

근데 VIM 으로 보면 Tab 표시가 안나타나서 Mac에서는 위와 같이 Vim 에디터에다가 YAML 유효성을 검증할 수 있는 플러그인을 설치하면 좋다.

php로 exec 실행하면 잘되는데,

apache 로 세팅해서 rest 로 호출하면 exec가 실행이 되지 않는다.


권한문제로,

apache로 실행되면 user가 다르기 때문


php 소스상에

echo system('whoami');


라고 코드를 넣어보면 수행하는 유저를 알 수가 있다.


그 유저에게 권한을 부여해주면됨


sudo nano /etc/sudoers


www-data       ALL=(ALL) NOPASSWD:ALL


이라고 추가하면 완료

대상 OS

CentOS release 6.8 (Final)



1. 패키지 파일 복사


2. 방화벽 설정


3. 아파치 설정


4. php56 설치

yum list php56-*

yum 리스트에 뜨질않는다면 repository 변경

rpm -Uvh https://mirror.webtatic.com/yum/el6/latest.rpm

yum clean all

yum install php-pear php-devel gcc make

yum clean all

yum list php56*


기존에 깔았던 php제거

yum -y remove php php-*


yum install php56w-devel php56w-pecl php56w-common php56w-mysql php56w-pear php56w-mbstring php56w-opcache php56w



5. Predis 설치

yum install php-pear

pear channel-discover pear.nrk.io

pear install nrk/Predis


6. 레디스 클러스터 설정

./redis-server ../7000/redis.conf

./redis-server ../7001/redis.conf

./redis-server ../7002/redis.conf

./redis-trib.rb create 127.0.0.1:7000 127.0.0.1:7001 127.0.0.1:7002



jsvc 로 데몬을 띄울려고 했는데 맥에서 아래와 같은 에러가 나온다.


Cannot find any VM in Java Home /Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home

Cannot locate JVM library file


해결

http://www.thomaskioko.com/hacks/cannot-find-any-vm-in-java-home-mac/

This is going to be a short one. so let’s get to it.

Today was one of those days you go past page 5 searching for an answer in Google. Hopefully you will not have to go through the same process I did to get a fix.

I have been working with daemons and i hit a snag. The VM/JVM not found snag.

I got the following error when running the daemon: “Cannot find any VM in Java Home /Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home
Cannot locate JVM library file”

After scrolling through the web I finally got a fix.

Solution:

Open terminal and type the following commands:

NB: Replace jdk1.7.0_71.jdk with your jdk version.

$ cd /Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents
$ sudo ln -s Home/jre/lib Libraries
$ cd Libraries
$ sudo ln -s server/libjvm.dylib libserver.dylib

That’s it. Problem solved :-)

Let me get back to what I love doing, saving the world.

개발중인 node.js 웹서버 부하테스트를 해보려고 찾은 간단한 부하테스트 툴이다.

# apt-get install siege

소스 설치 하려면,

여기에서 소스파일 받아서 빌드..

http://freecode.com/projects/siege


siege -c 50 -d 10 -t 3M http://localhost:3000

-c : concurrent user

-d : 다음요청 보내기 까지 시간(sec)

-t : 테스트시간


아래는 결과

...

Transactions:                   1696 hits

Availability:                 100.00 %

Elapsed time:                 179.53 secs

Data transferred:             730.34 MB

Response time:                  0.18 secs

Transaction rate:               9.45 trans/sec

Throughput:                     4.07 MB/sec

Concurrency:                    1.72

Successful transactions:        1696

Failed transactions:               0

Longest transaction:            1.25

Shortest transaction:           0.05



관련 블로그

http://blog.remarkablelabs.com/2012/11/benchmarking-and-load-testing-with-siege

http://www.joedog.org/siege-manual/

http://www.euperia.com/linux/tools-and-utilities/speed-testing-your-website-with-siege-part-one/720



http://blog.daum.net/cypanic/2143317

+ Recent posts