Are you trying to update Openldap global or config database configuration? Getting insufficient access error (50)?
So, What is the BIND dn (i.e username) you are using? The error simply says that BIND dn authentication successful but it does not have write access to database you are trying to modify.
# ldapmodify –axw ppsswwdd -D "cn=manager,dc=sunt,dc=com" -f db.ldif
modifying entry "olcDatabase={2}bdb,cn=config"
ldap_modify: Insufficient access (50)
On RHEL 6 LDAP client configuration involves editing multiple files such pam, nssswitch, authconfig etc. But “authconfig” command made it easier for us. I walk you through how it can be done in two steps.
Install client packages. openldap-clients pam_ldap nss-pam-ldapd
By default all user has access to command “su”. This command allows login to other user from current shell. Of course they should know target user password. The problem is you cannot have control/log of users once they switched successfully. What happens if the user by chance able to switch as root?
Desired secure method to switch across user is restrict “su” command. Enforce them to use “sudo” instead.
Linux kernel remounts the filesystem into read-only mode whenever it cannot process I/O. This might happen due to various reasons such as disk failure, SAN connectivity issue, disk with bad blocks etc. On Virtual machine and SAN based storage environment even the high latency may lead to I/O hung and result in read-only mode.
Debugging pacemaker cluster through logs will be much more easier post reading this article. This would help you in either troubleshooting or root cause analysis. It does not need any additional tools except your attention. Have reproduced and collected logs from various scenario to present here as example. I used SUSE 11 with HAE system for testing.
The first thing to do is look in system log for the terms ERROR and WARN.
#grep -e ERROR -e WARN /var/log/messages
Usually SUDO used by non-superuser to run command with root privileges. But in few scenario application/commands stick with it native user. Even with root user privileges it won’t work as expected. For example to run any oracle commands you need to be oracle user.
Here consider mission critical application “xapp1” and it uses user “app1”. Allowing others to login as app1 will result in trouble. The secure way is to allow user to execute limited commands as app1 user.
Using Xming & Putty can connect to remote Linux X-server from windows desktop. By this way you will be able to view remote server GUI from windows desktop. This avoids need of physical console access to server.
Because granting server console access to application or normal user is a bad idea. One of my user pressed Ctr+Alt+Del while working on VMware virtual machine console. Which made system to reboot.
Usage of sudo command alias and it various useful features with examples given.
Syntax
Cmnd_Alias NAME = cmnd1, cmnd2, cmnd3 ….
To define command alias in sudoers file must remember two hard coded rules
How does Pacemaker Corosync cluster operates? What is the relation between pacemaker and corosync? The functionality and concept overview has been explained here. SUSE Linux high availability and Redhat high availability using pacemaker corosync cluster majorly. Still many other flavors such as Ubuntu, Debian are using pacemaker with corosync as their high availability solution.
1. Password quality check for OpenLDAP
2. Configure password quality check – Openldap
There is no standard OpenLDAP module for password quality check. How to make OpenLDAP server to check the strength and quality of password? How to reject the password which does not meet desired standards? There is an alternate solution available.