SUMMARY: LSM startup "not privileged" error

From: Iain Barker (ibarker@aastra.com)
Date: Tue Mar 23 2004 - 12:28:56 EST


Many thanks to Roger Sars, Dr. Tom Blinn and Johan Brusche for their suggestions.

The cause of this problem is not really be due to user privilleges at all. The problem was that the SIA security subsystem had failed to initialise during the boot.

Adding a zero-length file /etc/sia/siainitgood as recommended by Johan and rebooting fixes the problem.

man siainit(8) for further details.

-----Original Message-----
From: tru64-unix-managers-owner@ornl.gov
[mailto:tru64-unix-managers-owner@ornl.gov]On Behalf Of Iain Barker
Sent: Tuesday, 23 March, 2004 06:53
To: tru64-unix-managers@ornl.gov
Subject: LSM startup "not privileged" error

I have a system that suffered a power outage. Now when I attempt to boot (even trying genvmunix) I get an error from voldiod "not privileged" - startup console logs below.

Any ideas how to recover from this?

lvm0: configured.
lvm1: configured.
lvm2: configured.
kernel console: ace0
i2c: Server Management Hardware Present
ADVFS: using 1308 buffers containing 10.21 megabytes of memory
Starting secondary cpu 1
You are not privileged to run voliod
lsm:vold: Warning: Plex swapvol-02 for swap volume is stale or unusable
INIT: SINGLE-USER MODE
#

thanks,
        Iain



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:55 EDT