[Most Recent Entries]
Below are the 20 most recent journal entries recorded in
[ << Previous 20 ]
[ << Previous 20 ]
|Monday, November 15th, 2004|
Alright then, let's get this project started.
I need to create a Horde/IMP/Kronolith/Turba installation on serverA in CA.
I have logged in and unpacked the Horde framework tarball.
Now I am trying to figure out what is already on the server.
I assume I have to use the apache install that is already there. I don't know if it has all of what I need.
First thing I am going to do is try to connect to the existing apache install. This may require tunneling.
I will through up a phpinfo page( I need to look up the exact syntax again) to figure out what I have on there already.
|Tuesday, November 9th, 2004|
LDAP in Outlook
One of my goals today is to access the LDAP address book using Outlook.
The hard bit is creating the tunnel necessary to access the LDAP server.
I am going to try putty first, if that doesn't work, I have Cygwin. Nothing seems to be installed on it yet, but I will have to figure out how to use it sometime anyway.
Track my progress in comments. Current Mood: busy
|Thursday, October 28th, 2004|
Nothing like getting paid to motivate you
I have my perfect job. Flying out to meet the team tomorrow morning at the buttcrack of dawn.
The preferred mail client was not available for my old os, so I am installing a whole new os as the upgrade process from redhat to fedora core is messy. Fruck it, I am installing Debian.
If I don't get this running right in two hours, I am screwed.
Feels good to be back in the real world.
|Monday, October 11th, 2004|
A little birdy told me that my first project for my new job could be setting up a VPN. I will, of course, be researching openvpn. It looks better than most proprietary solutions. It may be a little harder to configure at first, but it doesn't really look that complicated and the ability to customize is important in a heterogeneous network.
Details of this project will be posted to this thread. Current Mood: groggy
|Wednesday, October 6th, 2004|
I am glad to see this is still here
All sorts of geek stuff going on and I haven't been documenting. Bad stormer, bad.
Current geekly doings:
I have a RH8 install updated to legacy with asterisk and a digium wildcard containing one fxo and one fxs module. Everything seems to be in working order, I just need to figure out how to configure.
I have installed FC2 on my main desktop. Took forever to get the sound working as I have an old isa sound card and Kmix defaults to zero volume as well as asound.stat (alsa?). Anywho, it all seems to be working great now. Previously I had used gnome but am using kde on two systems now. The difference to me seems minimal.
I am currently downloading and burning disks to distribute at GSLUG Saturday. I need to free up a box to test distros on.
More details soon.
|Wednesday, May 19th, 2004|
My albatross testing has been put aside for a bit as I create a fresh solaris 8 install. The install went fairly smoothly and the upgrades are happening now. The boss said it may take a long time, so I am doing some reading on jumpstart servers to be prepared for the next step in this project. Current Mood: blank
|Monday, May 17th, 2004|
I am currently using ab to test albatross mycompany software response time in a variety of situations. This data will be used to gain insight into a problem on a similar production server with client installations.
Ab is a program that comes with apache if you build it right.
Man ab and then feel free to peruse the comments to follow my progress. Current Mood: apathetic
|Tuesday, May 11th, 2004|
I am so bad.
I have been doing stuff without documenting it.
While you were out of the loop, I installed RedHat Enterprise Linux ES on an old Proliant server. 128M RAM oooh boy.
Now, instead of installing OTRS, I have been tasked with installing an instance of company software. It appears to be a webserver setup connected to some kind of database.
I have the skeleton of instructions for doing this from my boss. I need to flesh it out as I go.
I am already having a little trouble. One of the first steps is to tar up a directory at our remote location and bring it over to a office box. The boss says scp works through the firewall within the VPN, but I haven't had any luck.
I am thinking perhaps some kind of acl on the local machine I am trying to bring it to is not set up correctly.
Here's the syntax and error messages:
Server names have been changed to protect the guilty.
The boss said you have to call for the file from the office side.
enchiladas>scp -v firstname.lastname@example.org:/albatross/a
Everything seems to go well until:
Executing: program /usr/bin/ssh host enchiladas.office.mycompany.com, user me, command scp -v -t /tmp/
OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: Connecting to enchiladas.office.mycompany.com [someip] port 22.
. . . . .
debug1: connect to address someip port 22: Connection timed out
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: rcvd eof
debug1: channel 0: output open -> drain
debug1: channel 0: rcvd close
ssh: connect to host enchiladas.mycompany.com port 22: Connection timed out
I am off to check ssh_config for trusted network settings. Current Mood: working
|Wednesday, May 5th, 2004|
Next on the agenda
I am happily finished with the webmail move and forums have been updated.
It is about frickin' time.
Anyway, next on my plate is a RedHat Enterprise Linux ES install on a HP Proliant.
Fortunately, it currently has a functioning RedHat install, so I don't think I will need to screw with the bios config as a few sources have indicated may be necessary.
This server will be OTRS's new home. Current Mood: accomplished
|Monday, April 26th, 2004|
Oh boy, oh boy. First I took the time to move a bulletin board that hasn't been used in over a year and now I have to upgrade it. Current Mood: grumpy
|Tuesday, April 20th, 2004|
Now for the real thing.
The previous jailing process was practice for moving webmail over to the same system.
There have been some updates to our webmail software since the last install. I think I will move the current system, as it is and get it working before applying upgrades. I won't make the final switch until the upgrades are done. Current Mood: chipper
|Monday, April 19th, 2004|
Hi Mom! I'm in JAIL
Next on my work agenda is moving a currently functioning bulletin board site that is currently chrooted on network server it really shouldn't be on. My task is to create a jail for it on a more appropriate server and get it functioning in the jail environment. This is also practice for moving webmail over to the same system the same way.
If I am talking jails, I am talking FreeBSD. Current Mood: busy
|Wednesday, April 14th, 2004|
The power of root
rm -r * never ceases to make me nervous. I always double check my directory before using it, but it always gives me butterflies.
On the upside, I fixed imp today before anybody noticed it was broken. I restarted mysql and it was all better. Current Mood: nervous
|Tuesday, April 13th, 2004|
You know you are going to have a struggle getting service when the operator asks you what OS you are running and
"Free B S D"
"B as in boy, S as in Stan, D as in Dog?"
"Hold please. . ."
That was quite a few minutes ago. I am still on hold. Current Mood: pessimistic
|Monday, April 12th, 2004|
Single process jails
The boss wants me to read up on jailing single processes. He wants me to figure out what could be gained and how hard it would be to jail processes in a skeletal jail system instead of chrooting them.
I am going to do some reading on running single processes in a stripped down jail and then attempt to run a jailed bind process on a testing machine. Current Mood: mellow
|Thursday, April 8th, 2004|
Why I hate working with external vendor's code
Solved an annoying bug at work in the newest wireless reference driver from the radio vendor
Although it was supposed to support WPA () the OS didn't seem to think it did.
Before WPA there was an enum in ntddndis.h that looked like this:( DetailsCollapse )
Zenutech Download Manager (ZDM)
I have been tasked with creating a running installation of ZDM.
My boss has given me several options of where to put this.
I have decided to install on my Linux desktop box as it already has a functioning apache install with PHP working.
The entirety of documentation I was able to find on this program is at:http://www.zenutech.com/software/scripts/zdm/?strPage=documentation
I will also post it in it's entirety in a comment. (For all the good it'll do ya.)
I have followed the instructions and am able to get to the zdm page, but it simply shows a link to the download file that redirects to the same page you are on. No download happens. The apache error log shows:
[Thu Apr 8 09:18:04 2004] [error] [client 127.0.0.1] script not found or unable to stat: /usr/local/apacheimp/cgi-bin/mgetmetar.pl
The instructions, of course, don't mention anything about this perl script it needs.
I have done some preliminary searching to no avail. Off to do some more. Current Mood: annoyed
So, it has been a few days since I have been able to post here which is really too bad because I have been doing a lot. I will lament my lack of documentation, yes I will.
So, the boss is gone. We have had two hard drive failures and backups are not running properly. Obviously, I have been stressed and busy.
Of course I haven't spent all my time just watching the errors piling up and stressing. Nope, not ALL day.
I also completed the RT install on and fired up the old OTRS install to compare.
RT is fabulous. Very customizable, will run in a jail, and has any feature you could ever really need as long as you are willing to use add ons.(The customer interface leaves a lot to be desired, but they seem to be working on that. It would be ideal for a large company ticket tracking solution.
However, with just two "agents" it is overkill. Difficult to set up and so customizable as to be burdensome.
I like the interface of OTRS better. Softer, more pleasant. And it is easier to set up as well as having a customer interface for ticket tracking and FAQ access.(RTFM doesn't have customer access yet. You can't tell someone to RTFM if they can't get to it. Sheesh.)
When my boss get's back, we will talk about modifying the host server so I can run OTRS in a jail.
I have also been fixing a MRTG installation. Apparently, config files from previous versions will give you spikes in your data. I have updated the config file for the switch with the problem, and all seems well.
Can't decipher my acronyms? What is mrtg, rt, otrs?
Now I am off to get ZDM(http://www.zenutech.com/software/scripts/zdm/?strPage=features
) to work. I will document that in another thread.
See you there. Current Mood: busy
|Thursday, April 1st, 2004|
The last thing a system admin wants to hear in the morning when she comes in the first day her boss is on vacation is a beeeeeep beeeeeep beeeeeep from the server room.
I, of course, handled it like a champ.
Crawled around leaning my ear against cases trying to locate the wailing computer.
Finding it was one hosting some fairly important services, I logged in and verified that these services were still, indeed, running. They were. Phew.
I kicked it. It still continued to wail. (just kidding)
I checked dmessg and /var/log but everything seemed just fine minus the obnoxious, very loud beep coming from the server room that could be heard throughout the building. I felt like I was in one of those dreams where you end up at school nekkid. Vulnerable, oogled, and feeling like it was my fault the thing has been going off for several hours making the early birds in the office a tad bid cranky. Beeeep, beeeep, beeep.
Rebooted, the alarm came back on after reboot. Tried to jot down the start up messages, the once that came up when the alarm began beeping again after post scrolled by far faster than I could write or commit to memory.
So I called my boss and gave him as many details as I was able to collect.
He guessed that the raid controller was crying because a drive died and to look into silencing the alarm somewhere in the bios.
It took some research and hacking around in the bios to figure out the raid adapter was configured in a separate start up screen from the normal bios that had to be entered into farther down the boot process.
The documentation was a little difficult to find, but once I had it, shutting off that frickin' noise was pretty easy. Current Mood: accomplished