Onde ficam os Logs

[leandrorodrigosantos]

Bom dia Galera.
Alguem sabe me informar se existe algum log onde eu posso identificar que o linux caiu da rede e porque?
E onde ficaria este log?

[Arthur Bernardes]

Pode executar dmesg em terminal, ou visualizar em /var/log/syslog

[leandrorodrigosantos]

Obrigado, agora consegui pegar e abrir o log.
Porém não entendo muito dele, alguem poderia me ajudar a entender porque o linux fica caindo da rede? Vou postar o log abaixo.

Código Selecionar Expandir


Jun 24 09:24:11 SERVIDOR smbd[1883]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Jun 24 09:24:21 SERVIDOR NetworkManager[900]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Jun 24 09:24:21 SERVIDOR kernel: [ 4327.398518] r8169 0000:02:00.0: eth0: link down
Jun 24 09:24:24 SERVIDOR NetworkManager[900]: <info> (eth0): carrier now ON (device state 8)
Jun 24 09:24:24 SERVIDOR kernel: [ 4330.215273] r8169 0000:02:00.0: eth0: link up
Jun 24 09:24:27 SERVIDOR smbd[1887]: [2013/06/24 09:24:27.602817,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 09:24:27 SERVIDOR smbd[1887]: [2013/06/24 09:24:27.602891,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 09:24:27 SERVIDOR smbd[1887]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 09:24:27 SERVIDOR smbd[1887]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Jun 24 09:39:02 SERVIDOR smbd[1853]: [2013/06/24 09:39:02.926131,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 09:39:02 SERVIDOR smbd[1853]: [2013/06/24 09:39:02.926232,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 09:39:02 SERVIDOR smbd[1853]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 09:39:02 SERVIDOR smbd[1853]:   read_fd_with_timeout: client 0.0.0.0 read error = No route to host.
Jun 24 10:17:01 SERVIDOR CRON[2027]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 24 10:20:41 SERVIDOR smbd[1905]: [2013/06/24 10:20:41.235856,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:20:41 SERVIDOR smbd[1905]: [2013/06/24 10:20:41.235953,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:20:41 SERVIDOR smbd[1905]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:20:41 SERVIDOR smbd[1905]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Jun 24 10:20:45 SERVIDOR smbd[1936]: [2013/06/24 10:20:45.011256,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:20:45 SERVIDOR smbd[1936]: [2013/06/24 10:20:45.011321,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:20:45 SERVIDOR smbd[1936]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:20:45 SERVIDOR smbd[1936]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Jun 24 10:20:59 SERVIDOR smbd[1942]: [2013/06/24 10:20:59.278790,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:20:59 SERVIDOR smbd[1942]: [2013/06/24 10:20:59.278870,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:20:59 SERVIDOR smbd[1942]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:20:59 SERVIDOR smbd[1942]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Jun 24 10:21:57 SERVIDOR NetworkManager[900]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Jun 24 10:21:57 SERVIDOR kernel: [ 7782.879238] r8169 0000:02:00.0: eth0: link down
Jun 24 10:22:02 SERVIDOR NetworkManager[900]: <info> (eth0): device state change: 8 -> 2 (reason 40)
Jun 24 10:22:02 SERVIDOR NetworkManager[900]: <info> (eth0): deactivating device (reason: 40).
Jun 24 10:22:02 SERVIDOR avahi-daemon[903]: Withdrawing address record for 192.168.0.100 on eth0.
Jun 24 10:22:02 SERVIDOR avahi-daemon[903]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.100.
Jun 24 10:22:02 SERVIDOR avahi-daemon[903]: Interface eth0.IPv4 no longer relevant for mDNS.
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> (eth0): carrier now ON (device state 2)
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> (eth0): device state change: 2 -> 3 (reason 40)
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) starting connection 'Auto eth0'
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> (eth0): device state change: 3 -> 4 (reason 0)
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> (eth0): device state change: 4 -> 5 (reason 0)
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> (eth0): device state change: 5 -> 7 (reason 0)
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Jun 24 10:22:23 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jun 24 10:22:23 SERVIDOR kernel: [ 7809.339211] r8169 0000:02:00.0: eth0: link up
Jun 24 10:22:23 SERVIDOR avahi-daemon[903]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.100.
Jun 24 10:22:23 SERVIDOR avahi-daemon[903]: New relevant interface eth0.IPv4 for mDNS.
Jun 24 10:22:23 SERVIDOR avahi-daemon[903]: Registering new address record for 192.168.0.100 on eth0.IPv4.
Jun 24 10:22:24 SERVIDOR NetworkManager[900]: <info> (eth0): device state change: 7 -> 8 (reason 0)
Jun 24 10:22:24 SERVIDOR NetworkManager[900]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jun 24 10:22:24 SERVIDOR NetworkManager[900]: <info> Activation (eth0) successful, device activated.
Jun 24 10:22:24 SERVIDOR NetworkManager[900]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 24 10:22:36 SERVIDOR init: nmbd pre-start process (2094) terminated with status 127
Jun 24 10:22:58 SERVIDOR ntpdate[2090]: adjust time server 91.189.94.4 offset -0.325337 sec
Jun 24 10:25:10 SERVIDOR smbd[1953]: [2013/06/24 10:25:10.286130,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:25:10 SERVIDOR smbd[1953]: [2013/06/24 10:25:10.286221,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:25:10 SERVIDOR smbd[1953]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:25:10 SERVIDOR smbd[1953]:   read_fd_with_timeout: client 0.0.0.0 read error = No route to host.
Jun 24 10:29:37 SERVIDOR smbd[1536]: [2013/06/24 10:29:37.550135,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:29:37 SERVIDOR smbd[1536]: [2013/06/24 10:29:37.550229,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:29:37 SERVIDOR smbd[1536]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:29:37 SERVIDOR smbd[1536]:   read_fd_with_timeout: client 0.0.0.0 read error = Invalid argument.
Jun 24 10:40:43 SERVIDOR smbd[1852]: [2013/06/24 10:40:43.662135,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:40:43 SERVIDOR smbd[1852]: [2013/06/24 10:40:43.662240,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:40:43 SERVIDOR smbd[1852]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:40:43 SERVIDOR smbd[1852]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection timed out.
Jun 24 10:41:17 SERVIDOR smbd[1851]: [2013/06/24 10:41:17.454137,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:41:17 SERVIDOR smbd[1851]: [2013/06/24 10:41:17.454221,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:41:17 SERVIDOR smbd[1851]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:41:17 SERVIDOR smbd[1851]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection timed out.
Jun 24 10:43:36 SERVIDOR smbd[1867]: [2013/06/24 10:43:36.718124,  0] lib/util_sock.c:474(read_fd_with_timeout)
Jun 24 10:43:36 SERVIDOR smbd[1867]: [2013/06/24 10:43:36.718213,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Jun 24 10:43:36 SERVIDOR smbd[1867]:   getpeername failed. Error was Transport endpoint is not connected
Jun 24 10:43:36 SERVIDOR smbd[1867]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection timed out.
Jun 24 10:59:35 SERVIDOR gdm-session-worker[1325]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jun 24 10:59:44 SERVIDOR gdm-session-worker[2174]: WARNING: Unable to load file '/etc/gdm/custom.conf': Arquivo ou diretório não encontrado
Jun 24 11:00:17 SERVIDOR gdm-session-worker[2174]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jun 24 11:00:19 SERVIDOR NetworkManager[900]: <error> [1372082419.803648] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jun 24 11:00:19 SERVIDOR NetworkManager[900]: <error> [1372082419.864903] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jun 24 11:00:20 SERVIDOR kernel: [10086.380402] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 82
Jun 24 11:00:20 SERVIDOR kernel: [10086.380407] [drm:drm_edid_block_valid] *ERROR* Raw EDID:
Jun 24 11:00:20 SERVIDOR kernel: [10086.380411] <3>00 ff ff ff ff ff ff 00 40 a2 8f 03 01 01 01 01  ........@.......
Jun 24 11:00:20 SERVIDOR kernel: [10086.380415] <3>20 12 01 03 08 29 1a 78 ea d6 a5 a2 59 4a 95 24   ....).x....YJ.$
Jun 24 11:00:20 SERVIDOR kernel: [10086.380418] <3>14 50 54 af cf 00 81 80 95 00 95 0f 81 40 81 4f  .PT..........@.O
Jun 24 11:00:20 SERVIDOR kernel: [10086.380421] <3>01 01 01 01 01 01 9a 29 a0 d0 00 00 00 00 00 0a  .......)........
Jun 24 11:00:20 SERVIDOR kernel: [10086.380424] <3>7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
Jun 24 11:00:20 SERVIDOR kernel: [10086.380427] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
Jun 24 11:00:20 SERVIDOR kernel: [10086.380429] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
Jun 24 11:00:20 SERVIDOR kernel: [10086.380432] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
Jun 24 11:00:20 SERVIDOR kernel: [10086.380434]
Jun 24 11:00:20 SERVIDOR kernel: [10086.482957] i2c i2c-0: sendbytes: NAK bailout.
Jun 24 11:00:20 SERVIDOR kernel: [10086.598289] i2c i2c-0: sendbytes: NAK bailout.
Jun 24 11:00:21 SERVIDOR kernel: [10086.714264] i2c i2c-0: sendbytes: NAK bailout.
Jun 24 11:00:21 SERVIDOR kernel: [10086.826270] i2c i2c-0: sendbytes: NAK bailout.
Jun 24 11:00:21 SERVIDOR rtkit-daemon[1330]: Successfully made thread 2266 of process 2266 (n/a) owned by '1000' high priority at nice level -11.
Jun 24 11:00:21 SERVIDOR rtkit-daemon[1330]: Supervising 4 threads of 2 processes of 2 users.
Jun 24 11:00:21 SERVIDOR rtkit-daemon[1330]: Successfully made thread 2279 of process 2266 (n/a) owned by '1000' RT at priority 5.
Jun 24 11:00:21 SERVIDOR rtkit-daemon[1330]: Supervising 5 threads of 2 processes of 2 users.
Jun 24 11:00:21 SERVIDOR rtkit-daemon[1330]: Successfully made thread 2281 of process 2266 (n/a) owned by '1000' RT at priority 5.
Jun 24 11:00:21 SERVIDOR rtkit-daemon[1330]: Supervising 6 threads of 2 processes of 2 users.
Jun 24 11:00:22 SERVIDOR rtkit-daemon[1330]: Successfully made thread 2288 of process 2288 (n/a) owned by '1000' high priority at nice level -11.
Jun 24 11:00:22 SERVIDOR rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 2 users.
Jun 24 11:00:22 SERVIDOR pulseaudio[2288]: pid.c: Daemon already running.
Jun 24 11:00:23 SERVIDOR kernel: [10088.970168] i2c i2c-0: sendbytes: NAK bailout.
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: snd_pcm_avail_delay() returned strange values: delay 0 is less than avail 8.
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: snd_pcm_dump():
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: Soft volume PCM
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: Control: PCM Playback Volume
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: min_dB: -51
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: max_dB: 0
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: resolution: 256
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c: Its setup is:
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   stream       : CAPTURE
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   access       : MMAP_INTERLEAVED
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   format       : S16_LE
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   subformat    : STD
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   channels     : 2
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   rate         : 44100
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   exact rate   : 44100 (44100/1)
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   msbits       : 16
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   buffer_size  : 88192
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   period_size  : 44096
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   period_time  : 999909
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   tstamp_mode  : ENABLE
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   period_step  : 1
Jun 24 11:00:23 SERVIDOR pulseaudio[2266]: alsa-util.c:   avail_min    : 87310


[Arthur Bernardes]

Precisamos entender como está suas interfaces de rede.

Execute os comandos a seguir em terminal e cole os resultados aqui.

sudo lshw -C network
ifconfig -a
iwconfig
nm-tool
rfkill list wifi
dmesg | tail

Obs: Use a tag "code" , fica bem mais fácil para visualizar as respostas dos comandos.

Código Selecionar Expandir

Veja.

[leandrorodrigosantos]

Arthur segue o resultado dos comandos.

Código Selecionar Expandir


administrador@SERVIDOR:~$ sudo lshw -C network
[sudo] password for administrador:
  *-network               
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 02
       serial: 90:e6:ba:13:2b:2f
       size: 100MB/s
       capacity: 1GB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=192.168.0.100 latency=0 link=yes multicast=yes port=MII speed=100MB/s
       resources: irq:42 ioport:e800(size=256) memory:febff000-febfffff memory:fdff0000-fdffffff memory:febc0000-febdffff


administrador@SERVIDOR:~$ ifconfig -a
eth0      Link encap:Ethernet  Endereço de HW 90:e6:ba:13:2b:2f 
          inet end.: 192.168.0.100  Bcast:192.168.0.255  Masc:255.255.255.0
          endereço inet6: fe80::92e6:baff:fe13:2b2f/64 Escopo:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Métrica:1
          pacotes RX:430095 erros:0 descartados:0 excesso:0 quadro:0
          Pacotes TX:444242 erros:0 descartados:0 excesso:0 portadora:0
          colisões:0 txqueuelen:1000
          RX bytes:35641417 (35.6 MB) TX bytes:510873038 (510.8 MB)
          IRQ:42 Endereço de E/S:0x6000

lo        Link encap:Loopback Local 
          inet end.: 127.0.0.1  Masc:255.0.0.0
          endereço inet6: ::1/128 Escopo:Máquina
          UP LOOPBACK RUNNING  MTU:16436  Métrica:1
          pacotes RX:22 erros:0 descartados:0 excesso:0 quadro:0
          Pacotes TX:22 erros:0 descartados:0 excesso:0 portadora:0
          colisões:0 txqueuelen:0
          RX bytes:1300 (1.3 KB) TX bytes:1300 (1.3 KB)

administrador@SERVIDOR:~$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.


administrador@SERVIDOR:~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth0  [Auto eth0] ----------------------------------------------------
  Type:              Wired
  Driver:            r8169
  State:             connected
  Default:           yes
  HW Address:        90:E6:BA:13:2B:2F

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         on

  IPv4 Settings:
    Address:         192.168.0.100
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.0.1

    DNS:             8.8.8.8
    DNS:             8.8.4.4


administrador@SERVIDOR:~$ rfkill list wifi
administrador@SERVIDOR:~$ dmesg | tail
[16481.880760] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[16481.880762] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[16481.880764] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[16481.880766]
[16481.983270] i2c i2c-0: sendbytes: NAK bailout.
[16482.098318] i2c i2c-0: sendbytes: NAK bailout.
[16482.218831] i2c i2c-0: sendbytes: NAK bailout.
[16482.330547] i2c i2c-0: sendbytes: NAK bailout.
[16484.910226] i2c i2c-0: sendbytes: NAK bailout.
[16487.498059] i2c i2c-0: sendbytes: NAK bailout.


[Arthur Bernardes]

Estou percebendo que seu Servidor recebe o endereço IP via DHCP.

Verifique se não há nenhuma máquina na rede que cause essa queda, verifique cabos de rede também.

Afinal, qual versão do Ubuntu está usando?

[leandrorodrigosantos]

Eu configurei o ip na placa dele direto, como faço para ele não receber o dhcp da rede?
Ja verifiquei cabos, ja troquei switchs e roteadores, ja instalei umq placa de rede nova e não resolveu ai eu removi ela.
Estou usando o ubuntu 10.04.

[Arthur Bernardes]

Amigo, essa já é uma versão antiga, tente instalar o Ubuntu 12.04 nesse servidor, dê preferência a versão Server, se já domina.

[leandrorodrigosantos]

Será que ela pode estar dando problema? Ele foi usando durante 2 anos sem ter nenhum tipo de problema.

[Arthur Bernardes]

Devemos ir eliminando as hipóteses para chegar no problema final.

Você definiu como os endereços IP? Através do NM ou pelo "interfaces"?

Tem algum Firewall ativo?

Servidor de quê?

[leandrorodrigosantos]

Pelas Interfaces, fui em preferencia e fui nas configurações.
Firewall no linux?? Não coloquei nenhum que eu me lembre.
É um servidor de aplicação, é um programa feito em delphi, ele é um servidor dedicado, fica tudo parado nele, as maquinas windows acessam a aplicação, tem em média umas 10 maquinas acessando ele.
Desculpe a versão que é usada é a 10.10

[Arthur Bernardes]

Uma versão não-LTS num servidor.

Recomendo fortemente que use a versão 12.04 LTS Server, se já domina o campo, se não, instale o Ubuntu 12.04 mesmo.

[NOOB Saibot]

Só uma sugestão, antes de atualizar, certifique-se que a aplicação em Delphi funcionará
perfeitamente na nova versão do Ubuntu
Se essa aplicação faz acesso a um banco de dados, backup das tabelas, etc.

Quando se trata de um servidor de uma empresa, todo cuidado é pouco

[leandrorodrigosantos]

Só uma sugestão, antes de atualizar, certifique-se que a aplicação em Delphi funcionará
perfeitamente na nova versão do Ubuntu
Se essa aplicação faz acesso a um banco de dados, backup das tabelas, etc.

Quando se trata de um servidor de uma empresa, todo cuidado é pouco

Então NOOB Saibot, ele funciona como um servidor de arquivos na verdade, o programa delphi e o banco firebird ficam no linux, as maquinas windows acessam via atalho a aplicação, o linux fica quietinho.
Foi eu que coloquei esse linux la, tem uns 2 anos, agora que começou esse problema, apenas o linux sai da rede, as outras maquinas continuam.
A versão 12.04, qual é a recomendada? Porque eu vi 2, a 12.04.2 LTS (Precise Pangolin) e uma outra 12.04.2 LTS.

[Arthur Bernardes]

A versão 12.04.2 é um Service Pack, ela vem com Kernel 3.5

Pode instalar sem problemas.