Vague Message of the Day

What you’re about to read is true. The name has been changed to protect the idiot…

My computer allows me to log in sometime, I dont know why. Could you please help me with this issue.

–
Best Regards,

Manny Shevitz

This just came in as a trouble ticket

Status: New

Queue: Tech. Svc. Help Desk

Summary: Flies in men’s bathroom

Details: We have small flies that keep appearing in the men’s and women’s bathrooms in our office.

jonas says: Get bigger pants, get bigger flies.

E-mail from SysAdmin:

The new datasource DataSourceName has been created on both development and production environments.

E-mail from Developer:

Please send me the name of the Datasource so I can change it in my application.

Subject: DBA Customer Requests

Body: Need privilege

Jonastio:  Don’t we all?

From: Sr. Sysadmin and DBA
To: Me
Subject: SElinux and config.sh

SElinux is preventing me from running config.sh on hostname1. I can run config.sh on hostname2, what could be causing that?

From: Me
To: Sr. Sysadmin and DBA
Subject: Re: SElinux and config.sh

selinux should be disabled on both of those hosts. Do you have strace output, or audit logs indicating that somehow selinux was the culprit?

From: Sr. Sysadmin and DBA
To: Me
Subject: Re: SElinux and config.sh

I checked, and selinux is disabled on both, and I rebooted just to make sure. Where would I find audit logs or strace output?
all I get is “bash: ./config.sh: Permission denied”

From: Me
To: Sr. Sysadmin and DBA
Subject: Re: SElinux and config.sh

[root@hostname1 bin] # ls -l config.sh
-rw-rw-r– 1 weblogic weblogic 4952 2008-09-03 09:21 config.sh

Editorial note: Weblogic is installed from an RPM; and has all file permission correct after installation; so somebody *cough* had to manually change the permissions at some point. Because the machine was just built from Kickstart, and only one Admin had logged in, my guess is it was the same admin who decided that “selinux was preventing him running config.sh”

From: Alleged UNIX System Administrator
To: Me
Subject: RE: Application in weblogic domain

Hmm…
[weblogic@hostname ~]$ confignode –domain=WebLogicDomain
Starting WebLogic NodeManager for weblogic on :5555
Enter UNIX password for user weblogic:
Cannot open /home/weblogic/.ssh/known_hosts for writing at /opt/weblogic/libexec/enrollNodes line 103.
[weblogic@hostname ~]$

From: Me
To: Alleged UNIX System Administrator
Subject: RE: Application in weblogic domain

That error means that somehow /home/weblogic/.ssh/known_hosts was not writable to user weblogic.

Ensure /home/weblogic/.ssh exists and is writable to user weblogic, and make sure /home/weblogic/.ssh/known_hosts is writable to user weblogic, and try it again.

From: Alleged UNIX System Administrator
To: me
Subject: RE: Application in weblogic domain

Both conditions are true; same result on rerun.

From: Me
To: Alleged UNIX System Administrator
Subject: RE: Application in weblogic domain

[weblogic@hostname ~]$ ls -al ~/.ssh/known_hosts
-rw-r–r– 1 root root 1737 Jul 14 14:25 ~/.ssh/known_hosts

From: Weblogic and Systems Administrator
Subject: Cannot start managed server — stacktrace

How do I clear the lock for the managed server, as per the stacktrace below
<snip>

From: Me
Subject: Re: Cannot start managed server — stacktrace

If you look at the server on which the managed-server is deployed, you will see that again, the server is running, and again, if you attempt to interrogate it, it just sits and spins. And so, again, the solution is to kill the server; and possibly restart nodemanager to be “safe”.

If however, you ever encountered a situation where it was claimed that the Lock was in use, but the server was not running, the lockfile is (for managed servers) in $NODEMGR_HOME/<servername>/ldap/ldapfiles/EmbeddedLDAP.lok. Removing that lock file would clear the condition.

From: Weblogic and Systems Administrator
Subject: Re: Cannot start managed server — stacktrace

It looks like a bad application deployment. After removing $NODEMGR_HOME/<servername>/ldap/ldapfiles/EmbeddedLDAP.lok I get the following stack-trace:
<snip>

From: Me
Subject: Re: Cannot start managed server — stacktrace

So, I’m guessing you skimmed over the part of my email where I said ‘And so, again, the solution is to kill the server; and possibly restart nodemanager to be “safe”.’ And jumped strait to the part where it said that if a server was NOT running, that you could clear the lock by removing the lock file.

Of course, in this circumstance, as I stated, the server IS running, (pid 6544), and so clearing the lock without killing the process, and restarting a new process writing to the locked file likely corrupted the embedded LDAP store beyond all repair.

So, at this moment, on the server, run:

kill -15 6544; sleep 2; kill -9 6544
/etc/init.d/wlnm restart


and try to start the managed server again from the admin console. If it is unable to start, you will need to do the following:


rm -rf /u01/app/bea/nodemanager/SomeDomainSrv1/
/etc/init.d/wlnm restart


From: Weblogic and Systems Administrator
Subject: Re: Cannot start managed server — stacktrace

Looks like the lock problem still exists, regardless. I’ll kill the process and restart node manager.

We’re doin the ol’ switcharoo.  I got plumb sick and tired of *constantly* deleting a metric shitton of spam from the old blog proggy.  I’ve used this proggy before and the anti-comment-spam features are pretty slick.

That and I’m a little more familiar with this interface.  I’m going to be tweaking the interface a bit over the course of the next couple of days.  The php in wordpress themes is pretty easy to wade through so I should have something a bit more respectable than the old site up pretty soon.  Not like anyone really READS this shit.  Except for the bots.  That leave the goddamn spam.  Which is why I’m having to do this switch.

Bastards.

From: IT Specialist
Subject: Missing files

Hi, I think server107 might be having disk errors. I removed the file “~” and now all my files are missing.

From: IT Specialist
Subject: SSH is down
I’m trying to telnet via ssh to a server, but ssh keeps hanging and timing out:

C:\>telnet servername 22
Trying 1.2.3.4…
Connected to servername (1.2.3.4).
Escape character is ‘^]’.
SSH-2.0-OpenSSH_4.3