Forums

Resolved
0 votes
Hi all,

I've got a emergency. When I reboot, I no longer got SSH and Consol screen (on local display) display an error message : user not know underlying authentification module.

Why did I reboot :

  1. I wasn't abled to start new ssh session error : ssh_exchange_identification: read: Connection reset by peer
  2. When I look to my directories (with ll) I've got 0 as owner instead of root

I thought that a rebood my solve both theese issue but I doesn't.

I've tryed to :

  • reboot as normal default menu entry
  • reboot on previous kernel version
  • reboot with debuging... I still wait for message


I guess I could try to boot on rescue entry. But does any one has suggestion for the root cause ? And how to fix that ?

I guessed this is something around authentification so user's directory...

Taryck.
Saturday, July 29 2017, 03:35 PM
Share this post:
Responses (12)
  • Accepted Answer

    Monday, July 31 2017, 06:49 PM - #Permalink
    Resolved
    0 votes
    I am really surprised they are not there. You could try a
    find / -name "configuration_backup"
    I thought this was part of the basic set up. If it is not, I suggest you install it.

    [edit]
    Based on my new test box it is part of the standard installation so I wonder why the files are missing.
    [/edit]
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 31 2017, 01:42 PM - #Permalink
    Resolved
    0 votes
    No I do not have such mapping in /etc/fstab and I do not remember doing such a thing.
    I've discovered this directory I guess while doing a search on clearos key work from root directory...
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 31 2017, 11:17 AM - #Permalink
    Resolved
    0 votes
    As you are using the LVM, could /var/clearos/configuration_backup actually used be mapped to somewhere else on your disk, perhaps under /store?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 31 2017, 08:27 AM - #Permalink
    Resolved
    0 votes
    Hi,

    I've got a /var/clearos/configuration_backup
    but it's empty....
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 31 2017, 05:58 AM - #Permalink
    Resolved
    0 votes
    Better than an LDAP restore is a full config restore. I am not at my system but somewhere under /usr/clearos you'll find some backup files. Use one of them. Either in it or by it I think there is a file installed.txt which also has a list of all installed programs which may be of use. It is probably better to install all to apps before you do a config restore or do a second one afterwards.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 31 2017, 12:57 AM - #Permalink
    Resolved
    0 votes
    Hi,

    At this moment I'm on the fresh install of 7.3 which have no need of network driver (instead installing it using rpm of version 7.1).
    I've worked on transfering ldap user instead of creting them using webconfig. I could try this because I've got a ldap dump each week.
    And it seams to work.
    I use this re-install time to note (to speed up install process) every improvment I can do like Quick Selection Files (and yum version of QSF)
    Because package that are not marketplace ones doesn't work.

    I keep you inform on my investigation about service login failure...
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, July 30 2017, 08:55 PM - #Permalink
    Resolved
    0 votes
    I would tend to agree. The login service could be the problem. When booting up there is a possibility of booting to a recovery kernel. There is also a rescue mode on the installation disc, but I think documentation is scant. Here is a document which shows going into recovery mode, from where a lot of command line stuff will be available. It may be the ldap database is messed up. This site should have information on restoring a backup copy which I'm afraid I can't research tonight. Then there is Google. Beyond Google I am not sure where to go.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, July 30 2017, 10:11 AM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    I've got a limited control of this serveur. Let me explain.
    If I remove Hardrives that are in fstab boot fails and let me set my root password to get access to limited commands (no ssh is wroking as this time).
    If I do not remove hardrives I've got a text windows indicating that underliyng module for autorisation doesn't works.

    I guess that the root cause is : [FAILED] Failed to start Login Service.

    But I've no idea on how to investigate and fix in such rescue situation....

    I've installed a fresh 7.3 on an other disk in order to gain access to my crashed install and I've done some "fix" that doesn't works yet :

    1. revert back /etc/passwd to previous version passwd- (that removed the last user created)
    2. Revert back hostname that i've changed
    3. comment in fstab disk that are missing (to prevent data loss)


    I guess that I should put back fstab errors in order to get rescue mode ?
    And then try : systemctl status login
    and hope I recieve a comprehensive answer and I could fix it...

    Am I correct ?
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, July 30 2017, 08:07 AM - #Permalink
    Resolved
    0 votes
    Have you checked out all the packages failing to start to see why? In the log it gives you the command to use ("systemctl status .....). It looks like NFS, networking and others have failed. There may be a common root cause.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, July 29 2017, 10:50 PM - #Permalink
    Resolved
    0 votes
    Find in /var/log/mailog :
    Jul 29 17:15:34 home postfix[3068]: fatal: file /etc/postfix/main.cf: parameter default_privs: unknown user name value: nobody
    Jul 29 17:15:43 home postfix/sendmail[4621]: fatal: file /etc/postfix/main.cf: parameter default_privs: unknown user name value: nobody
    Jul 29 17:20:07 SAPNW750 postfix[3061]: fatal: file /etc/postfix/main.cf: parameter default_privs: unknown user name value: nobody
    Jul 29 17:20:16 SAPNW750 postfix/sendmail[4718]: fatal: file /etc/postfix/main.cf: parameter default_privs: unknown user name value: nobody

    It seams before reboot that user correspondance fails...

    The same event from /var/log/secure :
    Jul 29 16:26:33 home sshd[21747]: Received disconnect from 10.0.0.170: 11: disconnected by user
    Jul 29 16:26:33 home sshd[21747]: pam_succeed_if(sshd:session): error retrieving information about user 0
    Jul 29 16:26:33 home sshd[21747]: pam_unix(sshd:session): session closed for user root
    Jul 29 16:26:33 home sshd[21747]: fatal: login_init_entry: Cannot find user "root"
    Jul 29 16:26:33 home sshd[21749]: pam_succeed_if(sshd:session): error retrieving information about user 0
    Jul 29 16:26:33 home sshd[21749]: pam_unix(sshd:session): session closed for user root
    Jul 29 16:52:26 home sshd[16057]: Exiting on signal 15
    Jul 29 16:52:26 home sshd[24076]: Exiting on signal 15
    Jul 29 16:52:26 home sshd[9706]: Exiting on signal 15
    Jul 29 16:52:26 home sshd[9708]: Exiting on signal 15
    Jul 29 16:52:26 home login: pam_console(login:session): getpwnam failed for clearconsole
    Jul 29 16:52:26 home sshd[16059]: Exiting on signal 15
    Jul 29 16:52:26 home sshd[16059]: pam_systemd(sshd:session): Failed to release session: Interrupted system call
    Jul 29 17:15:35 home login: pam_unix(login:account): could not identify user (from getpwnam(clearconsole))
    Jul 29 17:15:35 home login: pam_ldap(login:account): error opening connection to nslcd: No such file or directory
    Jul 29 17:15:35 home login: User not known to the underlying authentication module


    in /var/log/syswatch :
    Sat Jul 29 16:22:55 2017  info:  system - heartbeat...
    Sat Jul 29 16:32:55 2017 info: system - heartbeat...
    Sat Jul 29 16:42:55 2017 info: system - heartbeat...
    Sat Jul 29 16:52:55 2017 info: system - heartbeat...
    Sat Jul 29 16:52:57 2017 info: system - syswatch terminated
    Sat Jul 29 17:15:35 2017 info: system - syswatch started
    Sat Jul 29 17:15:35 2017 info: config - IP referrer tool is not installed
    Sat Jul 29 17:15:35 2017 info: config - debug level - 0
    Sat Jul 29 17:15:35 2017 info: config - retries - 5
    Sat Jul 29 17:15:35 2017 info: config - heartbeat - 10
    Sat Jul 29 17:15:35 2017 info: config - interval - 60 seconds
    Sat Jul 29 17:15:35 2017 info: config - offline interval - 10 seconds
    Sat Jul 29 17:15:35 2017 info: config - referrer IP detection - disabled
    Sat Jul 29 17:15:35 2017 info: config - ping server auto-detect - enabled
    Sat Jul 29 17:15:35 2017 info: config - try pinging gateway - yes
    Sat Jul 29 17:15:35 2017 info: config - number of external networks - 1
    Sat Jul 29 17:15:35 2017 info: config - monitoring external network - enp3s0
    Sat Jul 29 17:15:35 2017 info: config - number of standby networks - 0
    Sat Jul 29 17:15:35 2017 info: info - loading network configuration
    Sat Jul 29 17:15:35 2017 info: info - network configuration for enp3s0 - config: ifcfg-enp3s0
    Sat Jul 29 17:15:35 2017 info: info - network configuration for enp3s0 - onboot: enabled
    Sat Jul 29 17:15:35 2017 info: info - network configuration for enp3s0 - type: static
    Sat Jul 29 17:15:35 2017 info: info - network configuration for enp3s0 - wifi: disabled
    Sat Jul 29 17:15:35 2017 info: info - network configuration for enp3s0 - gateway: 10.0.0.138
    Sat Jul 29 17:15:35 2017 info: enp3s0 - network - IP address - 10.0.0.142
    Sat Jul 29 17:15:35 2017 info: enp3s0 - network - gateway - 10.0.0.138
    Sat Jul 29 17:15:35 2017 info: enp3s0 - network - type - private IP range
    Sat Jul 29 17:15:36 2017 info: system - changing active WAN list - enp3s0 (was startup)
    Sat Jul 29 17:15:36 2017 info: system - current WANs in use - enp3s0
    Sat Jul 29 17:15:36 2017 info: system - restarting firewall
    Sat Jul 29 17:17:49 2017 info: system - syswatch terminated
    Sat Jul 29 17:20:07 2017 info: system - syswatch started

    Hearbeat stops and syswatch crashed and do not restart until reboot @ 17:20
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, July 29 2017, 09:45 PM - #Permalink
    Resolved
    0 votes
    Here is the /var/log/boot.log :
    [root@home log]# cat boot.log
    [ OK ] Started Show Plymouth Boot Screen.
    [ OK ] Reached target Paths.
    [ OK ] Reached target Basic System.
    Mounting Configuration File System...
    [ OK ] Mounted Configuration File System.
    [ OK ] Found device /dev/mapper/clearos-root.
    Starting File System Check on /dev/mapper/clearos-root...
    [ OK ] Started dracut initqueue hook.
    Starting dracut pre-mount hook...
    [ OK ] Reached target Remote File Systems (Pre).
    [ OK ] Reached target Remote File Systems.
    systemd-fsck[933]: root: clean, 150988/366480 files, 971090/1465344 blocks
    [ OK ] Started File System Check on /dev/mapper/clearos-root.
    [ OK ] Started dracut pre-mount hook.
    Mounting /sysroot...
    [ OK ] Mounted /sysroot.
    [ OK ] Reached target Initrd Root File System.
    Starting Reload Configuration from the Real Root...
    [ OK ] Started Reload Configuration from the Real Root.
    [ OK ] Reached target Initrd File Systems.
    [ OK ] Reached target Initrd Default Target.

    Welcome to ClearOS 7 (Final)!

    [ OK ] Stopped Switch Root.
    [ OK ] Stopped Journal Service.
    Starting Journal Service...
    [ OK ] Listening on udev Kernel Socket.
    Mounting Debug File System...
    [ OK ] Listening on LVM2 metadata daemon socket.
    Mounting Huge Pages File System...
    [ OK ] Listening on /dev/initctl Compatibility Named Pipe.
    [ OK ] Listening on Delayed Shutdown Socket.
    [ OK ] Listening on LVM2 poll daemon socket.
    [ OK ] Created slice User and Session Slice.
    [ OK ] Reached target Slices.
    Mounting NFSD configuration filesystem...
    [ OK ] Listening on udev Control Socket.
    [ OK ] Reached target Host and Network Name Lookups.
    Mounting POSIX Message Queue File System...
    [ OK ] Listening on Device-mapper event daemon FIFOs.
    Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
    [ OK ] Set up automount Arbitrary Executable File Formats File System Automount Point.
    [ OK ] Created slice system-getty.slice.
    [ OK ] Stopped File System Check on /dev/mapper/clearos-root.
    Stopping File System Check on /dev/mapper/clearos-root...
    Starting Collect Read-Ahead Data...
    [ OK ] Created slice system-systemd\x2dfsck.slice.
    Starting Replay Read-Ahead Data...
    [ OK ] Created slice system-selinux\x2dpolicy\x2dmigrate\x2dlocal\x2dchanges.slice.
    [ OK ] Stopped target Switch Root.
    [ OK ] Stopped target Initrd Root File System.
    [ OK ] Stopped target Initrd File Systems.
    [ OK ] Reached target RPC Port Mapper.
    [ OK ] Mounted Debug File System.
    [ OK ] Mounted Huge Pages File System.
    [ OK ] Mounted POSIX Message Queue File System.
    [ OK ] Started Collect Read-Ahead Data.
    [ OK ] Started Journal Service.
    [ OK ] Started Replay Read-Ahead Data.
    [FAILED] Failed to mount NFSD configuration filesystem.
    See 'systemctl status proc-fs-nfsd.mount' for details.
    [DEPEND] Dependency failed for GSSAPI Proxy Daemon.
    [DEPEND] Dependency failed for NFS Mount Daemon.
    [DEPEND] Dependency failed for NFS server and services.
    [DEPEND] Dependency failed for NFSv4 ID-name mapping service.
    Starting File System Check on Root Device...
    Starting Load legacy module configuration...
    Starting Apply Kernel Variables...
    Starting Create Static Device Nodes in /dev...
    [ OK ] Started LVM2 metadata daemon.
    Starting LVM2 metadata daemon...
    [ OK ] Started Apply Kernel Variables.
    [ OK ] Started Load legacy module configuration.
    [ 14.066156] systemd-fsck[1036]: root: clean, 150988/366480 files, 971090/1465344 blocks
    [ OK ] Started File System Check on Root Device.
    Starting Remount Root and Kernel File Systems...
    [ OK ] Started Create Static Device Nodes in /dev.
    [ OK ] Started Remount Root and Kernel File Systems.
    Starting udev Coldplug all Devices...
    Starting Configure read-only root support...
    Starting udev Kernel Device Manager...
    [ OK ] Started Configure read-only root support.
    [ OK ] Started udev Kernel Device Manager.
    [ OK ] Started udev Coldplug all Devices.
    Starting udev Wait for Complete Device Initialization...
    [ OK ] Created slice system-lvm2\x2dpvscan.slice.
    Starting LVM2 PV scan on device 8:32...
    Starting LVM2 PV scan on device 8:64...
    [ OK ] Found device WDC_WD50EZRX-00MVLB1 primary.
    Starting LVM2 PV scan on device 8:128...
    Starting LVM2 PV scan on device 8:96...
    Starting LVM2 PV scan on device 8:144...
    Starting LVM2 PV scan on device 8:112...
    [ OK ] Found device Samsung_SSD_850_EVO_500GB boot.
    [ OK ] Found device ST8000VN0002-1Z8112 DD_8T_btfrs.
    [ OK ] Found device Samsung_SSD_850_EVO_500GB swap-0.
    [ OK ] Found device WDC_WD1500HLFS-01G6U4 VMwareActive.
    [ OK ] Found device WDC_WD6401AALS-00L3B2 Home.
    Activating swap /dev/disk/by-uuid/596ec92a-d8bd-4483-9c2b-a7c8f6f292f4...
    Starting LVM2 PV scan on device 65:32...
    Starting LVM2 PV scan on device 65:16...
    Starting LVM2 PV scan on device 65:0...
    Starting LVM2 PV scan on device 8:176...
    Starting LVM2 PV scan on device 8:208...
    Starting LVM2 PV scan on device 8:192...
    Starting LVM2 PV scan on device 8:3...
    Starting LVM2 PV scan on device 8:160...
    [ OK ] Activated swap /dev/disk/by-uuid/596ec92a-d8bd-4483-9c2b-a7c8f6f292f4.
    [ OK ] Reached target Swap.
    [ OK ] Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
    [ OK ] Reached target Local File Systems (Pre).
    Starting File System Check on /dev/disk/by-uuid/6c9938f4-d56e-4e01-8349-a1425e013d18...
    Starting File System Check on /dev/disk/by-uuid/4aab1eba-0d5b-4ad8-9e56-85254bff5762...
    Starting File System Check on /dev/disk/by-uuid/6a5f88d2-d2a9-4364-b6ce-4c5ef1b9c58b...
    Starting File System Check on /dev/disk/by-uuid/056d0cdf-39da-4542-ad88-61fd1683e74f...
    Starting File System Check on /dev/disk/by-uuid/91bf4505-001b-4e9d-9e58-d7aea5f33cff...
    [ OK ] Started File System Check on /dev/disk/by-uuid/6c9938f4-d56e-4e01-8349-a1425e013d18.
    [ 14.529899] systemd-fsck[1271]: boot: clean, 362/38400 files, 55618/153600 blocks
    [ OK ] Started File System Check on /dev/disk/by-uuid/056d0cdf-39da-4542-ad88-61fd1683e74f.
    [ 14.566075] systemd-fsck[1269]: Home: clean, 39447/39075840 files, 35507139/156282320 blocks
    [ 14.566984] systemd-fsck[1270]: VMwareActive: clean, 35/9150464 files, 17538262/36596062 blocks
    [ OK ] Started File System Check on /dev/disk/by-uuid/91bf4505-001b-4e9d-9e58-d7aea5f33cff.
    Mounting /store/dd_8T_btrfs...
    Mounting /boot...
    Mounting /store/dd_5T_btrfs...
    [ OK ] Mounted /boot.
    [ OK ] Started File System Check on /dev/disk/by-uuid/6a5f88d2-d2a9-4364-b6ce-4c5ef1b9c58b.
    Mounting /store/dd_vm...
    [ OK ] Mounted /store/dd_vm.
    [ OK ] Started File System Check on /dev/disk/by-uuid/4aab1eba-0d5b-4ad8-9e56-85254bff5762.
    Mounting /store/dd_500G_torrent...
    [ OK ] Mounted /store/dd_500G_torrent.
    Mounting /sapmnt...
    Mounting /usr/sap...
    Mounting /cal...
    Mounting /sybase...
    [ OK ] Mounted /sapmnt.
    [ OK ] Mounted /usr/sap.
    [ OK ] Mounted /sybase.
    [ OK ] Mounted /cal.
    [ OK ] Started udev Wait for Complete Device Initialization.
    Starting Activation of DM RAID sets...
    [ OK ] Started LVM2 PV scan on device 8:144.
    [ OK ] Started LVM2 PV scan on device 8:112.
    [ OK ] Found device /dev/WD_Group/Store.
    [ OK ] Started LVM2 PV scan on device 65:16.
    Starting File System Check on /dev/WD_Group/Store...
    [ OK ] Started LVM2 PV scan on device 8:192.
    [ OK ] Started Activation of DM RAID sets.
    [ OK ] Reached target Encrypted Volumes.
    [ 15.838689] systemd-fsck[1389]: Film_Part: clean, 66021/610467840 files, 2047466149/2441848832 blocks
    [ OK ] Started File System Check on /dev/WD_Group/Store.
    Mounting /store/lv_store...
    [ OK ] Started LVM2 PV scan on device 65:32.
    [ OK ] Found device /dev/mapper/clearos-home.
    [ OK ] Started LVM2 PV scan on device 8:3.
    [ OK ] Found device /dev/mapper/clearos-var.
    Starting File System Check on /dev/mapper/clearos-var...
    Starting File System Check on /dev/mapper/clearos-home...
    [ 15.964928] systemd-fsck[1446]: var: clean, 8130/732960 files, 1226691/2929664 blocks
    [ OK ] Started File System Check on /dev/mapper/clearos-var.
    [ 15.967920] systemd-fsck[1447]: home: clean, 28/28901376 files, 1865641/115601408 blocks
    Mounting /var...
    [ OK ] Started File System Check on /dev/mapper/clearos-home.
    Mounting /home...
    [ OK ] Mounted /var.
    Starting Flush Journal to Persistent Storage...
    Starting Load/Save Random Seed...
    [ OK ] Started Load/Save Random Seed.
    [ OK ] Started Flush Journal to Persistent Storage.
    [ OK ] Mounted /home.
    Mounting /home/rtorrent...
    [ OK ] Mounted /home/rtorrent.
    Mounting /var/flexshare/shares/torrent.watch...
    [ OK ] Started LVM2 PV scan on device 8:208.
    [ OK ] Mounted /var/flexshare/shares/torrent.watch.
    [ OK ] Started Device-mapper event daemon.
    Starting Device-mapper event daemon...
    [ OK ] Mounted /store/lv_store.
    Mounting /var/flexshare/shares/films...
    Mounting /var/flexshare/shares/iso...
    Mounting /var/flexshare/shares/divx...
    Mounting /home/rtorrent/complete/films/vus...
    Mounting /home/rtorrent/complete/iso...
    Mounting /var/flexshare/shares/mes_iso...
    Mounting /home/rtorrent/complete/films/a_voir...
    [ OK ] Mounted /var/flexshare/shares/films.
    [ OK ] Mounted /home/rtorrent/complete/films/vus.
    [ OK ] Mounted /home/rtorrent/complete/iso.
    [ OK ] Mounted /var/flexshare/shares/mes_iso.
    [ OK ] Mounted /var/flexshare/shares/divx.
    [ OK ] Mounted /var/flexshare/shares/iso.
    [ OK ] Mounted /home/rtorrent/complete/films/a_voir.
    [ OK ] Started LVM2 PV scan on device 8:32.
    [ OK ] Started LVM2 PV scan on device 8:96.
    [ OK ] Started LVM2 PV scan on device 65:0.
    [ OK ] Started LVM2 PV scan on device 8:176.
    [ OK ] Started LVM2 PV scan on device 8:160.
    [ OK ] Found device /dev/WD_6T_Red/Raid1.
    Starting File System Check on /dev/WD_6T_Red/Raid1...
    [ OK ] Started File System Check on /dev/WD_6T_Red/Raid1.
    Mounting /store/lv_raid...
    [ OK ] Started LVM2 PV scan on device 8:128.
    [ OK ] Started LVM2 PV scan on device 8:64.
    [ OK ] Mounted /store/lv_raid.
    Mounting /var/flexshare/shares/cpt.att...
    Mounting /home/dju...
    Mounting /var/flexshare/shares/home_lazer...
    Mounting /home/lazer...
    Mounting /var/flexshare/shares/commun...
    Mounting /var/flexshare/shares/mes_mp3...
    Mounting /var/flexshare/shares/raid...
    Mounting /home/rtorrent/complete/mp3...
    Mounting /store/lv_raid_ROnly...
    Mounting /var/flexshare/shares/mp3...
    [ OK ] Mounted /var/flexshare/shares/raid.
    [ OK ] Mounted /var/flexshare/shares/commun.
    [ OK ] Mounted /home/rtorrent/complete/mp3.
    [ OK ] Mounted /var/flexshare/shares/mes_mp3.
    [ OK ] Mounted /var/flexshare/shares/home_lazer.
    [ OK ] Mounted /home/lazer.
    [ OK ] Mounted /home/dju.
    [ OK ] Mounted /var/flexshare/shares/cpt.att.
    [ OK ] Mounted /store/lv_raid_ROnly.
    [ OK ] Mounted /var/flexshare/shares/mp3.
    Mounting /var/flexshare/shares/raid_read_only...
    [ OK ] Mounted /var/flexshare/shares/raid_read_only.
    [ OK ] Mounted /store/dd_5T_btrfs.
    [ OK ] Mounted /store/dd_8T_btrfs.
    [ OK ] Reached target Local File Systems.
    Starting Import network configuration from initramfs...
    Starting Preprocess NFS configuration...
    Starting Tell Plymouth To Write Out Runtime Data...
    [ OK ] Started Preprocess NFS configuration.
    [ OK ] Started Import network configuration from initramfs.
    Starting Create Volatile Files and Directories...
    [ OK ] Started Tell Plymouth To Write Out Runtime Data.
    [ OK ] Started Create Volatile Files and Directories.
    Starting Security Auditing Service...
    Mounting RPC Pipe File System...
    [FAILED] Failed to mount RPC Pipe File System.
    See 'systemctl status var-lib-nfs-rpc_pipefs.mount' for details.
    [DEPEND] Dependency failed for RPC security service for NFS server.
    [DEPEND] Dependency failed for RPC security service for NFS client and server.
    [ OK ] Reached target NFS client services.
    [ OK ] Reached target Remote File Systems (Pre).
    [ OK ] Reached target Remote File Systems.
    [ OK ] Started Security Auditing Service.
    Starting Update UTMP about System Boot/Shutdown...
    [ OK ] Started Update UTMP about System Boot/Shutdown.
    [ OK ] Reached target System Initialization.
    [ OK ] Listening on RPCbind Server Activation Socket.
    [ OK ] Reached target Paths.
    [ OK ] Reached target Timers.
    [ OK ] Listening on UUID daemon activation socket.
    [ OK ] Listening on D-Bus System Message Bus Socket.
    [ OK ] Listening on Name Service Cache Daemon Socket.
    [ OK ] Reached target Sockets.
    [ OK ] Reached target Basic System.
    Starting LSB: Bring up/down networking...
    Starting VirtualBox Linux kernel module...
    [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
    Starting Self Monitoring and Reporting Technology (SMART) Daemon...
    Starting Initialize hardware monitoring sensors...
    Starting Network Time Service...
    Starting Resets System Activity Logs...
    Starting SASL authentication daemon....
    Starting Name Service Cache Daemon...
    Starting Dump dmesg to /var/log/dmesg...
    Starting ACPI Event Daemon...
    Starting Login Service...
    Starting Authorization Manager...
    [ OK ] Started irqbalance daemon.
    Starting irqbalance daemon...
    Starting Load CPU microcode update...
    Starting Permit User Sessions...
    [ OK ] Started D-Bus System Message Bus.
    Starting D-Bus System Message Bus...
    [FAILED] Failed to start VirtualBox Linux kernel module.
    See 'systemctl status vboxdrv.service' for details.
    [ OK ] Started Network Time Service.
    [ OK ] Started Resets System Activity Logs.
    [ OK ] Started SASL authentication daemon..
    [ OK ] Started Name Service Cache Daemon.
    [ OK ] Started Dump dmesg to /var/log/dmesg.
    [ OK ] Started ACPI Event Daemon.
    [FAILED] Failed to start Login Service.
    See 'systemctl status systemd-logind.service' for details.
    [FAILED] Failed to start Authorization Manager.
    See 'systemctl status polkit.service' for details.
    [DEPEND] Dependency failed for Dynamic System Tuning Daemon.
    [ OK ] Started Load CPU microcode update.
    [ OK ] Started Permit User Sessions.
    [FAILED] Failed to start Initialize hardware monitoring sensors.
    See 'systemctl status lm_sensors.service' for details.
    [FAILED] Failed to start LSB: Bring up/down networking.
    See 'systemctl status network.service' for details.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, July 29 2017, 04:01 PM - #Permalink
    Resolved
    0 votes
    After wiating it's finished with the following screen.
    Where the first error is : Failed to start Authorization Manager
    The reply is currently minimized Show
Your Reply