1. 구성

프로젝트명은 ProjYj2024, 사용자는 projyj 라고 간주하고 설명함
- 신규 개발한 ProjYj2024, 기존에 개발된 ProjYjSvr(ProjYj) 프로젝트에 모두 접속할 수 있도록 구성함
- ProjYj2024 는 ProjYjSvr 의 API 를 사용

1-1. SSD

Oracel/MySQL 엔진
서버
OS : CentOs Stream 9

🔶 CentOs Stream 9

IP : 192.168.1.999 / PORT : 22
ID : root / PW : password$$

1-2. HDD

🔶 MySQL

ID : root / PW : password$$

1-3. 포트별 접속 정보

https://192.168.1.111:9090/podman : Podman
http://192.168.1.111:8070/ : Tomcat
http://192.168.1.111:8080/ : Jenkins

🔶 Jenkins

초기 패스워드 : 070b01f500e94ca1b1a3c3fa01b0c911
Admin User 정보
- ID : projyj / PW : password$$ / E-Mail : [email protected]

🔶 Github

ID : [email protected] / PW : password$$
Repository : https://github.com/projyj/ProjYj2024.git
Token 패스워드 : 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

2. CentOs Stream 9

참고 : CentOS Stream 9 설치 (Virtual Box) / CentOS 9 개요 및 설치 방법
CentOs Stream 9 부팅 > 언어 설정 후 Continue > 아래 설정 적용 후 Installation 수행

🔶 Keyboard

English 로 설정함

🔶 Installation Destination

저장소 구성은 변경하지 않고 기본으로 설치하였음

🔶 소프트웨어 선택

설치하고 싶은 환경을 선택 후 Done
일반적으로 테스트 목적으로 Server with GUI 환경으로 설치

🔶 Network & Host

이더넷이 잘 켜져있는지 확인 후 Done

2-1. 접속

CentOs Stream 9 부팅 > root 계정으로 접속 > IP 확인

[root@localhost ~]$ hostname -I
192.168.1.999

Putty 로 ssh 접속하여 계속 진행

🔶 OS 정보 확인

cat /etc/os-release

[root@localhost ~]# cat /etc/os-release
NAME="CentOS Stream"
VERSION="9"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="9"
PLATFORM_ID="platform:el9"
PRETTY_NAME="CentOS Stream 9"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:centos:centos:9"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"

🔶 hostnamectl 정보

아무 인자없이 hostnamectl 실행 시 > 시스템의 호스트명, Chassis, Machine ID, Boot ID, 가상화, 커널 버전 등의 정보를 출력
호스트명 변경 시 : set-hostname 과 변경할 호스트명을 입력 (hostnamectl set-hostname [변경할 호스트명])

[root@localhost ~]# hostnamectl
   Static hostname: (unset)
Transient hostname: localhost
         Icon name: computer-desktop
           Chassis: desktop 🖥️
        Machine ID: aea36b66c60547078fd6d43ffc1a4736
           Boot ID: afece10043164066a0a98a689a500628
  Operating System: CentOS Stream 9
       CPE OS Name: cpe:/o:centos:centos:9
            Kernel: Linux 5.14.0-427.el9.x86_64
      Architecture: x86-64
   Hardware Vendor: Micro-Star International Co., Ltd.
    Hardware Model: MS-7D22
  Firmware Version: 1.30

2-2. 파티션 확인

참고 : 하드 디스크 파티션 확인 및 마운트 시키기 / 디스크와 파티션을 보는 4가지 방법
파티션 현황 확인 : fdisk -l
- Device : 장치명
- Boot : 별(*) 표시가 있는 파티션이 부팅 파티션이라는 의미 (아래 블록에는 조회되지 않음)
- -l : 목록 / -u : 섹터 단위로 표시

[root@localhost ~]# fdisk -l
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO Plus 500GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3B8AB5CB-8566-4D97-AB1B-9596BE837479

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1230847   1228800   600M EFI System
/dev/nvme0n1p2 1230848   3327999   2097152     1G Linux filesystem
/dev/nvme0n1p3 3328000 976773119 973445120 464.2G Linux LVM


Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HDN724040AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 42B2D9E1-D9F9-4E97-A835-008CB7AC2269

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7814035455 7814033408  3.6T Microsoft basic data


Disk /dev/mapper/cs-root: 70 GiB, 75161927680 bytes, 146800640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/cs-swap: 15.65 GiB, 16806576128 bytes, 32825344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/cs-home: 378.52 GiB, 406432251904 bytes, 793812992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

블록 장치를 나열 : lsblk
- -f : 디스크에 대한 추가 정보 확인 가능
- Linux 컴퓨터의 디스크와 파티션을 볼 수 있음

[root@localhost ~]# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   3.6T  0 disk
└─sda1        8:1    0   3.6T  0 part
nvme0n1     259:0    0 465.8G  0 disk
├─nvme0n1p1 259:1    0   600M  0 part /boot/efi
├─nvme0n1p2 259:2    0     1G  0 part /boot
└─nvme0n1p3 259:3    0 464.2G  0 part
  ├─cs-root 253:0    0    70G  0 lvm  /
  ├─cs-swap 253:1    0  15.7G  0 lvm  [SWAP]
  └─cs-home 253:2    0 378.5G  0 lvm  /home

[root@localhost ~]# lsblk -f
NAME        FSTYPE      FSVER    LABEL   UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1      ntfs                 새 볼륨 E4E8BF2DE8BEFD3C
nvme0n1
├─nvme0n1p1 vfat        FAT32            933D-493E                               591.3M     1% /boot/efi
├─nvme0n1p2 xfs                          b4540b96-808f-4545-8966-77d007090acf    654.4M    32% /boot
└─nvme0n1p3 LVM2_member LVM2 001         5JEvcU-09gj-HmWW-FznL-mQ7n-oKBq-je5vqM
  ├─cs-root xfs                          9548f8c3-cb9a-4d44-918d-a24064024222     62.8G    10% /
  ├─cs-swap swap        1                e291fe33-1624-46e7-ac50-4a0d6548e92a                  [SWAP]
  └─cs-home xfs                          3d3e737e-3c9d-438e-ad4b-0a87558a061c    375.7G     1% /home

하드웨어 정보 확인 : hwinfo
- 하드웨어, 특히 저장 디스크에 대한 정보를 보는 데 유용

# 디스크 또는 해당 파티션에 대한 정보
[root@localhost ~]# sudo hwinfo --disk
# 블록 장치의 개요
[root@localhost ~]# sudo hwinfo --short --block
# 모든 디스크의 요약
[root@localhost ~]# sudo hwinfo --disk --short

Logical Volume 상태 : lvdisplay
- LVM(Logical Volume Manager) : 물리적 한계에 제약받지 않고 디스크를 효율적으로 분할하여 사용 가능
- LV 로 나뉜 파티션은 최종적으로 파일 시스템을 할당받고 특정 디렉토리에 마운트 될 수 있음

[root@localhost ~]# lvdisplay
  --- Logical volume ---
  LV Path                /dev/cs/swap
  LV Name                swap
  VG Name                cs
  LV UUID                1PJ2Bq-YVVQ-bWwC-Mcc5-GXNG-may4-IzfLRw
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain, 2024-03-15 09:41:23 +0900
  LV Status              available
  # open                 2
  LV Size                15.65 GiB
  Current LE             4007
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

  --- Logical volume ---
  LV Path                /dev/cs/home
  LV Name                home
  VG Name                cs
  LV UUID                DNN5i1-x5Gy-j4jH-7nOd-n3sC-bg4n-pH1Y6K
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain, 2024-03-15 09:41:23 +0900
  LV Status              available
  # open                 1
  LV Size                <378.52 GiB
  Current LE             96901
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2

  --- Logical volume ---
  LV Path                /dev/cs/root
  LV Name                root
  VG Name                cs
  LV UUID                Nbo7SF-68jP-2IsP-Sd4e-K4kt-vAXa-4baXqc
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain, 2024-03-15 09:41:23 +0900
  LV Status              available
  # open                 1
  LV Size                70.00 GiB
  Current LE             17920
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

🔶 bash: hwinfo: command not found...

아래 명령어로 설치부터 진행

sudo apt install hwinfo         [On Debian, Ubuntu and Mint]
sudo yum install hwinfo         [On RHEL/CentOS/Fedora and Rocky Linux/AlmaLinux]
sudo emerge -a sys-apps/hwinfo  [On Gentoo Linux]
sudo pacman -S hwinfo           [On Arch Linux]
sudo zypper install hwinfo      [On OpenSUSE]

🔶 저장 공간 확인

저장 공간 확인 : df [옵션] [디렉토리 또는 마운트 지점]
- -h : human-readable 옵션을 사용하면 용량을 보기 쉬운 형식으로 출력
- 디렉토리 또는 마운트 지점 : 특정 디렉토리나 마운트 지점의 파일 시스템 정보만 표시

[root@localhost ~]# df -h
Filesystem           Size  Used Avail Use% Mounted on
devtmpfs             4.0M     0  4.0M   0% /dev
tmpfs                 16G     0   16G   0% /dev/shm
tmpfs                6.2G   18M  6.2G   1% /run
/dev/mapper/cs-root   70G  7.2G   63G  11% /
/dev/nvme0n1p2       960M  306M  655M  32% /boot
/dev/mapper/cs-home  379G  2.7G  376G   1% /home
/dev/nvme0n1p1       599M  7.5M  592M   2% /boot/efi

🔶 Linux GUI

Linux 데스크톱 컴퓨터 > GUI(그래픽 사용자 인터페이스) 애플리케이션 > 디스크 목록을 확인 가능
시스템 메뉴 > 디스크 애플리케이션 검색 > 디스크와 해당 파티션을 확인

2-3. 하드디스크 파티션

parted로 파티션 테이블 보기 : parted /dev/sda1

[root@localhost ~]# parted /dev/sda1
GNU Parted 3.5
Using /dev/sda1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Error: /dev/sda1: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/sda1: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags:
(parted)

파티션 상태 확인 : fdisk -l
- Physical Volume 까지 생성됨

[root@localhost ~]# fdisk -l /dev/sda1
Disk /dev/sda1: 3.64 TiB, 4000785104896 bytes, 7814033408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x73736572

Volume Group 만들기

[root@localhost ~]# vgcreate VG01 /dev/sda1
  Physical volume "/dev/sda1" successfully created.
  Volume group "VG01" successfully created

Logical Volume 만들기

[root@localhost ~]# lvcreate --size 900GB --name lv01cargo VG01
  Logical volume "lv01cargo" created.
[root@localhost ~]# lvcreate --size 900GB --name lv02cargo VG01
  Logical volume "lv02cargo" created.
[root@localhost ~]# lvcreate --size 900GB --name lv01vm VG01
  Logical volume "lv01vm" created.
[root@localhost ~]# lvcreate --size 900GB --name lv02vm VG01
  Logical volume "lv02vm" created.
[root@localhost ~]#

현재 상태 확인

[root@localhost ~]# vgdisplay VG01
  --- Volume group ---
  VG Name               VG01
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               <3.64 TiB
  PE Size               4.00 MiB
  Total PE              953861
  Alloc PE / Size       921600 / <3.52 TiB
  Free  PE / Size       32261 / <126.02 GiB
  VG UUID               1A8hCi-yvbQ-1IRg-yIkr-724H-LONA-7y2yVY

Volume 할당 공간 확인

[root@localhost ~]# pvs -a
  PV             VG   Fmt  Attr PSize   PFree
  /dev/nvme0n1p3 cs   lvm2 a--  464.17g       0
  /dev/sda1      VG01 lvm2 a--   <3.64t <126.02g

[root@localhost ~]# lvs -a
  LV        VG   Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  lv01cargo VG01 -wi-a-----  900.00g
  lv01vm    VG01 -wi-a-----  900.00g
  lv02cargo VG01 -wi-a-----  900.00g
  lv02vm    VG01 -wi-a-----  900.00g
  home      cs   -wi-ao---- <378.52g
  root      cs   -wi-ao----   70.00g
  swap      cs   -wi-ao----   15.65g

파일 시스템과 마운트
- mkfs.xfs /dev/VG01/lv01cargo, mkfs.xfs /dev/VG01/lv02cargo, mkfs.xfs /dev/VG01/lv01vm, mkfs.xfs /dev/VG01/lv02vm

[root@localhost ~]# mkfs.xfs /dev/VG01/lv01cargo
meta-data=/dev/VG01/lv01cargo    isize=512    agcount=4, agsize=58982400 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1    bigtime=1 inobtcount=1 nrext64=0
data     =                       bsize=4096   blocks=235929600, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=115200, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

디렉토리 생성 및 마운트

[root@localhost ~]# mkdir /cargo1
[root@localhost ~]# mkdir /cargo2
[root@localhost ~]# mkdir /vm1
[root@localhost ~]# mkdir /vm2
[root@localhost ~]# mount /dev/VG01/lv01cargo /cargo1
[root@localhost ~]# mount /dev/VG01/lv02cargo /cargo2
[root@localhost ~]# mount /dev/VG01/lv01vm /vm1
[root@localhost ~]# mount /dev/VG01/lv02vm /vm2

디렉토리 구성과 실제 사용하는 파일시스템 크기 확인

[root@localhost ~]# df -Th
Filesystem                 Type      Size  Used Avail Use% Mounted on
devtmpfs                   devtmpfs  4.0M     0  4.0M   0% /dev
tmpfs                      tmpfs      16G     0   16G   0% /dev/shm
tmpfs                      tmpfs     6.2G   18M  6.2G   1% /run
/dev/mapper/cs-root        xfs        70G  7.2G   63G  11% /
/dev/nvme0n1p2             xfs       960M  306M  655M  32% /boot
/dev/mapper/cs-home        xfs       379G  2.7G  376G   1% /home
/dev/nvme0n1p1             vfat      599M  7.5M  592M   2% /boot/efi
/dev/mapper/VG01-lv01cargo xfs       900G  6.4G  894G   1% /cargo1
/dev/mapper/VG01-lv02cargo xfs       900G  6.4G  894G   1% /cargo2
/dev/mapper/VG01-lv01vm    xfs       900G  6.4G  894G   1% /vm1
/dev/mapper/VG01-lv02vm    xfs       900G  6.4G  894G   1% /vm2

🔶 Partition does not start on physical sector boundary

참고 : Partition does not start on physical sector boundary
Partition 4 does not start on physical sector boundary. : 파티션의 시작이 섹터의 경계에서 시작하지 않는다는 뜻
- Sector size > 논리섹터 512 bytes와 물리섹터 4096 byte와 크기가 맞지 않아 생기는 오류

[root@localhost ~]# fdisk -l /dev/sd*
Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HDN724040AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 42B2D9E1-D9F9-4E97-A835-008CB7AC2269

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7814035455 7814033408  3.6T Microsoft basic data


Disk /dev/sda1: 3.64 TiB, 4000785104896 bytes, 7814033408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x73736572

Device      Boot      Start        End    Sectors   Size Id Type
/dev/sda1p1      1920221984 3736432267 1816210284   866G 72 unknown
/dev/sda1p2      1936028192 3889681299 1953653108 931.6G 6c unknown
/dev/sda1p3               0          0          0     0B  0 Empty
/dev/sda1p4        27722122   27722568        447 223.5K  0 Empty

Partition 4 does not start on physical sector boundary.
Partition table entries are not in disk order.

위의 마운트 단계까지 수행하고 다시 조회해보면 해당 내용은 뜨지 않음

2-4. 기본 설정

참고 : CentOS Stream 9 설치 및 기본 설정 / DNS 설정

🔶 네임서버 설정

네임서버 및 도메인 지정 역할을 해주는 설정 파일
현재 네트워크는 연결되어 있지만 DNF(자동) 패키지 설치 즉, 외부 도메인 미러 사이트를 찾기 위해 특정 ISP(인터넷을 제공하는 개인이나 기업)에 미리 지정해주는 게 좋음
resolv.conf 파일 수정
- nameserver : 내가 사용할 도메인서버 IP 주소 (리눅스는 최대 3개까지 인식 가능)
- search : 도메인 명을 지정 (대부분 호스트명과 도메인명을 함께 사용하나, 특별하게 호스트명만 사용되었을 때 사용하게 될 기본 도메인 명)

[root@localhost ~]# vi /etc/resolv.conf

# Generated by NetworkManager
nameserver 210.94.0.73
nameserver 210.220.163.82
nameserver 192.168.1.999
search localdomain.com

Generated by NetworkManager : 네트워크를 재시작하면 NM(NetworkManager)에 의해 이 파일이 바뀌기 때문에 초기화 될 수 있음
네트워크를 재시작하기 전에 chattr +i /etc/resolv.conf 명령어 수행
- 리부팅 시에 resolv.conf 파일이 초기화 되는데, write(쓰기-편집)를 못하게 보호하는 명령어
- 해제는 chattr -i /etc/resolv.conf
이후 네트워크를 재시작하여 적용 : systemctl restart network 또는 service network restart
- 재시작 후에도 여전히 /etc/resolv.conf 파일이 초기화 되지 않고 살아있는 것 확인

🔶 업데이트

현재 설치되어있는 전체 패키지와 커널을 업그레이드
보안을 위해 하는 부분으로 아무것도 설치되어 있지 않는 상태에서 하는 것을 권고
- 이미 돌아가고 있는 서버에서 하게 되면 부팅 실패나 장애 발생 가능성 있음
- 설치가 완료될 경우 새로 설치된 것과 업데이트한 패키지가 리스트에 나오게 됨

[root@localhost ~]# dnf update
Last metadata expiration check: 2:16:12 ago on Wed 20 Mar 2024 03:20:24 PM KST.
Dependencies resolved.
=============================================================================================================================================================
 Package                                            Architecture                 Version                               Repository                       Size
=============================================================================================================================================================
Installing:
 kernel                                             x86_64                       5.14.0-430.el9                        baseos                           44 k
Upgrading:
 NetworkManager                                     x86_64                       1:1.47.2-1.el9                        baseos                          2.3 M
############ (중략) ############

Transaction Summary
=============================================================================================================================================================
Install   5 Packages
Upgrade  41 Packages

Total download size: 147 M
Is this ok [y/N]: y
Downloading Packages:
(1/46): kernel-5.14.0-430.el9.x86_64.rpm                     0% [                                                          ] ---  B/s |   0  B     --:-- ETA
############ (중략) ############
(46/46): kernel-devel-5.14.0-430.el9.x86_64.rpm                                                                              973 kB/s |  16 MB     00:16
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                        5.3 MB/s | 147 MB     00:27
CentOS Stream 9 - BaseOS                                                                                                     1.6 MB/s | 1.6 kB     00:00
Importing GPG key 0x8483C65D:
 Userid     : "CentOS (CentOS Official Signing Key) <[email protected]>"
 Fingerprint: 99DB 70FA E1D7 CE22 7FB6 4882 05B5 55B3 8483 C65D
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
Is this ok [y/N]: y
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Running scriptlet: selinux-policy-targeted-38.1.35-2.el9.noarch                                                                                        1/1
  Preparing        :                                                                                                                                     1/1
  Upgrading        : selinux-policy-38.1.35-2.el9.noarch                                                                                                1/87
  Running scriptlet: selinux-policy-38.1.35-2.el9.noarch                                                                                                1/87
  Running scriptlet: container-selinux-3:2.230.0-1.el9.noarch                                                                                          87/87
  Running scriptlet: tzdata-2024a-1.el9.noarch                                                                                                         87/87

🔶 selinux 비활성화

일종의 보안정책으로 모든 프로세스나 특정 객체에 대하여 관리 규정을 지을 수 있음
기본적으로 활성(enforcing)되어 있음 > 서버 운영 중 네트워크 방화벽 및 특정 프로세스가 막히거나 구동이 되지 않는 상황이 발생할 수 있음
- 비활성(disabled) 적용 후 재부팅하여 방지할 수 있음

[root@localhost ~]# vi /etc/sysconfig/selinux

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
#SELINUX=enforcing
SELINUX=disabled

🔶 IPTABLES 방화벽 사용 (🚫Firewall 사용 시에는 생략)

CentOS 7부터는 iptables를 사용하지 않고 Firewall 방식을 도입
- 때문에 /etc/sysconfig/iptables 파일이 존재하지 않음
기존 iptables를 사용하는 경우에만 아래 내용 진행
- systemd 기반으로 작동되기 때문에 systemctl 명령어 이용해야 함

[root@localhost ~]# systemctl stop firewalld  [Firewalld 방화벽 중지]
[root@localhost ~]# systemctl mask firewalld  [Firewalld 자동실행 중지]
[root@localhost ~]# yum install -y iptables-services  [iptables 서비스 관련 패키지 설치]
[root@localhost ~]# systemctl enable iptables  [iptables기본 사용 설정]
[root@localhost ~]# systemctl start iptables  [iptables서비스 시작]
[root@localhost ~]# iptables -nL  [작동 확인]
[root@localhost ~]# /etc/sysconfig/iptables  [설정 파일 위치]

2-5. CentOS 패키지 확장

repo 목록 확인

[root@localhost /]# yum repolist
repo id                      repo name
appstream                    CentOS Stream 9 - AppStream
baseos                       CentOS Stream 9 - BaseOS
epel                         Extra Packages for Enterprise Linux 9 - x86_64
epel-cisco-openh264          Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64
epel-next                    Extra Packages for Enterprise Linux 9 - Next - x86_64
extras-common                CentOS Stream 9 - Extras packages

Docker 대신 Podman 설치 (RedHat 기준)
패키지 확장을 위해 HDD 파티션 작업 선행 > LVM 으로 컨테이너, VM, DB 공간 확보
- /vm1 : 테스트용 가상 머신 설치
- /vm2 : 컨테이너 설치
- /cargo1, /cargo2 : DBMS 사용자 테이블 공간
남아있는 공간은 재분배

3. 원격 데스크톱 연결

3-1. xrdp를 통해 원격 데스크톱 연결 (Windows -> CentOS)

참고 : 원격 데스크톱으로 연결하는 방법 / firewall-cmd 명령어로 방화벽 관리하기
RDP(Remote Desktop Protocol, 원격 데스크톱 프로토콜)
- 터미널 서버와 터미널 서버 클라이언트 간의 통신에 사용
- TCP 내에서 캡슐화되고 암호화되어 정보 전달
xrdp
- 리눅스 시스템에서 원격 데스크톱 접속을 제공하는 오픈 소스 프로젝트 (리눅스 서버를 원격으로 관리할 때 사용)
- xrdp는 RDP를 사용하여 원격 클라이언트가 리눅스 시스템에 접속하여 GUI를 사용할 수 있도록 함

🔶 기본 환경 설치

# 업그레이드
[root@localhost ~]# yum update
Last metadata expiration check: 3:32:45 ago on Thu 21 Mar 2024 05:35:46 AM KST.
Dependencies resolved.
Nothing to do.
Complete!
[root@localhost ~]# yum upgrade
Last metadata expiration check: 3:32:52 ago on Thu 21 Mar 2024 05:35:46 AM KST.
Dependencies resolved.
Nothing to do.
Complete!

# epel repository 설치
$ yum install -y epel-release
Last metadata expiration check: 3:32:59 ago on Thu 21 Mar 2024 05:35:46 AM KST.
Dependencies resolved.
=============================================================================================================================================================
 Package                                    Architecture                    Version                             Repository                              Size
=============================================================================================================================================================
Installing:
 epel-release                               noarch                          9-7.el9                             extras-common                           19 k
Installing weak dependencies:
 epel-next-release                          noarch                          9-7.el9                             extras-common                          8.1 k
############ (중략) ############
Complete!

# xrdp 및 tigervnc 설치
$ yum install -y xrdp tigervnc-server
Extra Packages for Enterprise Linux 9 - x86_64                                                                               6.0 MB/s |  21 MB     00:03
Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64                                                         335  B/s | 2.5 kB     00:07
Extra Packages for Enterprise Linux 9 - Next - x86_64                                                                        487 kB/s | 1.4 MB     00:02
Last metadata expiration check: 0:00:01 ago on Thu 21 Mar 2024 09:09:15 AM KST.
Dependencies resolved.
=============================================================================================================================================================
 Package                                        Architecture                  Version                                 Repository                        Size
=============================================================================================================================================================
Installing:
 tigervnc-server                                x86_64                        1.13.1-8.el9                            appstream                        224 k
 xrdp                                           x86_64                        1:0.9.24-1.el9                          epel                             459 k
############ (중략) ############
Complete!

🔶 3389 Port 상시 허용

방화벽에 3389 Port를 상시 허용으로 등록 및 재실행

[root@localhost ~]# sudo firewall-cmd --permanent --zone=public --add-port=3389/tcp
success
[root@localhost ~]# sudo firewall-cmd --reload
success
[root@localhost ~]# sudo firewall-cmd --list-port
3389/tcp

🔶 xrdp 서비스 등록 및 구동 확인

[root@localhost ~]# sudo systemctl enable xrdp.service
Created symlink /etc/systemd/system/multi-user.target.wants/xrdp.service → /usr/lib/systemd/system/xrdp.service.
[root@localhost ~]# sudo systemctl start xrdp.service
[root@localhost ~]# systemctl status xrdp.service
● xrdp.service - xrdp daemon
     Loaded: loaded (/usr/lib/systemd/system/xrdp.service; enabled; preset: disabled)
     Active: active (running) since Thu 2024-03-21 09:41:57 KST; 6s ago
       Docs: man:xrdp(8)
             man:xrdp.ini(5)
   Main PID: 345161 (xrdp)
      Tasks: 1 (limit: 202223)
     Memory: 1.0M
        CPU: 4ms
     CGroup: /system.slice/xrdp.service
             └─345161 /usr/sbin/xrdp --nodaemon

Mar 21 09:41:57 localhost.localdomain systemd[1]: Started xrdp daemon.
Mar 21 09:41:57 localhost.localdomain xrdp[345161]: [INFO ] starting xrdp with pid 345161
Mar 21 09:41:57 localhost.localdomain xrdp[345161]: [INFO ] address [0.0.0.0] port [3389] mode 1
Mar 21 09:41:57 localhost.localdomain xrdp[345161]: [INFO ] listening to port 3389 on 0.0.0.0
Mar 21 09:41:57 localhost.localdomain xrdp[345161]: [INFO ] xrdp_listen_pp done

🔶 포트 상태 및 접속할 IP 확인

3389 포트 상태 확인

[root@localhost ~]# netstat -nap | grep 3389
tcp6       0      0 :::3389                 :::*                    LISTEN      345161/xrdp

IP : 192.168.1.999

[root@localhost ~]# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.999  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::dabb:c1ff:fe4d:c443  prefixlen 64  scopeid 0x20<link>
        ether d8:bb:c1:4d:c4:43  txqueuelen 1000  (Ethernet)
        RX packets 1140040  bytes 860949800 (821.0 MiB)
        RX errors 0  dropped 110087  overruns 0  frame 0
        TX packets 201157  bytes 16165519 (15.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xa1200000-a1220000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 65  bytes 5351 (5.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 65  bytes 5351 (5.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

🔶 firewall public zone 상태 확인

[root@localhost ~]# sudo firewall-cmd --zone=public --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: eno1
  sources:
  services: cockpit dhcpv6-client ssh
  ports: 3389/tcp
  protocols:
  forward: yes
  masquerade: no
  forward-ports:
  source-ports:
  icmp-blocks:
  rich rules:

3-2. Windows 에서 CentOS 원격 연결

시작 > 원격 데스크톱 연결 > 192.168.1.999
- 사용자 이름 등록하지 않고 바로 연결할 것
root 계정 접속은 안되도록 설정되어 있음
- 아래 내용 수행해도 되지 않아서 보류

🔶 root 계정 접속 허용/해제

sshd_config 파일을 수정

[root@localhost ssh]# cd /etc/ssh/
[root@localhost ssh]# vi sshd_config

PermitRootLogin : root 계정으로 로그인 시 허용 여부를 설정하는 값

(...)
# Authentication:

#LoginGraceTime 2m
#PermitRootLogin prohibit-password
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
(...)

PermitRootLogin 설정 값을 변경 후에도 바로 root 계정 로그인 제한이 되진 않음
- 제한 설정을 적용하기 위해서는 sshd를 재시작

[root@localhost ssh]# service sshd restart

3-3. 서버 주소 수동 변경

설치 시 자동으로 할당 받은 주소를 수동으로 재지정
원격 데스크톱 > 상단 네트워크 아이콘 > Settings
Network > Wired > Connected - 100 Mb/s 켜기 및 설정 버튼 클릭
IPv4 탭 클릭하여 고정 IP 설정
- IPv4 Method : Manual (수동)
- Address : 주소, 넷마스크, 게이트웨이 주소 입력 (192.168.1.999, 255.255.255.0, 192.168.1.1)
- DNS > Automatic 해제
- DNS : 210.94.0.73, 210.220.163.82 (여러 개의 DNS를 입력할 경우 쉼표로 구분)

[root@localhost ~]# vi /etc/resolv.conf

nameserver 210.94.0.73
nameserver 210.220.163.82

상단의 적용 버튼 클릭 (터미널의 systemctl restart network 와 동일한 효과)

4. 가상머신

4-1. RHEL 9, Cockpit 웹 콘솔 설정

가상머신을 관리하기 위한 웹 콘솔 가상머신 플러그인 설치
웹 콘솔이 시스템에 설치되어 활성화되어 있는지 확인

[root@localhost /]# systemctl status cockpit.socket
○ cockpit.socket - Cockpit Web Service Socket
     Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; disabled; preset: disabled)
     Active: inactive (dead)
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)

cockpit-machines 플러그인을 설치

[root@localhost /]# dnf install cockpit-machines
Last metadata expiration check: 1:33:14 ago on Thu 21 Mar 2024 12:44:55 PM KST.
Dependencies resolved.
============================================================================================================================================================
 Package                                              Architecture         Version                                            Repository               Size
============================================================================================================================================================
Installing:
 cockpit-machines                                     noarch               308-1.el9                                          appstream               1.1 M
############ (중략) ############
Total download size: 37 M
Installed size: 153 M
Is this ok [y/N]: y
############ (중략) ############
Complete!

활성화

[root@localhost /]# systemctl enable cockpit.socket
Created symlink /etc/systemd/system/sockets.target.wants/cockpit.socket → /usr/lib/systemd/system/cockpit.socket.
[root@localhost /]# systemctl start cockpit.socket

🔶 웹 콘솔에 액세스

참고 : CentOS/RHEL 8에 KVM을 설치하는 방법
- KVM(커널 기반 가상 머신) : Linux에 긴밀하게 통합된 오픈 소스이자 사실상의 표준 가상화 솔루션
https://localhost:9090 에 로그인
- Unable to connect - Firefox can’t establish a connection to the server at localhost:9090.
- Windows > https://192.168.1.999:9090/ 로 접속하여 확인
제한된 접근 해제 > 암호 입력 후 인증 버튼 클릭 > 관리 액세스 모드로 바뀜
libvirt Hypervisor 드라이버를 실행하도록 설정되어 있는지 확인

[root@localhost /]# virt-host-validate
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for device assignment IOMMU support                         : WARN (No ACPI DMAR table found, IOMMU either disabled in BIOS or not supported by this hardware platform)
  QEMU: Checking for secure guest support                                    : WARN (Unknown if this platform has Secure Guest support)

kvm 모듈이 커널에 로드되었는지 확인

[root@localhost /]# lsmod  | grep kvm
kvm_intel             442368  0
kvm                  1335296  1 kvm_intel
irqbypass              16384  1 kvm

방화벽 상태는 cockpit 까지 열려있음 (만약 외부 접속이 허용되어 있지 않다면, 방화벽에 cockpit 서비스 추가)

[root@localhost /]# firewall-cmd --add-service=cockpit --permanent
Warning: ALREADY_ENABLED: cockpit
success
[root@localhost /]# firewall-cmd --reload
success

https://192.168.1.999:9090/ 로 접속하여 확인
- root 계정 접속이 안되어, 사용자 계정으로 로그인 함

5. Podman

CentOS 8 버전부터 Docker 대신 Podman 이 기본 Container API 임
Centos에 Podman 설치하기 - Podman 컨테이너 기초
Windows > https://192.168.1.999:9090/ 로 접속
좌측 목록에서 Podman Container 클릭
- '포드맨 서비스가 동작하지 않습니다.' > 부트 시 자동으로 podman 시작 클릭

🔶 Podman 저장소

Podman https://192.168.1.111:9090/storage > MySQL 작업 완료 후 확인해본 모습

5-1. Podman 환경 구성

registry 접근 정보

[root@localhost /]# view /etc/containers/registries.conf

unqualified-search-registries = ["registry.access.redhat.com", "registry.redhat.io", "docker.io"]
############ (중략) ############
insecure = false
blocked = false   // 필요에 따라 차단 등록을 한다

현재 redhat 계정은 없으므로 실제로 pulling 할 수 없음 (docker.io 만 가능함)
repo에서 적합한 mysql 찾아보기

🔶 Podman 기본 정보

버전 및 설치 환경 정보 확인

[root@localhost system-connections]# podman -v
podman version 4.9.3-dev

[root@localhost system-connections]# podman info

  kernel: 5.14.0-430.el9.x86_64

  remoteSocket:
    exists: false
    path: /run/podman/podman.sock

store:
  configFile: /etc/containers/storage.conf
  graphRoot: /var/lib/containers/storage
  imageCopyTmpDir: /var/tmp
  runRoot: /run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
  
version:
  APIVersion: 4.9.3-dev
  Built: 1707216158
  BuiltTime: Tue Feb  6 19:42:38 2024
  GitCommit: ""
  GoVersion: go1.21.3
  Os: linux
  OsArch: linux/amd64
  Version: 4.9.3-dev

🔶 podman-compose 버전

podman-compose 설치 및 버전 확인

[root@localhost ~]# podman-compose version
bash: podman-compose: command not found...
Install package 'podman-compose' to provide command 'podman-compose'? [N/y] y


 * Waiting in queue...
 * Loading list of packages....
The following packages have to be installed:
 gvisor-tap-vsock-6:0.7.3-2.el9.x86_64  Go replacement for libslirp and VPNKit
 podman-compose-1.0.6-3.el9.noarch      Run docker-compose.yml using podman
 podman-plugins-2:5.0.0-1.el9.x86_64    Plugins for podman
 python3-click-8.0.3-1.el9.noarch       Simple wrapper around optparse for powerful command line utilities
 python3-dotenv-0.19.2-3.el9.noarch     Read key-value pairs from a .env file and set them as environment variables
 python3-dotenv+cli-0.19.2-3.el9.noarch Metapackage for python3-dotenv: cli extras
Proceed with changes? [N/y] y

 * Waiting in queue...
 * Waiting for authentication...
 * Waiting in queue...
 * Downloading packages...
 * Requesting data...
 * Testing changes...
 * Installing packages...
podman-compose version: 1.0.6
['podman', '--version', '']
using podman version: 4.9.4-dev
podman-compose version 1.0.6
podman --version
podman version 4.9.4-dev
exit code: 0

[root@localhost ~]# podman-compose version
podman-compose version: 1.0.6
['podman', '--version', '']
using podman version: 4.9.4-dev
podman-compose version 1.0.6
podman --version
podman version 4.9.4-dev
exit code: 0

6. Java

현재 Java 는 이미 설치되어 있음
- 11 다운로드 명령어 : yum install java-11-openjdk-devel.x86_64
- 1.8.0 다운로드 명령어 : yum install java-1.8.0-openjdk-devel.x86_64

[root@localhost /]# java -version
openjdk version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-b08)
OpenJDK 64-Bit Server VM (build 25.362-b08, mixed mode)

yum 패키지 확인하기

[root@localhost /]# yum search openjdk
Last metadata expiration check: 2:28:07 ago on Thu 21 Mar 2024 12:44:55 PM KST.
============================================================= Name & Summary Matched: openjdk ==============================================================
java-1.8.0-openjdk.x86_64 : OpenJDK 8 Runtime Environment
java-1.8.0-openjdk-demo.x86_64 : OpenJDK 8 Demos
############ (중략) ############

링크 확인

[root@localhost /]# readlink -f /usr/bin/java
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre/bin/java

6-1. JAVA_HOME 환경변수

CentOS 에서는 /etc/profile.d 폴더에 custom.sh 파일로 개별 설정을 만들도록 권고
- /etc/profile 을 직접 수정하는 방식보다는 목적에 따라

[root@localhost ~]# export JAVA_HOME=$(readlink -f /usr/bin/java | sed "s:bin/java::")

.bash_profile 에만 적용

[root@localhost ~]# env | grep JAVA
JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre/

Java 설치 확인

[root@localhost ~]# ls /usr/lib/jvm
java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64  jre-1.8.0          jre-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64
jre                                            jre-1.8.0-openjdk  jre-openjdk

🔶 Java 버전 변경 시

Java 버전 alternatives

[root@localhost ~]# alternatives --config java

There is 1 program that provides 'java'.

  Selection    Command
-----------------------------------------------
*+ 1           java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre/bin/java)

Enter to keep the current selection[+], or type selection number: 1

JAVA_HOME 은 source 로 구동하거나 재로그인을 해야 변경됨

[root@localhost ~]# source .bash_profile
# 환경변수 변경된 내용 확인
[root@localhost ~]# env | grep JAVA
JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre/

alternatives 심볼릭 링크 생성 상태 확인

[root@localhost ~]# ls -l /etc/alternatives/jre*
lrwxrwxrwx. 1 root root 62 Mar 15 09:48 /etc/alternatives/jre -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre
lrwxrwxrwx. 1 root root 62 Mar 15 09:48 /etc/alternatives/jre_1.8.0 -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre
lrwxrwxrwx. 1 root root 57 Mar 15 09:48 /etc/alternatives/jre_1.8.0_openjdk -> /usr/lib/jvm/jre-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64
lrwxrwxrwx. 1 root root 62 Mar 15 09:48 /etc/alternatives/jre_openjdk -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre

7. MySQL

CentOS 에서 패키지 설치는 가능한 dnf 를 사용
ProjYj 2022 에서 모든 테스트가 완료되면 Podman image 로 생성
- 우분투 22 my8 환경 만들기.hwp 참고
MySQL 공통 PW : password$$ (기본 설정 > 소문자 구성도 허용)

7-1. MySQL 설치 파일 다운로드

/home/projyj/Downloads 경로에 세팅 > 웹 콘솔에서 다운로드하거나, Windows 다운로드 후 FileZilla 이용
http://repo.mysql.com/yum/mysql-8.0-community/ > el/9/x86_64 목록
- mysql80-community-release-el9-1.noarch.rpm 다운로드
- mysql-community-server-8.0.32-1.el9.x86_64.rpm 다운로드

[root@localhost Downloads]$ ll
total 50304
-rw-r--r--. 1  root  root    10534 Mar 22 10:23 mysql80-community-release-el9-1.noarch.rpm
-rw-r--r--. 1  root  root 51495202 Mar 22 09:59 mysql-community-server-8.0.32-1.el9.x86_64.rpm

🔶 MySQL Yum Repository

https://dev.mysql.com/downloads/repo/yum/
Red Hat Ent Linux 9 버전용 정보 확인
rpm 파일명 : mysql80-community-release-el9-1.noarch.rpm

7-2. MySQL 설치

중간에 오류 발생했으므로, 하단 Error: GPG check FAILED 부분까지 확인 필요
설치 실행

[root@localhost Downloads]$ sudo rpm -Uvh mysql80-community-release-el9-1.noarch.rpm
warning: mysql80-community-release-el9-1.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID 3a79bd29: NOKEY
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:mysql80-community-release-el9-1  ################################# [100%]

[root@localhost Downloads]$ rpm -Uvh  mysql-community-server-8.0.32-1.el9.x86_64.rpm
warning: mysql-community-server-8.0.32-1.el9.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 3a79bd29: NOKEY
error: Failed dependencies:
        mysql-community-client(x86-64) >= 8.0.11 is needed by mysql-community-server-8.0.32-1.el9.x86_64
        mysql-community-common(x86-64) = 8.0.32-1.el9 is needed by mysql-community-server-8.0.32-1.el9.x86_64
        mysql-community-icu-data-files = 8.0.32-1.el9 is needed by mysql-community-server-8.0.32-1.el9.x86_64

설치 상태 확인
- mysql-community-server-8.0.32-1.el9.x86_64.rpm 가 설치 실패함
- 이후 dnf install 성공 시에도 결과가 동일해서 일단 보류

[root@localhost Downloads]$ rpm -qi  mysql-community-server-8.0.32-1.el9.x86_64.rpm
warning: mysql-community-server-8.0.32-1.el9.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 3a79bd29: NOKEY
Name        : mysql-community-server
Version     : 8.0.32
Release     : 1.el9
Architecture: x86_64
Install Date: (not installed)
Group       : Applications/Databases
Size        : 246795859
License     : Copyright (c) 2000, 2022, Oracle and/or its affiliates. Under GPLv2 license as shown in the Description field.
Signature   : RSA/SHA256, Sat 17 Dec 2022 09:25:25 PM KST, Key ID 467b942d3a79bd29
Source RPM  : mysql-community-8.0.32-1.el9.src.rpm
Build Date  : Sat 17 Dec 2022 01:08:25 AM KST
Build Host  : pb2-el9-01.regionaliad02.mysql2iad.oraclevcn.com
Packager    : MySQL Release Engineering <[email protected]>
Vendor      : Oracle and/or its affiliates
URL         : http://www.mysql.com/
Summary     : A very fast and reliable SQL database server
Description :
############ (중략) ############

dnf 로 설치하기
- sudo dnf remove : 설치된 패키지 제거하기

[root@localhost Downloads]$ sudo dnf install mysql-community-server-8.0.32-1.el9.x86_64.rpm
[sudo] password for  root:
Last metadata expiration check: 2:39:58 ago on Fri 22 Mar 2024 12:28:45 PM KST.
Dependencies resolved.
=============================================================================================================================================================
 Package                                            Architecture               Version                           Repository                             Size
=============================================================================================================================================================
Installing:
 mysql-community-server                             x86_64                     8.0.32-1.el9                      @commandline                           49 M
     replacing  mariadb-connector-c-config.noarch 3.2.6-1.el9
Installing dependencies:
 mysql-community-client                             x86_64                     8.0.36-1.el9                      mysql80-community                     3.4 M
 mysql-community-client-plugins                     x86_64                     8.0.36-1.el9                      mysql80-community                     1.4 M
 mysql-community-common                             x86_64                     8.0.32-1.el9                      mysql80-community                     544 k
 mysql-community-icu-data-files                     x86_64                     8.0.32-1.el9                      mysql80-community                     2.2 M
 mysql-community-libs                               x86_64                     8.0.36-1.el9                      mysql80-community                     1.4 M

Transaction Summary
=============================================================================================================================================================
Install  6 Packages

Total size: 58 M
Total download size: 8.9 M
Is this ok [y/N]: y
Downloading Packages:
(1/5): mysql-community-common-8.0.32-1.el9.x86_64.rpm                                                                        1.8 MB/s | 544 kB     00:00
(2/5): mysql-community-client-plugins-8.0.36-1.el9.x86_64.rpm                                                                2.4 MB/s | 1.4 MB     00:00
(3/5): mysql-community-client-8.0.36-1.el9.x86_64.rpm                                                                        3.5 MB/s | 3.4 MB     00:00
(4/5): mysql-community-libs-8.0.36-1.el9.x86_64.rpm                                                                          3.4 MB/s | 1.4 MB     00:00
(5/5): mysql-community-icu-data-files-8.0.32-1.el9.x86_64.rpm                                                                2.9 MB/s | 2.2 MB     00:00
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                        8.4 MB/s | 8.9 MB     00:01
MySQL 8.0 Community Server                                                                                                   3.0 MB/s | 3.1 kB     00:00
Importing GPG key 0x3A79BD29:
 Userid     : "MySQL Release Engineering <[email protected]>"
 Fingerprint: 859B E8D7 C586 F538 430B 19C2 467B 942D 3A79 BD29
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
Is this ok [y/N]: y
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
Public key for mysql-community-client-8.0.36-1.el9.x86_64.rpm is not installed. Failing package is: mysql-community-client-8.0.36-1.el9.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
Public key for mysql-community-client-plugins-8.0.36-1.el9.x86_64.rpm is not installed. Failing package is: mysql-community-client-plugins-8.0.36-1.el9.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
Public key for mysql-community-libs-8.0.36-1.el9.x86_64.rpm is not installed. Failing package is: mysql-community-libs-8.0.36-1.el9.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

🔶 Error: GPG check FAILED

dnf install 진행 시 오류 발생
원인 : GPG-KEY 인증이 되고 있지 않았기 때문
인증을 위해서 rpm 에 key 를 import 시킴

[root@localhost rpm-gpg]$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
[sudo] password for  root:
[root@localhost Downloads]$ sudo rpm --import https://repo.mysql.com/RPM-GPG-KEY-mysql-2022

# 시도 했다가 다시 2022 로 돌렸음 (혹시 영향이 있을까봐 기재)
[root@localhost Downloads]$ sudo rpm --import https://repo.mysql.com/RPM-GPG-KEY-mysql-2023

위의 내용을 수행하고 다시 dnf install 진행해도 오류 발생
dnf check-update 수행

[root@localhost Downloads]$ dnf check-update
CentOS Stream 9 - BaseOS                                                                                                     1.1 MB/s | 8.0 MB     00:07
CentOS Stream 9 - AppStream                                                                                                  2.6 MB/s |  19 MB     00:07
CentOS Stream 9 - Extras packages                                                                                            2.3 kB/s |  16 kB     00:06
Extra Packages for Enterprise Linux 9 - x86_64                                                                               4.2 MB/s |  21 MB     00:04
Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64                                                         463  B/s | 2.5 kB     00:05
Extra Packages for Enterprise Linux 9 - Next - x86_64                                                                        453 kB/s | 1.4 MB     00:03
MySQL 8.0 Community Server                                                                                                   3.2 MB/s | 1.4 MB     00:00
MySQL Connectors Community                                                                                                   227 kB/s |  45 kB     00:00
MySQL Tools Community                                                                                                        1.6 MB/s | 536 kB     00:00

mysql80-community-release.noarch                                                 el9-5                                                      mysql80-community
xrdp.x86_64                                                                      1:0.9.25-2.el9                                             epel
xrdp-selinux.x86_64                                                              1:0.9.25-2.el9                                             epel
Obsoleting Packages
mysql-community-server.x86_64                                                    8.0.30-1.el9                                               mysql80-community
############ (중략) ############

🔶 dnf install 재실행

[root@localhost Downloads]$ sudo dnf install mysql-community-server-8.0.32-1.el9.x86_64.rpm
Last metadata expiration check: 3:13:05 ago on Fri 22 Mar 2024 12:28:45 PM KST.
Dependencies resolved.
=============================================================================================================================================================
 Package                                            Architecture               Version                           Repository                             Size
=============================================================================================================================================================
Installing:
 mysql-community-server                             x86_64                     8.0.32-1.el9                      @commandline                           49 M
     replacing  mariadb-connector-c-config.noarch 3.2.6-1.el9
Installing dependencies:
 mysql-community-client                             x86_64                     8.0.36-1.el9                      mysql80-community                     3.4 M
 mysql-community-client-plugins                     x86_64                     8.0.36-1.el9                      mysql80-community                     1.4 M
 mysql-community-common                             x86_64                     8.0.32-1.el9                      mysql80-community                     544 k
 mysql-community-icu-data-files                     x86_64                     8.0.32-1.el9                      mysql80-community                     2.2 M
 mysql-community-libs                               x86_64                     8.0.36-1.el9                      mysql80-community                     1.4 M

Transaction Summary
=============================================================================================================================================================
Install  6 Packages

Total size: 58 M
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] mysql-community-client-8.0.36-1.el9.x86_64.rpm: Already downloaded
[SKIPPED] mysql-community-client-plugins-8.0.36-1.el9.x86_64.rpm: Already downloaded
[SKIPPED] mysql-community-common-8.0.32-1.el9.x86_64.rpm: Already downloaded
[SKIPPED] mysql-community-icu-data-files-8.0.32-1.el9.x86_64.rpm: Already downloaded
[SKIPPED] mysql-community-libs-8.0.36-1.el9.x86_64.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                     1/1
  Installing       : mysql-community-common-8.0.32-1.el9.x86_64                                                                                          1/7
  Installing       : mysql-community-client-plugins-8.0.36-1.el9.x86_64                                                                                  2/7
  Installing       : mysql-community-libs-8.0.36-1.el9.x86_64                                                                                            3/7
  Running scriptlet: mysql-community-libs-8.0.36-1.el9.x86_64                                                                                            3/7
  Installing       : mysql-community-client-8.0.36-1.el9.x86_64                                                                                          4/7
  Installing       : mysql-community-icu-data-files-8.0.32-1.el9.x86_64                                                                                  5/7
  Running scriptlet: mysql-community-server-8.0.32-1.el9.x86_64                                                                                          6/7
  Installing       : mysql-community-server-8.0.32-1.el9.x86_64                                                                                          6/7
  Running scriptlet: mysql-community-server-8.0.32-1.el9.x86_64                                                                                          6/7
  Obsoleting       : mariadb-connector-c-config-3.2.6-1.el9.noarch                                                                                       7/7
  Running scriptlet: mariadb-connector-c-config-3.2.6-1.el9.noarch                                                                                       7/7
  Verifying        : mysql-community-client-8.0.36-1.el9.x86_64                                                                                          1/7
  Verifying        : mysql-community-client-plugins-8.0.36-1.el9.x86_64                                                                                  2/7
  Verifying        : mysql-community-common-8.0.32-1.el9.x86_64                                                                                          3/7
  Verifying        : mysql-community-icu-data-files-8.0.32-1.el9.x86_64                                                                                  4/7
  Verifying        : mysql-community-libs-8.0.36-1.el9.x86_64                                                                                            5/7
  Verifying        : mysql-community-server-8.0.32-1.el9.x86_64                                                                                          6/7
  Verifying        : mariadb-connector-c-config-3.2.6-1.el9.noarch                                                                                       7/7

Installed:
  mysql-community-client-8.0.36-1.el9.x86_64            mysql-community-client-plugins-8.0.36-1.el9.x86_64    mysql-community-common-8.0.32-1.el9.x86_64
  mysql-community-icu-data-files-8.0.32-1.el9.x86_64    mysql-community-libs-8.0.36-1.el9.x86_64              mysql-community-server-8.0.32-1.el9.x86_64

Complete!

활성화 및 비활성화된 MySQL 리포지토리를 모두 나열

[root@localhost Downloads]$ dnf repolist all | grep mysql
mysql-cluster-8.0-community           MySQL Cluster 8.0 Community       disabled
mysql-cluster-8.0-community-debuginfo MySQL Cluster 8.0 Community - Deb disabled
mysql-cluster-8.0-community-source    MySQL Cluster 8.0 Community - Sou disabled
mysql-connectors-community            MySQL Connectors Community        enabled
mysql-connectors-community-debuginfo  MySQL Connectors Community - Debu disabled
mysql-connectors-community-source     MySQL Connectors Community - Sour disabled
mysql-tools-community                 MySQL Tools Community             enabled
mysql-tools-community-debuginfo       MySQL Tools Community - Debuginfo disabled
mysql-tools-community-source          MySQL Tools Community - Source    disabled
mysql80-community                     MySQL 8.0 Community Server        enabled
mysql80-community-debuginfo           MySQL 8.0 Community Server - Debu disabled
mysql80-community-source              MySQL 8.0 Community Server - Sour disabled

설치된 mysql * 패키지 목록

[root@localhost mysql]$ sudo dnf list installed | grep mysql
mysql-community-client.x86_64                    8.0.36-1.el9                       @mysql80-community
mysql-community-client-plugins.x86_64            8.0.36-1.el9                       @mysql80-community
mysql-community-common.x86_64                    8.0.32-1.el9                       @mysql80-community
mysql-community-icu-data-files.x86_64            8.0.32-1.el9                       @mysql80-community
mysql-community-libs.x86_64                      8.0.36-1.el9                       @mysql80-community
mysql-community-server.x86_64                    8.0.32-1.el9                       @@commandline
mysql-ref-manual-8.0-en-html-chapter.noarch      1-20220914                         @mysql80-community
mysql80-community-release.noarch                 el9-1                              @System
pcp-pmda-mysql.x86_64                            6.2.0-1.el9                        @AppStream

🔶 패키지 추가 설치

repo 에서 추가 설치 가능한 패키지 확인하기

[root@localhost mysql]$ dnf --disablerepo=\* --enablerepo='mysql*-community*' list available
No read/execute access in current directory, moving to /
MySQL Cluster 8.0 Community                                                                                                  2.4 MB/s | 1.5 MB     00:00
MySQL 8.0 Community Server - Debuginfo                                                                                       386 kB/s | 136 kB     00:00
MySQL Connectors Community - Debuginfo                                                                                        15 kB/s | 7.6 kB     00:00
MySQL Tools Community - Debuginfo                                                                                             65 kB/s |  25 kB     00:00
MySQL Cluster 8.0 Community - Debuginfo                                                                                      315 kB/s | 155 kB     00:00
MySQL 8.0 Community Server - Source                                                                                          8.3 kB/s | 3.2 kB     00:00
MySQL Connectors Community - Source                                                                                          8.9 kB/s | 5.1 kB     00:00
MySQL Tools Community - Source                                                                                               6.6 kB/s | 2.8 kB     00:00
MySQL Cluster 8.0 Community - Source                                                                                         5.9 kB/s | 2.9 kB     00:00
Available Packages
mysql-cluster-community.src                                                       8.0.36-1.el9                          mysql-cluster-8.0-community-source
mysql-cluster-community-client.x86_64                                             8.0.36-1.el9                          mysql-cluster-8.0-community
mysql-cluster-community-client-debuginfo.x86_64                                   8.0.36-1.el9                          mysql-cluster-8.0-community-debuginfo
mysql-cluster-community-client-plugins.x86_64                                     8.0.36-1.el9                          mysql-cluster-8.0-community
mysql-cluster-community-client-plugins-debuginfo.x86_64                           8.0.36-1.el9                          mysql-cluster-8.0-community-debuginfo
mysql-cluster-community-common.x86_64                                             8.0.36-1.el9                          mysql-cluster-8.0-community
############ (중략) ############

mysql-ref-manual-8.0-en-html-chapter.noarch 패키지 추가 설치

[root@localhost mysql]$ sudo dnf install mysql-ref-manual-8.0-en-html-chapter.noarch
Last metadata expiration check: 0:56:36 ago on Fri 22 Mar 2024 03:42:06 PM KST.
Dependencies resolved.
=============================================================================================================================================================
 Package                                                 Architecture              Version                        Repository                            Size
=============================================================================================================================================================
Installing:
 mysql-ref-manual-8.0-en-html-chapter                    noarch                    1-20220914                     mysql80-community                    7.9 M

Transaction Summary
=============================================================================================================================================================
Install  1 Package

Total download size: 7.9 M
Installed size: 41 M
Is this ok [y/N]: y
Downloading Packages:
mysql-ref-manual-8.0-en-html-chapter-1-20220914.noarch.rpm                                                                   8.1 MB/s | 7.9 MB     00:00
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                        8.1 MB/s | 7.9 MB     00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                     1/1
  Installing       : mysql-ref-manual-8.0-en-html-chapter-1-20220914.noarch                                                                              1/1
  Verifying        : mysql-ref-manual-8.0-en-html-chapter-1-20220914.noarch                                                                              1/1

Installed:
  mysql-ref-manual-8.0-en-html-chapter-1-20220914.noarch

Complete!

7-3. MySQL DB 데이터 저장소 변경

조건 : systemctl status mysqld 결과 inactive (dead) 상태여야 함
DB 데이터 저장소로 지정될 경로 : /cargo1
my.cnf 파일 > datadir, socket 경로 수정
- 테이블명 조회 시 대소문자 구분 없이 사용하도록 하는 설정도 함께 추가

[root@localhost mysql]$ sudo vi /etc/my.cnf

[mysqld]
#datadir=/var/lib/mysql
#socket=/var/lib/mysql/mysql.sock
datadir=/cargo1/mysql
socket=/cargo1/mysql/mysql.sock
lower_case_table_names=1
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

rsync 작업 시 기존 스키마들을 모두 복사하여 가져옴 (현재 환경에는 생성된 스키마가 없지만 우선 따라함)

# mysql 복사
[root@localhost mysql]$ sudo rsync -av /var/lib/mysql /cargo1
sending incremental file list
mysql/

sent 64 bytes  received 20 bytes  168.00 bytes/sec
total size is 0  speedup is 0.00

# mysql 권한 부여
[root@localhost mysql]$ sudo chown -R mysql:mysql /cargo1/mysql

SElinux 보안 추가
- 프로세스에 새로 권한을 추가해주었기 때문에 해당 경로의 SElinux 보안 컨텍스트를 추가해야 함
- 추가하지 않으면 MySQL 실행시 permission 에러 발생 (에러 내용은 /var/log/audit/audit.log 에서 확인 가능)
- 안된다고 SElinux 를 해제하는것은 매우 위험하므로 비추

[root@localhost mysql]$ sudo semanage fcontext -a -t mysqld_db_t "/cargo1/mysql(/.*)?"
[root@localhost mysql]$ sudo restorecon -R /cargo1/mysql

# 설정 완료되었는지 확인
[root@localhost mysql]$ sudo semanage fcontext -l | grep mysql
/cargo1/mysql(/.*)?                                all files          system_u:object_r:mysqld_db_t:s0

7-4. MySQL 실행

systemctl status mysqld : 상태 확인
- systemctl start mysqld : MySQL 실행
- systemctl stop mysqld : MySQL 종료

[root@localhost mysql]$ systemctl status mysqld
○ mysqld.service - MySQL Server
     Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; preset: disabled)
     Active: inactive (dead)
       Docs: man:mysqld(8)
             http://dev.mysql.com/doc/refman/en/using-systemd.html
[root@localhost mysql]$ systemctl start mysqld
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to start 'mysqld.service'.
Authenticating as: YNJCH (root)
Password:
==== AUTHENTICATION COMPLETE ====
[root@localhost mysql]$ systemctl status mysqld
● mysqld.service - MySQL Server
     Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; preset: disabled)
     Active: active (running) since Fri 2024-03-22 16:34:12 KST; 13s ago
       Docs: man:mysqld(8)
             http://dev.mysql.com/doc/refman/en/using-systemd.html
    Process: 417304 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
   Main PID: 417378 (mysqld)
     Status: "Server is operational"
      Tasks: 39 (limit: 202223)
     Memory: 451.2M
        CPU: 6.081s
     CGroup: /system.slice/mysqld.service
             └─417378 /usr/sbin/mysqld

Mar 22 16:33:25 localhost.localdomain systemd[1]: Starting MySQL Server...
Mar 22 16:34:12 localhost.localdomain systemd[1]: Started MySQL Server.

/cargo1/mysql 경로에 파일들이 생긴 것 확인 가능

[root@localhost mysql]$ pwd
/cargo1/mysql
[root@localhost mysql]$ sudo ls
 auto.cnf        ca-key.pem        client-key.pem       ib_buffer_pool  '#innodb_redo'   mysql.ibd         performance_schema   server-cert.pem   undo_001
 binlog.000001   ca.pem           '#ib_16384_0.dblwr'   ibdata1         '#innodb_temp'   mysql.sock        private_key.pem      server-key.pem    undo_002
 binlog.index    client-cert.pem  '#ib_16384_1.dblwr'   ibtmp1           mysql           mysql.sock.lock   public_key.pem       sys

🔶 systemctl start mysqld 실패

아래와 같이 오류 발생과 함께 start 되지 않음

[root@localhost mysql]$ systemctl start mysqld
############ (중략) ############
Job for mysqld.service failed because the control process exited with error code.
See "systemctl status mysqld.service" and "journalctl -xeu mysqld.service" for details.

/var/log/mysqld.log 에서 아래 문구 확인 (https://dev-taerin.tistory.com/14)

2024-03-22T07:47:45.105142Z 1 [ERROR] [MY-011087] [Server] Different lower_case_table_names settings for server ('1') and data dictionary ('0').
2024-03-22T07:47:45.105570Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.

lower_case_table_names=1 값의 위치, #datadir 등의 주석 처리가 제대로 되었는지 확인
- systemctl stop mysqld 후 파일 수정을 해야 함
이후에도 계속 문제 발생 시, my.cnf 가 초기화 시에 수정이 이루어진 것인지 체크
- MySQL 초기화(제거 및 재설치) 후 my.cnf 부터 수정하도록 위의 절차 다시 진행

[root@localhost mysql]$ sudo vi /etc/my.cnf

[mysqld]
#datadir=/var/lib/mysql
#socket=/var/lib/mysql/mysql.sock
datadir=/cargo1/mysql
socket=/cargo1/mysql/mysql.sock
lower_case_table_names=1
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

chmod 755 my.cnf 명령어 수행

[root@localhost etc]# chmod 755 my.cnf

-rwxr-xr-x.   1 root root      1326 Mar 25 10:37 my.cnf

🔶 3306 Port 상시 허용

방화벽에 3306 Port를 상시 허용으로 등록 및 재실행

[root@localhost ~]# sudo firewall-cmd --permanent --zone=public --add-port=3306/tcp
success
[root@localhost ~]# sudo firewall-cmd --reload
success
[root@localhost ~]# sudo firewall-cmd --list-port
3306/tcp 3389/tcp

🔶 status 확인

mysql> status
--------------
mysql  Ver 8.0.36 for Linux on x86_64 (MySQL Community Server - GPL)

Connection id:          13
Current database:
Current user:           root@localhost
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server version:         8.0.32 MySQL Community Server - GPL
Protocol version:       10
Connection:             Localhost via UNIX socket
Server characterset:    utf8mb4
Db     characterset:    utf8mb4
Client characterset:    utf8mb4
Conn.  characterset:    utf8mb4
UNIX socket:            /cargo1/mysql/mysql.sock
Binary data as:         Hexadecimal

🔶 Character Set 확인

Character Set : utf8 / 4byte (변경할 사항 없음)

mysql> show variables like "ch%";
+--------------------------+--------------------------------+
| Variable_name            | Value                          |
+--------------------------+--------------------------------+
| character_set_client     | utf8mb4                        |
| character_set_connection | utf8mb4                        |
| character_set_database   | utf8mb4                        |
| character_set_filesystem | binary                         |
| character_set_results    | utf8mb4                        |
| character_set_server     | utf8mb4                        |
| character_set_system     | utf8mb3                        |
| character_sets_dir       | /usr/share/mysql-8.0/charsets/ |
| check_proxy_users        | OFF                            |
+--------------------------+--------------------------------+
9 rows in set (0.01 sec)

mysql> show variables like "col%";
+----------------------+--------------------+
| Variable_name        | Value              |
+----------------------+--------------------+
| collation_connection | utf8mb4_0900_ai_ci |
| collation_database   | utf8mb4_0900_ai_ci |
| collation_server     | utf8mb4_0900_ai_ci |
+----------------------+--------------------+
3 rows in set (0.00 sec)

8. MySQL 계정

8-1. root 접속

임시 패스워드 확인 & root 패스워드 변경

[root@localhost mysql]$ sudo grep 'temporary password' /var/log/mysqld.log
2024-03-22T07:33:42.873919Z 6 [Note] [MY-010454] [Server] A temporary password is generated for root@localhost: duy4Xcq-aH%L

root 접속

[root@localhost mysql]$ mysql -uroot -p
Enter password: [duy4Xcq-aH%L]

🔶 Can't connect to local MySQL server through socket

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'
MySQL의 소켓 파일인 mysql.sock 파일이 없거나 정확하지 않아서 발생하는 에러
/cargo1/mysql 로 디렉토리 변경하면서 발생됨
- (24.04.01 삭제 후 재설치하니 socket 위치 기재하지 않아도 접속됨)

[root@localhost mysql]# mysql -uroot -p -S '/cargo1/mysql/mysql.sock'

위와 같이 소켓 파일 위치를 직접 지정해줄 수 있음
로그 확인 : tail -f /var/log/mysqld.log

mysql.sock 파일 위치 찾기

[root@localhost /]# find / -name mysql.sock
find: ‘/run/user/1000/gvfs’: Permission denied
/cargo1/mysql/mysql.sock

8-2. root 패스워드 변경

임시 패스워드에서 초기화해야 함
대문자를 포함해야 해서 소문자만으로도 사용할 수 있도록 패스워드 구성 방법 변경 필요

mysql> alter user 'root'@'localhost' identified by 'password$$';
ERROR 1819 (HY000): Your password does not satisfy the current policy requirements

mysql> alter user 'root'@'localhost' identified by 'password$$';
Query OK, 0 rows affected (0.06 sec)

mysql> show variables like 'val%';
+--------------------------------------+--------+
| Variable_name                        | Value  |
+--------------------------------------+--------+
| validate_password.check_user_name    | ON     |
| validate_password.dictionary_file    |        |
| validate_password.length             | 8      |
| validate_password.mixed_case_count   | 1      |
| validate_password.number_count       | 1      |
| validate_password.policy             | MEDIUM |
| validate_password.special_char_count | 1      |
+--------------------------------------+--------+
7 rows in set (0.00 sec)

mysql> SET GLOBAL validate_password.mixed_case_count = 0;
Query OK, 0 rows affected (0.00 sec)

# 다시 'password$$' 으로 PW 변경

앞으로 로그인 시

[root@localhost mysql]# mysql -uroot -p -S '/cargo1/mysql/mysql.sock'
Enter password: [password$$]

8-3. 계정 추가 및 권한 설정

'root'@'%' 설정

mysql> create user 'root'@'%' identified by 'password$$';
Query OK, 0 rows affected (0.02 sec)

mysql> create user 'projyj'@localhost identified by 'password$$';
Query OK, 0 rows affected (0.02 sec)

mysql> create user 'projyj'@'%' identified by 'password$$';
Query OK, 0 rows affected (0.01 sec) 

mysql> grant all privileges on *.* to 'projyj'@'%';
Query OK, 0 rows affected (0.02 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.01 sec)

select host, user, authentication_string from USER; 로 확인 가능

🔶 암호화 방식 변경

8.0.32 버전 암호화 방식 확인 : caching_sha2_password

mysql> SELECT User, Host, plugin FROM mysql.user;
+------------------+-----------+-----------------------+
| User             | Host      | plugin                |
+------------------+-----------+-----------------------+
| projyj            | %         | caching_sha2_password |
| root             | %         | caching_sha2_password |
| projyj            | localhost | caching_sha2_password |
| root             | localhost | caching_sha2_password |
| mysql.infoschema | localhost | caching_sha2_password |
| mysql.session    | localhost | caching_sha2_password |
| mysql.sys        | localhost | caching_sha2_password |
+------------------+-----------+-----------------------+

ProjYj 사용 계정은 예전 방식의 암호체계 mysql_native_password 로 변경해야 함

mysql> ALTER USER 'projyj'@'%' IDENTIFIED WITH mysql_native_password BY 'password$$';
mysql> ALTER USER 'projyj'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password$$';

🔶 MySQL 사용자 계정 비밀번호 정책

MySQL 사용자 계정 비밀번호 정책 변경
validate_password_policy 를 LOW 로 설정

mysql> set global validate_password.policy=LOW;
Query OK, 0 rows affected (0.00 sec)

9. MySQL 테이블 생성

9-1. 데이터베이스 생성

projyj 데이터베이스 생성

mysql> create database projyj;
Query OK, 1 row affected (0.15 sec)

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| projyj              |
| information_schema |
| mysql              |
| performance_schema |
| sys                |
+--------------------+
5 rows in set (0.00 sec)

9-2. 테이블 생성

FileZilla > /home > EZMIG_init.sql, ALTER_TABLE.sql, ALTER_TABLE_COLUMN.sql 파일을 업로드

[root@localhost home]# cd /home
[root@localhost home]# ls
ALTER_TABLE_COLUMN.sql  ALTER_TABLE.sql  EZMIG_init.sql  projyj

EZMIG_init.sql 실행 > 57개 테이블이 생성되면 성공

[root@localhost home]#  mysql -uroot -p projyj -S '/cargo1/mysql/mysql.sock' < EZMIG_init.sql
Enter password:

ALTER_TABLE_COLUMN.sql 실행 > 테이블 및 컬럼 코멘트가 생성되면 성공

[root@localhost home]#  mysql -uroot -p projyj -S '/cargo1/mysql/mysql.sock' < ALTER_TABLE.sql
Enter password:
[root@localhost home]#  mysql -uroot -p projyj -S '/cargo1/mysql/mysql.sock' < ALTER_TABLE_COLUMN.sql
Enter password:

🔶 DBeaver 에서 확인

Public Key Retrieval is not allowed 오류 발생 시, URL 에 ?useSSL=false&allowPublicKeyRetrieval=true 추가
URL : jdbc:mysql://192.168.1.111:3306/projyj?useSSL=false&allowPublicKeyRetrieval=true
ID : projyj / PW : password$$

10. 네트워크 상태 확인

서버의 기본 사용 포트를 유지하며, ProjYj Web 서버는 8070 포트를 사용하도록 함
포트 확인 : netstat -ltnp | grep 8070
포트 죽이기 : kill -9 [PID]

10-1. 네트워크 상태 확인

netstat > 모든 수신 소켓과 연결을 확인
lsof > TCP port 접속 정보 확인 및 요약 보기

[root@localhost home]# netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:44321         0.0.0.0:*               LISTEN      2195/pmcd
tcp        0      0 127.0.0.1:5910          0.0.0.0:*               LISTEN      349956/Xvnc
tcp        0      0 127.0.0.1:4330          0.0.0.0:*               LISTEN      3175/pmlogger
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      351164/sshd: /usr/s
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      1/systemd
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      1324/cupsd
tcp6       0      0 :::9090                 :::*                    LISTEN      1/systemd
tcp6       0      0 ::1:44321               :::*                    LISTEN      2195/pmcd
tcp6       0      0 ::1:4330                :::*                    LISTEN      3175/pmlogger
tcp6       0      0 ::1:5910                :::*                    LISTEN      349956/Xvnc
tcp6       0      0 :::33060                :::*                    LISTEN      549541/mysqld
tcp6       0      0 :::22                   :::*                    LISTEN      351164/sshd: /usr/s
tcp6       0      0 :::111                  :::*                    LISTEN      1/systemd
tcp6       0      0 :::3389                 :::*                    LISTEN      345161/xrdp
tcp6       0      0 :::3306                 :::*                    LISTEN      549541/mysqld
tcp6       0      0 ::1:631                 :::*                    LISTEN      1324/cupsd
tcp6       0      0 ::1:3350                :::*                    LISTEN      345160/xrdp-sesman

[root@localhost home]# sudo lsof -i TCP -P |grep LISTEN
systemd        1  root   80u  IPv4  777988      0t0  TCP *:111 (LISTEN)
systemd        1  root   84u  IPv6  777019      0t0  TCP *:111 (LISTEN)
systemd        1  root  248u  IPv6  802458      0t0  TCP *:9090 (LISTEN)
cupsd       1324  root    6u  IPv6   20817      0t0  TCP localhost:631 (LISTEN)
cupsd       1324  root    7u  IPv4   20818      0t0  TCP localhost:631 (LISTEN)
pmcd        2195   pcp    0u  IPv4   17264      0t0  TCP localhost:44321 (LISTEN)
pmcd        2195   pcp    3u  IPv6   17265      0t0  TCP localhost:44321 (LISTEN)
pmlogger    3175   pcp    7u  IPv4 1337160      0t0  TCP localhost:4330 (LISTEN)
pmlogger    3175   pcp    8u  IPv6 1337161      0t0  TCP localhost:4330 (LISTEN)
xrdp-sesm 345160  root   11u  IPv6  742974      0t0  TCP localhost:3350 (LISTEN)
xrdp      345161  root   11u  IPv6  746744      0t0  TCP *:3389 (LISTEN)
Xvnc      349956  root    6u  IPv4  760993      0t0  TCP localhost:5910 (LISTEN)
Xvnc      349956  root    7u  IPv6  760994      0t0  TCP localhost:5910 (LISTEN)
sshd      351164  root    3u  IPv4  763481      0t0  TCP *:22 (LISTEN)
sshd      351164  root    4u  IPv6  763483      0t0  TCP *:22 (LISTEN)
mysqld    549541 mysql   21u  IPv6 1688602      0t0  TCP *:33060 (LISTEN)
mysqld    549541 mysql   24u  IPv6 1684797      0t0  TCP *:3306 (LISTEN)

[root@localhost home]# sudo lsof -i -nP | grep LISTEN | awk '{print $(NF-1)" "$1}' | sort
*:111 systemd
*:111 systemd
127.0.0.1:4330 pmlogger
127.0.0.1:44321 pmcd
127.0.0.1:5910 Xvnc
127.0.0.1:631 cupsd
[::1]:3350 xrdp-sesm
[::1]:4330 pmlogger
[::1]:44321 pmcd
[::1]:5910 Xvnc
[::1]:631 cupsd
*:22 sshd
*:22 sshd
*:33060 mysqld
*:3306 mysqld
*:3389 xrdp
*:9090 systemd

11. Tomcat 설치

8.0.36 버전을 기준으로 설치
rpm 배포 파일이 없고, 압축 파일로만 제공됨 > wget 으로 다운로드 진행

# 디렉토리 생성
[root@localhost /]# mkdir projyjengine
[root@localhost /]# mkdir tomcat
# wget 으로 다운로드
[root@localhost Downloads]# pwd
/root/Downloads
[root@localhost Downloads]# wget https://archive.apache.org/dist/tomcat/tomcat-8/v8.0.36/bin/apache-tomcat-8.0.36.tar.gz
--2024-03-28 09:45:52--  https://archive.apache.org/dist/tomcat/tomcat-8/v8.0.36/bin/apache-tomcat-8.0.36.tar.gz
Resolving archive.apache.org (archive.apache.org)... 65.108.204.189, 2a01:4f9:1a:a084::2
Connecting to archive.apache.org (archive.apache.org)|65.108.204.189|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9277365 (8.8M) [application/x-gzip]
Saving to: ‘apache-tomcat-8.0.36.tar.gz’

apache-tomcat-8.0.36.tar.gz             100%[============================================================================>]   8.85M   939KB/s    in 11s

2024-03-28 09:46:04 (831 KB/s) - ‘apache-tomcat-8.0.36.tar.gz’ saved [9277365/9277365]

/tomcat 경로에 압축 풀기

[root@localhost Downloads]# tar -xvf  apache-tomcat-8.0.36.tar.gz -C /tomcat/
apache-tomcat-8.0.36/bin/catalina.sh
apache-tomcat-8.0.36/bin/configtest.sh
apache-tomcat-8.0.36/bin/daemon.sh

11-1. Tomcat 설정

server.xml : 8080 포트를 8070 로 변경하고 저장

[root@localhost conf]# pwd
/tomcat/apache-tomcat-8.0.36/conf
[root@localhost conf]# vi server.xml

    <Connector port="8070" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />

Time zone 확인

[root@localhost conf]# timedatectl
               Local time: Thu 2024-03-28 09:51:11 KST
           Universal time: Thu 2024-03-28 00:51:11 UTC
                 RTC time: Thu 2024-03-28 09:51:11
                Time zone: Asia/Seoul (KST, +0900)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: yes

방화벽 8070 포트 열기 (8888 이었다가 변경함)

[root@localhost ~]# firewall-cmd --permanent --zone=public --add-port=8070/tcp
success
[root@localhost ~]# firewall-cmd --reload
success
[root@localhost ~]# firewall-cmd --list-port
3306/tcp 3389/tcp 8070/tcp 8888/tcp

Java Version 확인 : openjdk version "1.8.0_362"

[root@localhost conf]# java -version
openjdk version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-b08)
OpenJDK 64-Bit Server VM (build 25.362-b08, mixed mode)

🔶 환경변수 설정

환경변수 설정 진행하진 않았으나, 일단 기록해둔 것임
/etc/profile 을 직접 수정

[root@localhost etc]# cd /etc
[root@localhost etc]# vi profile

JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre
CATALINA_HOME=/tomcat/apache-tomcat-8.0.36

11-2. Tomcat 구동

http://192.168.1.999:8070/ 정상 접속되는 것 확인

[root@localhost bin]# pwd
/tomcat/apache-tomcat-8.0.36/bin
[root@localhost bin]# ./startup.sh
Using CATALINA_BASE:   /tomcat/apache-tomcat-8.0.36
Using CATALINA_HOME:   /tomcat/apache-tomcat-8.0.36
Using CATALINA_TMPDIR: /tomcat/apache-tomcat-8.0.36/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /tomcat/apache-tomcat-8.0.36/bin/bootstrap.jar:/tomcat/apache-tomcat-8.0.36/bin/tomcat-juli.jar
Tomcat started.

12. CentOS IP 변경

참고 : 네트워크 설정 - IP 변경 / CentOS7 IP 변경하기 / CentOS 에서 IP 설정 및 변경하기 / CentOS 7 고정 IP 설정
이 방법으로 되지 않아서 아래 명령어 수행 후, 13. CentOS IP 변경 으로 넘어감

[root@localhost network-scripts]# rm -rf ifcfg-eno1

12-1. 이더넷 세팅

네트워크 인터페이스 name 확인 : eno1
- inet 192.168.1.999 을 확인

[root@localhost bin]# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.999  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::dabb:c1ff:fe4d:c443  prefixlen 64  scopeid 0x20<link>
        ether d8:bb:c1:4d:c4:43  txqueuelen 1000  (Ethernet)
        RX packets 480472  bytes 169286658 (161.4 MiB)
        RX errors 0  dropped 32337  overruns 0  frame 0
        TX packets 249470  bytes 258333052 (246.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xa1200000-a1220000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 62902  bytes 3802084 (3.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 62902  bytes 3802084 (3.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# 아래 방법으로도 확인 가능
[root@localhost bin]# ls /sys/class/net
eno1  lo

ifcfg-eno1 파일이 없어서 새로 생성
- BOOTPROTO : dhcp 대신 static 으로 설정 (dhcp: 자동할당 / static: 수동으로 설정)
- IPADDR : 설정할 IP 주소
- NETMASK : 서브넷 마스크 주소
- GATEWAY : 게이트웨이 주소
- DNS : DNS주소 (웹 사이트 연결하지 않을 경우 필요 없음)
- ONBOOT : no일 경우 yes로 바꾸기 (부팅할 때 자동 네트워크 활성화 설정하는 것)
- DEVICE : 위의 name 값 eno1

[root@localhost network-scripts]# cd /etc/sysconfig/network-scripts
[root@localhost network-scripts]# touch ifcfg-eno1
[root@localhost network-scripts]# vi ifcfg-eno1

# 내용 확인
[root@seob network-scripts]# cat ifcfg-eno1 
TYPE=Ethernet
PROXY_METHOD=none
BOOTPROTO=static
IPADDR=192.168.1.111
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
ONBOOT=yes
DEVICE=eno1
NAME=eno1
#USERCTL=no

12-2. Network Server 재시작

service network restart, systemctl restart network 명령어로 재시작
- CentOS 8 이상에서는 서비스 명칭이 Network 대신 NetworkManager 로 변경됨

[root@localhost ~]# service network restart
Redirecting to /bin/systemctl restart network.service
Failed to restart network.service: Unit network.service not found.

service NetworkManager restart 명령어로 재시작

[root@localhost network-scripts]# service NetworkManager restart
Redirecting to /bin/systemctl restart NetworkManager.service

12-3. 재시작 전후로 상태 확인

dmesg 시스템 부팅 로그 확인

[root@localhost network-scripts]# dmesg | grep eth
[    1.524205] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) d8:bb:c1:4d:c4:43
[    1.524207] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[    1.524356] e1000e 0000:00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FFFFFF-0FF
[    1.719672] e1000e 0000:00:1f.6 eno1: renamed from eth0
[root@localhost network-scripts]# dmesg | grep eno1
[    1.719672] e1000e 0000:00:1f.6 eno1: renamed from eth0
[   25.238976] e1000e 0000:00:1f.6 eno1: NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[   25.239153] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready

PCI 드라이버 확인

[root@localhost network-scripts]# lspci | grep Ethernet
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (10) I219-V (rev 11)

systemctl status 서비스

[root@localhost ~]# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-03-28 10:57:46 KST; 45s ago
       Docs: man:NetworkManager(8)
   Main PID: 118424 (NetworkManager)
      Tasks: 3 (limit: 202236)
     Memory: 5.4M
        CPU: 39ms
     CGroup: /system.slice/NetworkManager.service
             └─118424 /usr/sbin/NetworkManager --no-daemon

Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7788] device (lo): Activation: successful, device activated.
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7792] policy: set 'eno1' (eno1) as default for IPv4 routing and DNS
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7804] device (eno1): state change: ip-config -> ip-check (reason 'none', s>
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7863] device (eno1): state change: ip-check -> secondaries (reason 'none',>
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7864] device (eno1): state change: secondaries -> activated (reason 'none'>
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7866] manager: NetworkManager state is now CONNECTED_SITE
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7869] device (eno1): Activation: successful, device activated.
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7873] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7874] manager: startup complete
Mar 28 10:57:46 localhost.localdomain NetworkManager[118424]: <info>  [1711591066.7921] policy: set-hostname: set hostname to 'localhost.localdomain' (no ho>
...skipping...

IP 주소 확인하기

[root@localhost network-scripts]# ip addr show eno1
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d8:bb:c1:4d:c4:43 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 192.168.1.999/24 brd 192.168.1.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::dabb:c1ff:fe4d:c443/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

사용 가능한 모든 장치의 상태 표시 : nmcli dev status / 사용 가능한 모든 연결의 상태를 표시 : nmcli con show

[root@localhost network-scripts]# nmcli dev status
DEVICE  TYPE      STATE                   CONNECTION
eno1    ethernet  connected               eno1
lo      loopback  connected (externally)  lo

네트워크 정보 확인 (IP 주소만 보기) : ifconfig eno1 | grep inet

🔶 기타 작업

네트워크 재시작 후에도 IP 주소가 변경되지 않아 장치 비활성화 시도
eno1 장치 활성화/비활성화 : ifup eno1, ifdown eno1

[root@localhost network-scripts]# ifdown eno1
bash: ifdown: command not found...
Install package 'NetworkManager-initscripts-updown' to provide command 'ifdown'? [N/y] y

 * Waiting in queue...
 * Loading list of packages....
The following packages have to be installed:
 NetworkManager-initscripts-updown-1:1.47.2-1.el9.noarch        Legacy ifup/ifdown scripts for NetworkManager that replace initscripts (network-scripts)
Proceed with changes? [N/y] y

설치하라는 문구가 나와 설치 진행
아래와 같은 오류 발생

[root@localhost network-scripts]# ifdown eno1
Error: '/etc/sysconfig/network-scripts/ifcfg-eno1' is not an active connection.
Error: no active connection provided.
Failure to deactivate file "eno1"!

See all profiles with `nmcli connection`.
Reload files from disk with `nmcli connection reload`
Deactivate the desired profile with `nmcli connection down \"$NAME\"`

13. CentOS IP 변경

eno1.nmconnection 파일 > IP 주소 변경

[root@localhost system-connections]# cd /etc/NetworkManager/system-connections/
[root@localhost system-connections]# ls
eno1.nmconnection
[root@localhost system-connections]# vi eno1.nmconnection

# 내용 수정
[ipv4]
address1=192.168.1.111/24,192.168.1.1
dns=210.94.0.73;210.220.163.82;
ignore-auto-dns=true
method=manual

Network Server 재시작

[root@localhost system-connections]# service NetworkManager restart
Redirecting to /bin/systemctl restart NetworkManager.service

IP 주소 확인하기 (inet 192.168.1.111 가 추가됨)

[root@localhost network-scripts]# ip addr show eno1
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d8:bb:c1:4d:c4:43 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 192.168.1.999/24 brd 192.168.1.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet 192.168.1.111/24 brd 192.168.1.255 scope global secondary noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::dabb:c1ff:fe4d:c443/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

접속도 잘 되는 것으로 확인됨

14. 계정 생성

projyj 추가로 생성
- adduser : 사용자 홈 디렉토리를 포함한 사용자 관련 설정을 자동 생성 / 사용자가 설정한 기본 쉘을 사용자의 쉘로 지정
- useradd : 사용자 홈 디렉토리를 포함한 사용자 관련 설정을 자동생성 하지 않음 / 홈 디렉토리와 패스워드 그 외에도 여러가지 설정을 따로 해줘야 함 / 기본 쉘인 sh가 할당됨

[root@localhost ~]# whoami
root
[root@localhost home]# adduser projyj -p password$$
[root@localhost projyj]# id projyj # 정보 조회
uid=1001(projyj) gid=1001(projyj) groups=1001(projyj)

패스워드 변경

[root@localhost home]# passwd projyj
Changing password for user projyj.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

🔶 생성 계정 확인

설정된 계정 ID 확인

[root@localhost home]# grep /bin/bash /etc/passwd | cut -f1 -d:
root
projyj

🔶 계정 삭제

-r : 계정의 home directory 등을 포함한 완전 삭제

userdel [user]		// 사용자 계정만 삭제
userdel -r [user]	// home directory 등을 포함한 완전 삭제

14-1. 계정 권한 부여

visudo 또는 vi /etc/sudoers 로 해당 파일 확인
- sudoers 수정 시에는 visudo 사용을 권고하고 있음

[root@localhost home]# visudo
visudo: /etc/sudoers.tmp unchanged
[root@localhost home]# vi /etc/sudoers

projyj 계정도 root 권한 주기

## Allow root to run any commands anywhere
root    ALL=(ALL)       ALL
projyj    ALL=(ALL)       ALL

15. Jenkins

5. Podman 에 이어서 Podman 작업
Docker Hub 와 Podman 은 잘 호환된다고 함 > Docker Hub 의 Jenkins 이미지를 사용

15-1. Podman 설치

이미지 다운로드 (podman pull)

[root@localhost home]# podman pull jenkins/jenkins:lts
✔ docker.io/jenkins/jenkins:lts
Trying to pull docker.io/jenkins/jenkins:lts...
Getting image source signatures
Copying blob 8d7cd7345072 done   |
Copying blob 71215d55680c done   |
Copying blob c8dac3aae91a done   |
Copying blob 1830bd5f9b45 done   |
Copying blob 35af8fb55c2f done   |
Copying blob 234e1154c2a1 done   |
Copying blob a89f7edcbd51 done   |
Copying blob 83597e279c9f done   |
Copying blob 6c39e3e60898 done   |
Copying blob 29150353c9ba done   |
Copying blob 33fe415a6139 done   |
Copying blob c5d8e31128fd done   |
Copying config 2371da2306 done   |
Writing manifest to image destination
2371da23064a2c39b40101d0851ef5c51adff752a013949cc129eb616228d5cd

이미지 태그 설정 (podman tag)

[root@localhost home]# podman tag jenkins/jenkins:lts projyj/jenkins:2.204.2
[root@localhost home]# podman tag jenkins/jenkins:lts docker.io/projyj/jenkins:2.204.2
[root@localhost home]# podman images
REPOSITORY                 TAG         IMAGE ID      CREATED     SIZE
docker.io/projyj/jenkins    2.204.2     2371da23064a  8 days ago  471 MB
localhost/projyj/jenkins    2.204.2     2371da23064a  8 days ago  471 MB
docker.io/jenkins/jenkins  lts         2371da23064a  8 days ago  471 MB

🔶 이미지 확인

이미지 검색 (podman search)

[root@localhost home]# podman search --tls-verify jenkins
NAME                                                                 DESCRIPTION
registry.access.redhat.com/openshift3/jenkins-2-rhel7                This image provides a Jenkins server, primar...
registry.access.redhat.com/openshift3/jenkins-1-rhel7                Jenkins image which can be used to set up a...
############ (중략) ############
docker.io/rancher/jenkins-jnlp-slave
docker.io/jenkins/core-pr-tester                                     Docker image for testing pull-requests sent...
docker.io/jenkins/jnlp-agent-alpine
docker.io/rancher/jenkins-slave                                      Jenkins Build Slave
docker.io/jenkins/jnlp-agent-coresdk
docker.io/jenkins/evergreen                                          An automatically self-updating Jenkins distr...

이미지 목록 출력 (podman images)

[root@localhost home]# podman images
REPOSITORY                 TAG         IMAGE ID      CREATED     SIZE
docker.io/jenkins/jenkins  lts         2371da23064a  8 days ago  471 MB

이미지 세부 정보 확인 (podman inspect)

[root@localhost home]# podman inspect jenkins/jenkins:lts
[
     {
          "Id": "2371da23064a2c39b40101d0851ef5c51adff752a013949cc129eb616228d5cd",
          "Digest": "sha256:1fd79ceb68ce883fb86db70bdbf7f9eaa8b25e580aafe7a240235240396e3916",
          "RepoTags": [
               "docker.io/jenkins/jenkins:lts"
          ],
          "RepoDigests": [
               "docker.io/jenkins/jenkins@sha256:1fd79ceb68ce883fb86db70bdbf7f9eaa8b25e580aafe7a240235240396e3916",
               "docker.io/jenkins/jenkins@sha256:55ca11703b6b90031030be36c9fe9f064b38a4bd2bd253100d0246efd0054a8a"
          ],
          "Parent": "",
          "Comment": "",
          "Created": "2024-03-20T16:37:24.770285139Z",
          "Config": {
               "User": "jenkins",
               "ExposedPorts": {
                    "50000/tcp": {},
                    "8080/tcp": {}
               },
               "Env": [
                    "PATH=/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                    "LANG=C.UTF-8",
                    "JENKINS_HOME=/var/jenkins_home",
                    "JENKINS_SLAVE_AGENT_PORT=50000",
                    "REF=/usr/share/jenkins/ref",
                    "JENKINS_VERSION=2.440.2",
                    "JENKINS_UC=https://updates.jenkins.io",
                    "JENKINS_UC_EXPERIMENTAL=https://updates.jenkins.io/experimental",
                    "JENKINS_INCREMENTALS_REPO_MIRROR=https://repo.jenkins-ci.org/incrementals",
                    "COPY_REFERENCE_FILE_LOG=/var/jenkins_home/copy_reference_file.log",
                    "JAVA_HOME=/opt/java/openjdk"
               ],
               "Entrypoint": [
                    "/usr/bin/tini",
                    "--",
                    "/usr/local/bin/jenkins.sh"
               ],
               "Volumes": {
                    "/var/jenkins_home": {}
               },
               "Labels": {
                    "org.opencontainers.image.description": "The Jenkins Continuous Integration and Delivery server",
                    "org.opencontainers.image.licenses": "MIT",
                    "org.opencontainers.image.revision": "8b3d5836ae21390ab374b154b94b7ac33d615243",
                    "org.opencontainers.image.source": "https://github.com/jenkinsci/docker",
                    "org.opencontainers.image.title": "Official Jenkins Docker image",
                    "org.opencontainers.image.url": "https://www.jenkins.io/",
                    "org.opencontainers.image.vendor": "Jenkins project",
                    "org.opencontainers.image.version": "2.440.2"
               }
          },
          "Version": "",
          "Author": "",
          "Architecture": "amd64",
          "Os": "linux",
          "Size": 471191196,
          "VirtualSize": 471191196,
############ (중략) ############
          "Labels": {
               "org.opencontainers.image.description": "The Jenkins Continuous Integration and Delivery server",
               "org.opencontainers.image.licenses": "MIT",
               "org.opencontainers.image.revision": "8b3d5836ae21390ab374b154b94b7ac33d615243",
               "org.opencontainers.image.source": "https://github.com/jenkinsci/docker",
               "org.opencontainers.image.title": "Official Jenkins Docker image",
               "org.opencontainers.image.url": "https://www.jenkins.io/",
               "org.opencontainers.image.vendor": "Jenkins project",
               "org.opencontainers.image.version": "2.440.2"
          },
          "Annotations": {},
          "ManifestType": "application/vnd.oci.image.manifest.v1+json",
          "User": "jenkins",
          "History": [
############ (중략) ############
          ],
          "NamesHistory": [
               "docker.io/jenkins/jenkins:lts"
          ]
     }
]

🔶 이미지 삭제

이미지 삭제 (podman rmi)

$ podman rmi localhost/projyj/jenkins:2.204.2
Untagged: localhost/projyj/jenkins:2.204.2

$ podman rmi docker.io/projyj/jenkins:2.204.2
Untagged: docker.io/projyj/jenkins:2.204.2

15-2. Podman 컨테이너 생성 및 구동

컨테이너 생성 및 백그라운드 실행 (podman run)

[root@localhost home]# podman run --name jenkins -d -p 8080:8080 -p 50000:50000 jenkins/jenkins:lts
e5c906face7a150af68d9672d019e4ca60775a981f21bb516c5ff34d097652b7

컨테이너 목록 확인 (podman ps)
- 컨테이너 실행 확인과 사용 가능한 모든 컨테이너 출력

[root@localhost home]# podman ps -a
CONTAINER ID  IMAGE                          COMMAND     CREATED         STATUS         PORTS                                             NAMES
d7020c058f90  docker.io/jenkins/jenkins:lts              42 seconds ago  Up 42 seconds  0.0.0.0:8080->8080/tcp, 0.0.0.0:50000->50000/tcp  jenkins

컨테이너 구동 확인 (podman logs)

[root@localhost home]# podman logs -f jenkins
Running from: /usr/share/jenkins/jenkins.war
webroot: /var/jenkins_home/war
2024-03-29 00:34:08.819+0000 [id=1]     INFO    winstone.Logger#logInternal: Beginning extraction from war file
2024-03-29 00:34:09.458+0000 [id=1]     WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath
2024-03-29 00:34:09.494+0000 [id=1]     INFO    org.eclipse.jetty.server.Server#doStart: jetty-10.0.20; built: 2024-01-29T20:46:45.278Z; git: 3a745c71c23682146f262b99f4ddc4c1bc41630c; jvm 17.0.10+7
2024-03-29 00:34:09.640+0000 [id=1]     INFO    o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
2024-03-29 00:34:09.670+0000 [id=1]     INFO    o.e.j.s.s.DefaultSessionIdManager#doStart: Session workerName=node0
2024-03-29 00:34:09.940+0000 [id=1]     INFO    hudson.WebAppMain#contextInitialized: Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
2024-03-29 00:34:10.007+0000 [id=1]     INFO    o.e.j.s.handler.ContextHandler#doStart: Started w.@332820f4{Jenkins v2.440.2,/,file:///var/jenkins_home/war/,AVAILABLE}{/var/jenkins_home/war}
2024-03-29 00:34:10.014+0000 [id=1]     INFO    o.e.j.server.AbstractConnector#doStart: Started ServerConnector@68fa0ba8{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
2024-03-29 00:34:10.019+0000 [id=1]     INFO    org.eclipse.jetty.server.Server#doStart: Started Server@2a7686a7{STARTING}[10.0.20,sto=0] @1502ms
2024-03-29 00:34:10.020+0000 [id=27]    INFO    winstone.Logger#logInternal: Winstone Servlet Engine running: controlPort=disabled
2024-03-29 00:34:10.150+0000 [id=35]    INFO    jenkins.InitReactorRunner$1#onAttained: Started initialization
2024-03-29 00:34:10.162+0000 [id=56]    INFO    jenkins.InitReactorRunner$1#onAttained: Listed all plugins
2024-03-29 00:34:10.642+0000 [id=56]    INFO    jenkins.InitReactorRunner$1#onAttained: Prepared all plugins
2024-03-29 00:34:10.645+0000 [id=56]    INFO    jenkins.InitReactorRunner$1#onAttained: Started all plugins
2024-03-29 00:34:10.649+0000 [id=52]    INFO    jenkins.InitReactorRunner$1#onAttained: Augmented all extensions
2024-03-29 00:34:10.758+0000 [id=41]    INFO    jenkins.InitReactorRunner$1#onAttained: System config loaded
2024-03-29 00:34:10.758+0000 [id=40]    INFO    jenkins.InitReactorRunner$1#onAttained: System config adapted
2024-03-29 00:34:10.758+0000 [id=51]    INFO    jenkins.InitReactorRunner$1#onAttained: Loaded all jobs
2024-03-29 00:34:10.759+0000 [id=51]    INFO    jenkins.InitReactorRunner$1#onAttained: Configuration for all jobs updated
2024-03-29 00:34:10.769+0000 [id=69]    INFO    hudson.util.Retrier#start: Attempt #1 to do the action check updates server
2024-03-29 00:34:11.025+0000 [id=48]    INFO    jenkins.install.SetupWizard#init:

*************************************************************
*************************************************************
*************************************************************

Jenkins initial setup is required. An admin user has been created and a password generated.
Please use the following password to proceed to installation:

070b01f500e94ca1b1a3c3fa01b0c911

This may also be found at: /var/jenkins_home/secrets/initialAdminPassword

*************************************************************
*************************************************************
*************************************************************

2024-03-29 00:34:25.553+0000 [id=55]    INFO    jenkins.InitReactorRunner$1#onAttained: Completed initialization
2024-03-29 00:34:25.564+0000 [id=26]    INFO    hudson.lifecycle.Lifecycle#onReady: Jenkins is fully up and running
2024-03-29 00:34:26.480+0000 [id=69]    INFO    h.m.DownloadService$Downloadable#load: Obtained the updated data file for hudson.tasks.Maven.MavenInstaller
2024-03-29 00:34:26.481+0000 [id=69]    INFO    hudson.util.Retrier#start: Performed the action check updates server successfully at the attempt #1

🔶 Podman 컨테이너 구동/중지/재시작

컨테이너 구동 (podman start) / 중지 (podman stop) / 재시작 (podman restart)

# 컨테이너 중지 (podman stop)
[root@localhost home]# podman stop jenkins
jenkins
[root@localhost home]# podman ps -a
CONTAINER ID  IMAGE                          COMMAND     CREATED        STATUS                       PORTS                                             NAMES
d7020c058f90  docker.io/jenkins/jenkins:lts              7 minutes ago  Exited (143) 16 seconds ago  0.0.0.0:8080->8080/tcp, 0.0.0.0:50000->50000/tcp  jenkins

# 컨테이너 구동 (podman start)
[root@localhost home]# podman start jenkins
jenkins
[root@localhost home]# podman ps -a
CONTAINER ID  IMAGE                          COMMAND     CREATED        STATUS         PORTS                                             NAMES
d7020c058f90  docker.io/jenkins/jenkins:lts              8 minutes ago  Up 11 seconds  0.0.0.0:8080->8080/tcp, 0.0.0.0:50000->50000/tcp  jenkins

# 컨테이너 재시작 (podman restart)
[root@localhost home]# podman restart jenkins
jenkins
[root@localhost home]# podman ps -a
CONTAINER ID  IMAGE                          COMMAND     CREATED        STATUS       PORTS                                             NAMES
d7020c058f90  docker.io/jenkins/jenkins:lts              8 minutes ago  Up 1 second  0.0.0.0:8080->8080/tcp, 0.0.0.0:50000->50000/tcp  jenkins

컨테이너 삭제 (podman rm)

[root@localhost home]# podman rm jenkins

🔶 Podman 컨테이너 사용법

컨테이너의 프로세스 실행 및 접속 (podman exec)

[root@localhost home]# podman exec -it jenkins /bin/bash
jenkins@d7020c058f90:/$ whoami
jenkins
jenkins@d7020c058f90:/$ cd /var/jenkins_home/secrets
jenkins@d7020c058f90:~/secrets$ cat initialAdminPassword
070b01f500e94ca1b1a3c3fa01b0c911

컨테이너의 프로세스 확인 (podman top)

[root@localhost home]# podman top jenkins
USER        PID         PPID        %CPU        ELAPSED          TTY         TIME        COMMAND
jenkins     1           0           0.000       4m19.290914938s  ?           0s          /usr/bin/tini -- /usr/local/bin/jenkins.sh
jenkins     2           1           8.485       4m19.29096756s   ?           22s         java -Duser.home=/var/jenkins_home -Djenkins.model.Jenkins.slaveAgentPort=50000 -Dhudson.lifecycle=hudson.lifecycle.ExitLifecycle -jar /usr/share/jenkins/jenkins.war

컨테이너의 포트 상태 확인 (podman port)

[root@localhost home]# podman port jenkins
8080/tcp -> 0.0.0.0:8080
50000/tcp -> 0.0.0.0:50000

15-4. Jenkins 접속

참고 : Jenkins 설치 가이드
15-2. Podman 컨테이너 생성 및 구동 에서 확인된 비밀번호 복사 : 070b01f500e94ca1b1a3c3fa01b0c911
http://192.168.1.111:8080 로 접속하여 구동된 것 확인
비밀번호 입력 > Continue
Customize Jenkins > Install suggested plugins
Create First Admin User > 계정 정보 입력
- 계정명 : projyj
- 암호 : password$$
- 이름 : projyj
- 이메일 주소 : [email protected]
Jenkins URL : Jenkins Web UI에 접근하기 위한 Jenkins URL 설정 (기본으로 유지함)
Jenkins is ready! > Start using Jenkins

16. Jenkins 에 Github 연동

참고 : Jenkins와 GitHub 연동하기 / 젠킨스와 깃허브 연동(GitHub Web Hook) / WebHook을 이용한 자동 배포
- 추가 : Jenkins와 github 연동하기 - Github Push 자동 빌드 / Jenkins 자동 배포하기
Jenkins 언어 설정 변경 필요 시 Jenkins Locale 언어 설정하기 참고

16-1. Github Token 발급

Github > Settings(https://github.com/settings/profile) > Developer Settings > Personal access tokens > Tokens (classic)
Generate new token (classic) 클릭
- Note : CentOS 9 ProjYj
- Expiration : No expiration (The token will never expire!)
- Select scopes : repo, admin:org, admin:repo_hook 선택
Generate token : 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 (발급 받은 token 은 다시 볼 수 없으므로 따로 저장)

16-2. Jenkins Credentials 생성

Dashboard > Jenkins 관리 > Credentials
Stores scoped to Jenkins > System 의 Domains (global) 선택
Add Credentials
- Kind : Username with password
- Scope : Global (Jenkins, nodes, items, all child items, etc)
- Username : projyj (GitHub 아이디)
- Treat username as secret 체크 해제
- Password : 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 (위에서 발급 받은 GitHub token)
- ID : github_token (Credentials 이름)
- Description : github_token (Optional)

16-3. Jenkinsfile 작성

빌드할 GitHub Repository 경로 안에 Jenkinsfile 이 존재해야 함
2024.04.12 > Pipeline 으로 구성할 때만 필요

pipeline {
    agent any
    
    stages {
        
        stage('github-clone') {
            steps {
                git branch: 'ProjYj2024main', credentialsId: 'github_token', url: 'https://github.com/projyj/ProjYj2024.git'
            }
        }
        
   		// stage...
   	}
}

16-4. Jenkins Freestyle project 설정

Dashboard > 새로운 Item > Freestyle project 선택
item name : ProjYj2024
2024.04.12 > Pipeline 으로 구성했었으나, 빌드 후 조치 사용을 위해 Freestyle project 로 변경하였음 (각 타입별 Configure 는 하단 참고)
자동 실행 등 빌드 후 작업은 21. Jenkins 빌드 및 실행 에서 이어서 확인

🔶 Freestyle project Configure

참고 : Jenkins 새로운 Item 생성 및 설정 / Jenkins와 github 연동하기
General > GitHub project 선택
- Project url : https://github.com/projyj/ (GitHub Repository 경로)
소스 코드 관리 > Git
- Repository URL : https://github.com/projyj/ProjYj2024.git (GitHub Repository 경로.git)
- Credentials : (위에서 생성한 Credentials)
- Branch Specifier : */ProjYj2024main (trigger Branch)
빌드 유발(Build Triggers) > GitHub hook trigger for GITScm polling 선택
- push에 의한 hook 이벤트가 발생할 경우 저장소를 polling해서 젠킨스의 자동 빌드를 유발
- GitHub 의 hook trigger 를 받으면 빌드 하겠다는 의미
빌드 환경 > Provide Node & npm bin/ folder to PATH 선택
- NodeJS Installation : NodeJS 20.9.0
- npmrc file : - use system default -
- Cache location : Default (~/.npm or %APP_DATA%\npm-cache)
저장

🔶 Pipeline Configure

General > GitHub project 선택
- Project url : https://github.com/projyj/ (GitHub Repository 경로)
Build Triggers > GitHub hook trigger for GITScm polling 선택
Pipeline > Definition > Pipeline script from SCM 선택
- SCM : Git 선택
- Repository URL : https://github.com/projyj/ProjYj2024.git (GitHub Repository 경로.git)
- Credentials : (위에서 생성한 Credentials)
- Branch Specifier : ProjYj2024main (trigger Branch)
- Script Path : Jenkinsfile (루트 프로젝트에서 Jenkinsfile의 경로 - 기본값 유지)
저장

16-5. GitHub Repository Webhooks 설정

GitHub Repository 의 Settings > Webhooks > Add webhook
- Payload URL : http://192.168.1.111:8080/github-webhook/ (http://Jenkins주소/github-webhook/)
- Content type : application/json
- Let me select individual events 선택 > Pull requests, Pushes 선택
- Active 체크 유지
Add webhook

🔶 지금 빌드

지금 빌드 > 아래와 같이 workspace 가 생김

[root@localhost workspace]# pwd
/var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace
[root@localhost workspace]# ls
ProjYj2024  ProjYj2024@tmp

컨테이너의 프로세스 실행 및 접속 (podman exec)

[root@localhost home]# podman exec -it jenkins /bin/bash
jenkins@d7020c058f90:~/workspace$ cd /var/jenkins_home/workspace
jenkins@d7020c058f90:~/workspace$ ls
ProjYj2024  ProjYj2024@tmp

🔶 Jenkins 를 위한 권한 부여

Jenkins 빌드 시 Permission denied 방지

[root@localhost storage]# pwd
/var/lib/containers/storage
[root@localhost storage]# chmod 755 volumes/
[root@localhost storage]# ls -al
total 144
drwxr-xr-x   3 root root     78 Mar 29 14:31 volumes

[root@localhost volumes]# pwd
/var/lib/containers/storage/volumes
[root@localhost volumes]# chmod 755 4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb

[root@localhost _data]# pwd
/var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data
[root@localhost _data]# chmod 777 logs/* #파일 생성 권한
[root@localhost _data]# chmod 777 logs

16-6. Plugin 설치 - Post build task

참고 : Jenkins 빌드 후 처리 플러그인 /
Jenkins > Dashboard > Jenkins 관리 > Plugins > Available plugins
Post build task 선택하여 설치

16-7. Plugin 설치 - NodeJS

Jenkins 빌드 시 npm not found error 방지
Jenkins > Dashboard > Jenkins 관리 > Plugins > Available plugins
NodeJS 선택하여 설치
Dashboard > Jenkins 관리 > Tools > NodeJS installations > Add NodeJS 클릭
- Name : NodeJS 20.9.0
- Version : NodeJS 20.9.0 (node -version 일치)

17. Node.js, NPM

참고 : How to Install Node.js on CentOS Stream 9
ProjYj2024 프로젝트 실행을 위한 단계
Before installing Node.js, it’s essential to ensure your system is up to date

[root@localhost ~]# dnf update -y
Last metadata expiration check: 0:18:29 ago on Fri 29 Mar 2024 02:00:07 PM KST.
Dependencies resolved.
=========================================================================================================================================================================
 Package                                                    Architecture               Version                               Repository                             Size
=========================================================================================================================================================================
Installing:
 kernel                                                     x86_64                     5.14.0-432.el9                        baseos                                 66 k
Upgrading:
 bpftool                                                    x86_64                     7.3.0-432.el9                         baseos                                842 k
############ (중략) ############

Transaction Summary
=========================================================================================================================================================================
Install    5 Packages
Upgrade  142 Packages

Total download size: 227 M
Downloading Packages:
(1/147): kernel-5.14.0-432.el9.x86_64.rpm                                                                                                345 kB/s |  66 kB     00:00
(2/147): kernel-core-5.14.0-432.el9.x86_64.rpm                                                                                           2.2 MB/s |  15 MB     00:06
############ (중략) ############

17-1. Node.js

Node.js list

[root@localhost ~]# dnf module list nodejs
Last metadata expiration check: 0:24:35 ago on Fri 29 Mar 2024 02:00:07 PM KST.
CentOS Stream 9 - AppStream
Name                            Stream                          Profiles                                                       Summary
nodejs                          18                              common [d], development, minimal, s2i                          Javascript runtime
nodejs                          20                              common [d], development, minimal, s2i                          Javascript runtime

Hint: [d]efault, [e]nabled, [x]d

Install Node.js 20

[root@localhost ~]# dnf module install nodejs:20 -y
Last metadata expiration check: 0:25:33 ago on Fri 29 Mar 2024 02:00:07 PM KST.
Dependencies resolved.
=========================================================================================================================================================================
 Package                               Architecture                Version                                                          Repository                      Size
=========================================================================================================================================================================
Installing group/module packages:
 nodejs                                x86_64                      1:20.9.0-1.module_el9+743+ad38546c                               appstream                       14 M
 npm                                   x86_64                      1:10.1.0-1.20.9.0.1.module_el9+743+ad38546c                      appstream                      2.6 M
Installing weak dependencies:
 nodejs-docs                           noarch                      1:20.9.0-1.module_el9+743+ad38546c                               appstream                      8.1 M
 nodejs-full-i18n                      x86_64                      1:20.9.0-1.module_el9+743+ad38546c                               appstream                      8.5 M
Installing module profiles:
 nodejs/common
Enabling module streams:
 nodejs                                                            20

Transaction Summary
=========================================================================================================================================================================
Install  4 Packages

Total download size: 33 M
Installed size: 175 M
Downloading Packages:
(1/4): nodejs-docs-20.9.0-1.module_el9+743+ad38546c.noarch.rpm                                                                           2.4 MB/s | 8.1 MB     00:03
(2/4): npm-10.1.0-1.20.9.0.1.module_el9+743+ad38546c.x86_64.rpm                                                                          1.0 MB/s | 2.6 MB     00:02
(3/4): nodejs-full-i18n-20.9.0-1.module_el9+743+ad38546c.x86_64.rpm                                                                      1.3 MB/s | 8.5 MB     00:06
(4/4): nodejs-20.9.0-1.module_el9+743+ad38546c.x86_64.rpm                                                                                1.3 MB/s |  14 MB     00:10
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                    2.8 MB/s |  33 MB     00:11
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                                 1/1
  Installing       : nodejs-docs-1:20.9.0-1.module_el9+743+ad38546c.noarch                                                                                           1/4
############ (중략) ############

Installed:
  nodejs-1:20.9.0-1.module_el9+743+ad38546c.x86_64                                      nodejs-docs-1:20.9.0-1.module_el9+743+ad38546c.noarch
  nodejs-full-i18n-1:20.9.0-1.module_el9+743+ad38546c.x86_64                            npm-1:10.1.0-1.20.9.0.1.module_el9+743+ad38546c.x86_64

Complete!

17-2. NPM

NPM list

[root@localhost ~]# dnf list npm
Last metadata expiration check: 0:27:47 ago on Fri 29 Mar 2024 02:00:07 PM KST.
Installed Packages
npm.x86_64                                1:10.1.0-1.20.9.0.1.module_el9+743+ad38546c                             @appstream

Install NPM (Node Package Manager)

[root@localhost ~]# dnf install npm -y
Last metadata expiration check: 0:29:43 ago on Fri 29 Mar 2024 02:00:07 PM KST.
Package npm-1:10.1.0-1.20.9.0.1.module_el9+743+ad38546c.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

🔶 Node.js, NPM 버전 확인

개인 로컬 PC 버전은 각각 v20.10.0 / 10.2.3

[root@localhost ~]# node --version
v20.9.0
[root@localhost ~]# npm --version
10.1.0

17-3. npm run dev

npm run dev

[root@localhost ProjYj2024]# npm run dev

> [email protected] dev
> quasar dev

sh: line 1: quasar: command not found

ProjYj2024main Branch 에는 .quasar, node_modules 폴더가 없음 (gitignore 캐시 삭제 처리 git rm -r --cached 진행했기 때문)
- FileZilla > /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace > 수동으로 복사 붙여넣기

[root@localhost .bin]# npm run dev

> [email protected] dev
> quasar dev

sh: line 1: /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024/node_modules/.bin/quasar: Permission denied

권한 부여

[root@localhost .bin]# pwd
/var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024/node_modules/.bin

[root@localhost .bin]# chmod 755 *

🔶 9000 Port 상시 허용

방화벽에 9000 Port를 상시 허용으로 등록 및 재실행

[root@localhost ~]# firewall-cmd --permanent --zone=public --add-port=9000/tcp
success
[root@localhost ~]# firewall-cmd --reload
success
[root@localhost ~]# firewall-cmd --list-port
3306/tcp 3389/tcp 8070/tcp 8888/tcp 9000/tcp

18. projyjengine

/projyjengine 경로에 logs, projyj, blib 디렉토리 생성

[root@localhost projyjengine]# pwd
/projyjengine
[root@localhost projyjengine]# mkdir logs
[root@localhost projyjengine]# mkdir projyj
[root@localhost projyjengine]# mkdir blib
[root@localhost projyjengine]# ls
blib  projyj  logs

18-1. FTP 파일 업로드

FileZilla > C:\home\projyj\projyjengine\blib 의 폴더 및 파일을 /projyjengine/blib 경로에 업로드
- 다운로드 경로 : C:\Users\PROJYJ\PROJYJ_YJ\2. ProjYj\1. 설치\서버환경 구축

19. ProjYjSvr 배포

Eclipse > ProjYjSvr 소스 Export > WAR file > 기본 설정으로 'Finish'
FileZilla > 생성된 ProjYjSvr.war 파일을 /tomcat/apache-tomcat-8.0.36/webapps 경로에 이동

[root@localhost webapps]# cd /tomcat/apache-tomcat-8.0.36/webapps
[root@localhost webapps]# ls
docs  examples  ProjYjSvr.war  host-manager  manager  ROOT

19-1. globals.properties

WAR 파일 생성 전에 globals.properties 파일에서 DB 연결 정보 수정 필요

# \uc6b4\uc601\uc11c\ubc84 \ud0c0\uc785(WINDOWS, UNIX)
Globals.OsType=UNIX

# G4C \uc5f0\uacb0\uc6a9 IP (localhost)
Globals.LocalIp=192.168.1.111

# DB\uc11c\ubc84 \ud0c0\uc785(mysql,oracle,altibase,tibero) - datasource \ubc0f sqlMap \ud30c\uc77c \uc9c0\uc815\uc5d0 \uc0ac\uc6a9\ub428
Globals.DbType=mysql
Globals.DbServer=192.168.1.111
Globals.DbName=projyj
Globals.UserName=projyj
Globals.Password=password\$\$

#Globals.DbType = mysql
#Globals.UserName=root
#Globals.Password=

#oracle
#Globals.DriverClassName=oracle.jdbc.driver.OracleDriver
#Globals.Url=jdbc:oracle:thin:@192.168.1.104:1521:ORCL

# mysql
Globals.DriverClassName=net.sf.log4jdbc.DriverSpy
Globals.Url=jdbc:mysql://192.168.1.111:3306/projyj

WAR 파일 풀린 후의 경로 : /tomcat/apache-tomcat-8.0.36/webapps/ProjYjSvr/WEB-INF/classes/egovframework/egovProps

🔶 Could not open JDBC Connection

globals.properties > 특수문자는 역슬래쉬(\) 붙일 것 : Globals.Password=password\$\$
- 역슬래쉬 붙이지 않으면 아래와 같은 오류가 발생됨
에러 팝업 문구가 loadError : xhr=[object Object], st=parseerror, err=SyntaxError: Unexpected token '<'," 이고,
ProjYjServer.log 로그 메시지가 아래와 같음

2024-04-01 15:45:34,148 ERROR [egovframework.projsvr.service.impl.OptionServiceImpl] Could not open JDBC Connection for transaction; nested exception is org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'projyj'@'192.168.1.999' (using password: YES))
org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'projyj'@'192.168.1.999' (using password: YES))
        at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549) ~[commons-dbcp-1.4.jar:1.4]
(...중략)
Caused by: java.sql.SQLException: Access denied for user 'projyj'@'192.168.1.999' (using password: YES)

19-2. MySQL DB 데이터 세팅

bmig_option_tbl 테이블의 값 일부 변경
- WasURL : http://192.168.1.111:8070/ProjYjSvr/projsvr
- JVM : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-4.el9.x86_64/jre/bin/java
- JarHome : /projyjengine

19-3. Tomcat 재실행

./startup.sh 실행하여 WAR 파일이 풀린 것 확인

[root@localhost bin]# ./startup.sh
Using CATALINA_BASE:   /tomcat/apache-tomcat-8.0.36
Using CATALINA_HOME:   /tomcat/apache-tomcat-8.0.36
Using CATALINA_TMPDIR: /tomcat/apache-tomcat-8.0.36/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /tomcat/apache-tomcat-8.0.36/bin/bootstrap.jar:/tomcat/apache-tomcat-8.0.36/bin/tomcat-juli.jar
Tomcat started.
[root@localhost bin]# cd ../webapps/
[root@localhost webapps]# ls
docs  examples  ProjYjSvr  ProjYjSvr.war  host-manager  manager  ROOT

로그인 테스트까지 완료되면 OK (ID : admin / PW : admin)

🔶 로그 조회하기

log4j2.xml > <RollingFile name="rollingFile" fileName="/home/projyj/tomcat/projyjlog/ProjYjServer.log" 경로 확인

[root@localhost projyjlog]# cd /home/projyj/tomcat/projyjlog
[root@localhost projyjlog]# tail -f ProjYjServer.log

🔶 Alias 영구 등록

.bash_aliases 파일 생성하여 alias 등록

[root@localhost ~]# ls -al | grep bashrc
-rw-r--r--.  1 root root   429 Aug 10  2021 .bashrc
[root@localhost ~]# vi .bash_aliases

alias zlog='tail -f /home/projyj/tomcat/projyjlog/ProjYjServer.log'
alias ztc='cd /tomcat/apache-tomcat-8.0.36/bin/'
alias zstart='/tomcat/apache-tomcat-8.0.36/bin/startup.sh'
alias zshut='/tomcat/apache-tomcat-8.0.36/bin/shutdown.sh'

source .bash_aliases 명령어를 실행해야 사용 가능

19-4. 누락 파일 추가

Monitoring* 파일이 누락되어 각 경로에 추가함
- .class 다운로드 경로 : C:\Users\PROJYJ\PROJYJ_YJ\2. ProjYj\1. 설치\서버환경 구축\누락 파일
ProjYjSvr 프로젝트 자체에 추가하여 WAR 파일 Export 하는 것으로 변경 (24.04.03)
- .java 다운로드 경로 : C:\Users\PROJYJ\PROJYJ_YJ\2. ProjYj\1. 설치\ProjYjWAS 누락파일
- .war 파일 경로 : C:\Users\PROJYJ\PROJYJ_YJ\2. ProjYj\1. 설치\서버환경 구축

[root@localhost projsvr]# pwd # MonitoringController / MonitoringService / MonitoringServiceImpl / MonitoringDAO
/tomcat/apache-tomcat-8.0.36/webapps/ProjYjSvr/WEB-INF/classes/egovframework/projsvr
[root@localhost projsvr]# pwd # Monitoring_SQL_Mysql
/tomcat/apache-tomcat-8.0.36/webapps/ProjYjSvr/WEB-INF/classes/egovframework/sqlmap/projsvr

[root@localhost egovframework]# find | grep Monitoring
./projsvr/controller/MonitoringController.class
./projsvr/dao/MonitoringDAO.class
./projsvr/service/impl/MonitoringServiceImpl.class
./projsvr/service/MonitoringService.class
./sqlmap/projsvr/Monitoring_SQL_Mysql.xml

20. npm run dev

ProjYj2024 프로젝트 실행
17-3-npm-run-dev 의 절차 수행 후 다시 npm run dev

[root@localhost ProjYj2024]# npm run dev

> [email protected] dev
> quasar dev


 .d88888b.
d88P" "Y88b
888     888
888     888 888  888  8888b.  .d8888b   8888b.  888d888
888     888 888  888     "88b 88K          "88b 888P"
888 Y8b 888 888  888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888  888      X88 888  888 888
 "Y888888"   "Y88888 "Y888888  88888P' "Y888888 888
       Y8b


 » Reported at............ 3/29/2024 3:28:11 PM
 » App dir................ /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024
 » App URL................ http://localhost:9000/
                           http://192.168.1.999:9000/
                           http://192.168.1.111:9000/
                           http://10.88.0.1:9000/
 » Dev mode............... spa
 » Pkg quasar............. v2.14.1
 » Pkg @quasar/app-vite... v1.7.0
 » Browser target......... es2019|edge88|firefox78|chrome87|safari13.1

 App • Opening default browser at http://localhost:9000/


You installed esbuild on another platform than the one you're currently using.
This won't work because esbuild is written with native code and needs to
install a platform-specific binary executable.

Specifically the "esbuild-windows-64" package is present but this platform
needs the "esbuild-linux-64" package instead. People often get into this
situation by installing esbuild on Windows or macOS and copying "node_modules"
into a Docker image that runs Linux, or by copying "node_modules" between
Windows and WSL environments.

If you are installing with npm, you can try not copying the "node_modules"
directory when you copy the files over, and running "npm ci" or "npm install"
on the destination platform after the copy. Or you could consider using yarn
instead which has built-in support for installing a package on multiple
platforms simultaneously.

If you are installing with yarn, you can try listing both this platform and the
other platform in your ".yarnrc.yml" file using the "supportedArchitectures"
feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
Keep in mind that this means multiple copies of esbuild will be present.

Another alternative is to use the "esbuild-wasm" package instead, which works
the same way on all platforms. But it comes with a heavy performance cost and
can sometimes be 10x slower than the "esbuild" package, so you may also not
want to do that.

 App • ⚠️  Failed to open default browser

🔶 2024.03.29 현재 상황

http://192.168.1.111:9000/ 접속 시 연결은 되나, console 창에 다음 내용만 출력되고 아무것도 뜨지 않음
npm run dev 실행 상태를 종료하면 '사이트에 연결할 수 없음' 이 뜨는 것으로 보아 실행은 되었음

/* console 창 */
[vite] connecting...      client.ts:16
[vite] connected.         client.ts:53

🔶 2024.03.29 오류 내용

현재 사용 중인 플랫폼이 아닌 다른 플랫폼에 esbuild를 설치했습니다.
esbuild는 네이티브 코드로 작성되었으며 다음을 수행해야 하기 때문에 이는 작동하지 않습니다.
플랫폼별 바이너리 실행 파일을 설치합니다.

특히 "esbuild-windows-64" 패키지가 있지만 이 플랫폼은 대신 "esbuild-linux-64" 패키지가 필요합니다.
Windows 또는 macOS에 esbuild를 설치하고 "node_modules"를 복사하여 상황을 해결하세요.
Linux를 실행하는 Docker 이미지로 또는 "node_modules"를 복사하여 Windows 및 WSL 환경.

npm으로 설치하는 경우 "node_modules"를 복사하지 않아도 됩니다.
파일을 복사하고 "npm ci" 또는 "npm install"을 실행할 때 디렉터리 복사 후 대상 플랫폼에서. 아니면 원사 사용을 고려할 수도 있습니다.
대신 여러 곳에 패키지를 설치하는 기능이 내장되어 있습니다.

(중략)

20-1. You installed esbuild on another platform 해결

참고 : Error: The package "@esbuild/linux-x64" could not be found, and is needed by esbuild.
node_modules 폴더 삭제 (FileZilla 에서 수동으로 붙여넣기 했었는데, 직접 설치되게 하는 게 맞는 듯)

[root@localhost ProjYj2024]# ls
index.html     node_modules  package-lock.json   public            README.md  test1-src240131am.zip  test1-src240205pm.zip  test1-src240216pm.zip
jsconfig.json  package.json  postcss.config.cjs  quasar.config.js  src        test1-src240201pm.zip  test1-src240213pm.zip
[root@localhost ProjYj2024]# rm -rf node_modules/

npm i 로 다시 install 하여, node_modules 폴더 생성된 것 확인

[root@localhost ProjYj2024]# npm i
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '^18 || ^16 || ^14.19', npm: '>= 6.13.4', yarn: '>= 1.21.1' },
npm WARN EBADENGINE   current: { node: 'v20.9.0', npm: '10.1.0' }
npm WARN EBADENGINE }

added 424 packages, and audited 425 packages in 9s

84 packages are looking for funding
  run `npm fund` for details

3 vulnerabilities (2 moderate, 1 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

[root@localhost ProjYj2024]# ls
index.html     node_modules  package-lock.json   public            README.md  test1-src240131am.zip  test1-src240205pm.zip  test1-src240216pm.zip
jsconfig.json  package.json  postcss.config.cjs  quasar.config.js  src        test1-src240201pm.zip  test1-src240213pm.zip

npm run dev

[root@localhost ProjYj2024]# npm run dev

> [email protected] dev
> quasar dev


 .d88888b.
d88P" "Y88b
888     888
888     888 888  888  8888b.  .d8888b   8888b.  888d888
888     888 888  888     "88b 88K          "88b 888P"
888 Y8b 888 888  888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888  888      X88 888  888 888
 "Y888888"   "Y88888 "Y888888  88888P' "Y888888 888
       Y8b


 » Reported at............ 4/12/2024 10:14:15 AM
 » App dir................ /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024
 » App URL................ http://localhost:9000/
                           http://192.168.1.999:9000/
                           http://192.168.1.111:9000/
                           http://10.88.0.1:9000/
 » Dev mode............... spa
 » Pkg quasar............. v2.14.1
 » Pkg @quasar/app-vite... v1.7.0
 » Browser target......... es2019|edge88|firefox78|chrome87|safari13.1

 App • Opening default browser at http://localhost:9000/

 App • ⚠️  Failed to open default browser

Failed to open default browser 가 떴으나, http://192.168.1.111:9000/ 로 접속됨

21. Jenkins 빌드 및 실행

정상적으로 ProjYj2024가 실행되므로, npm run dev 가 자동 실행되도록 변경

21-1. log 파일 생성 경로 세팅

log 파일을 저장할 ProjYj2024_log 폴더 생성
경로 : /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/logs

[root@localhost logs]# pwd
/var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/logs
[root@localhost logs]# mkdir ProjYj2024_log
[root@localhost logs]# chmod 777 ProjYj2024_log/
[root@localhost logs]# ls -al
total 8
drwxrwxrwx  2 root  root     6 Apr 12 17:18 ProjYj2024_log
drwxr-xr-x  2 root  root  4096 Apr 12 03:01 tasks

21-2. npmrun.sh 파일 생성

npmrun.sh 파일 생성 및 권한 부여
경로 : /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data

[root@localhost _data]# pwd
/var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data
[root@localhost _data]# vi npmrun.sh
[root@localhost _data]# chmod 777 npmrun.sh

파일을 열어 아래와 같이 편집

#!/bin/sh
nowDate=`date "+%Y-%m-%d_%H:%M:%S"`
fileName="ProjYj2024_$nowDate.log"

cd ./workspace/ProjYj2024/ProjYj2024
pwd
nohup npm run dev > ../../../logs/ProjYj2024_log/$fileName &

실행 후 log 파일이 정상적으로 생성되는지 확인

[root@localhost _data]# ./npmrun.sh
/var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024
[root@localhost _data]# nohup: redirecting stderr to stdout

[root@localhost _data]# cd logs/ProjYj2024_log/
[root@localhost ProjYj2024_log]# ls
ProjYj2024_2024-04-12_13:57:26.log

🔶 백그라운드 실행 중단시키기

ps -ef | grep "quasar dev" : npm run dev 로 인해 실행된 목록 확인 및 중단

[root@localhost ProjYj2024]# ps -ef | grep "quasar dev"
root     1131847 1131836  0 11:49 pts/0    00:00:00 node /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024/node_modules/.bin/quasar dev
root     1131951 1131940  0 11:50 pts/0    00:00:00 node /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024/node_modules/.bin/quasar dev
root     1132841 1124565  0 11:56 pts/0    00:00:00 grep --color=auto quasar dev

[root@localhost ProjYj2024]# kill -9 1131847
[root@localhost ProjYj2024]# kill -9 1131951
[2]-  Exit 137                nohup ./startup.sh  (wd: /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace)
(wd now: /var/lib/containers/storage/volumes/4e56f41adaca53fa1652bb2d5e0aaa4f80905a278588c911343a283eb21be2fb/_data/workspace/ProjYj2024/ProjYj2024)

21-3. Jenkins 구성

Jenkins 빌드 후 조치는 아래 두 가지 방법으로 할 수 있음
- Item > Configure > Build Steps > Execute shell
- Item > Configure > 빌드 후 조치 > Post build task
Command : podman exec -it jenkins /bin/bash 에서 보는 경로 기준으로 작성하게 됨

21-4. Execute shell

무조건 실행되는 명령어로, Command 에 작성

echo "ProjYj2024 BUILD > Execute shell START ======================="
echo "ProjYj2024 BUILD > Execute shell END ======================="

지금 빌드 > Console Output 확인

ProjYj2024 BUILD > Execute shell START =======================
ProjYj2024 BUILD > Execute shell END =======================

21-5. Post build task

조건에 따라 실행되는 명령어로, Script 에 작성
git rev-list --no-walk 라는 키워드가 log 에 출력되면(즉, 성공하면) 실행하도록 구성

echo "ProjYj2024 BUILD > Post build task START ======================="
cd /var/jenkins_home
pwd
ps -ef | grep "quasar dev"
./npmrun.sh
ps -ef | grep "quasar dev"
echo "ProjYj2024 BUILD > Post build task END ======================="

21-6. npm: not found

Jenkins 에 NodeJS 플러그인 미설치 시 오류 발생
- ssh 실행 시, npm: not found 문구 출력

jenkins@d7020c058f90:~$ ./npmrun.sh
/var/jenkins_home/workspace/ProjYj2024/ProjYj2024
./npmrun.sh: 7: npm: not found

Jenkins 빌드 시 nohup: failed to run command 'npm': No such file or directory 문구 출력
Plugin 설치 - NodeJS 내용도 수행하였으나, 계속 오류 발생하는 상황
- 자동 실행은 현재 안되고 있음 > 우선은 직접 ./npmrun.sh 을 수행하는 방식으로 진행

Linux Server - ynjch97/YNJCH_WIKI GitHub Wiki

1. 구성

1-1. SSD

🔶 CentOs Stream 9

1-2. HDD

🔶 MySQL

1-3. 포트별 접속 정보

🔶 Jenkins

🔶 Github

2. CentOs Stream 9

🔶 Keyboard

🔶 Installation Destination

🔶 소프트웨어 선택

🔶 Network & Host

2-1. 접속

🔶 OS 정보 확인

🔶 hostnamectl 정보

2-2. 파티션 확인

🔶 bash: hwinfo: command not found...

🔶 저장 공간 확인

🔶 Linux GUI

2-3. 하드디스크 파티션

🔶 Partition does not start on physical sector boundary

2-4. 기본 설정

🔶 네임서버 설정

🔶 업데이트

🔶 selinux 비활성화

🔶 IPTABLES 방화벽 사용 (🚫Firewall 사용 시에는 생략)

2-5. CentOS 패키지 확장

3. 원격 데스크톱 연결

3-1. xrdp를 통해 원격 데스크톱 연결 (Windows -> CentOS)

🔶 기본 환경 설치

🔶 3389 Port 상시 허용

🔶 xrdp 서비스 등록 및 구동 확인

🔶 포트 상태 및 접속할 IP 확인

🔶 firewall public zone 상태 확인

3-2. Windows 에서 CentOS 원격 연결

🔶 root 계정 접속 허용/해제

3-3. 서버 주소 수동 변경

4. 가상머신

4-1. RHEL 9, Cockpit 웹 콘솔 설정

🔶 웹 콘솔에 액세스

5. Podman

🔶 Podman 저장소

5-1. Podman 환경 구성

🔶 Podman 기본 정보

🔶 podman-compose 버전

6. Java

6-1. JAVA_HOME 환경변수

🔶 Java 버전 변경 시

7. MySQL

7-1. MySQL 설치 파일 다운로드

🔶 MySQL Yum Repository

7-2. MySQL 설치

🔶 Error: GPG check FAILED

🔶 dnf install 재실행

🔶 패키지 추가 설치

7-3. MySQL DB 데이터 저장소 변경

7-4. MySQL 실행

🔶 systemctl start mysqld 실패

🔶 3306 Port 상시 허용

🔶 status 확인

🔶 Character Set 확인

8. MySQL 계정

8-1. root 접속

🔶 Can't connect to local MySQL server through socket

8-2. root 패스워드 변경

8-3. 계정 추가 및 권한 설정

🔶 암호화 방식 변경

🔶 MySQL 사용자 계정 비밀번호 정책

9. MySQL 테이블 생성

9-1. 데이터베이스 생성

9-2. 테이블 생성

🔶 DBeaver 에서 확인

10. 네트워크 상태 확인

10-1. 네트워크 상태 확인

11. Tomcat 설치

11-1. Tomcat 설정

🔶 환경변수 설정

11-2. Tomcat 구동

⚠️ GitHub.com Fallback ⚠️