On 5 July 2015 at 20:29, Pascal Hambourg <pas...@plouf.fr.eu.org> wrote:
> Beco a écrit : > > > > Just to be sure: this server doesn't have (nor need) wireless interface. > > It has one. If you don't need it, you can disable the kernel module > autoloading by creating a file /etc/modprobe.d/blacklist-rt2800pci.conf > containing the following line : > > blacklist rt2800pci > > > Hi guys, I'll report actions in order now: - Upgrade from wheezy to jessie yesterday nigh. No problems during upgrade. - Today email from users telling system is not usable (but online and you could login) - After inquiring the logs, I saw syslog with what seems to be 3 problems, spamming the logs * networkmanager reporting wpa_supplicant * wpa_supplicant trying to setup wlan0 * kernel attempting to load rt2860.bin Status: system could not create any files. I could not apt-get install lshw, for instance. Users (students) could not run "gcc" to compile, due to lack of resources. System is remote, using "ssh" to solve problems. 1st action: a loop created with a bash command: # while true; do echo clean syslog; cat /dev/null > syslog ; sleep 10; done This would allow me to see whats happening. I could install lshw. The Wanderer asked for --------- #ifconfig -a eth0 bla bla bla <cut> lo bla bla bla <cut> wlan0 Link encap:Ethernet HWaddr 00:0a:0c:49:83:9b BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) --------- So, yes, it has wlan0. Also this command: --------- # lshw -C network *-network description: Ethernet interface product: 82579V Gigabit Network Connection vendor: Intel Corporation physical id: 19 bus info: pci@0000:00:19.0 logical name: eth0 version: 05 serial: 38:60:77:93:3a:1c size: 100Mbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k duplex=full firmware=0.13-4 ip=10.0.3.2 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:42 memory:f7200000-f721ffff memory:f7228000-f7228fff ioport:f040(size=32) *-network DISABLED description: Wireless interface product: RT3062 Wireless 802.11n 2T/2R vendor: Ralink corp. physical id: 0 bus info: pci@0000:03:00.0 logical name: wlan0 version: 00 serial: 00:0c:0a:49:83:9b width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rt2800pci driverversion=3.16.0-4-amd64 firmware=N/A latency=32 link=no maxlatency=4 mingnt=2 multicast=yes wireless=IEEE 802.11bgn resources: irq:16 memory:f7100000-f710ffff --------- 2nd action: # apt-get remove wpasupplicant System stabilized. I let all my ssh sessions on, and went to grab a bite. (Not lunched today yet). ----------------- OH BOY SECTION!! Just to come back and see all sessions kicked out. System not accessible anymore. Ping was ok. But no connection. Ping was problably ok because a server before mine should be answering the pings. Any ssh give me time out! Oh, boy! So the worst came true: I needed physical access to a server in my room, sunday night. There I went. Drove there, all dark and empty. Sysadmins life. There I saw the Network-Manager icon (KDE) was not active. Well, I downloaded the wpasupplicant package using my notebook, passed via pendrive to the server, reinstalled it. 3rd action: Nothing working. Tried ifup, not recognized. Then I remember I had commented some lines before, in /etc/network/interfaces. I dis-commented this line: --- iface eth0 inet dhcp --- And #ifup eth0 All running. I needed to get out there, because the gate's keeper was not happy. Back to my home, now I think the server is running "ok". I need to figure out what is wrong, and if there is a better solution. Because I can't make sense of what just happened as reported above. In my understanding, I was supposed to let Network-manager run the game. Not wpa_supplicant, and not "ifup". Now I don't know where is Network-manager. wpa_supplicant was gone, and back again. System is stable. And "ifup" is configured. Last action: (Pascal's suggestion) I added the referred firmware to the blacklist Just in case So, where I am now after such modifications?! Tomorrow I'll have full access to the server, and hopefully no gatekeeper in my back, so I'll have some time. Should I research for Network-Manager? Comment back this "ifup" ? I'm kind of lost here. Thanks! Beco. PS. Kernel log was also full with: Jul 5 17:21:47 beco kernel: [73049.254557] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' Jul 5 17:21:47 beco kernel: [73049.254562] rt2800pci 0000:03:00.0: firmware: failed to load rt2860.bin (-2) Jul 5 17:21:47 beco kernel: [73049.254564] rt2800pci 0000:03:00.0: Direct firmware load failed with error -2 Jul 5 17:21:47 beco kernel: [73049.254565] rt2800pci 0000:03:00.0: Falling back to user helper Messages: Jul 4 21:06:23 beco kernel: [ 33.137376] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' Jul 4 21:06:23 beco kernel: [ 33.137448] rt2800pci 0000:03:00.0: Direct firmware load failed with error -2 Jul 4 21:06:23 beco kernel: [ 33.137449] rt2800pci 0000:03:00.0: Falling back to user helper 5 GB of this stuff. Daemon.log 31471 Jul 3 07:00:24 beco dhclient: send_packet: Operation not permitted 31472 Jul 3 07:00:44 beco dhclient: DHCPREQUEST on eth0 to 10.0.0.1 port 67 31473 Jul 3 07:00:44 beco dhclient: send_packet: Operation not permitted 31474 Jul 3 07:00:53 beco dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 31475 Jul 3 07:00:53 beco dhclient: DHCPACK from 10.0.0.1 31476 Jul 3 07:00:53 beco dhclient: bound to 10.0.3.2 -- renewal in 3534 seconds. 31477 Jul 3 07:59:47 beco dhclient: DHCPREQUEST on eth0 to 10.0.0.1 port 67 15 GB of this madness I wonder if this program really need to report such failure so many times and in 4 logs simultaneously. I know redundancy is good, but : 16GB syslog + 5 GB kern.log + 5 GB messages + 15 GB daemon.log = 41 GB! Thats a way to say: Hey! I can't install this firmware! (I'm afraid to open root's email and find there a message about it also!) I was walking down the street to grab a bite and a stranger yelled at me: Hey! Install firmware rt2860.bin! (True fact! Believe me!) -- Dr Beco A.I. researcher "I know you think you understand what you thought I said but I'm not sure you realize that what you heard is not what I meant" -- Alan Greenspan GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A Creation date: pgp.mit.edu ID as of 2014-11-09