Disk IO peste 70% constant

Peter Pony

Vedeta
Registered
Full Member
Incepand de Luni am observat ca imi apare la serverul dedicat de la online.net Disk IO sta undeva intre 70-75% constant. E de rau?
Sta acolo de 3 zile. Nici nu mai urca nici nu mai coboara, indiferent daca pe site sunt 150 sau 600 de vizitatori.
 
Asta inseamna ca ceva iti scrie sau citeste mult pe hdd.
Ce tip de HDD ai ales cand ai comandat la online.net?
Iti recomand sa verifici in ftp ca e posibil sa ai ceva shell sau virusi,

Mai poti verifica /var/log/messages si /var/log/syslog sa vezi ce iti spune.
La fel poate fi un inceput de hdd failure si asta doar DC iti poate rezolva problema.
Install acest program https://sourceforge.net/projects/smartmontools/ si apoi ruleaza comanda
smartctl -a /dev/sda1
fsck -f /dev/sda1

Poti vedea si cat din HDD este ocupat prin comanda:
df -h

Din experienta cred ca ai ceva bagat pe host fara sa stii.
 
Var/log/mesages spune ca de atunci si pana acum imi apare din 2 in doua secunde
Cod:
Oct 31 03:06:04 s1 kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:07:cb$
Si din cand in cand apare si asa.
Cod:
Oct 31 03:10:01 s1 systemd: Created slice user-0.slice.
Oct 31 03:10:01 s1 systemd: Starting user-0.slice.
Oct 31 03:10:01 s1 systemd: Started Session 10358 of user root.
Oct 31 03:10:01 s1 systemd: Starting Session 10358 of user root.
Oct 31 03:10:01 s1 systemd: Started Session 10359 of user root.
Oct 31 03:10:01 s1 systemd: Starting Session 10359 of user root.
Oct 31 03:10:02 s1 systemd: Removed slice user-0.slice.
Oct 31 03:10:02 s1 systemd: Stopping user-0.slice.
Posibil sa am atac pe UDP 5 zile incontinuu?
 
Cod:
Oct 31 03:10:01 s1 systemd: Created slice user-0.slice.
Oct 31 03:10:01 s1 systemd: Starting user-0.slice.
Oct 31 03:10:01 s1 systemd: Started Session 10358 of user root.
Oct 31 03:10:01 s1 systemd: Starting Session 10358 of user root.
Oct 31 03:10:01 s1 systemd: Started Session 10359 of user root.
Oct 31 03:10:01 s1 systemd: Starting Session 10359 of user root.
Oct 31 03:10:02 s1 systemd: Removed slice user-0.slice.
Oct 31 03:10:02 s1 systemd: Stopping user-0.slice.

Daca nu te-ai logat tu la ora respectiva, atunci cineva se logheaza cu userul root pe serverul tau.
 
Nu m-am logat. Si ce ar trebui sa fac?
 
Am pus Linia gresita.. Cele mai multe sunt asa
astea sunt ultimele.. Nu e atac pe UDP?
Cod:
Nov  4 09:59:32 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:34 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:36 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:39 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:40 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:42 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:44 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:46 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
Nov  4 09:59:49 s1 kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=00:07:cb$
 
Am ajuns din nou aici cautand pe google
kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=ff:ff:ff$
:(. Inca nu am gasit solutie...
 
Astazi se fac 2 saptamani de cand n-a mai coborat sub 70%. Inca mai astept idei...
 
Astazi se fac 2 saptamani de cand n-a mai coborat sub 70%. Inca mai astept idei...
Deschide un tichet de support la firma de unde ai serverul, poate e o problema de hardware.
 
Ai facut verificarile sugerate mai sus? Daca da, atunci care sunt rezultatele?
Te-ai uitat pe server dupa fisiere suspecte care ar putea genera acest load?
Ai continut video/stream direct de pe server?
 
Ai facut verificarile sugerate mai sus?
M-am uitat in /var/log/messages si am erorile alea de la firewall, nu asta o fi motivul? M-am uitat dupa fisiere suspecte, nu mi-a sarit nimic in ochi. Nu am video.
 
NU stiu daca am zis, dar erorile alea de firewall (sau ce sunt ele) au aparut tot de atunci.
 
Am zis ca poate asta e problema si de aia nu am mai verificat restul, Ca si cum daca n-am motorina la masina, nu ma mai uit daca e valabila rovigneta :). O sa fac maine si restul. Pot sa fac back-up inainte la server in cazul in care dau kix sa pot da restore la tot?
 
Cod:
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.0-327.36.1.el7.x86_64] (local b    uild)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SAMSUNG MZ7LN256HMJP-00000
Serial Number:    S2MJNX0H406443
LU WWN Device Id: 5 002538 d40cdc476
Firmware Version: MAV0100Q
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Nov 18 10:53:33 2016 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (    0) seconds.
Offline data collection
capabilities:                    (0x53) SMART execute Offline immediate.
                                        Auto Offline data collection on/off supp    ort.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 133) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_    FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -           0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -           3692
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -           3
170 Unknown_Attribute       0x0032   100   100   010    Old_age   Always       -           0
171 Unknown_Attribute       0x0032   100   100   010    Old_age   Always       -           0
172 Unknown_Attribute       0x0032   100   100   010    Old_age   Always       -           0
173 Unknown_Attribute       0x0033   055   055   005    Pre-fail  Always       -           562
174 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -           0
178 Used_Rsvd_Blk_Cnt_Chip  0x0013   100   100   010    Pre-fail  Always       -           0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0013   100   100   010    Pre-fail  Always       -           804
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -           0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -           0
194 Temperature_Celsius     0x0032   068   067   000    Old_age   Always       -           32
199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       -           0
233 Media_Wearout_Indicator 0x0013   053   053   000    Pre-fail  Always       -           8919885
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -           21635
242 Total_LBAs_Read         0x0032   099   099   000    Old_age   Always       -           244
249 Unknown_Attribute       0x0032   099   099   000    Old_age   Always       -           144000

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA    _of_first_error
# 1  Short offline       Completed without error       00%      2592         -
# 2  Short offline       Completed without error       00%       261         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
  255        0    65535  Read_scanning was never started
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
htop.png
Cod:
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.
Cod:
[root@s1 ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2       216G   37G  168G  19% /
devtmpfs        7.8G     0  7.8G   0% /dev
tmpfs           7.8G     0  7.8G   0% /dev/shm
tmpfs           7.8G  785M  7.0G  10% /run
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/sda1       4.7G  117M  4.4G   3% /boot
tmpfs           1.6G     0  1.6G   0% /run/user/990
tmpfs           1.6G     0  1.6G   0% /run/user/0

la htop, cele mai multe resurse oscileaza intre apache si mysql
 
Ultima editare:
Loading...
Back
Sus