Re: Didele problema. [oxygen @ 2009-11-19 20:43:36]

Tema: Re: Didele problema.
Autorius: oxygen
Data: 2009-11-19 20:43:36
va, istrauka is messages:

Nov 19 15:43:36 server kernel: ip_tables: (C) 2000-2006 Netfilter Core Team

Nov 19 15:48:32 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 15:48:34 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:03:13 server -- MARK --

Nov 19 16:03:48 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:03:50 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:03:52 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:03:54 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:10:58 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:11:00 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:11:02 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:11:04 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:13:56 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:13:58 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:14:00 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:14:02 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:18:00 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:18:02 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:18:04 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:18:06 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:43:14 server -- MARK --

Nov 19 16:46:33 server clamd[2240]: No stats for Database check - forcing 
reload

Nov 19 16:46:33 server clamd[2240]: Reading databases from /var/lib/clamav

Nov 19 16:46:44 server clamd[2240]: Database correctly reloaded (653325 
signatures)

Nov 19 16:57:44 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:57:46 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 16:57:48 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 16:57:50 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:00:44 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:00:46 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:00:48 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:00:50 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:09:54 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:09:56 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:09:58 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:10:00 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:12:00 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:12:02 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:12:04 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:12:06 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:23:14 server -- MARK --

Nov 19 17:28:10 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:28:12 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:28:14 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:28:16 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:42:28 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:42:30 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:42:32 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:42:34 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:46:44 server clamd[2240]: SelfCheck: Database modification 
detected. Forcing reload.

Nov 19 17:46:44 server clamd[2240]: Reading databases from /var/lib/clamav

Nov 19 17:46:57 server clamd[2240]: Database correctly reloaded (653326 
signatures)

Nov 19 17:56:36 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:56:38 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:56:40 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:56:42 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 17:57:40 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 17:57:42 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 18:23:15 server -- MARK --

Nov 19 18:43:15 server -- MARK --

Nov 19 18:56:01 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 18:56:13 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 18:56:15 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 18:56:17 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 18:59:02 server clamd[2240]: SelfCheck: Database status OK.

Nov 19 19:23:16 server -- MARK --

Nov 19 19:43:16 server -- MARK --

Nov 19 20:03:16 server -- MARK --

Nov 19 20:18:59 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 20:19:13 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 20:19:15 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 20:19:17 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 20:20:35 server clamd[2240]: SelfCheck: Database status OK.

Nov 19 20:26:05 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 20:26:07 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 20:36:13 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 20:36:15 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex

Nov 19 20:36:17 server kernel: e100: eth1: e100_watchdog: link down

Nov 19 20:36:19 server kernel: e100: eth1: e100_watchdog: link up, 100Mbps, 
full-duplex







"oxygen" <neturiu@mailo.px> wrote in message 
news:he43ad$2jl$1@trimpas.omnitel.net...
> Kiek supratau is linuxisto, imete skripta per www kazkoki, tas skriptas 
> susijes su kazkokiu portu. Dar rado pora "rootkit'us". Zodziu isvada kad 
> serva reikia perrasyti. Baisu. yra keli labai svarbus www ant servo. 
> Pakuoti su tar baisu irgi, nera garantijos kad viskas graziai persikels. 
> Reikia deti dar viena nauja serva salia seno, irasyti naujai ir kelti po 
> biski is seno i nauja. O situacija nepasikeite: kas kazkiek minuciu servas 
> perkrauna ruteri, o jei tuo metu srautas didelis buvo- ne tik perkrauna 
> bet ir pakabina. Keista viskas, serveriai, laidai, ruteris ir t.t. Lauzo 
> tikrai softwaras.
> "krx" <krx@d.lt> wrote in message news:he3501$glo$1@trimpas.omnitel.net...
>>
>> "ejs" <ejs@no.where> wrote in message 
>> news:he1va6$flf$1@trimpas.omnitel.net...
>>> Laimis rase:
>>>> ejs rase:
>>>>> seitan rase:
>>>>>> "linuxistas rado porta atvira"
>>>>>> o linuxistas gal tegu pasizhiuri servisus ir , kas svarbiausia logus?
>>>>>> dar nesu mates hardwaro luzhimo su 0 praneshimu loguose.
>>>>>
>>>>> tuomet nemates mirstancio disko.
>>>>
>>>> Kokion nors special, kad S.M.A.R.T.'as i dmesg'a nepatektu...?
>>>
>>> kaip irasyti i dmesg, jei diskui kapec?
>>> Aisku, kartais prasimusa tonos irasu apie disko problemas.
>>> Kartais.
>>
>> Tai normaliu atveju turbut vis del to sysloginti i kita diska/dar geriau 
>> syslog servisa?
>
>