Does this keypass error look familiar? This isn’t the first time I’ve seen it in OpenSUSE, but I can’t remember where else this cropped up before exactly. But the fix is easy. There’s a library that’s installed on the system already, but missing in the code.

I’m attempting to use a Windows Active Directory for user authentication in an OpenSUSE Linux environment. The configuration tools in OpenSUSE’s Yast take care of just about everything, or try to at least. But I found one instance where a default samba setting just doesn’t make the cut.

If your kernel is compiled with CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y you can rotate the framebuffer console output to match your rotated monitors.

The code above loops through a bunch of color codes, exporting the GREP_COLOR variable for each one and grepping something with that color highlighting from /proc/meminfo, a place all linux users should have available and get output from.

So your cluster service wont start because it’s in a failed state caused from the service attempting to start but failing too many times in too short of a time period (based on your cluster.conf retries and remember policy) or, more likely it’s failing to shutdown cleanly.

Manually enabling the service fails, right?

# clusvcadm -e host1service

Checking syslog, you will see the service refusing to start and the reason why. In this case it’s complaining it failed to stop cleanly, but the road block is really that it’s in a failed state.

# tail /var/log/messages
rgmanager: Service:host1service has failed; can not start.
rgmanager: Service:host1service failed to stop cleanly

Assuming cluster.conf is valid because you ran ccs_config_validate and it told you so, the problem is probably pretty simple. If a service is in a failed state, you can’t enable it unless you disable it first!

Perhaps this functionality is to stop you from starting a failed service because it’s already tried to start up a number of times and couldn’t already, so what’s the point of another try? In my case, what’s the harm? It’s already failed again and again. Why not just retry it when I step in and manually ask for the service to start?!

Oh well, … Read More »

Backing up an OpenLDAP installation is a very easy and non-intrusive process. You can backup the database while the old slapd is running using slapcat, so there’s no need for interruption while setting up the new instance. In my example, I will not backup individual databases with -n switch. I want the whole thing in one giant ldif because i’m going to restore the whole thing at once too. Keep it simple.

Send the USR1 signal to the pid using the kill command. Sending -9 or -15 will most definitely kill the dd, but sending the USR1 signal will output the current progress instead.