From: Bencsath Boldizsar <boldi@datacontact.hu>
Subject: error messages at restart
Date: Tue, 13 Mar 2001 14:19:42 +0100 (CET)
Next Article (by Date): Oopses or hangs at system start revisited Amon Ott
Previous Article (by Date): kernel oops 2.4.2+raid+smp+pre5 Bencsath Boldizsar
Articles sorted by: [Date]
[Author]
[Subject]
The console log is here: after starting "reboot" the followings come up ( many EINVALIDDEV messages have been cut) Note, 03:05 is hda5 which is the root device. raid1d(10) flushing signals. md: recovery thread got woken up ... md: recovery thread finished ... mdrecoveryd(9) flushing signals. VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... rsbac_get_attr(): Could not lookup device! rsbac_adf_request(): rsbac_get_attr() for security_level returned EINVALIDDEV! rsbac_get_attr(): Could not lookup device! rsbac_adf_request(): rsbac_get_attr() for security_level returned EINVALIDDEV! ... rsbac_adf_set_attr(): rsbac_get_attr() for log_array_low returned error! rsbac_get_attr(): Could not lookup device! rsbac_adf_set_attr_rc(): rsbac_get_attr() returned error -1016! rsbac_get_attr(): Could not lookup device! rsbac_adf_set_attr_auth(): rsbac_get_attr() returned error! rsbac_get_attr(): Could not lookup device! rsbac_adf_request(): rsbac_get_attr() for log_program_based returned error! rsbac_get_attr(): Could not lookup device! rsbac_adf_set_attr(): rsbac_get_attr() for log_array_low returned error! rsbac_adf_set_attr(): request EXECUTE, caller_pid 405, target-type FILE, tid Device 3:5 Inode 31140 Path /bin/moun3 do_execve() [sys_execve]: rsbac_adf_set_attr() returned error rsbac_get_attr(): Could not lookup device! rsbac_adf_request(): rsbac_get_attr() for security_level returned EINVALIDDEV! .... rsbac_adf_set_attr(): rsbac_get_attr() for log_array_low returned error! rsbac_get_attr(): Could not lookup device! ... rsbac_adf_set_attr(): request EXECUTE, caller_pid 406, target-type FILE, tid Device 3:5 Inode 220020 Path /etc/ini3 do_execve() [sys_execve]: rsbac_adf_set_attr() returned error ... rsbac_adf_request(): request SEARCH, caller_pid 406, caller_prog_name S50raid2, caller_uid 0, target-type DIR, tidL rsbac_get_attr(): Could not lookup device! ... rsbac_adf_request(): request SEARCH, caller_pid 406, caller_prog_name S50raid2, caller_uid 0, target-type DIR, tidL rsbac_get_attr(): Could not lookup device! .. rsbac_adf_set_attr(): request EXECUTE, caller_pid 407, target-type FILE, tid Device 3:5 Inode 31147 Path /bin/sed,3 do_execve() [sys_execve]: rsbac_adf_set_attr() returned error ... rsbac_adf_request(): request SEARCH, caller_pid 407, caller_prog_name sed, caller_uid 0, target-type DIR, tid DeviL rsbac_get_attr(): Could not lookup device! ... rsbac_adf_set_attr(): request EXECUTE, caller_pid 408, target-type FILE, tid Device 3:5 Inode 217747 Path /etc/ini3 do_execve() [sys_execve]: rsbac_adf_set_attr() returned error rsbac_adf_set_attr_rc(): rsbac_get_attr() returned error -1016! rsbac_get_attr(): Could not lookup device! rsbac_adf_request(): request SEARCH, caller_pid 408, caller_prog_name S90reboot, caller_uid 0, target-type DIR, tiL rsbac_get_attr(): Could not lookup device! acl_lookup_device(): Invalid device 03:05 rsbac_acl_get_rights(): Could not lookup device! rsbac_acl_check_right(): rsbac_acl_get_rights() returned error RSBAC_EINVALIDDEV! rsbac_adf_request(): request SEARCH, caller_pid 408, caller_prog_name S90reboot, caller_uid 0, target-type DIR, tiL rsbac_get_attr(): Could not lookup device rsbac_adf_set_attr(): request EXECUTE, caller_pid 409, target-type FILE, tid Device 3:5 Inode 155593 Path /sbin/ha3 do_execve() [sys_execve]: rsbac_adf_set_attr() returned error rsbac_adf_request(): rsbac_get_attr() for security_level returned EINVALIDDEV! stopping all md devices. marking sb clean... md: updating md1 RAID superblock on device hda7 [events: 0000007f](write) hda7's sb offset: 2048192 hda6 [events: 0000007f](write) hda6's sb offset: 2048192 . md1 switched to read-only mode. Restarting system. -------------------------------- Bencsath Boldizsar boldi@etl.hu -------------------------------- - To unsubscribe from the rsbac list, send a mail to majordomo@rsbac.org with unsubscribe rsbac as single line in the body.
Next Article (by Date): Oopses or hangs at system start revisited Amon Ott
Previous Article (by Date): kernel oops 2.4.2+raid+smp+pre5 Bencsath Boldizsar
Articles sorted by: [Date]
[Author]
[Subject]