UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1282 views

Remote Manage cant be accessed by Admin

I am running SLES 11 SP3 / OES11 SP2 and for some reason the admin account can no longer access the Remote Manager but the Root user can. I did an "id admin" and it says No such user.

I checked in Imanager and it shows that the admin account has LUM values. I used to be able to access it but not sure when it stopped working.

What could be wrong?

Sincerely,
Ken
Labels (2)
0 Likes
8 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Is LUM's service (namcd) working on the system? If you run 'getent
passwd' do any eDirectory-provided users show up? Feel free to post your
/etc/nam.conf for review, and include details about what all of the IP
addresses in there are. It may be worthwhile to restart the namcd
service, or do some tracing on the eDirectory box to which LUM/namcd is
pointed to see if anything shows up there when you try things like
authenticating.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Absent Member.
Absent Member.

I was forced to do a hard shutdown this afternoon cause the server was hung while trying to login as root. Once I did a hard shutdown, it took a very long time to boot but it finally did. I did an id admin and it showed the LUM information this time and it also shows up when I did a getent passwd. However it still does not want to access Remote Manager and it logs an error in the messages log.

I have also found that it hangs after a little bit of being logged in. This server is running on VMware 5.0 and looking at the performance it goes from using the 4GB of Ram down almost 200MB of ram usage.

Sincerely,
Ken
0 Likes
Absent Member.
Absent Member.

OK I have gotten the nam.conf file but dont see how to attach it.

Ken
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Since it's usually on a dozen lines long or so it's probably easiest to
paste it within CODE tags (the '#' button at the bottom if using the
web-based interface to the forums).

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Absent Member.
Absent Member.

The following is the nam.conf (192.168.x.x is the Main server with the Master Replica)

base-name=O=RLMILLIES
workstation-context=O=RLMILLIES
admin-fdn=cn=admin,o=rlmillies
preferred-server=192.168.x.x.
num-threads=10
max-privfile-size=100
schema=rfc2307
enable-persistent-cache=yes
user-hash-size=211
group-hash-size=211
persistent-cache-refresh-period=28800
persistent-cache-refresh-flag=all
create-home=yes
type-of-authentication=2
certificate-file-type=der
ldap-ssl-port=636
ldap-port=389
support-alias-name=no
support-outside-base-context=yes
cache-only=no
persistent-search=no
one-exclude-deny-service=no
case-sensitive=no
convert-lowercase=no
log-level=0
umask=0022
nam-nss-timeout=60

Thanks,
Ken
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Looking at this, combined especially with your feedback earlier that the
'id admin' command is now working, I'm guessing LUM is fine. Next is
probably to troubleshoot NRM specifically, which is not a specialty of mine.

Perhaps NRM uses PAM, in which case seeing your /etc/nsswitch.conf file
along with some details in /etc/pam.d could potentially help, but that's
just a guess.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Absent Member.
Absent Member.

ab;2350911 wrote:
Looking at this, combined especially with your feedback earlier that the
'id admin' command is now working, I'm guessing LUM is fine. Next is
probably to troubleshoot NRM specifically, which is not a specialty of mine.

Perhaps NRM uses PAM, in which case seeing your /etc/nsswitch.conf file
along with some details in /etc/pam.d could potentially help, but that's
just a guess.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...


Is there a way to roll back updates? I did some updates on Sunday that may be making things worse. I used the Yast Online updater.

Assuming I can login to the server again is there a quick way to make a roll back?

Sincerely,
Ken
0 Likes
Absent Member.
Absent Member.

OK I always forget that we are paying for a maintenance agreement therefore we have tech support. Anyway, tech support found that the server certificates expired last week and was able to re-validate them. Once the certificates were reloaded everything is fine again.

ab - thanks for taking the time to look at and help out with this. Its people like you on this forum that has kept this forum a useful resource.

Thanks again,
Ken
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.