You are not logged in.
Pages: 1
Hello.
For a reason unknown to me, netctl-auto always fails at boot. I read in the wiki, that it may be caused by errors in the profile files, but I am convinced that it's not the case: I am able to start them manually using 'netctl start'.
This is what I get from 'systemctl status':
netctl-auto@wlp3s0.service -> '/org/freedesktop/systemd1/unit/netctl_2dauto_40wlp3s0_2eservice'
netctl-auto@wlp3s0.service - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled)
Active: failed (Result: exit-code) since St 2013-05-29 09:48:58 CEST; 9min ago
Docs: man:netctl.special(7)
Process: 191 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=1/FAILURE)
Well, that's not very verbose, isn't it? Please can you tell me, where can I get more detailed info why is the error happening? ('journalctl -xn' is not of much help either.)
Offline
I also need to issue:
sudo netctl start ethernet-static after boot to have access to the internet.
I'm not sure about the usage of netctl-auto.
I'm not great at systemd, but I have carefully followed the instructions on netctl and beginner pages.
Last edited by doru001 (2013-05-30 13:23:42)
Offline
Probably also worth mentioning: All my profiles are generated by wifi-menu and are enabled (by 'netctl enable'.) netctl-auto is enables as a systemd service.
Offline
They should not be enabled....
Read the multiple profiles section and disable all profiles.
https://wiki.archlinux.org/index.php/Netctl
Last edited by phil (2013-05-30 09:05:48)
Offline
Yes, this was the problem. I found out myself now too...
Still, I don't understant why there is nothing uselful in the 'systemctl status'. There aren't any other useful logs, right?
Offline
Yes, this was the problem. I found out myself now too...
Still, I don't understant why there is nothing uselful in the 'systemctl status'. There aren't any other useful logs, right?
kamahl, do this to find raw journal logging. The "status" is kind of a shortened version only including the most interesting highlights.
# journalctl [-b] -u netctl@<profile-name>
or
# journalctl [-b] -u netctl-auto@<interface>i"m not gauranteeing that you will find anything more interesting than what "systemctl status" gave you. But it might.
If you are looking for all netctl information regardless of what profile was being used, or whether or not your were using netctl-auto or netctl-ifplugd, then you can simply do something like:
# journalctl [-b] --no-pager | grep netctl Maybe there is a better, more "native journalctl" way to do it, but that is how I have done it when I have '@' services that I want to find all variants of in the journal. The "-b" is optional, as its presence will make it so that only the current boot is shown. I have marked it as being run as root (#) because unless you are in the "systemd-journal" group, you do not have access to the full journal, only your user's journal.
Last edited by WonderWoofy (2013-05-31 15:05:40)
Offline
Pages: 1