Topic: Strange error on admin login

[Alex Schaft]

Hi,

When trying to su admin from a root shell, I get "Real UID cannot exec script".

I also can't login directly?

What causes this?

Alex

[byte]

Any base problems please report to bug tracker making sure you give full history and/if you have changed/added anything

[hulyom]

I have posted this bug a week ago as Bug #2802 on http://bugs.contribs.org/show_bug.cgi?id=2802  but there is no any answer since then

[root@srvr2 ~]# su - admin
Real UID cannot exec script

any clue?

[pmstewart]

When trying to su admin from a root shell, I get "Real UID cannot exec script".

I'm no expert by any means with this stuff.....but it occurs to me the admin account for SME is an alias of root.

What leads me to this conclusion is when you log on using the shell under admin it should present you with the "SME Console" which is the shell partner to server-manager. Login to server-manger is done by admin username but has root permission. Mail for root is received by admin...etc.
The templating system gives them different jobs but root and admin seem to be fairly inter-related.

It's also my understanding if your logged on at a console or through a terminal session as "root" the "su" function is unnecessary.

Since no other information was given - such as SME version, method of logging in (say putty or consolel) or code being executed it may be a little hard to simply say there is a bug.

Like I said.....I ain't no expert - simply sharing an observation.

[hulyom]

Well, thanks for trying to help but the problem is that I can not access to server-manager from my web browser (or console), so I am trying to fix the problem accessing with admin user, but it kicks me out, so the only way to do is "su - admin" but you know the result...

I can access the console ( /sbin/e-smith/console ) from root I can access and fix the problem, but my question is:

if I run the console as root and fix the problem with the option 4 (reconfigure) will I have problems because of permissions with admin in the future?

Well and whole the explanation is on the bug link, so there is no very much point writing it again

Thanks

[bpivk]

Run signal-event post-upgrade and signal-event reboot and see if that solves your problem.

It's also my understanding if your logged on at a console or through a terminal session as "root" the "su" function is unnecessary.

Not exactly correct. su command is uset to switch users so it is necessary. Well not if you have a root account enabled but it would be usefull if you would use a normal user account and then su root to switch to your root account. I hope that this helped.