Network issues after weeks of usage

mrgnz

I am using a raspberry pi B+ and a hifiberry DAC. I have set up runeaudio on my SD card some weeks ago and used it since.
Then the other day, I wanted to add music from spotify to the queue. Nothing happened. Then Playback stopped, the playlist was empfty and more such issues occured. Somewhen I wasnt able to reach the interface via browser anymore. I was though able to ping it and log into it via ssh.
Netctl settings seemed untouched, nothing odd to see. So I rebooted the system. Since then, it will not appear on the network anymore.

I attached a keyboard and a monitor and was able to log in. systemctl and journalctl did not provide me any information I was able to compute. Anyhow, dmesg showed me some infos saying that the system wasnt able to up the eth0 device (or brm<foo>).

I am not that good in debugging linux systems and stuff connected to hardware isn't my area of expertise.
I tried to fire up eth0 via netctl and via systemctl which was using netctl. It worked once, but only for a short while and since then nothing i tried worked anymore.
SD card seems okay, I mounted it on my desktop. Beside the hifiberry, there is a usb hdd connected and network comes via rj45 cable.

btw, I used the search functionality but didnt find a suiting issue. Maybe you can prove me wrong.
Elsewise, do you have any ideas for me?

Edit: I can provide detailed information later after work.

mrgnz

There we go.
I managed to get the network going by doing

netctl restart eth0

However, it is not persistent and I have to do it after each reboot.

Here is the debug output:

http://pastebin.com/mncXuncv

mrgnz

~~~

hondagx35

Hi mrgnz,

please edit your post and provide your debug info via Pastebin.

How to collect DEBUG info

You can try to use the newest development version of RuneAudio.
see here

Frank

adr3nal1n

Had the same issue using a static IP address.

You need to do this to make it persistent.

#netctl enable eth0

Hope this helps.

mrgnz

Thanks
I simply forgot about pastebin.

Your hint worked.
How can I check if network auto-start is enabled?

mrgnz

This is what I get when I try to check if it is enabled.

netctl is-enabled eth0
Failed to get unit file state for netctl@eth0.service: No such file or directory

adr3nal1n wroteHad the same issue using a static IP address.

You need to do this to make it persistent.

#netctl enable eth0

Hope this helps.

adr3nal1n

Strange,

I had the same issue so i logged in via local console and did #netctl start eth0 and then did #netctl enable eth0 and it created the necessary symlinks in /etc/systemd/system/ and /etc/systemd/system/multi-user.target.wants/ and then rebooted and all good.

mrgnz

I have now switched to the nightly network management as indicated above by hondagx35 and ist seems to work. network was now persitent after one reboot. I will try to reboot again tomorrow.

If it will not persist, I will try your solution. Thanks for the help!

Seems it has been successful.

mrgnz

I read in a nother post, that it is now possible to use "update RuneUI" funtion in the dev section and it will automatically get the latest dev version of the UI? including the code connected to network issues?

ACX

mrgnz wroteI read in a nother post, that it is now possible to use "update RuneUI" funtion in the dev section and it will automatically get the latest dev version of the UI? including the code connected to network issues?

You will get updates from the dev branch only if you set it as source, as described here.