Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: mercyh on December 08, 2009, 05:06:05 PM
-
Hi,
I have an SME that I have inherited with a consulting job I have accepted. I do not know the history of this server. It is current with updates and I can run updates from server manager.
For some reason I cannot login as admin on the console of the server. Root login works fine but if I try to SU to admin in putty it gives the following error:
[root@mail ~]# su admin
Real UID cannot exec script
If I try to login directly as admin the putty session is immediately closed.
I get the same result directly from the server console as putty.
I have googled this and have been unable to find a satisfactory answer.
Has anyone seen this behavior before and do you have a suggestion of how to fix it?
Thanks in advance
-
what if you give
console
as root?
-
mercyh:
http://bugs.contribs.org/show_bug.cgi?id=2802 (http://bugs.contribs.org/show_bug.cgi?id=2802)
-
Stefano,
Thanks a million, I didn't know about the console command. I also had searched but did not find the bugs you referenced :-?
I have not looked at the groups issue but I am pretty sure we would be over the limit on this.
Royce
-
further research with problem still not resolved
console
at the root login takes me to a # prompt
after removing unnecessary groups to get the number of groups below 32, I no longer get the "Real UID cannot exec script error" but have the following results:
Login as admin directly in putty immediately closes the putty session.
su admin at the root prompt takes me to a # prompt
"I sure wish i knew the history of this server. It is a DC in a 20 user Domain and I am reluctant to do anything drastic while it is mostly working"
-
after removing unnecessary groups to get the number of groups below 32, I no longer get the "Real UID cannot exec script error" but have the following results:
Login as admin directly in putty immediately closes the putty session.
su admin at the root prompt takes me to a # prompt
Any clues in the log files, e.g. in /var/log/messages around the time you observed this behavior?
"I sure wish i knew the history of this server. It is a DC in a 20 user workgroup and I am reluctant to do anything drastic while it is mostly working"
A shot in the dark, but what is the output of:
db accounts show admin
-
A shot in the dark, but what is the output of:
db accounts show admin
really no clues here that I can see
admin=system
EmailForward=both
FirstName=Local
ForwardAddress=reports@moundridgemanor.net
LastName=Administrator
Lockable=no
PasswordSet=yes
Removable=no
Shell=/sbin/e-smith/console
VPNClientAccess=no
Will do some more research in the log files.
-
really no clues here that I can see
Nope, this looks OK to me as well.
-
another thing I found. I executed the following as root:
[root@mail ~]# /sbin/e-smith/console
Can't exec "/usr/bin/dialog": No such file or directory at /usr/lib/perl5/site_perl/esmith/console.pm line 184.
Couldn't exec:: No such file or directory
I thought I was getting no response when I issued
su admin
however if I scroll the putty window back up I find that same error.
Thanks a lot for your help in pointing me the right direction so far.....
-
[root@mail ~]# /sbin/e-smith/console
Can't exec "/usr/bin/dialog": No such file or directory at /usr/lib/perl5/site_perl/esmith/console.pm line 184.
Couldn't exec:: No such file or directory
It seems that the file is not found or inaccessible. Do you have dialog installed?
rpm -q dialogIf not can you have a look throught your yum log files to see if it was removed somehow:
grep -A 5 -B 5 -i dialog /var/log/yum/yum.log*
Thanks a lot for your help in pointing me the right direction so far.....
No problem.
-
It seems to be there.
[root@mail ~]# rpm -q dialog
dialog-1.0.20040731-3
-
It seems to be there.
root@mail ~]# rpm -q dialog
dialog-1.0.20040731-3
And these:
ls -la /usr/bin/dialog
rpm -V dialog
-
Cactus,
You are getting over my head, I am following you blindly here so you will have to interpret the output for me.......
[root@mail ~]# ls -la /usr/bin/dialog
ls: /usr/bin/dialog: No such file or directory
[root@mail ~]# rpm -V dialog
missing /usr/bin/dialog
missing /usr/share/locale/ca/LC_MESSAGES/dialog.mo
missing /usr/share/locale/cs/LC_MESSAGES/dialog.mo
missing /usr/share/locale/cy/LC_MESSAGES/dialog.mo
missing /usr/share/locale/da/LC_MESSAGES/dialog.mo
missing /usr/share/locale/de/LC_MESSAGES/dialog.mo
missing /usr/share/locale/el/LC_MESSAGES/dialog.mo
missing /usr/share/locale/es/LC_MESSAGES/dialog.mo
missing /usr/share/locale/et/LC_MESSAGES/dialog.mo
missing /usr/share/locale/eu/LC_MESSAGES/dialog.mo
missing /usr/share/locale/fr/LC_MESSAGES/dialog.mo
missing /usr/share/locale/hu/LC_MESSAGES/dialog.mo
missing /usr/share/locale/it/LC_MESSAGES/dialog.mo
missing /usr/share/locale/ja/LC_MESSAGES/dialog.mo
missing /usr/share/locale/nl/LC_MESSAGES/dialog.mo
missing /usr/share/locale/pl/LC_MESSAGES/dialog.mo
missing /usr/share/locale/pt/LC_MESSAGES/dialog.mo
missing /usr/share/locale/pt_BR/LC_MESSAGES/dialog.mo
missing /usr/share/locale/ru/LC_MESSAGES/dialog.mo
missing /usr/share/locale/uk/LC_MESSAGES/dialog.mo
missing d /usr/share/man/man1/dialog.1.gz
This doesn't look real promising to me.
One of the reasons I need to get to console is that I cannot yum from the command line, (I get the following error):
Setting up repositories
Cannot find a valid baseurl for repo: smeaddons
Error: Cannot find a valid baseurl for repo: smeaddons
and I need to see what is setup for network settings. I can use the software installer panel from server-manager just fine.
I may be needing to spend an afternoon onsite and just clean install this thing so I know what I have.
-
This is a little interesting:
[root@mail ~]# grep -A 5 -B 5 -i dialog /var/log/yum/yum.log*
/var/log/yum/yum.log-Mar 15 17:35:45 Installed: perl-Mail-SPF-Query.noarch 1.999.1-1.2.el4.rf
/var/log/yum/yum.log-Mar 15 17:35:45 Installed: mod_auth_tkt.i386 2.0.0rc1-4.2.el4.sme.of
/var/log/yum/yum.log-Mar 15 17:35:46 Installed: perl-Net_SSLeay.pm.i386 1.25-4.el4.at
/var/log/yum/yum.log-Mar 15 17:35:46 Installed: perl-IO-Socket-SSL.noarch 1.01-1.c4
/var/log/yum/yum.log-Mar 15 17:35:46 Installed: perl-IO-Zlib.noarch 1.04-1.2.el4.rf
/var/log/yum/yum.log:Mar 15 17:35:47 Installed: dialog.i386 1.0.20040731-3
/var/log/yum/yum.log-Mar 15 17:35:47 Updated: e-smith-lib.noarch 1.18.0-8.el4.sme
/var/log/yum/yum.log-Mar 15 17:35:48 Updated: e-smith-manager.noarch 1.14.0-1.el4.sme
/var/log/yum/yum.log-Mar 15 17:35:49 Updated: e-smith-samba.noarch 1.14.0-26.el4.sme
/var/log/yum/yum.log-Mar 15 17:35:49 Updated: e-smith-nutUPS.noarch 1.2.0-8.el4.sme
/var/log/yum/yum.log-Mar 15 17:35:49 Updated: e-smith-grub.noarch 1.0.0-5.el4.sme
but quite inconclusive.
-
I would download the rpm and force the reinstall..
-
I would download the rpm and force the reinstall..
I would do so as well, but perhaps this might work as well:
rpm -e --nodeps dialog
yum install dialog
-
That looks like the correct answer to me also. I will wait until a weekend or maybe over Christmas holidays and give it a shot.
Will report back once it is complete.
Thanks again for all your help and Happy Holidays to all...............
Royce
-
Just a note,
The sad thing about the location I am working on with this server is that it is moving to Windows Server 2008 in the middle of January. Their main application is built on Microsoft SQL server. The MS licensing alone for 25 users is around US $9,500.
I will not have contribs.org for reference and pointers in troubleshooting these kinds of problems and I have not found a good replacement for the VPN DAR offsite backup I am using so they will be going back to rotating tapes for their backup.
Why can't software vendors see that using open source platforms allows them to charge more for their software rather then giving half of the cost of the install to MS??
PS> Just a little off topic rant and a Big Thanks to Contribs.org and the users and developers that make it so great........
-
You guys did it again.
I would do so as well, but perhaps this might work as well:
rpm -e --nodeps dialog
yum install dialog
I had to use Cactus'
rpm -e --nodeps dialog
Then I took Stefano's suggestion and went out to pbone.net, found the correct RPM, dropped it on the server and yum localinstalled it.
Console now works like it is supposed too.
thanks a lot for your help.
Royce