[SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

danishraza · 2014-03-20 14:20:59

Hello, I'm really not very familiar with networking on Arch, but i tired every solution that i can found on google i guess ...

I discovered wifi-menu in arch. So, That worked fine for quite a while, until the other day when I shutdown my laptop while connected to my home network. Now connecting to any other network or back to home's network via wifi-menu returns:

Job for netctl@wlp12s0\x2dMeRcaN.service failed. See 'systemctl status netctl@wlp12s0\x2dMeRcaN.service' and 'journalctl -xn' for details.

Appropriately, systemctl status and journalctl follow:

netctl@wlp12s0x2dMeRcaN.service - Networking for netctl profile wlp12s0x2dMeRcaN
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Thu 2014-03-20 16:04:11 EET; 20min ago
     Docs: man:netctl.profile(5)
  Process: 4791 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 4791 (code=exited, status=1/FAILURE)

Mar 20 16:04:11 boss systemd[1]: Starting Networking for netctl profile wlp12s.....
Mar 20 16:04:11 boss network[4791]: Profile 'wlp12s0x2dMeRcaN' does not exist ...le
Mar 20 16:04:11 boss systemd[1]: netctl@wlp12s0x2dMeRcaN.service: main process...RE
Mar 20 16:04:11 boss systemd[1]: Failed to start Networking for netctl profile...N.
Mar 20 16:04:11 boss systemd[1]: Unit netctl@wlp12s0x2dMeRcaN.service entered ...e.
Hint: Some lines were ellipsized, use -l to show in full.

journalctl -xn
netctl@wlp12s0x2dMeRcaN.service - Networking for netctl profile wlp12s0x2dMeRcaN
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Thu 2014-03-20 16:04:11 EET; 20min ago
     Docs: man:netctl.profile(5)
  Process: 4791 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 4791 (code=exited, status=1/FAILURE)

Mar 20 16:04:11 boss systemd[1]: Starting Networking for netctl profile wlp12s.....
Mar 20 16:04:11 boss network[4791]: Profile 'wlp12s0x2dMeRcaN' does not exist ...le
Mar 20 16:04:11 boss systemd[1]: netctl@wlp12s0x2dMeRcaN.service: main process...RE
Mar 20 16:04:11 boss systemd[1]: Failed to start Networking for netctl profile...N.
Mar 20 16:04:11 boss systemd[1]: Unit netctl@wlp12s0x2dMeRcaN.service entered ...e.
Hint: Some lines were ellipsized, use -l to show in full.

NOW!! I'm not really sure where to go from here. I see that for some reason dhcp is failing. Any thoughts/help appreciated. Let me know if I need to post more details.It's Been really more than a week i am totally abandoned!

Last edited by danishraza (2014-04-05 06:00:32)

Raynman · 2014-03-20 15:37:36

danishraza wrote:

Job for netctl@wlp12s0\x2dMeRcaN.service failed. See 'systemctl status netctl@wlp12s0\x2dMeRcaN.service' and 'journalctl -xn' for details.

When you run that command exactly as-is, your shell eats the backslash. To pass the escaped hyphen to systemctl, you need to escape the backslash or quote the service name. When you do it right, you'll see

netctl@wlp12s0\x2dMeRcaN.service - Networking for netctl profile wlp12s0-MeRcaN

Normally, this would result in a status of 'inactive (dead)' without any interesting info because you got the name wrong, but in your case, it seems something actually tried to start the service with 'x2d' instead of a hyphen in the name. Did you do this manually? Otherwise it might be a bug in wifi-menu. I don't know where you see dhcp failing, but that journal entry clearly says "Profile 'wlp12s0x2dMeRcaN' does not exist".

Inxsible · 2014-03-20 17:17:08

that's why you shouldn't use hyphens in the profile names as is mentioned in the wiki.

Also, danishraza, welcome to the forums. Please use code tags when posting snippets. I've added them for you this time. Please take some time to go through the forum rules as well.

haaja · 2014-03-20 20:20:38

Inxsible wrote:

that's why you shouldn't use hyphens in the profile names as is mentioned in the wiki.

I didn't find this particular mention from the wiki. Nevertheless if hyphens are known to cause problems with profile names, I find it odd that the default profile name suggested by wifi-menu contains a hyphen (<device>-<SSID>).

Inxsible · 2014-03-20 21:53:54

There was an issue that even though the default examples contained hyphens, it used to parse it weirdly. I can't find it in the netctl wiki anymore, but there was a mention. Maybe it was in some other page. I will try to locate it.

danishraza · 2014-03-21 13:23:58

Hello To Every One and @Inxsible sorry i was not so conscious at that time for code blocking sorry for that but Guys,
Problem is not still solved i am very sorry. I don't really understand escapting backslash method. When i was using wifi-menu, all i was doing is just selecting network to use and wifi-menu was creating netowork profile and doing reset job automatically but what went wrong now. I am not sure but i am assuming that my dhcpcd is running my wifi service that is causing my archy not to connect to any network. i run sudo systemctl and find red lines with that

 dhcpcd@wlp12s0.service      loaded failed failed    dhcpcd on wlp12s0

netctl@w...2dMeRcaN.service loaded failed failed    Automatically generated prof

so, why my wifi is not working even it was okay before, Sorry if you guys find me frustrated!

WonderWoofy · 2014-03-21 15:22:32

Why do you have dhcpcd@.service enabled at all? You should not have more than one service trying to handle your networking.

Since Arch is so DIY focused, the install scripts don't automatically enable services upon installation and thus allow you to not only have more than one package that can potentially control the networking, but also allow you to shoot yourself in the foot and enable conflicting networking services if you please.

The issue with the escapes in the profile names seemed to be related to the fact that in systemd unit files, those slashes can have a very special meaning. If you look at 'systemctl --type=mount' you will see that all your entries from the fstab are converted to systemd.mount files. Their names are their mounpoint paths where the forward slashes are replaced by dashes/hyphens. ("/" replaced by "-"). This should be okay now, but if you want to just make sure, you can navigate to /etc/netctl and change your profile names to ones that don't have the leading "wlp12s0-".

singinsailor · 2014-03-21 18:01:38

hi guys,
i have a similar problem with my dhcp client. I have my network controlled just by dhcpcd since i ran into issues with gnome 3.10 after disabling networkmanager last time. I had to make a fresh install for that issue, so this time i just used dhcpcd.
I have clean wpa_supplicant.conf file where this line had to be added since the last update:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel

so now dhcpcd works on starting it manually, but the systemd service fails on boot. The only point i could guess is systemd asking for networkmanager on boot sequence now. Which will sure not be enabled on my machine.
Now i hope to find a way not to have it start manually every time, making the systemd service work again ( i could also use some kind of autostart function, but it is not elegant)
Maybe anyhow removing the call for networkmanager could help?
So maybe my reply could also help to allocate the problem a little bit, (if you need some output please dont hesitate to ask me for that, but i dont know every that could be important to that...)
thx, j

paretech · 2014-04-04 23:22:01

@WonderWoofy I had a similar problem to the OP after performing a pacman -Syu, your suggestion led me to a solution.

I disabled the dhcpcd service in systemctl and netctl wifi-menu works like it did a month ago.

Thank you,
-Matt

danishraza · 2014-04-05 05:37:55

Okay guys its been weeks, the solution has found and it's really awkward anyways, what i did is that i delete all of connected networks profile from here

/etc/netctl

and what else, time to delete the shitty enable services from systemd so, i navigate to

/etc/systemd/system/multi-user.target.wants

and delete my services for network and as i was having different network services enable for eht0 and wlan0. so, i delete a one!
Feeling great to solve this shit!! although sometime problem occurs again about that job for bla bla bla is failed! but don't panic repeat the process and even it says again then its router fault and your wirless is not configured (check with your friends windows if you don't believe it)

Last edited by danishraza (2014-04-05 06:02:20)

WonderWoofy · 2014-04-05 06:21:08

@danishraza, I think you should get a better handle on your network setup. In particular, I think it would be ideal if you read up a bit on how to use the 'netctl' command as well as 'systemctl' directly. These are both able to tell you which services/profiles are enabled and which aren't and can both be used to stop the unwanted services.

danishraza · 2014-04-05 06:42:26

@WonderWoofy you are right brother! i did mistakes in the start as i didn't use arch before and it was first experience so, that is why i messed up systemd or so. i am learning both of them so, i will learn about them in future with the time. thanks

singinsailor · 2014-04-09 22:04:04

looks like wpa-supplicant isnt called by dhcpcd on first try. The second starts everything as normal. Undependently whether it is user or systemd-started

Last edited by singinsailor (2014-04-09 22:05:49)

Arch Linux

#1 2014-03-20 14:20:59

[SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#2 2014-03-20 15:37:36

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#3 2014-03-20 17:17:08

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#4 2014-03-20 20:20:38

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#5 2014-03-20 21:53:54

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#6 2014-03-21 13:23:58

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#7 2014-03-21 15:22:32

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#8 2014-03-21 18:01:38

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#9 2014-04-04 23:22:01

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#10 2014-04-05 05:37:55

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#11 2014-04-05 06:21:08

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#12 2014-04-05 06:42:26

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

#13 2014-04-09 22:04:04

Re: [SOLVED] Job for netctl@wlp12s0\x2dMeRcaN.service failed.

Board footer