Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] start job running for LSB: Raise network interface

Ask for help with issues regarding the Installations of the Debian O/S.
Message
Author
hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#31 Post by hughparker1 »

Head_on_a_Stick wrote: Unfortunately, the Debian implementation of systemd-networkd does *not* support wireless connections without further hacks.

If you wish to use systemd-networkd rather than the custom unit file I have posted above, see this guide:
https://forums.bunsenlabs.org/viewtopic.php?id=546
Thanks for your clear step by step instructions. I wasn't looking to use systemd-networkd specifically (just anything related to systemd), systemd-networkd was just one to the hits on google.

I will follow your instructions and let you know how I get on. Thanks once again for your feedback.

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#32 Post by hughparker1 »

before I make the changes I have a couple of questions...
Head_on_a_Stick wrote:First, generate a wpa_supplicant configuration file for your access point:
# wpa_passphrase $SSID $PASSWORD >> /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
Replace $SSID with the name of your access point (use `iwlist scan wlan0|grep SSID` to find this)
I get this message when try to find my access point...

Code: Select all

hugh@hp530-Debian-8:~$ iwlist scan wlan0|grep SSID
bash: iwlist: command not found
hugh@hp530-Debian-8:~$ 
but I think I already know my ssid from /etc/network/interfaces , it's shown as wpa-ssid = TALKTALKA661B5

Q1. So I should use TALKTALKA661B5 ?
Head_on_a_Stick wrote:If your wireless interface is not called "wlan0"...
Q2. how do I confirm what my wireless interface is not called?

Q3. Do I need to use my network cable while performing these setup steps?
Head_on_a_Stick wrote:Then create a file at /etc/systemd/system/network-wireless@.service (as root!) with the following content
Q4. Is this best way to create this file ? ...

Code: Select all

$ su
$ cd /etc/systemd/system/
$ > network-wireless@.service
$ nano network-wireless@.service  # and enter text and save 
Head_on_a_Stick wrote:Then make sure that NetworkManager & WICD and all other networking .services are disabled.
Check all enabled .services with:
Code: Select all

Code: Select all

systemctl list-unit-files|grep enabled
here is the output for systemctl list-unit-files|grep enabled ....

Code: Select all

hugh@hp530-Debian-8:~$ systemctl list-unit-files|grep enabled
run-vmblock\x2dfuse.mount                  enabled 
acpid.path                                 enabled 
cups.path                                  enabled 
anacron-resume.service                     enabled 
anacron.service                            enabled 
atd.service                                enabled 
avahi-daemon.service                       enabled 
bluetooth.service                          enabled 
cron.service                               enabled 
cups-browsed.service                       enabled 
cups.service                               enabled 
dbus-org.bluez.service                     enabled 
dbus-org.freedesktop.Avahi.service         enabled 
dbus-org.freedesktop.ModemManager1.service enabled 
display-manager.service                    enabled 
getty@.service                             enabled 
hwclock-save.service                       enabled 
lightdm.service                            enabled 
live-config.service                        enabled 
ModemManager.service                       enabled 
open-vm-tools.service                      enabled 
rsyslog.service                            enabled 
ssh.service                                enabled 
sshd.service                               enabled 
syslog.service                             enabled 
acpid.socket                               enabled 
avahi-daemon.socket                        enabled 
cups.socket                                enabled 
uuidd.socket                               enabled 
remote-fs.target                           enabled 
hugh@hp530-Debian-8:~$ 
Q5. can you advise which service I should disable? I am not confident in picking the correct services.
Head_on_a_Stick wrote: List all interface names with `ip l`
Q6. I'm not sure what I should do here.

Sorry for all the questions but I just want to check I'm doing things correctly.

Thanks for your patience, you have been a great help to me so far.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#33 Post by Head_on_a_Stick »

hughparker1 wrote:I get this message when try to find my access point...

Code: Select all

hugh@hp530-Debian-8:~$ iwlist scan wlan0|grep SSID
bash: iwlist: command not found
hugh@hp530-Debian-8:~$ 
You need the wireless-tools package for that command ;)
but I think I already know my ssid from /etc/network/interfaces , it's shown as wpa-ssid = TALKTALKA661B5

Q1. So I should use TALKTALKA661B5 ?
Yes.
Q2. how do I confirm what my wireless interface is not called?
See "Q6"
Q3. Do I need to use my network cable while performing these setup steps?
No.
Q4. Is this best way to create this file ? ...

Code: Select all

$ su
$ cd /etc/systemd/system/
$ > network-wireless@.service
$ nano network-wireless@.service  # and enter text and save 
Yes, that would be fine.

I prefer vim though :D
here is the output for systemctl list-unit-files|grep enabled ....

Code: Select all

hugh@hp530-Debian-8:~$ systemctl list-unit-files|grep enabled
run-vmblock\x2dfuse.mount                  enabled 
acpid.path                                 enabled 
cups.path                                  enabled 
anacron-resume.service                     enabled 
anacron.service                            enabled 
atd.service                                enabled 
avahi-daemon.service                       enabled 
bluetooth.service                          enabled 
cron.service                               enabled 
cups-browsed.service                       enabled 
cups.service                               enabled 
dbus-org.bluez.service                     enabled 
dbus-org.freedesktop.Avahi.service         enabled 
dbus-org.freedesktop.ModemManager1.service enabled 
display-manager.service                    enabled 
getty@.service                             enabled 
hwclock-save.service                       enabled 
lightdm.service                            enabled 
live-config.service                        enabled 
ModemManager.service                       enabled 
open-vm-tools.service                      enabled 
rsyslog.service                            enabled 
ssh.service                                enabled 
sshd.service                               enabled 
syslog.service                             enabled 
acpid.socket                               enabled 
avahi-daemon.socket                        enabled 
cups.socket                                enabled 
uuidd.socket                               enabled 
remote-fs.target                           enabled 
hugh@hp530-Debian-8:~$ 
Q5. can you advise which service I should disable? I am not confident in picking the correct services.
Just the ModemManager.service:

Code: Select all

# systemctl disable ModemManager.service # NOTE: case-sensitive name!
As an aside, you do not appear to have NetworkManager.service enabled and this may be why your graphical desktop was not "remembering" your connection ;)
Head_on_a_Stick wrote: List all interface names with `ip l`
Q6. I'm not sure what I should do here.
Run this command in a terminal:

Code: Select all

ip l
It will then show all your networking interfaces, like this:

Code: Select all

empty@TheLab ~ % ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether f0:de:f1:46:a1:ac brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 00:24:d7:93:d2:08 brd ff:ff:ff:ff:ff:ff
In this example, the wireless interface is called "wlan0" so the configuration file should be left un-altered.
I just want to check I'm doing things correctly.
Very wise :)
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#34 Post by hughparker1 »

Thanks once again for your quick reply, I think I'm all set to make the changes...
Can I ask a couple more quick questions? .... you said in your reply
Head_on_a_Stick wrote: As an aside, you do not appear to have NetworkManager.service enabled and this may be why your graphical desktop was not "remembering" your connection
Q7.did you identify this because it was not listed in the output for 'systemctl list-unit-files|grep' ?

Q8. If so then how would I be able to enable this to see if it fixes having to manually connect to my wireless adapter each time I start the laptop?

NOTE: Even if this does fix this issue, I still think I would prefer to let systemd manage the connection instead, as you said it's *much* faster than /etc/network/interfaces and *much* lighter than NetworkManager or WICD. I like faster. So I will probably go ahead with the changes listed in your step-by-step as it's very clear now.

EDIT: this is the output of 'ip l'

Code: Select all

hugh@hp530-Debian-8:~$ ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:1b:38:31:59:95 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 00:1b:77:42:4a:87 brd ff:ff:ff:ff:ff:ff
hugh@hp530-Debian-8:~$

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#35 Post by Head_on_a_Stick »

hughparker1 wrote:
Head_on_a_Stick wrote: As an aside, you do not appear to have NetworkManager.service enabled and this may be why your graphical desktop was not "remembering" your connection
Q7.did you identify this because it was not listed in the output for 'systemctl list-unit-files|grep' ?
Yes, exactly so.
Q8. If so then how would I be able to enable this to see if it fixes having to manually connect to my wireless adapter each time I start the laptop?

Code: Select all

# systemctl enable NetworkManager
Please take some time to read systemctl(1) and try to understand the commands you are using.

To disable the custom unit file I posted above, use:

Code: Select all

# systemctl disable network-wireless@wlan0
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#36 Post by hughparker1 »

I tried to enable NetworkManager just to see if it made any difference, but got this message...

Code: Select all

hugh@hp530-Debian-8:~$ su
Password: 
root@hp530-Debian-8:/home/hugh# systemctl enable NetworkManager
Failed to execute operation: No such file or directory
root@hp530-Debian-8:/home/hugh# 
do I need to change directory first?

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#37 Post by Head_on_a_Stick »

No.

As I said, I don't use NetworkManager -- I know how to turn it off but that's about it :D

Perhaps you weren't even using it, IDK really.

You seemed to use "wicd" [sic] and NetworkManager interchangably so presumably you don't know how you're supposed to be connecting either, right?
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#38 Post by hughparker1 »

Head_on_a_Stick wrote:You seemed to use "wicd" [sic] and NetworkManager interchangably so presumably you don't know how you're supposed to be connecting either, right?
I just click on the icon in the system tray on bottom right and Wicd Network Manager pops up :D then I click connect button. I don't purposely go looking for it to be honest.

Never mind, I will go ahead with the change to let systemd manage the connection instead. Going for some lunch first, need some energy. I'll keep you posted and thanks again for your help.

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#39 Post by hughparker1 »

I have done the following setup steps...
generate a wpa_supplicant configuration file for your access point:

Code: Select all

$ su
$ wpa_passphrase TALKTALKA661B5 PASSWORD >> /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
$ cd /etc/wpa_supplicant/
$ ls			# good file is there
root@hp530-Debian-8:/etc/wpa_supplicant# cd ~
root@hp530-Debian-8:~# nano /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
file contents ...

Code: Select all

network={
        ssid="TALKTALKA661B5"
        #psk="PASSWORD"
        psk=66e5cf398fc4ffb270ebb17ab449aa9843e0939c6968324a965d84a67a00e378
} 
looks good?

Then create a file at /etc/systemd/system/network-wireless@.service (as root!) with the following content:

Code: Select all

$ su
$ cd /etc/systemd/system/
$ > network-wireless@.service
$ nano network-wireless@.service  # and enter text and save ## 
---------------------- begin text ----------------------

Code: Select all

[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

[Service]
Type=oneshot
RemainAfterExit=yes

ExecStart=/sbin/ip l set %i up
ExecStart=/sbin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant-%i.conf
ExecStart=/sbin/dhclient %i

ExecStop=/sbin/ip l set %i down

[Install]
WantedBy=multi-user.target 
Check all enabled .services with: systemctl list-unit-files|grep enabled
Disable any conflicting networking .services with: systemctl disable foo.service

in my case just disable the ModemManager.service:

Code: Select all

root@hp530-Debian-8:/etc/systemd/system# systemctl disable ModemManager.service
Removed symlink /etc/systemd/system/dbus-org.freedesktop.ModemManager1.service.
Removed symlink /etc/systemd/system/multi-user.target.wants/ModemManager.service.
root@hp530-Debian-8:/etc/systemd/system# 
Finally enable the custom unit file and reboot:

Code: Select all

root@hp530-Debian-8:/etc/systemd/system# systemctl enable network-wireless@wlan0.service
Created symlink from /etc/systemd/system/multi-user.target.wants/network-wireless@wlan0.service to /etc/systemd/system/network-wireless@.service.
root@hp530-Debian-8:/etc/systemd/system# 
reboot

after reboot,
I get following message briefly....

Code: Select all

[   7.533826] systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
[FAILED] Failed to start Wireless network connectivity (wlan0)
See 'systemctl status network-wireless@wlan0.service' for details
I am not connected to my wireless adapter, I didn't want to click on icon in system tray (which brings up Wicd, as I thought systemd would handle my connection.

any idea what I should do next?

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#40 Post by Head_on_a_Stick »

hughparker1 wrote:file contents ...

Code: Select all

network={
        ssid="TALKTALKA661B5"
        #psk="PASSWORD"
        psk=66e5cf398fc4ffb270ebb17ab449aa9843e0939c6968324a965d84a67a00e378
} 
looks good?
Yes, as long as your password is really "PASSWORD"
hughparker1 wrote:after reboot,
I get following message briefly....

Code: Select all

[   7.533826] systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
[FAILED] Failed to start Wireless network connectivity (wlan0)
See 'systemctl status network-wireless@wlan0.service' for details
[...]

any idea what I should do next?
Look at the output of the suggested command:

Code: Select all

systemctl status networkwireless@wlan0.service
Try this:

Code: Select all

# ip l set wlan0 down
# systemctl start network-wireless@wlan0
If it gives another "FAILED" message then post the output of:

Code: Select all

journalctl -xe
(the error message will suggest that you run this command, btw)
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#41 Post by hughparker1 »

thanks for your continued support, I just used "PASSWORD" for the post, but the correct password is there.

I'm just going for a late lunch, I'll come back in a couple of hours and run the commands you suggested. thanks again.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#42 Post by Head_on_a_Stick »

Remember: to get back to where you started, simply disable the custom unit and enable ModemManager again then reboot ;)

Use the list-unit-files option to double-check the status of the units.
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#43 Post by hughparker1 »

I was going to do the following...

step 1. Look at the output of the suggested command & post results here

Code: Select all

$ systemctl status networkwireless@wlan0.service
step 2. Run following two commands...

Code: Select all

$ ip l set wlan0 down

$ systemctl start network-wireless@wlan0
step 3. If above commands give "FAILED" message then post the output of following command...

Code: Select all

$ journalctl -xe	    #  error message in step 2 will suggest to run this command
Then I saw your later post...
Head_on_a_Stick wrote:Remember: to get back to where you started, simply disable the custom unit and enable ModemManager again then reboot ;)
step 4. Would this be the correct method to do this?

Code: Select all

$ systemctl disable network-wireless@wlan0	# disables the custom unit file ?

$ systemctl enable ModemManager.service 		# was previously disabled 
Question1: does this not reverse everything I've done previously? so we are going back to not using systemd to manage network connections?

Question2. Shall I do this before or after steps 1 to 3?
Head_on_a_Stick wrote:Use the list-unit-files option to double-check the status of the units.
step 6. I'm not sure how to do this step. can you advise the command I should use? Sorry, but I don't have great linux knowledge but I'm learning as I go.

Perhaps you could list out the sequence you wish me to run the above steps, thanks again for your input and advice. I do appreciate your patience with a linux novice like myself. And sorry for all the questions, I just want to do this in the correct way.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#44 Post by Head_on_a_Stick »

hughparker1 wrote:
Head_on_a_Stick wrote:Remember: to get back to where you started, simply disable the custom unit and enable ModemManager again then reboot ;)
step 4. Would this be the correct method to do this?

Code: Select all

$ systemctl disable network-wireless@wlan0	# disables the custom unit file ?

$ systemctl enable ModemManager.service 		# was previously disabled 
Question1: does this not reverse everything I've done previously? so we are going back to not using systemd to manage network connections?
Yes, I posted that in case you decided to change your mind.

Escape clauses are always good.
hughparker1 wrote:
Head_on_a_Stick wrote:Use the list-unit-files option to double-check the status of the units.
step 6. I'm not sure how to do this step. can you advise the command I should use?

Code: Select all

systemctl list-unit-files|grep enabled
This shows all enabled .services (and .targets & .sockets), "enabled" means "will start on boot automatically".

I have just this minute installed a fresh jessie system and converted from NetworkManager to this custom unit file and my output is now:

Code: Select all

empty@TheLab ~ % systemctl list-unit-files|grep enabled
getty@.service                         enabled 
hwclock-save.service                   enabled 
lm-sensors.service                     enabled 
network-wireless@.service              enabled 
uuidd.socket                           enabled 
default.target                         enabled 
multi-user.target                      enabled 
This is a working set up ;)

It is quick:

Code: Select all

empty@TheLab ~ % systemd-analyze critical-chain
[...]      └─network-wireless@wlan0.service @818ms +392ms
:D

One final thing: you will need to add some nameservers to the file at /etc/resolv.conf

Make the file look like this:

Code: Select all

nameserver 8.8.8.8
nameserver 8.8.4.4
Those are Google's nameservers, you can use your router IP instead if you prefer (this is what NetworkManager does).
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#45 Post by hughparker1 »

Thanks for the escape clause, I will persevere with trying to get systemd to manage my network connections for the time being since it seems to be faster and lighter.

step 1. Look at the output of the suggested command & post results here

Code: Select all

hugh@hp530-Debian-8:~$ systemctl status networkwireless@wlan0.service
● networkwireless@wlan0.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
hugh@hp530-Debian-8:~$ 
step 2. Run following two commands...

Code: Select all

hugh@hp530-Debian-8:~$ ip l set wlan0 down
RTNETLINK answers: Operation not permitted
hugh@hp530-Debian-8:~$  

hugh@hp530-Debian-8:~$ su
Password: 
root@hp530-Debian-8:/home/hugh# ip l set wlan0 down
root@hp530-Debian-8:/home/hugh# 

root@hp530-Debian-8:/home/hugh# systemctl start network-wireless@wlan0
Job for network-wireless@wlan0.service failed. See 'systemctl status network-wireless@wlan0.service' and 'journalctl -xn' for details.
root@hp530-Debian-8:/home/hugh# 
step 3. If above commands give "FAILED" message then post the output of journalctl -xe

Code: Select all

root@hp530-Debian-8:/home/hugh# journalctl -xe
Feb 14 21:39:25 hp530-Debian-8 kernel: scsi4 : usb-storage 2-1:1.0
Feb 14 21:39:25 hp530-Debian-8 mtp-probe[4701]: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb2
Feb 14 21:39:25 hp530-Debian-8 mtp-probe[4701]: bus: 2, device: 5 was not an MTP device
Feb 14 21:39:26 hp530-Debian-8 kernel: scsi 4:0:0:0: Direct-Access     Verbatim STORE N GO       5.00 PQ: 0 ANSI: 6
Feb 14 21:39:26 hp530-Debian-8 kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
Feb 14 21:39:30 hp530-Debian-8 kernel: sd 4:0:0:0: [sdb] 120795136 512-byte logical blocks: (61.8 GB/57.5 GiB)
Feb 14 21:39:30 hp530-Debian-8 kernel: sd 4:0:0:0: [sdb] Write Protect is off
Feb 14 21:39:30 hp530-Debian-8 kernel: sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
Feb 14 21:39:30 hp530-Debian-8 kernel: sd 4:0:0:0: [sdb] No Caching mode page found
Feb 14 21:39:30 hp530-Debian-8 kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 14 21:39:30 hp530-Debian-8 kernel:  sdb: sdb1 < sdb5 >
Feb 14 21:39:31 hp530-Debian-8 kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
Feb 14 21:39:35 hp530-Debian-8 kernel: FAT-fs (sdb5): utf8 is not a recommended IO charset for FAT filesystems, file
Feb 14 21:39:39 hp530-Debian-8 kernel: FAT-fs (sdb5): Volume was not properly unmounted. Some data may be corrupt. P
Feb 14 21:39:39 hp530-Debian-8 udisksd[1253]: Mounted /dev/sdb5 at /media/hugh/VERBATIM on behalf of uid 1000
Feb 14 21:39:39 hp530-Debian-8 org.gtk.Private.UDisks2VolumeMonitor[1155]: index_parse.c:191: indx_parse(): error op
Feb 14 21:39:39 hp530-Debian-8 org.gtk.Private.UDisks2VolumeMonitor[1155]: index_parse.c:191: indx_parse(): error op
Feb 14 21:40:27 hp530-Debian-8 su[4818]: Successful su for root by hugh
Feb 14 21:40:27 hp530-Debian-8 su[4818]: + /dev/pts/0 hugh:root
Feb 14 21:40:27 hp530-Debian-8 su[4818]: pam_unix(su:session): session opened for user root by (uid=1000)
Feb 14 21:42:36 hp530-Debian-8 ip[4882]: RTNETLINK answers: Operation not possible due to RF-kill
Feb 14 21:42:36 hp530-Debian-8 systemd[1]: network-wireless@wlan0.service: main process exited, code=exited, status=
Feb 14 21:42:36 hp530-Debian-8 systemd[1]: Failed to start Wireless network connectivity (wlan0).
-- Subject: Unit network-wireless@wlan0.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network-wireless@wlan0.service has failed.
-- 
-- The result is failed.
Feb 14 21:42:36 hp530-Debian-8 systemd[1]: Unit network-wireless@wlan0.service entered failed state.
lines 1188-1218/1218 (END)

 ESCOC
 2-1:1.0
us 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
vice: 5 was not an MTP device
t-Access     Verbatim STORE N GO       5.00 PQ: 0 ANSI: 6
d scsi generic sg2 type 0
20795136 512-byte logical blocks: (61.8 GB/57.5 GiB)
rite Protect is off
ode Sense: 23 00 00 00
o Caching mode page found
ssuming drive cache: write through

ttached SCSI removable disk
 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
me was not properly unmounted. Some data may be corrupt. Please run fsck.
/sdb5 at /media/hugh/VERBATIM on behalf of uid 1000
meMonitor[1155]: index_parse.c:191: indx_parse(): error opening /media/hugh/VERBATIM/BDMV/index.bdmv
meMonitor[1155]: index_parse.c:191: indx_parse(): error opening /media/hugh/VERBATIM/BDMV/BACKUP/index.bdmv
 root by hugh
:root
on): session opened for user root by (uid=1000)
: Operation not possible due to RF-kill
s@wlan0.service: main process exited, code=exited, status=2/INVALIDARGUMENT
 Wireless network connectivity (wlan0).

systemd-devel

reless@wlan0.service entered failed state.
lines 1188-1218/1218 (END)

 ESCOC

/2-1"


system will be case sensitive!
lease run fsck.

ening /media/hugh/VERBATIM/BDMV/index.bdmv
ening /media/hugh/VERBATIM/BDMV/BACKUP/index.bdmv

2/INVALIDARGUMENT 
Step 4. Use the list-unit-files option to double-check the status of the units.

Code: Select all

hugh@hp530-Debian-8:~$ systemctl list-unit-files|grep enabled
run-vmblock\x2dfuse.mount              enabled 
acpid.path                             enabled 
cups.path                              enabled 
anacron-resume.service                 enabled 
anacron.service                        enabled 
atd.service                            enabled 
avahi-daemon.service                   enabled 
bluetooth.service                      enabled 
cron.service                           enabled 
cups-browsed.service                   enabled 
cups.service                           enabled 
dbus-org.bluez.service                 enabled 
dbus-org.freedesktop.Avahi.service     enabled 
display-manager.service                enabled 
getty@.service                         enabled 
hwclock-save.service                   enabled 
lightdm.service                        enabled 
live-config.service                    enabled 
network-wireless@.service              enabled 
open-vm-tools.service                  enabled 
rsyslog.service                        enabled 
ssh.service                            enabled 
sshd.service                           enabled 
syslog.service                         enabled 
acpid.socket                           enabled 
avahi-daemon.socket                    enabled 
cups.socket                            enabled 
uuidd.socket                           enabled 
remote-fs.target                       enabled 
hugh@hp530-Debian-8:~$ 
looks like lm-sensors.service and default.target and multi-user.target are not in my list

Step 5. Add some nameservers to the file at /etc/resolv.conf

Code: Select all

 root@hp530-Debian-8:/home/hugh# cp -avr /etc/resolv.conf /home/hugh/resolv.conf.bak
‘/etc/resolv.conf’ -> ‘/home/hugh/resolv.conf.bak’
root@hp530-Debian-8:/home/hugh# 

root@hp530-Debian-8:/home/hugh# nano /etc/resolv.conf 
my current file looks like...

Code: Select all

domain lan
search lan
nameserver 192.168.1.1
nameserver 192.168.1.1
Make the file look like this:

Code: Select all

nameserver 8.8.8.8
nameserver 8.8.4.4
REBOOT still cannot connect to my wireless, same message as before....

Code: Select all

[   7.533826] systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
[FAILED] Failed to start Wireless network connectivity (wlan0)
See 'systemctl status network-wireless@wlan0.service' for details
does any of the output files above give a clue to what is causing this?

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#46 Post by Head_on_a_Stick »

hughparker1 wrote:

Code: Select all

hugh@hp530-Debian-8:~$ systemctl status networkwireless@wlan0.service
● networkwireless@wlan0.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
There is no file at /etc/systemd/system/network-wireless@.service

EDIT: No, sorry, your `status` command has a typo -- it should have a dash between "network" and "wireless"
deadbang

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#47 Post by Head_on_a_Stick »

hughparker1 wrote:

Code: Select all

root@hp530-Debian-8:/home/hugh# journalctl -xe
[...]
Feb 14 21:42:36 hp530-Debian-8 ip[4882]: RTNETLINK answers: Operation not possible due to RF-kill
Feb 14 21:42:36 hp530-Debian-8 systemd[1]: network-wireless@wlan0.service: main process exited, code=exited, status=
Feb 14 21:42:36 hp530-Debian-8 systemd[1]: Failed to start Wireless network connectivity (wlan0).
I think that's the problem.

Try:

Code: Select all

# rfkill unblock all
Then try to start network-wireless@wlan0.service again.
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#48 Post by hughparker1 »

I checked the file was there just to be sure....

Code: Select all

hugh@hp530-Debian-8:~$ cat /etc/systemd/system/network-wireless@.service
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

[Service]
Type=oneshot
RemainAfterExit=yes

ExecStart=/sbin/ip l set %i up
ExecStart=/sbin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant-%i.conf
ExecStart=/sbin/dhclient %i

ExecStop=/sbin/ip l set %i down

[Install]
WantedBy=multi-user.target
hugh@hp530-Debian-8:~$ 
Then I rand this command again with the dash between "network" and "wireless"

Code: Select all

hugh@hp530-Debian-8:~$ systemctl status network-wireless@wlan0.service
● network-wireless@wlan0.service - Wireless network connectivity (wlan0)
   Loaded: loaded (/etc/systemd/system/network-wireless@.service; enabled)
   Active: failed (Result: exit-code) since Sun 2016-02-14 22:45:10 GMT; 8min ago
  Process: 451 ExecStart=/sbin/ip l set %i up (code=exited, status=2)
 Main PID: 451 (code=exited, status=2)
hugh@hp530-Debian-8:~$ 
Does this output help ?

Then ran following as root ...

Code: Select all

hugh@hp530-Debian-8:~$ su
Password: 
root@hp530-Debian-8:/home/hugh# rfkill unblock all
root@hp530-Debian-8:/home/hugh# systemctl enable network-wireless@wlan0.service
root@hp530-Debian-8:/home/hugh# 
REBOOT but still not connected, get same message on startup.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: [***]A start job is running for LSB: Raise network inter

#49 Post by Head_on_a_Stick »

hughparker1 wrote:Then ran following as root ...

Code: Select all

hugh@hp530-Debian-8:~$ su
Password: 
root@hp530-Debian-8:/home/hugh# rfkill unblock all
root@hp530-Debian-8:/home/hugh# systemctl enable network-wireless@wlan0.service
root@hp530-Debian-8:/home/hugh# 
I didn't say "enable", the .service is already enabled, running that command again does nothing.

Did you actually read the man page I linked?
I wrote:try to understand the commands you are using
Here it is again:
http://manpages.debian.org/cgi-bin/man. ... &locale=en

I asked you to "start" the .service:

Code: Select all

# systemctl start network-wireless@wlan0
After running `rfkill unblock all` of course ;)

It would be prudent to also check that the `rfkill` command has worked, use `rfkill list all` for this.

If the output shows a "Hard Block" then you need to toggle the physical Wi-Fi switch on your machine :mrgreen:
deadbang

hughparker1
Posts: 177
Joined: 2014-10-09 21:53
Location: Paisley, United Kingdom

Re: [***]A start job is running for LSB: Raise network inter

#50 Post by hughparker1 »

Thanks for your patience once again. I have now run following as root ...

Code: Select all

hugh@hp530-Debian-8:~$ su
Password: 
root@hp530-Debian-8:/home/hugh# rfkill unblock all
root@hp530-Debian-8:/home/hugh# rfkill list all
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: hp-wifi: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: hp-gps: GPS
	Soft blocked: yes
	Hard blocked: yes
root@hp530-Debian-8:/home/hugh# systemctl start network-wireless@wlan0
root@hp530-Debian-8:/home/hugh#
after REBOOT I am connected to my wireless automatically :-) I got there in the end! thanks to your patient understanding.

Now when my laptop starts, the message following message is displayed for 20 seconds .....

Code: Select all

Loading, please wait...
fsck from util-linux 2.25.2
DEBIAN8: clean,144565/640848 files, 1014006/2560942 blocks
[   7.7480943] systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
Q. does this indicate eveything is running OK?

Post Reply