On 5 July 2015 at 16:19, Beco <r...@beco.cc> wrote:
> Hi guys,
>
> I need some help regarding this problem.
>
> Yesterday I upgraded from Wheezy to Jessie. Today I got an email saying
> the user could not create a "tmp" file to do anything.
>
> I checked the filesystem with:
>
> ------------
> # df -h
> Filesystem Size Used Avail Use% Mounted on
>
> /dev/sda1 46G 46G 0 100% /
>
> udev 10M 0 10M 0% /dev
>
> tmpfs 789M 82M 708M 11% /run
>
> tmpfs 2.0G 4.0K 2.0G 1% /dev/shm
>
> tmpfs 5.0M 4.0K 5.0M 1% /run/lock
>
> tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
>
> /dev/sda3 864G 4.0G 816G 1% /home
>
> tmpfs 395M 0 395M 0% /run/user/1000
>
> tmpfs 395M 0 395M 0% /run/user/1340
> tmpfs 395M 0 395M 0% /run/user/1328
> tmpfs 395M 0 395M 0% /run/user/1360
> ------------
>
> Also tried to find what was using such huge space with:
>
>
> ------------
> # find / -xdev -type f -size +200M -exec ls -lh {} \;
> -rw-r----- 1 root adm 4.2G Jul 5 16:05 /var/log/messages
> -rw-r----- 1 root adm 5.6G Jul 5 16:05 /var/log/kern.log
> -rw-r----- 1 root adm 16G Jul 5 16:05 /var/log/syslog
> -rw-r----- 1 root adm 9.6G Jul 5 16:05 /var/log/daemon.log
> ------------
>
> I'm not convinced that only 16G of syslog is my whole problem. But Id
> start with that, if I can make the system usable again. So I check the log
> just to see, over and over, this messages:
>
> ------------
> 1 Jul 5 15:35:58 beco kernel: [66691.859352] ieee80211 phy0:
> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
> 2 Jul 5 15:35:58 beco kernel: [66691.859358] rt2800pci 0000:03:00.0:
> firmware: failed to load rt2860.bin (-2)
> 3 Jul 5 15:35:58 beco kernel: [66691.859359] rt2800pci 0000:03:00.0:
> Direct firmware load failed with error -2
> 4 Jul 5 15:35:58 beco kernel: [66691.859361] rt2800pci 0000:03:00.0:
> Falling back to user helper
> ...
>
> Jul 5 15:35:58 beco systemd-udevd[16867]: failed to execute
> '/lib/udev/socket:@/org/freedesktop/hal/udev_event'
> 'socket:@/org/freedesktop/hal/u
> dev_event': No such file or directory
> ...
> 24 Jul 5 15:35:58 beco wpa_supplicant[2357]: Could not set interface
> wlan0 flags (UP): Cannot allocate memory
> 25 Jul 5 15:35:58 beco wpa_supplicant[2357]: nl80211: Could not set
> interface 'wlan0' UP
> 26 Jul 5 15:35:58 beco wpa_supplicant[2357]: Could not set interface
> wlan0 flags (UP): Cannot allocate memory
> 27 Jul 5 15:35:58 beco wpa_supplicant[2357]: WEXT: Could not set
> interface 'wlan0' UP
> 28 Jul 5 15:35:58 beco wpa_supplicant[2357]: wlan0: Failed to
> initialize driver interface
> ...
> 30 Jul 5 15:35:58 beco NetworkManager[1812]: <error> [1436121358.001526]
> [supplicant-manager/nm-supplicant-interface.c:856] interface_add_cb(): (w
> lan0): error adding interface: wpa_supplicant couldn't grab this
> interface.
> 31 Jul 5 15:35:58 beco NetworkManager[1812]: <info> (wlan0): supplicant
> interface state: starting -> down
> 32 Jul 5 15:35:58 beco systemd-udevd[16870]: failed to execute
> '/lib/udev/socket:@/org/freedesktop/hal/udev_event'
> 'socket:@/org/freedesktop/hal/u
> dev_event': No such file or directory
> ...
> ------------
>
>
Ok, I run:
# apt-get remove wpasupplicant
I could break the "while" loop deleting syslog. It stoped spamming. Looks
like all messages was linked to it.
I don't know very much wpasupplicant. Ill this software be needed in the
near future?
Im afraid the system is working only now, and will be unreachable next
reboot.
------
To keep up with Santiago and Joe:
Santiago, thanks for the file. I do prefer not use if not necessary,
though. Lets see how things goes.
Joe, I'm runing this server via ssh. And I cannot turn it off, as there are
users online now.
I'll read your other suggestions more easily now that its "kind of "
working.
Thanks.
Beco.
--
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
