Pusat Solusi IT

Recording 10/06/2026

request tarik recording ke oss di all layanan

DETAIL LOG ERROR / GEJALA

request tarik recording ke oss di all layanan

PROSEDUR SOLUSI FIX

buka ssh 30.23

/QA_REQ/KOORSODIQREQAMARTHA/

#!/bin/bash

FOLDER_BASE="oss://simrecording-infrequent/RECORDING/MANUAL/AMARTHA/"

DEST="/QA_REQ/KOORSODIQREQAMARTHA/RTP/"

# Format: "PATTERN|DD/MM/YYYY"

DATA=(

"5001280691|06/01/2026"

"5001905591|06/01/2026"

"7754740|07/01/2026"

"5002007107|07/01/2026"

"5001864001|08/01/2026"

"5002016700|09/01/2026"

"6556518|13/01/2026"

"5002073523|13/01/2026"

"7116300|14/01/2026"

"5002581179|14/01/2026"

"5001071537|14/01/2026"

"5002755490|19/01/2026"

"6283868|20/01/2026"

"5002047087|21/01/2026"

"5002131517|06/02/2026"

"5001765432|11/02/2026"

"5001998617|12/02/2026"

"5001923743|13/02/2026"

"5002569319|20/02/2026"

"7847082|23/02/2026"

"7674581|23/02/2026"

"5001919901|24/02/2026"

"5000115869|25/02/2026"

"5001924770|25/02/2026"

"5001736024|27/02/2026"

"5003488821|12/03/2026"

"5002073523|13/03/2026"

"5001816469|16/03/2026"

"2300845613|16/03/2026"

"5001816469|16/03/2026"

"2300845613|16/03/2026"

"2301386448|17/03/2026"

"5003629378|25/03/2026"

"5001897832|15/05/2026"

"5001768572|18/05/2026"

"7982428|22/05/2026"

"8623328|25/05/2026"

)

for entry in "${DATA[@]}"; do

PATTERN="${entry%%|*}"

DATE="${entry##*|}"

# ubah format DD/MM/YYYY ? YYYYMMDD

DAY=$(echo "$DATE" | cut -d'/' -f1)

MONTH=$(echo "$DATE" | cut -d'/' -f2)

YEAR=$(echo "$DATE" | cut -d'/' -f3)

FOLDER="${FOLDER_BASE}${YEAR}${MONTH}${DAY}/"

echo "Copy pola $PATTERN dari tanggal $DATE ($FOLDER)"

ossutil cp -r "$FOLDER" "$DEST" --include "*$PATTERN*"

done

Sunting

Server 04/06/2026

Zabbix kendala zabbix-agent.service: failed with result 'exit-code'

DETAIL LOG ERROR / GEJALA

Zabbix kendala zabbix-agent.service: failed with result 'exit-code'

PROSEDUR SOLUSI FIX

Zabbix kendala zabbix-agent.service: failed with result 'exit-code'

Pasted image 20260506062849.png

Berikut adalah langkah-langkah untuk memperbaikinya:

Perbaiki Nama Direktori Konfigurasi
Jalankan perintah ini untuk mengubah nama folder agar sesuai dengan yang diminta oleh sistem (menghilangkan .conf di tengah):

Bash
sudo mv /etc/zabbix/zabbix_agentd.conf.d /etc/zabbix/zabbix_agentd.d
2. Pastikan Direktori Log Tersedia
Pesan No such file or directory pada log menunjukkan folder /var/log/zabbix/ mungkin belum ada. Mari kita buat dan berikan izin akses ke user zabbix:

Bash
sudo mkdir -p /var/log/zabbix/
sudo chown -R zabbix:zabbix /var/log/zabbix/
3. Jalankan Ulang Service
Setelah struktur folder diperbaiki, lakukan restart pada agent:

Bash
sudo systemctl restart zabbix-agent
4. Verifikasi Hasil
Cek status service untuk memastikan sudah berwarna hijau (active/running):

Bash
sudo systemctl status zabbix-agent
Kenapa ini terjadi?
Zabbix Agent sangat sensitif terhadap jalur (path) yang didefinisikan di dalam file zabbix_agentd.conf. Karena di dalam file tersebut tertulis Include=/etc/zabbix/zabbix_agentd.d/*.conf, maka sistem wajib menemukan folder dengan nama yang sama persis. Jika nama folder berbeda satu karakter saja, service tidak akan mau berjalan.

jangan lupa di allow portnya
sudo ufw allow 10050/tcp

Pasted image 20260506062923.png

dipastikan di server grafananya server yg mau di tambahkan sudah konek

Pasted image 20260506072630.png

Sunting

Server 04/06/2026

Menambahkan server baru di grafana

DETAIL LOG ERROR / GEJALA

Menambahkan server baru di grafana

PROSEDUR SOLUSI FIX

buka server 172.16.30.30

cd /etc/prometheus/targets/node/

cp node-192-168-0-186.json node-192-168-0-x.json

lalu ubah isinya

nano node-192-168-0-x.json

disesuaikan aja isinya

Sunting

cloud 04/06/2026

membuat DNS lokal dan cloud alibaba

DETAIL LOG ERROR / GEJALA

membuat DNS lokal dan cloud alibaba

PROSEDUR SOLUSI FIX

Membuat DNS baru untuk server on premise

contoh : Server yang akan dibuat adalah server 172.16.70.81 yang akan dibuat DNS https://kardex-bicara.simgroup.co.id

Step 1: SSH ke server Load Balance ip 172.16.70.98

Step 2: masuk direktori config nginx di /etc/nginx/conf.d

Step 3: buat file conf dns nya yaitu kardex-bicara.simgroup.co.id.conf

root@load-balance:/etc/nginx/conf.d# nano kardex-bicara.simgroup.co.id.conf dan copy baris dibawah ini:

server {
server_name sys.db.bi-bicara.simgroup.co.id www.sys.db.bi-bicara.simgroup.co.id;

access_log /var/log/nginx/reverse-access-inbound.log;
error_log /var/log/nginx/reverse-error-inbound.log;

location / {
           proxy_pass http://172.16.70.81:7399;
           proxy_redirect off;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_set_header Host sys.db.bi-bicara.simgroup.co.id;
           proxy_connect_timeout 5000s;
           proxy_read_timeout 5000s;

}
}

Step 4: setelah itu buat cek conf dan reload service nginxnya

nginx -t # output harus OK

Step5: reload service nginx

systemctl reload nginx.service

step6: Buat records DNS baru dicloudflare -> https://dash.cloudflare.com/eae3ffda149a6f25f33c9543ebd74bf8/simgroup.co.id/dns/records -> add records

di set seperti ini jika ip local mengarah ke load balance:

jika ip cloud set nya berbeda IPv4 address mengarak ke ip publik, cek ip publiknya di alibaba cloude di instance detail server nya

Step 7: lalu buat https dengan jalankan perintah di server loadbalance ip 172.16.70.98

certbot --nginx -d kardex-bicara.simgroup.co.id

certbot --nginx -d sdmonitoring.simgroup.co.id

output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator nginx, Installer nginx Obtaining a new certificate Performing the following challenges: http-01 challenge for kardex-bicara.simgroup.co.id Waiting for verification... Cleaning up challenges Deploying Certificate to VirtualHost /etc/nginx/conf.d/kardex-bicara.simgroup.co.id.conf

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.

1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration.

Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Redirecting all traffic on port 80 to ssl in /etc/nginx/conf.d/kardex-bicara.simgroup.co.id.conf

Congratulations! You have successfully enabled https://kardex-bicara.simgroup.co.id

You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=kardex-bicara.simgroup.co.id

IMPORTANT NOTES:

Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/kardex-bicara.simgroup.co.id/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/kardex-bicara.simgroup.co.id/privkey.pem Your cert will expire on 2026-05-05. To obtain a new or tweaked version of this certificate in the future, simply run certbot again with the "certonly" option. To non-interactively renew all of your certificates, run "certbot renew"
If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le

jika server dari cloud alibaba kirimkan filenya untuk di upload ke uaf:

alu ambil filenya disini sesuai dengan nama nya
/etc/letsencrypt/live/

lalu kita ambil file:
-fullchain.pem
-privkey.pem

Sunting

cloud 04/06/2026

ssl expaired dan mendaftarkan ssl

DETAIL LOG ERROR / GEJALA

catatan tentang ssl expaired dan mendaftarkan ssl

PROSEDUR SOLUSI FIX

buka ssh load balance 172.16.70.98

jalankan ini:

certbot --nginx -d helpdesk.simgroup.co.id (untuk mendaftarkan ssl, nama nya disesuaikan aja sesuai kebutuhan)

certbot --force-renewal --nginx -d kardex-bicara.simgroup.co.id (untuk perbarui ssl, nama nya disesuaikan aja jika ada yg sudah expaired)

lalu ambil filenya disini sesuai dengan nama nya

/etc/letsencrypt/live/

lalu kita ambil file:

-fullchain.pem

-privkey.pem

file ini untuk di upload di alibaba nya

contoh script live ssh:

root@load-balance:~# certbot --force-renewal --nginx -d helpdesk.simgroup.co.id

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Plugins selected: Authenticator nginx, Installer nginx

Renewing an existing certificate

Performing the following challenges:

http-01 challenge for helpdesk.simgroup.co.id

Waiting for verification...

Cleaning up challenges

Deploying Certificate to VirtualHost /etc/nginx/conf.d/helpdesk.simgroup.co.id.conf

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1: No redirect - Make no further changes to the webserver configuration.

2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for

new sites, or if you're confident your site works on HTTPS. You can undo this

change by editing your web server's configuration.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2

Traffic on port 80 already redirecting to ssl in /etc/nginx/conf.d/helpdesk.simgroup.co.id.conf

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Your existing certificate has been successfully renewed, and the new certificate

has been installed.

The new certificate covers the following domains:

https://helpdesk.simgroup.co.id

You should test your configuration at:

https://www.ssllabs.com/ssltest/analyze.html?d=helpdesk.simgroup.co.id

Sunting

Server 04/06/2026

zabbix server merah

DETAIL LOG ERROR / GEJALA

server merah di zabix tidak konek

PROSEDUR SOLUSI FIX

1. Cek apakah Zabbix Agent hidup (running)

Di server cloudopenvpn2 (IP: 149.129.253.93):

CentOS / Rocky / Alma / RHEL

systemctl status zabbix-agent

systemctl restart zabbix-agent

Ubuntu / Debian

systemctl status zabbix-agent

systemctl restart zabbix-agent

Kalau statusnya inactive atau failed, berarti masalahnya di sini.

2. Pastikan port agent terbuka (default 10050)

Test dari server Zabbix:

telnet 149.129.253.93 10050

atau

nc -vz 149.129.253.93 10050

Kalau “Connection refused” ? service mati.

Kalau “Timed out” ? firewall blokir.

3. Cek firewall server

FirewallD

firewall-cmd --list-all

firewall-cmd --add-port=10050/tcp --permanent

firewall-cmd --reload

UFW

ufw allow 10050/tcp

ufw reload

4. Cek konfigurasi /etc/zabbix/zabbix_agentd.conf

Pastikan:

Server=

ServerActive=

Hostname=cloudopenvpn2

Contoh:

Server=172.16.0.10

ServerActive=172.16.0.10

Hostname=cloudopenvpn2

Setelah edit:

systemctl restart zabbix-agent

5. Cek di Zabbix UI (Web)

Masuk ke:

Monitoring ? Hosts ? cloudopenvpn2 ? tab Latest Data

Kalau merah, biasanya muncul error seperti:

Get value from agent failed

No such file or directory

Connection timeout 10050

Klik ikon ZBX merah ? Details ? akan terlihat pesan error lengkap.

Analisa Tepatnya

Dari server Zabbix:

telnet 149.129.253.93 10050

Jadi masalahnya sekarang tinggal 2 kemungkinan:

1. Port 10050 di server 149.129.253.93 tertutup

Walaupun kamu bisa SSH, belum tentu port 10050 terbuka.

Cek dari server 149.129.253.93:

sudo systemctl status zabbix-agent

sudo ss -tlnp | grep 10050

Harusnya muncul:

LISTEN 0 0 0.0.0.0:10050

Kalau tidak muncul ? agent tidak jalan.

2. Firewall di server 149.129.253.93 memblokir port 10050

Cek:

CentOS/RHEL (firewalld)

firewall-cmd --list-all

firewall-cmd --add-port=10050/tcp --permanent

firewall-cmd --reload

UFW (Ubuntu)

ufw status

ufw allow 10050/tcp

iptables

iptables -L -n | grep 10050

Sekarang kita pastikan dulu:

Tolong jalankan di server 149.129.253.93:

1 Cek service agent

systemctl status zabbix-agent

2 Cek apakah port 10050 listen

ss -tlnp | grep 10050

3 Cek firewall

iptables -L -n

root@OpenVPN2 ~]# firewall-cmd --list-all

public

target: default

icmp-block-inversion: no

interfaces:

sources:

services: dhcpv6-client ssh

ports: 514/udp 514/tcp

protocols:

masquerade: yes

forward-ports:

source-ports:

icmp-blocks:

rich rules:

ChatGPT said:

Terlihat jelas dari output firewall Anda:

services: dhcpv6-client ssh

ports: 514/udp 514/tcp

Tidak ada port 10050 atau 10051 yang di-allow.

Maka Zabbix Server tidak bisa masuk ke agent (port 10050)

Dan Agent juga tidak bisa connect ke server (port 10051)

Inilah penyebab semua error Active Check.

SOLUSI: Izinkan port Zabbix

1 Izinkan port untuk Zabbix Agent (10050)

firewall-cmd --add-port=10050/tcp --permanent

2 Izinkan port untuk Zabbix Server (10051)

Jika server Zabbix ada di IP 149.129.253.93, maka izinkan juga:

firewall-cmd --add-port=10051/tcp --permanent

3 Reload firewall

firewall-cmd --reload

4 Verifikasi

firewall-cmd --list-all

Harus muncul:

ports: 514/udp 514/tcp 10050/tcp 10051/tcp

Sunting

Recording 04/06/2026

script copy recording

DETAIL LOG ERROR / GEJALA

jika ada request ambil recording

PROSEDUR SOLUSI FIX

find /var/spool/asterisk/monitor/2025/12/29/ -type f -name "*0811651573*"

cp -Rf /var/spool/asterisk/monitor/2026/01/12/*081376813373* /root/GoogleDrive/RECORDING/REQ231225/

find /root/GoogleDrive/RECORDING/MTF_TASK_FORCE/2025/12/12 -iname "*MTF_TASK_FORCE*" | wc -l

find /var/spool/asterisk/monitor/2025/12/12 -iname "*MTF_TASK_FORCE*" | wc -l

Sunting

Tugas-pagi 04/06/2026

Cek storage all server

DETAIL LOG ERROR / GEJALA

script ubah data di excel

PROSEDUR SOLUSI FIX

Sub FINAL_Storage_Report()

Dim ws As Worksheet

Dim lastRow As Long

Dim i As Long

Dim dict As Object

Dim host As String

Dim keepMounts As Variant

Dim rng As Range

Set ws = ThisWorkbook.Sheets("Storage Report")

Set dict = CreateObject("Scripting.Dictionary")

' ================= DAFTAR SERVER =================

dict.Add "FIF_C0", True

dict.Add "DATA-ENTRY", True

dict.Add "Training_CC", True

dict.Add "ASSET-LOB-CC", True

dict.Add "TELEINTERVIEWER", True

dict.Add "SME-CentOs", True

dict.Add "FIF-MMU", True

dict.Add "fif-telesales-autodial", True

dict.Add "Sehati DC", True

dict.Add "RESERVE PROXY LB", True

dict.Add "APP_MTF_CS", True

dict.Add "mtf-cs-onebox-ubuntu", True

dict.Add "FIFWA_OFFICIAL", True

dict.Add "Grafana", True

dict.Add "WA-MUF", True

dict.Add "fif-reminder-app", True

dict.Add "FIF_DC", True

dict.Add "Remedial", True

dict.Add "STORAGE 70.23", True

dict.Add "NAS 30.4", True

dict.Add "LKS", True

dict.Add "cloudopenvpn", True

dict.Add "Ping Autodial", True

dict.Add "BCAF-DC-AUTO", True

dict.Add "fif-reminder-db_pbx", True

dict.Add "multiclient-v3", True

dict.Add "JULO_CTC", True

dict.Add "MTF_OVRS", True

dict.Add "apps_dataentry", True

dict.Add "BFI-WA", True

dict.Add "AUTODIAL_C1_CLOUD", True

dict.Add "MTF-AUTODIAL", True

dict.Add "MUF-CLOUD", True

dict.Add "QA Telecollection", True

dict.Add "Itop", True

dict.Add "NEW-CC-DRIVE", True

dict.Add "MTF_CS_INBOUND_CLOUD", True

dict.Add "OVRS-MTFPROJECT-CLOUD", True

dict.Add "FIF_Telesales", True

dict.Add "Bcaf DC", True

dict.Add "Dashboard OTC 70.120", True

dict.Add "FIF TELE-AUDIT", True

dict.Add "Server FTPS NAsional", True

dict.Add "btpn-web", True

dict.Add "AWDA-DC-CLOUD", True

dict.Add "Reporting Dev Cloud", True

dict.Add "STORAGE 172.16.70.15", True

dict.Add "FIF_DC_DB_dan_ASTERISK", True

dict.Add "Backup-KR1", True

dict.Add "btpn-fileserver", True

dict.Add "autodial-smg-new", True

dict.Add "FIF filtering WA", True

dict.Add "FIF-AUTOKRANGGAN", True

dict.Add "btpn-reporting", True

dict.Add "MTF-BALNOL", True

dict.Add "cloudsymmetricsds", True

dict.Add "OVRS-KRANGGAN-CLOUD", True

dict.Add "FIF-WA", True

dict.Add "DevOnebox", True

dict.Add "FIF_PROJECT_BALNOL", True

dict.Add "BS-NSP", True

dict.Add "cloudopenvpn2", True

dict.Add "PINCALL SUCCESS-FEE", True

dict.Add "MTF_SKIPTRACE", True

dict.Add "DATA-WAREHOUSE", True

dict.Add "Zabbix server", True

dict.Add "Bcaf-va", True

dict.Add "MTF-WA", True

dict.Add "btpn-mobile", True

dict.Add "Danastra", True

dict.Add "Webcam Monitoring by PKP", True

dict.Add "FIF_PV_CLOUD", True

dict.Add "BOP-WAREHOUSE", True

dict.Add "wa-non_official-fif-tele", True

dict.Add "Multicam Premis", True

dict.Add "mtf", True

dict.Add "FIF_SKIPTRACE", True

dict.Add "Multicampaign", True

dict.Add "ADIRA", True

dict.Add "icoll", True

dict.Add "NASREC-SIM", True

dict.Add "wa-astrapay", True

dict.Add "btpn-scheduller", True

dict.Add "teleremedial-wa-official", True

dict.Add "Service Warehouse", True

' =================================================

keepMounts = Array("/", "/BACKUP", "/BACKUP3", "/etc/hostname")

lastRow = ws.Cells(ws.Rows.Count, "A").End(xlUp).Row

Set rng = ws.Range("A1:G" & lastRow)

Application.ScreenUpdating = False

' Reset

If ws.AutoFilterMode Then ws.AutoFilterMode = False

ws.Rows.Hidden = False

' ===== FILTER SERVER (AUTOFILTER ONLY) =====

rng.AutoFilter Field:=1, Criteria1:=dict.Keys, Operator:=xlFilterValues

' ===== FILTER MOUNT =====

rng.AutoFilter Field:=2, Criteria1:=keepMounts, Operator:=xlFilterValues

' ===== FIX DATA (ANTI PERSEN RIBUAN) =====

For i = 2 To lastRow

If Not ws.Rows(i).Hidden Then

' Disk 0 ? 1

If ws.Cells(i, "C").Value = 0 Then ws.Cells(i, "C").Value = 1

' ===== FIX USAGE% AMAN =====

If IsNumeric(ws.Cells(i, "D").Value) Then

If ws.Cells(i, "D").Value > 1 Then

ws.Cells(i, "D").Value = ws.Cells(i, "D").Value / 100

End If

Next i

' Format Usage%

ws.Columns("D").NumberFormat = "0%"

' Sembunyikan kolom Mount

ws.Columns("B").Hidden = True

Application.ScreenUpdating = True

MsgBox "? Storage Report selesai & Usage% AMAN (anti ribuan)", vbInformation

End Sub

Sunting

Tugas-pagi 04/06/2026

snapshoot

DETAIL LOG ERROR / GEJALA

ambil nama snapshoot

PROSEDUR SOLUSI FIX

=VLOOKUP(C2,'[ecs_snapshotLink_list_ap-southeast-5_2026-06-06.csv]ecs_snapshotLink_list_ap-southe'!$E$2:$J$168,6,0)

instance name

CCCM-AWDA-NEW-KRANGGAN

CCCM-wa-non_official-succesfee

CCCM-fif-c0

CCCM-FIF-WA

CCCM-FIF-filtering-WA

CCCM-Data-warehouse

CCCM-Fif-teleaudit

CCCM-ovrs-kranggan

CCCM-MTF_autodial

CCCM-Roleplay

CCCM-ovrs-project

CCCM-Ovrs-Semarang

CCCM-Fifauto-kr

CCCM-Bop-warehouse

CCCM-Fif-PV

CCCM-Webcam-pkp

CCCM-Pingcall_Success-Fee

HO-Teleinterview

CCCM-Autodial-C1

CCCM-Maybank

CCCM-Myrep_API

CCCM-MyRep_DB

CCCM-Myrep_pabx

CCCM-MyRep_APPS

CCCM-multicampaign

CCCM-jogja2

CCCM-autodial-semarang2

CCCM-autodial-semarang

CCCM-autodial-jogja1

CCCM-Symmetric_DS

CCCM-Openvpn1

CCCM-openvpn-router

CCCM-fif-dashboard

CCCM-Autodial-smg3

CCCM-MUF

CCCM-wa-official-muf

CCCM-bcaf-auto

CCCM-FIF-WA-OFFICIAL

CCCM-mtf-balnol

CCCM-apps_mtf-cs-onebox

CCCM-Mtf-cs-inbound

CCCM-BTPN-fileserver

CCCM-BTPN-app-mobile

CCCM-BTPN-app-web

CCCM-BTPN-reporting

HO-BS-NSP

CCCM-Danastra

CCCM-reminder-app1

CCCM-fif-reminder-db_pbx

CCCM-fif-telesales-autodial

CCCM-adira

CCCM-btpn-icoll

CCCM-wa-astrapay

CCCM-wa-bfi (hilang)

CCCM-Amartha

CCCM-fif-teleremedial-waofficial

CCCM-MulticlientV3

CCCM-btpn-scheduller

CCCM-bcaf-va

CCCM-reminder-app2

CCCM-PPTP-cloud-mikrotik

CCCM-Openvpn-YGK

CCCM-Openvpn-SMG2

CCCM-LKS

CCCM-wa-non_official-fif-tele

CCCM-Tiketing

CCCM-Reminder-Autodial

CCCM-wa-call-fif-c2c-app3-smg

CCCM-wa-call-fif-c2c-app2-smg

CCCM-wa-call-fif-c2c-app1-smg

CCCM-wa-call-fif-c2c-jgj2

CCCM-wa-call-fif-c2c-jgj1

CCCM-Wa-call-fif-c2c-kr

CCCM-wa-fif-pv

CCCM-Tiketing

CCCM-fifdc-bali-asterisk

CCCM-fifdc-bali-app

Sunting

Tugas-pagi 04/06/2026

Snapshoot

DETAIL LOG ERROR / GEJALA

script ubah data di excel

PROSEDUR SOLUSI FIX

Sub FilterByAllowedNames()

Dim ws As Worksheet

Dim lastRow As Long

Dim i As Long

Dim allowedList As Object

Dim nama As String

' === Daftar nama yang ingin dipertahankan ===

' (Tambahkan / edit di sini sesuai kebutuhan)

Dim allowedArray As Variant

allowedArray = Array( _

"CCCM-AWDA-NEW-KRANGGAN", "CCCM-wa-non_official-succesfee", "CCCM-fif-c0", "CCCM-FIF-WA", "CCCM-FIF-filtering-WA", _

"CCCM-Data-warehouse", "CCCM-Fif-teleaudit", "CCCM-ovrs-kranggan", "CCCM-MTF_autodial", _

"CCCM-Roleplay", "CCCM-ovrs-project", "CCCM-Ovrs-Semarang", "Fifauto-kr", _

"CCCM-Bop-warehouse", "CCCM-Fif-PV", "CCCM-Webcam-pkp", "CCCM-Pingcall_Success-Fee", _

"HO-Teleinterview", "CCCM-Autodial-C1", "CCCM-Maybank", "CCCM-Myrep_API", "CCCM-MyRep_DB", _

"CCCM-Myrep_pabx", "CCCM-MyRep_APPS", "CCCM-multicampaign", "CCCM-jogja2", _

"CCCM-autodial-semarang2", "CCCM-autodial-semarang", "CCCM-autodial-jogja1", _

"CCCM-Symmetric_DS", "CCCM-Openvpn1", "CCCM-openvpn-router", "CCCM-Fif-Dashboard", _

"CCCM-Autodial-smg3", "CCCM-MUF", "CCCM-wa-official-muf", "CCCM-bcaf-auto", _

"CCCM-FIF-WA-OFFICIAL", "CCCM-mtf-balnol", "CCCM-apps_mtf-cs-onebox", "CCCM-Mtf-cs-inbound", _

"CCCM-BTPN-fileserver", "CCCM-BTPN-app-mobile", "CCCM-wa-non_official-fif-tele", "CCCM-BTPN-app-web", _

"CCCM-BTPN-reporting", "HO-BS-NSP", "CCCM-Danastra", "CCCM-reminder-app1", _

"CCCM-fif-reminder-db_pbx", "CCCM-fif-telesales-autodial", "CCCM-adira", "CCCM-btpn-icoll", _

"CCCM-wa-astrapay", "CCCM-wa-bfi", "CCCM-Amartha", "CCCM-fif-teleremedial-waofficial", _

"CCCM-MulticlientV3", "CCCM-btpn-scheduller", "CCCM-bcaf-va", "CCCM-reminder-app2", _

"CCCM-Openvpn1", "CCCM-Openvpn-YGK", "CCCM-Openvpn-SMG2", "CCCM-Reminder-Autodial", "CCCM-LKS", _

"CCCM-PPTP-cloud-mikrotik", "CCCM-Tiketing", "CCCM-wa-call-fif-c2c-app3-smg", "CCCM-wa-call-fif-c2c-app2-smg", _

"CCCM-wa-call-fif-c2c-app1-smg", "CCCM-wa-call-fif-c2c-jgj2", "CCCM-wa-call-fif-c2c-jgj1", "CCCM-wa-call-fif-c2c-kr", _

"CCCM-wa-fif-pv", "CCCM-Tiketing", "CCCM-fifdc-bali-app", "CCCM-fifdc-bali-asterisk" _

)

' Buat dictionary untuk pengecekan cepat

Set allowedList = CreateObject("Scripting.Dictionary")

For i = LBound(allowedArray) To UBound(allowedArray)

allowedList(Trim(LCase(allowedArray(i)))) = True

Next i

Set ws = ActiveSheet

Const colS As Long = 19 ' Kolom S

lastRow = ws.Cells(ws.Rows.Count, colS).End(xlUp).Row

' Loop dari bawah agar aman saat menghapus baris

For i = lastRow To 2 Step -1

nama = Trim(LCase(ws.Cells(i, colS).Value))

' Jika nama tidak ada di daftar ? hapus baris

If Not allowedList.exists(nama) Then

ws.Rows(i).Delete

End If

Next i

MsgBox "Selesai! Hanya data yang ada dalam daftar yang tersisa.", vbInformation

End Sub

Sunting

Tugas-pagi 04/06/2026

CEK PC MONITORING HO

DETAIL LOG ERROR / GEJALA

nyalakan pc dan menampilkan monitoring yang akan di tampilkan di tv

PROSEDUR SOLUSI FIX

10.10.12.188

https://dashboard-fif-dc.simgroup.co.id/autodial/fif_dc_dashboard/index.php/home/loginpage

sim_opr

ts4m4r@_R3st0

chrome

arahin ke kranggan

10.10.12.186

sim123

pkp123

https://wfhmonitor.simgroup.co.id:7100/dashboard

chrome

10.10.12.250

sim123

https://api-myrep.simgroup.co.id/dashboardPDS/dashboard.html

mozila

password

123456

Sunting

Jaringan 03/06/2026

Kendala Pengiriman Data MTF Gagal

DETAIL LOG ERROR / GEJALA

Tujuan: Troubleshooting ketika terjadi kegagalan atau gangguan saat mengirimkan data hasil call ke sistem MTF.

PROSEDUR SOLUSI FIX

1 CEK KONEKSI DASAR DARI SERVER

Lakukan pengecekan awal dari server 32.215 untuk memastikan jaringan aman.

ping 172.24.42.4

Catatan

Jika ping RTO / loss, kemungkinan ada kendala jaringan
Selesaikan masalah jaringan terlebih dahulu sebelum cek IPsec

2 CEK IPSEC POLICY MTF

Masuk ke Mikrotik:

IP ? IPsec ? Policies

Cari policy dengan Peer: MTF
Pastikan policy enable
Perhatikan Dst. Address (IP tujuan MTF)

Contoh IP tujuan MTF:

103.125.223.91

3 CEK STATUS PEER IPSEC

Masuk ke:

IP ? IPsec ? Peers ? Status

Yang dicek:

Peer: MTF
Status: Connected / Established
Dst. Address sesuai dengan IP tujuan (103.125.223.91)

4 CEK ACTIVE PEERS

Masuk ke:

IP ? IPsec ? Active Peers

Perhatikan:

State harus established
Traffic harus berjalan (ada paket RX/TX)

???? Jika traffic 0 / 0 atau state tidak normal ? indikasi koneksi bermasalah

5 TINDAKAN JIKA IPSEC STUCK

Jika ditemukan:

State established tapi traffic 0 / 0
Pengiriman MTF tetap gagal

???? Lakukan clear / kill koneksi IPsec

Langkah:

Pilih Active Peer MTF
Klik Remove / Disable (kill)
Tunggu beberapa detik
Biarkan IPsec reconnect otomatis

6 VALIDASI AKHIR

Setelah IPsec reconnect:

Pastikan status kembali established
Traffic sudah berjalan
Lakukan retry pengiriman MTF
Pastikan pengiriman berhasil

CATATAN PENTING

Jangan langsung kill IPsec tanpa cek ping
Pastikan IP tujuan MTF tidak berubah
Jika sering gagal, cek routing, firewall, atau laporkan ke pihak MTF / ISP

Sunting

Server 03/06/2026

Konfigurasi Server - Ganti IP, Port SSH, dan Password Root

DETAIL LOG ERROR / GEJALA

Tujuan: Panduan standar melakukan pengerasan keamanan (hardening) server dengan mengubah IP Address, Port default SSH, dan Password user root pada Linux.

PROSEDUR SOLUSI FIX

#ganti ip server

sudo nano /etc/netplan/50-cloud-init.yaml

Ganti isinya jadi ini (PASTE FULL)

network:

version: 2

ethernets:

ens18:

dhcp4: no

addresses:

- 172.16.70.81/16

gateway4: 172.16.70.1

nameservers:

addresses:

- 8.8.8.8

- 1.1.1.1

lalu jalankan: sudo netplan apply

cek hasil:

ip a

ip route

ping -c 3 8.8.8.8

#ganti password root

sudo passwd root

#agar root bisa di akses dan dipakai

sudo nano /etc/ssh/sshd_config

Edit SSH config:

sudo nano /etc/ssh/sshd_config

Cari:

#PermitRootLogin, diubah jadi PermitRootLogin yes

jika sudah Restart SSH socket:

sudo systemctl restart ssh.socket

#cara ganti port ssh:

Buka config SSH

sudo vim /etc/ssh/sshd_config

cari

#Port 22

ganti

Port 35827

HARUS ADA SATU BARIS SAJA, contoh:

Port 35827

Jangan ada Port lain, jangan pakai #

Test & restart

sudo sshd -t

sudo systemctl restart ssh

Cek lagi

sudo ss -tlnp | grep ssh

Targetnya:

0.0.0.0:35827

[::]:35827

Restart SSH socket:

sudo systemctl restart ssh.socket

Sunting

Server 03/06/2026

Panduan Menambahkan Host Server Baru di Zabbix Monitoring

DETAIL LOG ERROR / GEJALA

Tujuan: Langkah-langkah mendaftarkan infrastruktur server atau router baru ke dalam sistem monitoring Zabbix agar resource-nya dapat terpantau.

PROSEDUR SOLUSI FIX

buka ssh server 172.16.70.108

#buka:

vim /etc/zabbix/zabbix_agentd.conf

#ubah script dibawah ini di sesusaikan

Server=0.0.0.0/0

ServerActive=127.0.0.1

Hostname=Reminder-app3 -> nama host ini akan di sesuaikan di web zabix

#save script, lalu restart zabbix-agent

systemctl restart zabbix-agent

systemctl status zabbix-agent

ss -tlnp | grep 10050

tail -f /var/log/zabbix/zabbix_agentd.log (cek log)

selanjutnya masuk ke web zabix

http://172.16.70.108/zabbix/hosts.php

klik create host, setelah itu isinya di sesuaikan ya seperti gambar berikut

Sunting

Jaringan 03/06/2026

Alur Kendala Jaringan - Beyond Lemot / Telko Massal

DETAIL LOG ERROR / GEJALA

Pengecekan kendala jaringan lemot pada layanan web, on-premises, atau gangguan massal pada Telko PKP.

PROSEDUR SOLUSI FIX

1. Web Lemot: Jalankan traceroute ke google dari router (tunggu sampai 100 sent): tool traceroute 8.8.8.8

2. Jika traceroute aman tapi tetap lemot (On-Premises): - Cek dari agen: traceroute ke IP Beyond dan IP Mikrotik. - Jika ping time tinggi -> Kendala kemungkinan di Switch. - Jika hanya 1 agen -> Cek IP agen tersebut di menu Queue, apakah terkena limit bandwidth.

3. Kendala Telko Massal: - Jalankan traceroute ke IP Publik Telko (Contoh: 103.113.133.30 atau 182.253.222.86):tool traceroute 103.113.133.30 use-dns=yes - Jika LOST di hop 1 dan terakhir -> Kendala di ISP. - Sebelum lapor, cek jalur ISP lain yang bagus dengan perintah: tool traceroute 103.113.133.30 use-dns=yes routing-table=iforte tool traceroute 103.113.133.30 use-dns=yes routing-table=tachyon-fo tool traceroute 103.113.133.30 use-dns=yes routing-table=MYREP - Jika sudah ketemu ISP yang bersih (tidak lost), ubah jalur IP Telko PKP di menu "IP -> Route" ke ISP tersebut. - Setelah dialihkan, laporkan ISP yang kendala.

Sunting

Jaringan 03/06/2026

Kendala Layanan Cloud & Pengalihan Gateway Mikrotik

DETAIL LOG ERROR / GEJALA

Terjadi lost / RTO saat mengakses layanan cloud atau IP layanan tertentu (Contoh: Multicampaign 192.168.0.186 / 192.168.0.189).

PROSEDUR SOLUSI FIX

1. Jalankan traceroute ke IP layanan dari Mikrotik: tool traceroute 192.168.0.186 - Jika LOST di hop 1 -> Kendala di server VPN. - Jika LOST di hop2 -> Kendala di server internal (Cek CPU, RAM, dll).

2. Solusi Pengalihan Jalur (Gateway): - Masuk ke menu "IP -> Route", cari IP layanan/segment-nya. - Ubah gateway ke salah satu jalur VPN cloud yang bagus: * KR3TOCLOUD (16.16.6.1) * LT2P-TOCLOUD (15.15.5.1) * OVPN CLOUD (10.55.0.1)

3. Wajib Clear Connection setelah pindah jalur: - Masuk ke "IP -> Firewall -> Connection". - Filter berdasarkan "Dst. Address" = IP Tujuan (contoh: 192.168.0.186), lalu Ctrl+A dan klik tanda minus (-) untuk hapus.

4. Jika Agen/LAN tetap tidak bisa akses (RTO) setelah dialihkan, tambahkan NAT Rule: - Chain: srcnat - Dst. Address: 192.168.0.0/24 - Out. Interface: YGYTOCLOUD (atau nama interface VPN aktif) - Action: masquerade

5. Cek IP Publik ISP untuk laporan Best Route: - Masuk menu Interface -> Pilih jalur VPN (misal KR3TOCLOUD) -> Menu Dial Out -> Lihat IP Publiknya (contoh: 8.215.48.238). - Gunakan parameter "use-dns=yes" saat traceroute untuk mengetahui nama ISP.

Sunting

Jaringan 03/06/2026

Troubleshooting Server On-Premise & Bandwidth LAN

DETAIL LOG ERROR / GEJALA

Kendala koneksi internet lambat secara umum atau akses lambat ke server lokal (on-premise).

PROSEDUR SOLUSI FIX

1. Pengecekan Awal: - Lakukan ping ke internet (8.8.8.8), jika RTO langsung laporkan ke ISP utama (iForte sebagai main link).

2. Jika Ping Aman tapi Tetap Lemot: - Cek penggunaan bandwidth internet di menu Interface (LAN / TO KR5 / TOCLOUD, dll). - Pastikan RX dan TX tidak melebihi 100 Mbps. - Jika melebihi 100 Mbps, lakukan Torch IP untuk mencari user/IP yang memakan bandwidth besar. - Solusi Cloud: Alihkan gateway IP yang rakus tersebut ke MYREP atau Tachyon di "IP -> Route". - Solusi LAN: Kecilkan limit bandwidth IP tersebut di menu "Queue".

3. Jika Kendala Khusus Server On-Premise Lemot: - Cek process list di Database (DB). - Cek Load Average (LA) server. - Cek kapasitas Harddisk (HDD) apakah penuh atau tidak. - Cek ping time dari komputer agen ke Mikrotik (172.16.70.1) dan ke server Beyond.

Sunting

Jaringan 03/06/2026

Integrasi & Dokumentasi API FIF / FIF PV

DETAIL LOG ERROR / GEJALA

Pengecekan parameter jaringan, pengecekan pagi hari, dan dokumentasi tautan (link) pengiriman data ke FIF / FIF PV.

PROSEDUR SOLUSI FIX

1. Pengecekan Pagi (FIF PV Kendala Lama Masuk/Kirim Data): - Lakukan ping dari router (70.1) ke server internal: ping 192.168.0.215 - Cek backend FIF PV dengan melakukan ping ke: ws-sim2-new.fifgroup.co.id (104.18.7.51)

2. Pengujian Konektivitas API (Sesuai tipe kendala, lakukan Trace, Ping, dan Telnet): - Jika Kendala FIF DC: Cek wssmartcoll.fifgroup.co.id (104.18.6.51) - Jika Kendala FIF PV: Cek ws-sim2.fifgroup.co.id

3. Daftar Link/URL Integrasi FIF (Jika user/klien menanyakan): - Link Kirim Hasil Call FIF: https://wssmartcoll.fifgroup.co.id/restsmartcoll/api/deskcall/send_call_result - Link Kirim FIF PV: https://ws-sim2.fifgroup.co.id/ atau ws-sim2.fifgroup.co.id:10080 - URL FIF Validasi: https://new-fm-collection.fifgroup.co.id:9443/fifmcs.webapp/Main (Host: new-fm-collection.fifgroup.co.id) - VPN Endpoint: vpn.fifgroup.co.id - Catatan tambahan: Beyond FIF Validasi.

Sunting

Jaringan 03/06/2026

Daftar IP Publik & Gateway Jaringan Kranggan

DETAIL LOG ERROR / GEJALA

Dokumentasi acuan IP publik, IP gateway, dan kebijakan routing (traffic management) untuk aplikasi spesifik.

PROSEDUR SOLUSI FIX

Daftar ISP, Gateway, dan IP Publik:

1. iForte (Main Link) - Gateway: 103.165.198.81 - IP Publik: 103.165.198.82

2. MyRepublic (MYREP) - Gateway: 103.121.20.9 - IP Publik: 103.121.20.10

3. Tachyon - Gateway: 115.124.64.129 - IP Publik: 115.124.64.130

4. Tachyon MW - Gateway: 115.124.64.185 Kebijakan Routing Khusus Aplikasi

(Dialihkan ke Tachyon via 115.124.64.129): - WhatsApp Traffic: Segment 149.154.167.0/24 - Telegram Traffic: Segment 149.154.167.0/24 - YouTube Traffic: Segment 13.224.249.0/24

Sunting

Jaringan 03/06/2026

Koneksi Telnet Terhenti (Trying...) - Whitelist IP Cloud

DETAIL LOG ERROR / GEJALA

Gagal melakukan telnet ke endpoint eksternal melalui port tertentu. Contoh kasus: Gagal telnet ke wstest.simgroup.co.id port 33061 dari server reminder (muncul status "Trying 103.165.198.82...").

PROSEDUR SOLUSI FIX

Solusi Perbaikan:

1. Cari tahu IP Publik dari server asal yang mengalami kendala (Contoh kasus: FIF Reminder IP Publiknya adalah 147.139.172.232). - Data Teknis FIF Reminder (Asterisk & DB): * IP Publik: 147.139.172.232 * IP Lokal: 192.168.0.28 * Port: 35827 * Kredensial

2. Daftarkan IP Publik tersebut ke dalam daftar whitelist Mikrotik: - Masuk ke menu: IP -> Firewall -> Address List - Klik tombol Add (+) - Name / List: Pilih "WhiteListIPCLOUD" - Address: Masukkan IP Publik server yang kendala (Contoh: 147.139.172.232) 3. Lakukan pengujian telnet kembali dari server asal.

Sunting

Jaringan 03/06/2026

Kendala Akses Aplikasi ESTAR

DETAIL LOG ERROR / GEJALA

Aplikasi ESTAR tidak dapat diakses sama sekali oleh pengguna.

PROSEDUR SOLUSI FIX

Langkah Troubleshooting Jaringan ESTAR:

1. Jalankan traceroute ke IP target aplikasi ESTAR.

2. Jika didapati hasil RTO / LOST pada hop terakhir, segera kumpulkan buktinya lalu laporkan ke pihak MTF.

3. Jika hasil traceroute aman namun aplikasi tetap tidak bisa diakses, lakukan pengecekan pada konfigurasi IPsec VPN: - Masuk ke menu IP -> IPsec -> Pilih tab Peers. - Periksa status dan IP Publik peer tujuan (Bagian Peers Address MTF: 103.125.223.4).

4. Untuk menyegarkan koneksi, pindah ke sub-menu Active Peers (masih di menu IPsec), pilih IP Publik terkait, lalu klik hapus/clear connection.

Sunting

Jaringan 03/06/2026

Gagal Akses / Ping MyRepublic (MYREP) di Pagi Hari

DETAIL LOG ERROR / GEJALA

Koneksi internet atau IP gateway MyRepublic tidak merespon/tidak dapat di-ping ketika pengecekan rutin di pagi hari.

PROSEDUR SOLUSI FIX

Solusi Perbaikan Cepat: Kendala ini biasanya disebabkan oleh service cloudapi yang tersangkut pada sesi ppp Mikrotik.

1. Buka Winbox / konsol Mikrotik.

2. Masuk ke menu: PPP.

3. Pindah ke tab: Active Connections.

4. Cari koneksi dengan nama user: cloudapi

5. Klik kanan atau pilih session "cloudapi" tersebut, lalu klik tanda minus (-) / Kill Connection untuk memutuskan sesi gantung. Setelah di-kill, koneksi akan terbentuk ulang secara bersih dan normal kembali.

Sunting

Server 03/06/2026

Docker Storage Penuh (Root 97%)

DETAIL LOG ERROR / GEJALA

Muncul error "no space left on device" saat build image baru.

PROSEDUR SOLUSI FIX

1. Jalankan: docker system prune -a --volumes 2. Cek sisa storage dengan: df -h

Sunting

Database 03/06/2026

PostgreSQL Connection Timeout

DETAIL LOG ERROR / GEJALA

Aplikasi memunculkan error "Too many connections" saat jam sibuk.

PROSEDUR SOLUSI FIX

Edit file postgresql.conf, naikkan nilai "max_connections = 500" lalu restart service postgres.

Sunting

Arsip Troubleshooting

request tarik recording ke oss di all layanan

Zabbix kendala zabbix-agent.service: failed with result 'exit-code'

Menambahkan server baru di grafana

membuat DNS lokal dan cloud alibaba

ssl expaired dan mendaftarkan ssl

zabbix server merah

script copy recording

Cek storage all server

snapshoot

Snapshoot

CEK PC MONITORING HO

Kendala Pengiriman Data MTF Gagal

1 CEK KONEKSI DASAR DARI SERVER

2 CEK IPSEC POLICY MTF

3 CEK STATUS PEER IPSEC

4 CEK ACTIVE PEERS

5 TINDAKAN JIKA IPSEC STUCK

6 VALIDASI AKHIR

CATATAN PENTING

Konfigurasi Server - Ganti IP, Port SSH, dan Password Root

Panduan Menambahkan Host Server Baru di Zabbix Monitoring

Alur Kendala Jaringan - Beyond Lemot / Telko Massal

Kendala Layanan Cloud & Pengalihan Gateway Mikrotik

Troubleshooting Server On-Premise & Bandwidth LAN

Integrasi & Dokumentasi API FIF / FIF PV

Daftar IP Publik & Gateway Jaringan Kranggan

Koneksi Telnet Terhenti (Trying...) - Whitelist IP Cloud

Kendala Akses Aplikasi ESTAR

Gagal Akses / Ping MyRepublic (MYREP) di Pagi Hari

Docker Storage Penuh (Root 97%)

PostgreSQL Connection Timeout