Skocz do zawartości

Be4ver

Użytkownicy
  • Zawartość

    83
  • Rejestracja

  • Ostatnio

Reputacja

2 Normalna

1 obserwujący

O Be4ver

  • Ranga
    Regularny użytkownik
  1. [PHP] json i POST

    Dostajesz jakieś dane JSON'em, które zmapowałeś do postaci obiektu PHP'owego. W tym momencie możesz spokojne odwoływać się do każdej z tych danych. Przypuszczam, że dane z programu chcesz zapisywać do bazy więc poniżej przykład kodu, którym wygenerujesz zapytania dodające modele do bazy danych: $obj = json_decode($_POST['Dane_JSON']); $sql = ''; foreach($obj->MODELE_PRODUCENTA as $ob) { $sql .= 'INSERT INTO tabela (id, index, kolejne_pola) VALUES ($ob->ID, $ob->INDEX, $ob->kolejne_pola)'; } //a tu robisz już mysql_query($sql)
  2. Dla polecenia: hostname --fqdn Otrzymuję: asterix.{domena}.pl Natomiast parametr myhostname faktycznie był źle ustawiony. Dzięki
  3. W ciągu kilku dni zauważyłem, że niektóre serwery zwracają mi maile z informacją: <kontakt@{domena-docelowa}.pl>: host {serwer}.ceti.pl[XX.XXX.XXX.XX] said: 504 <asterix>: Helo command rejected: need fully-qualified hostname (in reply to RCPT TO command) Rekordy SPF są skonfigurowane poprawnie, serwer nazwany jest asterix.{moja-domena}.pl Rzecz w tym, że z w/w serwera są wysyłane maile z 3 różnych domen (2 firmowe (*.pl, *.com), 1 prywatna (*.eu)) i nie jestem w stanie (jeśli mylę się - poprawcie mnie) ustawić 3 różnych nazw serwera dla jednego systemu. Dodam, że zwrotki nie dotyczą maili, które są wysyłane z domeny pod którą stoi serwer.
  4. Reseller domen od strony technicznej

    Dzięki. Właśnie tej informacji mi brakowało. Podziękowania dla pomocnych forumowiczów i dla Bogów, że nie spadły na mnie pioruny, ani grzmoty Temat z mojej strony do zamknięcia. Pozdrawiam
  5. Reseller domen od strony technicznej

    Nie wiem jak to w HRD wygląda, jednakże w OVH dostawałem FVAT na osobę, która była wpisana jako klient końcowy. Pytam, bo nie wiem, a mam pewne doświadczenia z innymi rejestratorami. Logiczne chyba?
  6. Reseller domen od strony technicznej

    Wszystko fajnie i cacy, tylko w momencie, gdy abonentem jest klient końcowy to faktura przychodzi na niego. A powinna przyjść na mnie, abym mógł nałożyć marżę i wystawić własną fakturę klientowi.
  7. Reseller domen od strony technicznej

    W takim razie czy muszę jakieś (jeśli tak to jakie) kroki poczynić, abym pojawił się w domenie na pozycji REJESTRATOR rejestrując domeny np. w HRD? Rzecz w tym, że księgowa nie przepuści mi faktury do momentu, aż będę w stanie udowodnić, że jestem właścicielem produktu. Natomiast w tej sytuacji, normalnie rejestruję domenę na działalność gospodarczą i wystawiam rachunek klientowi na zasadzie "wynajmu" domeny. Rzecz w tym, że klient wtedy pyta się czemu rejestratorem jest jakaś zewnętrzna firma, a ja jestem właścicielem domeny skoro on płaci za nią. Ok, jest przypisana do klienta, ale u mnie jest przypisana czy u rejestratora typu HRD?
  8. Reseller domen od strony technicznej

    W takim razie na jakiej podstawie pobieram opłatę od klienta przedłużając domenę?
  9. Jak w temacie, ciekaw jestem jak wygląda kwestia sprzedaży/odsprzedaży (nie wiem jak to ująć) ze strony technicznej i prawnej. Mam tu na myśli działalność firm typu home i nazwa. Jeśli dobrze rozumiem, kupuję domenę np. w hrd.pl, staje się ona moją własnością, a następnie odsprzedaję ją Klientowi. Pytanie tylko jak sytuacja wygląda przy odnowieniu (domena przecież nie jest już wtedy moją własnością). Jeśli jestem w błędzie, wyprowadźcie mnie proszę z niego.
  10. Zajrzałem jeszcze w /proc/mdstat i otrzymałem taki rezultat... cat /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md3 : active raid1 sda4[0] sdb4[1] 1822442815 blocks super 1.2 [2/2] [uU] md2 : active raid1 sda3[0] sdb3[1] 1073740664 blocks super 1.2 [2/2] [uU] [>....................] resync = 0.0% (393280/1073740664) finish=135634.7min speed=131K/sec md1 : active raid1 sda2[0] sdb2[1] 524276 blocks super 1.2 [2/2] [uU] md0 : active (auto-read-only) raid1 sda1[0] sdb1[1] 33553336 blocks super 1.2 [2/2] [uU] unused devices: <none> Czy przypadkiem to nie jest też kwestia (jeśli dobrze interpretuję) odtwarzania się jednej partycji?
  11. Tak mi się po ciuchu wydawało, że może być to wina dysku, ale wolałem nie krakać... Co do monitorowania SMART/kontrolera RAID, liczyłem, że dostawca u którego mam tego dedyka, zajmie się tym - jak widać złudne nadzieje... Przy okazji... czy są jeszcze jakieś parametry na które warto zwrócić uwagę podczas eksploatacji sprzętu?
  12. Niestety mnie to za wiele nie mówi vnstat 2 10: procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 0 0 0 6860628 112524 8960508 0 0 75 70 22 52 0 0 88 12 0 0 0 6860992 112524 8960628 0 0 0 1 415 1125 0 0 100 0 0 0 0 6862356 112528 8960624 0 0 0 4998 157 313 0 0 100 0 0 0 0 6860124 112528 8960624 0 0 0 0 351 1039 0 0 100 0 0 0 0 6860124 112528 8960636 0 0 0 0 492 1449 0 0 100 0 0 0 0 6860496 112536 8960636 0 0 0 14 336 1012 0 0 96 4 0 0 0 6860496 112536 8960636 0 0 0 0 483 1447 0 0 100 0 0 0 0 6860620 112536 8960636 0 0 0 0 475 1421 0 0 100 0 0 0 0 6859516 112536 8960640 0 0 0 0 595 1553 0 0 100 0 0 0 0 6859928 112536 8960640 0 0 0 0 360 1079 0 0 100 0 Dysk ma software raid 1, więc wydaje mi się, że oba na raz musiałyby się kończyć. smartctl --all sda smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.4.18] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: S1F0B9GJ LU WWN Device Id: 5 000c50 04a625637 Firmware Version: CC4B User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Nov 24 15:09:52 2012 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: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported.SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail Always - 75398600 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 7 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76207336 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 5092 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 7 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032835 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 064 063 045 Old_age Always - 36 (Min/Max 31/37) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 5837 194 Temperature_Celsius 0x0022 036 040 000 Old_age Always - 36 (0 21 0 0) 197 Current_Pending_Sector 0x0012 100 001 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 001 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 231026290856807 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 17263800474514 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 87472142477933 SMART Error Log Version: 1 ATA Error Count: 6 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days.Error 6 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:33.798 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:33.798 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:33.798 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:33.798 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 29d+06:17:33.797 SET FEATURES [set transfer mode] Error 5 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:30.881 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:30.881 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:30.881 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:30.880 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 29d+06:17:30.880 SET FEATURES [set transfer mode]Error 4 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:27.973 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:27.972 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:27.972 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:27.972 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:27.972 IDENTIFY DEVICE Error 3 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:25.089 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:25.088 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:25.088 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:25.088 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:25.088 IDENTIFY DEVICEError 2 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:21.238 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:21.238 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:21.238 READ FPDMA QUEUED 60 00 80 ff ff ff 4f 00 29d+06:17:21.237 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:21.237 SET FEATURES [Reserved for Serial ATA] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 5 - 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 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. sdb smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.4.18] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: S1F0B9GJ LU WWN Device Id: 5 000c50 04a625637 Firmware Version: CC4B User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Nov 24 15:09:55 2012 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: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported.SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail Always - 75494000 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 7 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76207367 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 5092 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 7 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032835 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 064 063 045 Old_age Always - 36 (Min/Max 31/37) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 5837 194 Temperature_Celsius 0x0022 036 040 000 Old_age Always - 36 (0 21 0 0) 197 Current_Pending_Sector 0x0012 100 001 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 001 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 245775208551271 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 17263800474514 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 87553746451309 SMART Error Log Version: 1 ATA Error Count: 6 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days.Error 6 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:33.798 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:33.798 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:33.798 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:33.798 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 29d+06:17:33.797 SET FEATURES [set transfer mode] Error 5 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:30.881 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:30.881 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:30.881 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:30.880 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 29d+06:17:30.880 SET FEATURES [set transfer mode]Error 4 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:27.973 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:27.972 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:27.972 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:27.972 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:27.972 IDENTIFY DEVICE Error 3 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:25.089 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:25.088 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:25.088 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 29d+06:17:25.088 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 29d+06:17:25.088 IDENTIFY DEVICEError 2 occurred at disk power-on lifetime: 4648 hours (193 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 29d+06:17:21.238 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:21.238 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 29d+06:17:21.238 READ FPDMA QUEUED 60 00 80 ff ff ff 4f 00 29d+06:17:21.237 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 29d+06:17:21.237 SET FEATURES [Reserved for Serial ATA] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 5 -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 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. Drugi admin przyznał się, że logował się na serwer w czasie szkolenia (wirtualny linux na żywym windowsie) - w sumie godziny pokrywają się, może nie co do sekundy, ale... Hasła zmienione, maszyna leci pod backup i do zaorania...
  13. Zaraz po przebudzeniu na równe nogi postawił mnie mail od Hetzner Support, że mój serwer generuje dużą ilość zapytań do innego serwera. Okazało się, że ktoś (do teraz nie jestem w stanie ustalić jak to się stało) uruchomił pnscan jako root. Problem w tym, że zaraz po wyłączeniu aplikacji zrestartowałem serwer (i to był moj błąd). Po restarcie co prawda pnscan nie uruchomił się, lecz system bardzo powoli działa, a kontenery OpenVZ podnoszą się piekielnie powoli (około 10 minut, a są tylko 4), serwer wykazuje Load na poziomie 4-5 (Intel® Core™ i7-2600 Quad-Core + 16GB Ram), Na procesorze nic nie widać (10-15% na jednym rdzeniu, reszta 0%, ram 2.2 GB zajęte) Postanowiłem więc uruchomić serwer w trybie rescue (z systemu ratunkowego). Obecnie backup'uje kontenery, lecz również bardzo mozolnie to idzie. Tutaj pojawia się moje pytanie - czy w takiej sytuacji winny jest wirus-skrypt(?) czy też sprzęt? A może jeszcze jakaś inna opcja jest? Od czego proponujecie zacząć poszukiwania winowajcy?
  14. Poprawione. [NIEAKTUALNE]
  15. Jak w temacie. Poszukuję osoby lub firmy która z gotowego zakodowanego kodu HTML/CSS przygotuje szablon pod Wordpress'a i wdroży go do działającego już skryptu. Kontakt na PW lub mail: janusz [AT] pyzio.eu Budżet: 150zł.
×