Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: start-up halts at "started WPA supplicant daemon" message

  1. #1

    Default start-up halts at "started WPA supplicant daemon" message

    I installed Leap 15.1 on clean disks, everything went fine. In network manager I created a hidden wireless connection for WLAN0. Later on I had to delete WLAN0 and configure WLAN1, but I spend yesterday afternoon updating the software packages on the system, so I assumed everything was okay.

    This morning, I went to bring up Leap 15.1, but the startup halts after outputting the message "Started WPA Supplicant daemon". I am assuming that the problem is the hidden wireless network is not being discovered, since the SSID is not being broadcast.

    At the moment I am stuck, how would someone go about dealing with this issue? I want to stay with the hidden wireless network, if possible.

    Thank you.

    - Randall

  2. #2
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    1,674

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Quote Originally Posted by randallrathbun View Post
    At the moment I am stuck, how would someone go about dealing with this issue? I want to stay with the hidden wireless network, if possible.
    Hi, writing this from a Leap 15.1 which automatically connected to a hidden SSID WiFi router, so what you need is definitely possible.
    Maybe a detailed description of what you actually did to configure WLAN0 and then WLAN1 might help; do you have more than a WiFi card in your system?
    Please be aware that a clear title in the "Network/Internet" subforum is more likely to attract the experts you need than this thread in the Install subforum...
    Main: Leap 15 Gnome on i7 4720HQ + Geforce GTX960M
    Test: Leap 42.3 (& others) on Core2Duo + GM965

  3. #3

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Quote Originally Posted by OrsoBruno View Post
    Hi, writing this from a Leap 15.1 which automatically connected to a hidden SSID WiFi router, so what you need is definitely possible.
    Maybe a detailed description of what you actually did to configure WLAN0 and then WLAN1 might help; do you have more than a WiFi card in your system?
    Please be aware that a clear title in the "Network/Internet" subforum is more likely to attract the experts you need than this thread in the Install subforum...
    I actually have dug into debugging on the systemd level and found that the stall during booting was NOT caused by the network manager missing the hidden wireless router, since I disabled the whole network.service and rebooted again, only to go into a stall mode.

    I followed directions from troubleshooting in the debug-shell and have gotten about 6 megabytes of log files from this, but I guess I need someone who is intimately familiar with the systemd bringup process, who can look at the journalctl log and dmesg log and systemctl status logs to pinpoint the actual problem.

    I believe I have ruled out the network from being the source of the stall during booting.

    - Randall
    Last edited by randallrathbun; 03-Jul-2019 at 15:18. Reason: changed network to wireless router as that is what is actually referenced

  4. #4
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,305
    Blog Entries
    2

    Default Re: start-up halts at "started WPA supplicant daemon" message

    If you prefer not to wade through the MAN files (most will try to avoid),
    The following is one of the most used articles on how to use journalctl

    https://www.digitalocean.com/communi...e-systemd-logs

    Recommend starting your troubleshooting by filtering on various error levels, then perhaps by specific services if you can narrow down.
    You can also specify specific bootlogs (ie last or before that, etc) or by time if you are certain approximately the time your error happened.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  5. #5
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,009

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Quote Originally Posted by randallrathbun View Post
    I actually have dug into debugging on the systemd level and found that the stall during booting was NOT caused by the network manager missing the hidden wireless router, since I disabled the whole network.service and rebooted again, only to go into a stall mode.

    I followed directions from troubleshooting in the debug-shell and have gotten about 6 megabytes of log files from this, but I guess I need someone who is intimately familiar with the systemd bringup process, who can look at the journalctl log and dmesg log and systemctl status logs to pinpoint the actual problem.

    I believe I have ruled out the network from being the source of the stall during booting.

    - Randall
    Your computer looks to me like a black hole: No details available. A nice starting point could be running the command: journalctl -b |grep Start and posting its output in this forum.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  6. #6

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Quote Originally Posted by karlmistelberger View Post
    Your computer looks to me like a black hole: No details available. A nice starting point could be running the command: journalctl -b |grep Start and posting its output in this forum.
    Yesterday I was learning about shell debug during start up and running journalctl -b and dmesg -T | less and other commands. Here is the output from "journalctl -b | grep Start"

    Do I assume from this that after the startkde was issued, that we're hung? ( I also noticed a lot of condition failed in the lines below, should I be concerned about that?)

    Jul 03 14:53:49 linux systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Jul 03 14:53:49 linux systemd[1]: Starting Load Kernel Modules...
    Jul 03 14:53:49 linux systemd[1]: Starting Journal Service...
    Jul 03 14:53:49 linux systemd[1]: Starting Create list of required static device nodes for the current kernel...
    Jul 03 14:53:49 linux systemd[1]: Starting Setup Virtual Console...
    Jul 03 14:53:49 linux systemd[1]: Started Create list of required static device nodes for the current kernel.
    Jul 03 14:53:49 linux systemd[1]: Starting Create Static Device Nodes in /dev...
    Jul 03 14:53:49 linux systemd[1]: Started Create Static Device Nodes in /dev.
    Jul 03 14:53:49 linux systemd[1]: Started Load Kernel Modules.
    Jul 03 14:53:49 linux systemd[1]: Starting Apply Kernel Variables...
    Jul 03 14:53:49 linux systemd[1]: Started Apply Kernel Variables.
    Jul 03 14:53:49 linux systemd[1]: Started Journal Service.
    Jul 03 14:53:49 linux systemd[1]: Started Setup Virtual Console.
    Jul 03 14:53:49 linux systemd[1]: Starting dracut ask for additional cmdline parameters...
    Jul 03 14:53:49 linux systemd[1]: Started dracut ask for additional cmdline parameters.
    Jul 03 14:53:49 linux systemd[1]: Starting dracut cmdline hook...
    Jul 03 14:53:49 linux systemd[1]: Started dracut cmdline hook.
    Jul 03 14:53:49 linux systemd[1]: dracut-pre-udev.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:49 linux systemd[1]: Starting udev Kernel Device Manager...
    Jul 03 14:53:49 linux systemd[1]: Started udev Kernel Device Manager.
    Jul 03 14:53:49 linux systemd[1]: Starting dracut pre-trigger hook...
    Jul 03 14:53:49 linux systemd[1]: Started dracut pre-trigger hook.
    Jul 03 14:53:49 linux systemd[1]: Starting udev Coldplug all Devices...
    Jul 03 14:53:49 linux systemd[1]: Started udev Coldplug all Devices.
    Jul 03 14:53:49 linux systemd[1]: Starting Show Plymouth Boot Screen...
    Jul 03 14:53:49 linux systemd[1]: dracut-initqueue.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:49 linux systemd[1]: dracut-pre-mount.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:49 linux systemd[1]: Started Show Plymouth Boot Screen.
    Jul 03 14:53:50 linux systemd[1]: systemd-ask-password-console.path: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:50 linux systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
    Jul 03 14:53:52 linux systemd[1]: Starting File System Check on /dev/disk/by-uuid/9bb02dda-f93f-4e94-831f-c4fffd4ad071...
    Jul 03 14:53:52 linux systemd[1]: Started File System Check on /dev/disk/by-uuid/9bb02dda-f93f-4e94-831f-c4fffd4ad071.
    Jul 03 14:53:52 linux systemd[1]: ostree-prepare-root.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:52 linux systemd[1]: Starting Reload Configuration from the Real Root...
    Jul 03 14:53:52 linux systemctl[424]: Calling manager for StartUnit on initrd-fs.target, replace
    Jul 03 14:53:52 linux systemctl[424]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:53:52 linux systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:53:52 linux systemctl[425]: Calling manager for StartUnit on initrd-cleanup.service, replace
    Jul 03 14:53:52 linux systemctl[425]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:53:52 linux systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:53:52 linux systemd[1]: Started Reload Configuration from the Real Root.
    Jul 03 14:53:52 linux systemd[1]: dracut-mount.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:52 linux systemd[1]: dracut-pre-pivot.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:52 linux systemd[1]: Starting Cleaning Up and Shutting Down Daemons...
    Jul 03 14:53:52 linux systemctl[426]: Calling manager for StartUnit on initrd-switch-root.target, isolate
    Jul 03 14:53:52 linux systemctl[426]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:53:52 linux systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:53:52 linux systemd[1]: ostree-prepare-root.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:52 linux systemd[1]: Starting Setup Virtual Console...
    Jul 03 14:53:52 linux systemd[1]: Starting Plymouth switch root service...
    Jul 03 14:53:52 linux systemd[1]: systemd-udevd.service: Got notification message from PID 278 (STOPPING=1, STATUS=Starting shutdown...)
    Jul 03 14:53:52 linux systemd[1]: Started Cleaning Up and Shutting Down Daemons.
    Jul 03 14:53:52 linux systemd[1]: Starting Cleanup udevd DB...
    Jul 03 14:53:52 linux systemd[1]: Started Cleanup udevd DB.
    Jul 03 14:53:52 linux systemd[1]: Started Setup Virtual Console.
    Jul 03 14:53:52 linux systemd[1]: Started Plymouth switch root service.
    Jul 03 14:53:52 linux systemd[1]: Starting Switch Root...
    Jul 03 14:53:54 linux systemd[1]: Starting Journal Service...
    Jul 03 14:53:54 linux systemd[1]: Starting Remount Root and Kernel File Systems...
    Jul 03 14:53:54 linux systemd[1]: Starting Create list of required static device nodes for the current kernel...
    Jul 03 14:53:54 linux systemd[1]: Starting Load Kernel Modules...
    Jul 03 14:53:54 linux systemd[1]: systemd-binfmt.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:54 linux systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
    Jul 03 14:53:54 linux systemd[1]: Started Early root shell on /dev/tty9 FOR DEBUGGING ONLY.
    Jul 03 14:53:54 linux systemd[1]: systemd-ask-password-console.path: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:54 linux systemd[1]: Starting Setup Virtual Console...
    Jul 03 14:53:54 linux systemd[1]: Started Create list of required static device nodes for the current kernel.
    Jul 03 14:53:54 linux systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
    Jul 03 14:53:54 linux systemd[1]: Started Journal Service.
    Jul 03 14:53:54 linux systemd[1]: Started Load Kernel Modules.
    Jul 03 14:53:54 linux systemd[1]: sys-fs-fuse-connections.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:54 linux systemd[1]: sys-kernel-config.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:55 linux systemd[1]: Started Remount Root and Kernel File Systems.
    Jul 03 14:53:55 linux systemd[1]: systemd-hwdb-update.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:55 linux systemd[1]: Starting udev Coldplug all Devices...
    Jul 03 14:53:55 linux systemd[1]: systemd-firstboot.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:55 linux systemd[1]: systemd-sysusers.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:55 linux systemd[1]: Starting Create Static Device Nodes in /dev...
    Jul 03 14:53:55 linux systemd[1]: Started LVM2 metadata daemon.
    Jul 03 14:53:55 linux systemd[1]: Started Setup Virtual Console.
    Jul 03 14:53:55 linux systemd[1]: Started udev Coldplug all Devices.
    Jul 03 14:53:55 linux systemd[1]: Started Create Static Device Nodes in /dev.
    Jul 03 14:53:55 linux systemd[1]: Starting udev Kernel Device Manager...
    Jul 03 14:53:56 linux systemd[1]: Started udev Kernel Device Manager.
    Jul 03 14:53:57 linux systemd[1]: sys-fs-fuse-connections.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:57 linux systemd[1]: systemd-binfmt.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:57 linux systemd[1]: systemd-firstboot.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:57 linux systemd[1]: sys-kernel-config.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:57 linux systemd[1]: Starting Setup Virtual Console...
    Jul 03 14:53:57 linux systemd[1]: systemd-hwdb-update.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:57 linux systemd[1]: systemd-sysusers.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: Started Setup Virtual Console.
    Jul 03 14:53:58 linux systemd[1]: Starting Show Plymouth Boot Screen...
    Jul 03 14:53:58 linux systemd[1]: Started Show Plymouth Boot Screen.
    Jul 03 14:53:58 linux systemd[1]: systemd-ask-password-console.path: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
    Jul 03 14:53:58 linux systemd[1]: Starting File System Check on /dev/disk/by-uuid/4de3e133-457f-4c68-a073-792b0e795f94...
    Jul 03 14:53:58 linux systemd[1]: Starting File System Check on /dev/disk/by-uuid/edf0ec89-eab6-4a62-a534-1d1b72c10599...
    Jul 03 14:53:58 linux systemd[1]: Starting File System Check on /dev/disk/by-uuid/a4c41b3b-9832-4c89-aa25-5c0c78b92dfa...
    Jul 03 14:53:58 linux systemd[1]: Starting File System Check on /dev/disk/by-uuid/d9c75afd-5013-4ff6-8732-74aae96660df...
    Jul 03 14:53:58 linux systemd[1]: systemd-firstboot.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: sys-fs-fuse-connections.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: systemd-hwdb-update.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: sys-kernel-config.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: systemd-binfmt.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: systemd-sysusers.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: systemd-ask-password-console.path: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: Started File System Check on /dev/disk/by-uuid/4de3e133-457f-4c68-a073-792b0e795f94.
    Jul 03 14:53:58 linux systemd[1]: Started File System Check on /dev/disk/by-uuid/edf0ec89-eab6-4a62-a534-1d1b72c10599.
    Jul 03 14:53:58 linux systemd[1]: Starting Apply Kernel Variables...
    Jul 03 14:53:58 linux systemd[1]: Started File System Check on /dev/disk/by-uuid/a4c41b3b-9832-4c89-aa25-5c0c78b92dfa.
    Jul 03 14:53:58 linux systemd[1]: Started File System Check on /dev/disk/by-uuid/d9c75afd-5013-4ff6-8732-74aae96660df.

    CONTINUED IN NEXT REPLY POST

  7. #7

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Quote Originally Posted by karlmistelberger View Post
    Your computer looks to me like a black hole: No details available. A nice starting point could be running the command: journalctl -b |grep Start and posting its output in this forum.
    2nd half of reply, finishing the contents of journalctl -b command

    Jul 03 14:53:58 linux systemd[1]: Started Apply Kernel Variables.
    Jul 03 14:53:58 linux systemd[1]: Starting Flush Journal to Persistent Storage...
    Jul 03 14:53:58 linux systemd[1]: var-run.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: Starting Load/Save RF Kill Switch Status...
    Jul 03 14:53:58 linux systemd[1]: var-lock.mount: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: Starting Load AppArmor profiles...
    Jul 03 14:53:58 linux systemd[1]: systemd-journal-catalog-update.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: systemd-update-done.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: systemd-machine-id-commit.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:58 linux systemd[1]: Starting Restore /run/initramfs on shutdown...
    Jul 03 14:53:58 linux systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
    Jul 03 14:53:58 linux systemd[1]: Starting Early Kernel Boot Messages...
    Jul 03 14:53:58 linux systemd[1]: Starting Load/Save Random Seed...
    Jul 03 14:53:58 linux systemd[1]: Started Restore /run/initramfs on shutdown.
    Jul 03 14:53:58 linux systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
    Jul 03 14:53:58 linux systemd[1]: Started Flush Journal to Persistent Storage.
    Jul 03 14:53:58 linux systemd[1]: Starting Create Volatile Files and Directories...
    Jul 03 14:53:58 linux systemd[1]: Started Load/Save Random Seed.
    Jul 03 14:53:59 linux systemd[1]: Started Load/Save RF Kill Switch Status.
    Jul 03 14:53:59 linux systemd[1]: Started Create Volatile Files and Directories.
    Jul 03 14:53:59 linux systemd[1]: Starting Security Auditing Service...
    Jul 03 14:53:59 linux auditd[761]: Started dispatcher: /sbin/audispd pid: 763
    Jul 03 14:53:59 linux systemd[1]: Started Early Kernel Boot Messages.
    Jul 03 14:53:59 linux systemd[1]: Started Security Auditing Service.
    Jul 03 14:53:59 linux systemd[1]: Starting Update UTMP about System Boot/Shutdown...
    Jul 03 14:53:59 linux systemd[1]: Started Update UTMP about System Boot/Shutdown.
    Jul 03 14:53:59 linux systemd[1]: Started Load AppArmor profiles.
    Jul 03 14:53:59 linux systemd[1]: Started Daily Cleanup of Snapper Snapshots.
    Jul 03 14:53:59 linux systemd[1]: Started Watch for changes in CA certificates.
    Jul 03 14:53:59 linux systemd[1]: Started Daily Cleanup of Temporary Directories.
    Jul 03 14:53:59 linux systemd[1]: Started CUPS Scheduler.
    Jul 03 14:53:59 linux systemd[1]: Started Watch /etc/sysconfig/btrfsmaintenance.
    Jul 03 14:53:59 linux systemd[1]: alsa-restore.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:59 linux systemd[1]: Starting System Logging Service...
    Jul 03 14:53:59 linux systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
    Jul 03 14:53:59 linux systemd[1]: purge-kernels.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:53:59 linux systemd[1]: Started D-Bus System Message Bus.
    Jul 03 14:54:00 linux systemd[1]: YaST2-Second-Stage.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:54:00 linux systemd[1]: Starting firewalld - dynamic firewall daemon...
    Jul 03 14:54:00 linux systemd[1]: Started irqbalance daemon.
    Jul 03 14:54:00 linux systemd[1]: Started CUPS Scheduler.
    Jul 03 14:54:00 linux systemd[1]: Starting Modem Manager...
    Jul 03 14:54:00 linux systemd[1]: Started Detect if the system suffers from bsc#1089761.
    Jul 03 14:54:00 linux systemd[1]: appstream-sync-cache.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:54:00 linux systemd[1]: YaST2-Firstboot.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:54:00 linux systemd[1]: alsa-state.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:54:00 linux systemd[1]: Starting Apply settings from /etc/sysconfig/keyboard...
    Jul 03 14:54:00 linux systemd[1]: Starting Machine Check Exception Logging Daemon...
    Jul 03 14:54:00 linux systemd[1]: Starting Name Service Cache Daemon...
    Jul 03 14:54:00 linux systemd[1]: Starting Update cron periods from /etc/sysconfig/btrfsmaintenance...
    Jul 03 14:54:00 linux systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
    Jul 03 14:54:00 linux systemd[1]: Started Machine Check Exception Logging Daemon.
    Jul 03 14:54:00 linux systemd[1]: Started Name Service Cache Daemon.
    Jul 03 14:54:00 linux systemd[1]: Starting Login Service...
    Jul 03 14:54:00 linux systemd[1]: Started Avahi mDNS/DNS-SD Stack.
    Jul 03 14:54:01 linux systemd[1]: Starting Authorization Manager...
    Jul 03 14:54:01 linux systemd[1]: Started Apply settings from /etc/sysconfig/keyboard.
    Jul 03 14:54:01 linux systemd[1]: Started Login Service.
    Jul 03 14:54:01 linux systemctl[1112]: Calling manager for StartUnit on btrfs-scrub.timer, replace
    Jul 03 14:54:01 linux systemctl[1112]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:54:01 linux systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:54:01 linux polkitd[1043]: Started polkitd version 0.114
    Jul 03 14:54:02 linux systemd[1]: Started System Logging Service.
    Jul 03 14:54:02 linux systemd[1]: Started Authorization Manager.
    Jul 03 14:54:02 linux systemd[1]: Started Modem Manager.
    Jul 03 14:54:03 linux systemd[1]: Started firewalld - dynamic firewall daemon.
    Jul 03 14:54:03 linux systemd[1]: Starting Login and scanning of iSCSI devices...
    Jul 03 14:54:03 linux systemd[1]: Starting NTP client/server...
    Jul 03 14:54:03 linux systemd[1]: Started Login and scanning of iSCSI devices.
    Jul 03 14:54:03 linux systemd[1]: Starting Permit User Sessions...
    Jul 03 14:54:03 linux systemd[1]: Started Permit User Sessions.
    Jul 03 14:54:03 linux systemd[1]: Starting Hold until boot process finishes up...
    Jul 03 14:54:03 linux systemd[1]: Started NTP client/server.
    Jul 03 14:54:03 linux systemd[1]: Started Scrub btrfs filesystem, verify block checksums.
    Jul 03 14:54:03 linux systemd[1]: Started Backup of /etc/sysconfig.
    Jul 03 14:54:03 linux systemd[1]: Started Timeline of Snapper Snapshots.
    Jul 03 14:54:03 linux systemd[1]: Started Discard unused blocks once a week.
    Jul 03 14:54:03 linux systemd[1]: Started Check if mainboard battery is Ok.
    Jul 03 14:54:03 linux systemd[1]: Started Backup of RPM database.
    Jul 03 14:54:03 linux systemd[1]: Started Daily rotation of log files.
    Jul 03 14:54:03 linux systemd[1]: postfix.service: About to execute: /bin/echo 'Starting mail service (Postfix)'
    Jul 03 14:54:03 linux systemd[1]: Starting Postfix Mail Transport Agent...
    Jul 03 14:54:03 linux systemd[1]: Started Do daily mandb update.
    Jul 03 14:54:03 linux systemd[1179]: postfix.service: Executing: /bin/echo 'Starting mail service (Postfix)'
    Jul 03 14:54:03 linux systemd[1]: Starting X Display Manager...
    Jul 03 14:54:03 linux systemd[1]: Started Balance block groups on a btrfs filesystem.
    Jul 03 14:54:03 linux echo[1179]: Starting mail service (Postfix)
    Jul 03 14:54:04 linux systemd[1]: Starting Locale Service...
    Jul 03 14:54:04 linux systemd[1]: Started Locale Service.
    Jul 03 14:54:04 linux systemd[1]: Started Hold until boot process finishes up.
    Jul 03 14:54:04 linux systemd[1]: Started Getty on tty1.
    Jul 03 14:54:04 linux systemd[1]: after-local.service: Starting requested but condition failed. Not starting unit.
    Jul 03 14:54:04 linux systemctl[1316]: Calling manager for StartUnit on btrfs-balance.timer, replace
    Jul 03 14:54:04 linux systemctl[1316]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:54:04 linux systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
    Jul 03 14:54:04 linux systemd[1]: Started Update cron periods from /etc/sysconfig/btrfsmaintenance.
    Jul 03 14:54:05 linux sddm[1312]: Starting...
    Jul 03 14:54:05 linux display-manager[1182]: Starting service sddm..done
    Jul 03 14:54:05 linux systemd[1]: Started X Display Manager.
    Jul 03 14:54:06 linux systemd[1]: Started Command Scheduler.
    Jul 03 14:54:06 linux systemd[1]: Starting Update UTMP about System Runlevel Changes...
    Jul 03 14:54:06 linux systemd[1]: Started Update UTMP about System Runlevel Changes.
    Jul 03 14:54:06 linux systemd[1]: Startup finished in 1.711s (kernel) + 3.591s (initrd) + 13.826s (userspace) = 19.128s.
    Jul 03 14:54:06 linux systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartupFinished cookie=3524 reply_cookie=0 error=n/a
    Jul 03 14:54:08 linux sddm-helper[1491]: [PAM] Starting...
    Jul 03 14:54:08 linux systemd-logind[1022]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=18 reply_cookie=0 error=n/a
    Jul 03 14:54:08 linux systemd[1]: Got message type=method_call sender=:1.3 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=18 reply_cookie=0 error=n/a
    Jul 03 14:54:08 linux systemd-logind[1022]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=19 reply_cookie=0 error=n/a
    Jul 03 14:54:08 linux systemd[1]: Got message type=method_call sender=:1.3 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=19 reply_cookie=0 error=n/a
    Jul 03 14:54:08 linux systemd-logind[1022]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=21 reply_cookie=0 error=n/a
    Jul 03 14:54:08 linux systemd[1]: Starting User Manager for UID 1000...
    Jul 03 14:54:08 linux systemd[1]: Got message type=method_call sender=:1.3 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=21 reply_cookie=0 error=n/a
    Jul 03 14:54:08 linux systemd[1]: Started Session 1 of user owner.
    Jul 03 14:54:08 linux systemd[1]: Started User Manager for UID 1000.
    Jul 03 14:54:08 linux systemd[1]: user@1000.service: Got notification message from PID 1493 (STATUS=Startup finished in 290ms.)
    Jul 03 14:54:08 linux systemd[1493]: Startup finished in 290ms.
    Jul 03 14:54:08 linux sddm-helper[1491]: Starting: "/etc/X11/xdm/Xsession \"/usr/bin/startkde\""

  8. #8

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Quote Originally Posted by tsu2 View Post
    If you prefer not to wade through the MAN files (most will try to avoid),
    The following is one of the most used articles on how to use journalctl

    https://www.digitalocean.com/communi...e-systemd-logs

    Recommend starting your troubleshooting by filtering on various error levels, then perhaps by specific services if you can narrow down.
    You can also specify specific bootlogs (ie last or before that, etc) or by time if you are certain approximately the time your error happened.

    TSU
    Thanks for that tip. Yesterday I spent some time learning how openSuse actually boots up and enables the services. Now, I want to find out why 17 services are missing and what to do about that. It takes some time to absorb all this, when a person has to wade through all the linux postings and weed out the non-systemd information.

  9. #9

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Quote Originally Posted by OrsoBruno View Post
    Hi, writing this from a Leap 15.1 which automatically connected to a hidden SSID WiFi router, so what you need is definitely possible.
    Maybe a detailed description of what you actually did to configure WLAN0 and then WLAN1 might help; do you have more than a WiFi card in your system?
    Please be aware that a clear title in the "Network/Internet" subforum is more likely to attract the experts you need than this thread in the Install subforum...
    Thanks for the information. I did have openSuse connecting to a hidden SSID wifi okay, I just assumed that the break down was occurring as wpa_supplicant tried to come up. More trouble shooting revealed that the problem was not in this area, it looks like a X-Windows manager problem, possibly.

    I have a lot to learn yet about the actual scripting and boot up process that openSuse uses, under the systemd management layer.

  10. #10
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,748

    Default Re: start-up halts at "started WPA supplicant daemon" message

    Video card and driver???

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •