Dudi,
Login to your box and do a "grep 0:0 /etc/passwd". You should get
at least two lines back, root, and root-admin. If root-admin is first
in the list, then that is why the system is saying you are root-admin.
Edit the passwd file and make sure the "root" entry is the first entry
in the file and see what that does. (If the root entry does not exist,
then copy the root-admin line and change it to say just "root" and
make that line first in the file).
--
Larry Smith
lesmith (at mark) ecsis.net
On Fri October 30 2009 05:34, Dudi Goldenberg wrote:
> Hello list,
>
>
>
> First post here for ~12 years...
>
>
>
> One of my BQ servers running BlueQuartz 5100R build 5102R has suddenly
> experienced some symptoms of a corrupted administrative db.
>
>
>
> I successfully converted the system to use flat files, but the symptoms
> were exactly the same, e.g. modquota.pl failing:
>
>
>
> Oct 28 00:45:32 tiger cced(smd)[4293]: handler
> handlers/base/disk/modquota.pl failed.
>
>
>
> After investigating, I found out that no matter what way I log in as
> root, be it console or ssh, I always end up logged as root-admin instead
> of root.
>
>
>
> The problem is the root-admin does not have sufficient group memberships
> to handle the required operations:
>
>
>
> [root@tiger ~]# id
>
> uid=0(root) gid=0(root)
> groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)
>
>
>
> [root@tiger ~]# id root-admin
>
> uid=0(root) gid=0(root) groups=0(root)
>
>
>
> So to resolve this I gave root-admin the required group memberships for
> now, and the machine functions Ok.
>
>
>
> Another symptom of this is that all files/directories that needs to be
> owned by root are owned by root-admin, group ownership of 'root' are not
> effected.
>
>
>
> I am not sure were this problem originated, could be one of the BQ-DEV
> yum updates but I am not sure.
>
>
>
> Pointers appreciated.
>
>
>
> Dudi Goldenberg
> CTO
> Kolcore Ltd.
> Registered Linux user #79506