Network Manager not starting at boot

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
randiroo76073

Network Manager not starting at boot

Post by randiroo76073 »

Mint ver 17.1 Rebecca
I don't know what the problem is, was working fine until I did an update(through update manager), did not see anything in the update that had anything to do with networking. My network manager fails to start now and I'm having long boot times because of it. Network Manager doesn't start till I'm on desktop for a full 60 seconds, then it finally starts up and connects(wifi). Is there a file that may have become corrupted somehow, I've tried reinstalling Network Manager to no avail.
Thanks for any help you can give
Randy
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
kukamuumuka

Re: Network Manager not starting at boot

Post by kukamuumuka »

Edit /etc/init/failsafe.conf file by uncommenting sleep rows.

Code: Select all

# failsafe

description "Failsafe Boot Delay"
author "Clint Byrum <clint@ubuntu.com>"

start on filesystem and net-device-up IFACE=lo
stop on static-network-up or starting rc-sysinit

emits failsafe-boot

console output

script
	# Determine if plymouth is available
	if [ -x /bin/plymouth ] && /bin/plymouth --ping ; then
		PLYMOUTH=/bin/plymouth
	else
		PLYMOUTH=":"
	fi

    # The point here is to wait for 2 minutes before forcibly booting 
    # the system. Anything that is in an "or" condition with 'started 
    # failsafe' in rc-sysinit deserves consideration for mentioning in
    # these messages. currently only static-network-up counts for that.

#### <---- here	sleep 20

    # Plymouth errors should not stop the script because we *must* reach
    # the end of this script to avoid letting the system spin forever
    # waiting on it to start.
	$PLYMOUTH message --text="Waiting for network configuration..." || :
#### <---- here	sleep 40

	$PLYMOUTH message --text="Waiting up to 60 more seconds for network configuration..." || :
#### <---- here	sleep 59
	$PLYMOUTH message --text="Booting system without full network configuration..." || :

    # give user 1 second to see this message since plymouth will go
    # away as soon as failsafe starts.
	sleep 1
    exec initctl emit --no-wait failsafe-boot
end script

post-start exec	logger -t 'failsafe' -p daemon.warning "Failsafe of 120 seconds reached."
Kalyk
Level 5
Level 5
Posts: 769
Joined: Wed Mar 12, 2014 5:29 pm
Location: The Netherlands

Re: Network Manager not starting at boot

Post by Kalyk »

Having to wait for 60 seconds sounds like a timeout problem.
Is the DHCP server in your network running properly?
If that is the router you might try restarting it.
You might also look in the logfiles of Mint, for example /var/log/messages or /var/log/boot.log, to see if they give any information regarding this issue.
Add (Solved) to the topic-title of the first post when appropriate so others know they might find a solution here.
randiroo76073

Re: Network Manager not starting at boot

Post by randiroo76073 »

@administrollaattori
The items were uncommented so I commented them out, I guess that's what you meant...


@Kalyk
I didn't see anything in the boot.log file and didn't see a messages file. Here's the boot.log file

Code: Select all

Scanning for Btrfs filesystems
 * Stopping adjust system clock and timezone[234G[ OK ]
 * Stopping Read required files in advance[234G[ OK ]
 * Starting Mount filesystems on boot[234G[ OK ]
 * Stopping Track if upstart is running in a container[234G[ OK ]
 * Starting Initialize or finalize resolvconf[234G[ OK ]
 * Starting set console keymap[234G[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[234G[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[234G[ OK ]
 * Starting Bridge udev events into upstart[234G[ OK ]
 * Starting Signal sysvinit that remote filesystems are mounted[234G[ OK ]
 * Stopping set console keymap[234G[ OK ]
 * Starting device node and kernel event manager[234G[ OK ]
 * Starting load modules from /etc/modules[234G[ OK ]
 * Starting cold plug devices[234G[ OK ]
 * Starting log initial device creation[234G[ OK ]
 * Stopping load modules from /etc/modules[234G[ OK ]
 * Starting Uncomplicated firewall[234G[ OK ]
 * Starting configure network device security[234G[ OK ]
 * Starting configure network device security[234G[ OK ]
 * Starting Mount network filesystems[234G[ OK ]
 * Stopping Mount network filesystems[234G[ OK ]
 * Starting Bridge socket events into upstart[234G[ OK ]
 * Starting configure network device[234G[ OK ]
 * Starting configure network device security[234G[ OK ]
 * Starting configure network device[234G[ OK ]
 * Starting Signal sysvinit that the rootfs is mounted[234G[ OK ]
 * Starting Clean /tmp directory[234G[ OK ]
 * Stopping Clean /tmp directory[234G[ OK ]
 * Stopping cold plug devices[234G[ OK ]
 * Stopping log initial device creation[234G[ OK ]
 * Starting enable remaining boot-time encrypted block devices[234G[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[234G[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[234G[ OK ]
 * Starting SMB/CIFS File Server[234G[ OK ]
 * Starting Signal sysvinit that local filesystems are mounted[234G[ OK ]
 * Starting restore software rfkill state[234G[ OK ]
 * Starting configure network device security[234G[ OK ]
 * Stopping restore software rfkill state[234G[ OK ]
 * Stopping Mount filesystems on boot[234G[ OK ]
 * Starting Failsafe Boot Delay[234G[ OK ]
 * Starting flush early job output to logs[234G[ OK ]
 * Starting Enabling additional executable binary formats[234G[ OK ]
 * Stopping flush early job output to logs[234G[ OK ]
 * Starting configure virtual network devices[234G[ OK ]
 * Starting Bridge file events into upstart[234G[ OK ]
 * Starting D-Bus system message bus[234G[ OK ]
 * Starting system logging daemon[234G[ OK ]
 * Starting bluetooth daemon[234G[ OK ]
 * Starting mDNS/DNS-SD daemon[234G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[234G[ OK ]
 * Stopping Reload cups, upon starting avahi-daemon to make sure remote queues are populated[234G[ OK ]
 * Starting SystemD login management service[234G[ OK ]
 * Starting SMB/CIFS File and Active Directory Server[234G[ OK ]
 * Starting SMB/CIFS File and Active Directory Server[234G[[31mfail[39;49m]
 * Starting CUPS printing spooler/server[234G[ OK ]
 * Starting Samba Auto-reload Integration[234G[ OK ]
 * Starting cups-browsed - Bonjour remote printer browsing daemon[234G[ OK ]
 * Stopping Samba Auto-reload Integration[234G[ OK ]
 * Stopping Failsafe Boot Delay[234G[ OK ]
 * Starting System V initialisation compatibility[234G[ OK ]
 [33m*[39;49m VirtualBox Additions disabled, not in a Virtual Machine
 * Setting sensors limits       [240G 
[234G[ OK ]
 * Setting up X socket directories...       [240G 
[234G[ OK ]
 * Stopping System V initialisation compatibility[234G[ OK ]
 * Loading cpufreq kernel modules...        * Starting System V runlevel compatibility[234G[ OK ]
 * Starting ISC DHCP IPv4 server[234G[ OK ]
 * Starting anac(h)ronistic cron[234G[ OK ]
 * Starting MDM Display Manager[234G[ OK ]
 * Starting save kernel messages[234G[ OK ]
[240G 
[234G[ OK ]
 * Starting ACPI daemon[234G[ OK ]
 * Starting regular background program processing daemon[234G[ OK ]
 * Stopping Send an event to indicate plymouth is up[234G[ OK ]
 * Stopping save kernel messages[234G[ OK ]
 * Stopping anac(h)ronistic cron[234G[ OK ]
 * CPU0...       [240G  * Starting CPU interrupts balancing daemon[234G[ OK ]
 * Starting automatic crash report generation[234G[ OK ]
 * CPU1...       [240G  * CPUFreq Utilities: Setting ondemand CPUFreq governor...        * Stopping Restore Sound Card State[234G[ OK ]
[240G 
[234G[ OK ]
 * Stopping ISC DHCP IPv6 server[234G[ OK ]
 * Starting ISC DHCP IPv4 server[234G[ OK ]
 * Starting dictionary server dictd       [240G 
[234G[ OK ]
 * Starting ISC DHCP IPv4 server[234G[ OK ]
 [33m*[39;49m Not starting fancontrol; run pwmconfig first.
 * Starting ISC DHCP IPv4 server[234G[ OK ]
 * speech-dispatcher disabled; edit /etc/default/speech-dispatcher
 * Starting ISC DHCP IPv4 server[234G[ OK ]
 [33m*[39;49m VirtualBox Additions disabled, not in a Virtual Machine
 * Starting NTP server ntpd       [240G 
[234G[ OK ]
randiroo76073

Re: Network Manager not starting at boot

Post by randiroo76073 »

While commenting out those lines did help my boot time, it now takes 90 sec after I get to the desktop before my Network Manager starts up ! Is there some other file I can modify to stop this behavior and get my Network Manager to start at boot again ?
randiroo76073

Re: Network Manager not starting at boot

Post by randiroo76073 »

No answers yet ???
Locked

Return to “Networking”