Tripwire Agent Install Problem and Solution: ERROR: pathname is a read-only mount.

Wednesday, July 9th, 2008

I was trying to reinstall a Tripwire agent on a Solaris 9 box when I ran into a problem during the package add. You see the agent in question needed to be upgraded, so I had removed it via the bin/uninstall.sh script which worked quite well. It appears that directory group permissions was the problem. Perhaps if it was a fresh install I never would have run into this.

I had sudo’ed over to root.

# uname -a
SunOS jobs-1 5.9 Generic_122300-02 sun4u sparc SUNW,UltraAX-i2

# ls -ld /usr/local/tripwire/te/agent
drwxr-xr-x 5 root root 512 Jul 3 12:26 /usr/local/tripwire/te/agent

# pkgadd -d te_agent.pkg TWeagent

Do you accept the terms of the License Agreement? (default: n) [y,n,?,q] y

Where should this package be installed? (default: /usr/local/tripwire/te/agent) [?,q] (I entered a CR)

ERROR: pathname is a read-only mount.

Where should this package be installed? (default: /usr/local/tripwire/te/agent) [?,q] /usr/local/tripwire/te/agent (This time I tried to force it to accept the destination)

ERROR: pathname is a read-only mount.

# chmod 775 /usr/local/tripwire/te/agent

# pkgadd -d te_agent.pkg TWeagent

And then the install works. This was for the 7.1 Tripwire Enterprise Agent.

intriguing writing - The Joel Test

Friday, May 27th, 2005

I’ve been around coders for years, almost 2 decades now.  Software development isn’t easy, especially if you’re not technical and you’re managing the developers.  I can clearly tell you that these precepts are essential.  Grade yourselves by them quarterly and you’ll make money IF your business model is sound.  Even great programming can’t sell turds as apple pies.

http://www.joelonsoftware.com/articles/fog0000000043.html

Troubleshooting HS Issues and Heavy Work Pace

Thursday, November 25th, 2004

did a little more analysis on the messed up system. I did install new hardware recently, so I disconnected it and it’s not solved the problem. I also installed some new drivers recently, but I backed them out and the reliability is still not high. I think I’m going to roll my system restore points all the way back to last Sunday and see what that gets me.

I’m also looking at the firmware level on the motherboard and it’s pretty old. They have a new revision available, but I’d like to back out my system restore points and see what I get. Then I guess I could attack the firmware upgrade and then possibly install the new hardware again.

Works kind of annoying at the moment. I’m on a 3 person team now. I don’t really like being on small teams. The on-call is pretty tight and if you’re the technical guy you’re basically on-call all of the time. Then this holiday my boss decides to head to South Dakota and my other co-worker takes off for the whole weekend too. I’m on-call, so I shouldn’t gripe so much, but seriously we’re in the middle of a horrendous migration and we have several outstanding production issues. There’s a time to step up to the plate and no one did.

I mean, basically at this point my days go kind of like this.

  1. Wake up. This can happen at any time. It happened at 3AM today.
  2. Figure out what broke while I was asleep. This may take a while. I try and eat if I can while I’m figuring it out.
  3. Triage. Fix things that are horribly wrong.
  4. Work-out. This usually means go for a run. This seems to be upsetting my co-workers but seriously I’m working a ton of hours. If I don’t get in the early morning run it just won’t happen. Only problem is that some nights I’m up to 3AM working on problems and then I sleep in(if I can.) but I still go running after my triage.
  5. Official work begins. Most days this is where I make it into the office. If the boss is in then I’ll review with him what I’ve recently found and am concerned about. I get my priorities from him and then go work them.
  6. Eating. It occurs at my desk as the day progresses. If I don’t pack a bunch of food it’s guaranteed that I’ll be stuck at work and grumpy. Menu plans are really helping me with this.
  7. Second Workout. This doesn’t happen too often, but if things seem in hand and I’m feeling good I’ll jaunt out on the bike or swim or something.
  8. Work some more. At this point I’m trying to shut the day down. By now we need to know what work we have to do tonight, who’s going to do it, do we have procedures, and figure out who’s going to be in the next day.
  9. Drive home. Before this happens I usually have something to kick off. Some job that’s not done yet. So I start it running and head home.
  10. Work more. I get home, login and see how things are going. I may be able to grab food at this point, just sort of depends on how the task is going.
  11. Chores. Yeah right. Some nights I get stuff done. Most I don’t. The house stinks of cat, dog, and me and I don’t even notice anymore. Friends don’t come over too often.
  12. Work more. I’m running about 70% of the events at this point. So if there’s night work to be done, I’ll be up doing it. I don’t sleep well early in the evening so it’s rare for me to nap before the work gets done.
  13. Send out my final emails for the night. They detail what happened and let everyone know that YES I’m still up and working. I don’t even state that I’ll be in late the next day anymore. If they can’t figure that out I’ll rip their heads off.
  14. Sleep. Fitfully and usually on the couch.
  15. (REPEAT AS NECESSARY)

Don’t get me wrong. I’m happy to be gainfully employed, but I wish my co-workers would pick up a bit of the slack too. I think one thing that really pissed me off last weekend is my co-worker Chris asked if I could cover his on-call on Sunday because they’re celebrating Thanksgiving. And yet I’m stuck being on-call and can’t visit with my parents during the official on-call rotation. I mean my parents piss me off and all, but I’d like to see them occasionally. It helps them to not nag me for a few months. They can verify that I’m alive and not dead in the bottom of a barrel. Somehow the telephone can’t fix that fear with them.

But back to Chris. I figure, hey, if you’re doing Thanksgiving a week early, why don’t we just trade the whole week. You’d not have on-call during your family celebration and likewise for me. Oh no, that’s no good because he really NEEDS his vacation. Also, he wasn’t asking to just swap one day of on-call with me, he was flat out asking that I work one of his days with no retribution.

At that point I pretty much just said, NOPE, sorry I’m going hunting on Sunday I can’t help you. And despite all that I still got called on Sunday to work a problem. And it’s a problem that I had already worked once and wrote a document on how to fix it. I published the document to the group. This is what I mean about small teams and being the technical guy.

And seriously the guys don’t really understand that this isn’t going to work in the long-run. I’m running a good bit now. But wait until it warms up and I’m riding 5 hours each weekend. But hey, that’s a management problem I suppose. Well, I’ve ranted enough. It’s time for me to go check and see if any of my processes need attention. Maybe I’ll have some breakfast. A little protein shake or something.