Tags: upgrading

06/15/13

  01:15:00 pm, by The Dreamer   , 694 words  
Categories: Software, FreeBSD, CFEngine

Meanwhile upgrading cfengine-3.4.4 to cfengine-3.5.0 not going well.

Upgrading the port was no problem....but it broke my cfengine. Why? The port puts the cfengine binaries in /usr/local/sbin, while the cfengine practice is that it has a private copy in /var/cfengine/bin. Which would be fine if the binaries didn't have shared library dependencies. Which they do, specifically libpromises.so.1 which is gone in cfengine-3.5.0...there's a libpromises.so.3.

Though before I discovered this problem, I first wanted to make some tweaks to update.cf so that I would have some indication that it had copied up new binaries from /usr/local/sbin to /var/cfengine/bin, since I noticed that files there newer than expected. Though I probably just rebuilt the same version port because a dependency had updated and /usr/ports/UPDATING indicated that I need to do that.

This probably is why at work, the person that setup our cfengine 2 went to extreme effort to create static cfengine executables...ignoring that such things are officially not supported on Solaris. Though we seemed to get away with running those executables, built on a Sol10u3 sun4u system...on systems more current up to Sol10u11, and a few Sol11 systems and systems that are sun4v architecture.

In a past life...we had run into a statically built executable (the installer) not working on our first UltraSPARC-III system (Sun v280r)...trying to recall what our build machine was back then.... my recollection says we only had the SPARCserver 20 and SPARCstation 10, before that. Though as I recall, we had to wait for a patch from Sun as well as rebuild the executable shared on the SPARCserver 20...to have it work. It wasn't long after that though that we retired support for sun4m, changing minimum requirements. Wonder if the application has become 64-bit yet? But, for ABI backwards compatibility claim to work, the executable needs to be built shared...so that it'll find the libraries provided on newer systems to allow older executables to still work.....

portmaster probably didn't know that it should save /usr/local/libexec/cfengine/libpromises.so.1, though would the old executables know how to find the library when its moved aside? (I do have SAVE_SHARED=wopt uncommented in my portmaster.rc file).

Occurs to me that I could just restore the file from backup, it would allow me to run

failsafe.cf

and get me to where everything should work again.

Though before I did that, I had invoked cf-promises (the one in my path -- /usr/local/sbin), and it complains about library.cf. Guess it doesn't like the old cfengine_stdlib.cf, the new one isn't where the old one was....it was here instead --> /usr/local/share/cfengine/CoreBase/libraries/cfengine_stdlib.cf I do a quick look at what's in it....mainly to make sure that bundles/bodies that I use are still there...and notice some interesting new ones....such as a package_method of freebsd_portmaster, someday I should look at cfengine3 to do port/package promising....

But first get cfengine working on policyhost, hopefully the other servers (at 3.4.4) are still working.....guess not, 3.4.4 doesn't like the 3.5.0 cfengine_stdlib.cf file. But, cf-promises is also not happy with some of my other promises....

Guess I'll update those while I get policyhost working again.

.
.
.

Or perhaps I need to revert....

root@zen:/var/cfengine/inputs 317# cf-agent
2013-06-15T13:22:53-0500    error: Bundle 'crontab' listed in the bundlesequence is not a defined bundle
2013-06-15T13:22:53-0500    error: Fatal CFEngine error: Errors in promise bundles
1.755u 0.113s 0:01.94 95.8%     172+2501k 133+12io 1pf+0w
root@zen:/var/cfengine/inputs 318# 
# cf-agent -v
...
2013-06-15T14:00:57-0500  verbose: Parsing file '/var/cfengine/inputs/do-crontab.cf'
...

Its there, why's it not working.... 'cf-agent -d' doesn't work, but it will only do failsafe....

Full story »

09/30/12

  11:49:00 pm, by The Dreamer   , 188 words  
Categories: Software, b2evolution

Finally upgraded b2evolution

From 4.1.3 to 4.1.5b.

Maybe I'm getting better at these small patches, because it didn't seem as hard to do. Or perhaps because I was able to figure out my own customizations and back patch them into the patch or that I'm getting better at where I put my customizations....

Plus one of them matched one of the patches....resulting in just shifts in line spacing and newer comments. &#59;D

Though was getting worried considering I put off applying 4.1.4 so long that 4.1.5 came out, and became 4.1.5b. Though I would have to do them separately, but then it occurred to me that if 4.1.5 changes anything in 4.1.4 it'll overwrite those files. So, all I had to do was three-way diff and figure out what from mine goes into 4.1.5b and lay that down on top.

Though I did see that I have files that don't exist in either 4.1.3 or 4.1.5b...probably left overs from much earlier 4.x versions. Though was surprised to see that a plugin was newer in 4.1.3 than in my version. Not sure how that got overlooked until now.

There's other plugins that need updating, but I'll do that later....

05/18/10

  08:29:00 am, by The Dreamer   , 703 words  
Categories: Software, Computer, Networking, BOINC, Ubuntu

'Accidentally' Upgraded 'box' to Lucid

Last night I wasn't thinking....running into the fact that my boinc-client package is broken on 'box', I thought..."why isn't it running the boinc-client from Lucid?" And, I proceeded to fix it with "apt-get"...and then realized that I'm still running karmic and unbreaking it wasn't. The boinc-client pre-Lucid is too old for a project I'm in, and it is annoying how ubuntu doesn't update packages within releases (which get's really annoying with LTS.)

Anyways....I decided the way to resolve the mess I had now made by downgrading my boinc-client, was to upgrade to Lucid Lynx 10.04LTS. It was my plan to upgrade both my Ubuntu servers to 10.04LTS (the other being 'orac' which is currently 8.04LTS)....but I was going to put it off to when I had more time and allow time for the release to stabilize (given all the issues I had when I first started running box on fresh Karmic).

So, it started....things got a little annoying, in that the upgrade requires attention....and I didn't want to spend my whole evening watching it upgrade. So, I'd check it now and then, and sometimes find it stuck waiting for me to make a decision for it, though the first one where it wants to restart stuff after a pam upgrade...that's annoying. Just do it okay, stuff it restarted weren't working right along the way anyways. Namely I found that I couldn't access websites...at first I thought the squid had become dorked, and I couldn't restart it because invoking /etc/init.d/squid said it was now a service...but using service didn't find it. Though later I realized it wasn't working because DNS was broke ('box' is my primary DNS server)... I was able to restart that in the usual manner.

Partly because of the pauses, and a bit due to slow download....it wasn't looking like I would finish before 'bedtime'....but it seemed that it would be close enough.... It wasn't, but I ended up staying up to the bitter end. So, that I could reboot and do a quick check that all was clean.

Namely, I checked that named, dhcpd, ntpd and squid were running (since these were some key services of this server, and were ones that often failed to start after boot in karmic...especially named. Manual start always worked...at one time I was restarting these services in rc.local where it always worked rather than at the 'normal' time).

Then I went to fill in the missing icons in my launcher panel....there were two holes, there also seemed to be a hole in the tray area. The missing icons were Evolution (which I right-clicked to make reappear), and boxee (which I installed the latest of). I then called it a night.

The next morning, I continued to poke around some more....adjust appearance, add some chat/broadcast accounts...and look into my ubuntuone issue....first the tray thing was missing, apparently its by design...but, I don't remember that. I poked around some more and some more....then I looked at 'ulkc' and saw that it also didn't have the tray applet anymore, and I just didn't miss it... So, I then went to check that it was connected to my account and sync'd. Actually, it really was syncing, etc. When I was at Penguicon, I had put a copy of the pictures I had taken into my cloud...expecting to see them later on 'box' when I got home. But, it would never appear. Upgrading 'ulkc' didn't help things.

During the poking around, I disconnected 'box' and reconnected...and that apparently fixed whatever was wrong, as it started syncing...and soon the folders appeared.

While this was going on, I thought that maybe I would need to finish things up by remote....so sadly I discovered that remote desktop still doesn't work in Lucid. Turning it on, consumes 50% of my CPU. My 8.04LTS (orac) doesn't suffer from this problem. But, I want to bring both servers in sync eventually, so I can see about getting failover for dhcp working between the two.

Oh well....at least it seems more successful than when I had upgraded 'box' to Karmic. And, now I'm at an LTS where it can stay for the next 2 years.... We'll see what happens when I upgrade from 8.04LTS to 10.04LTS next month....

11/07/09

  06:30:40 pm, by The Dreamer   , 175 words  
Categories: Software, Computer, Networking

Another problem with karmic upgrade of box

Found another problem with my karmic upgrade of 'box'. The clocks on everything were starting to drift....well 'box' is my NTP server.

I check the ntp.conf, and it was still correct. Then I realized ntp started while bind wasn't....so it omitted a time server to sync with. (and nothing for the initial sync).

So, that's another thing to bounce in /etc/rc.local on boot.

I did find a posting somewhere that suggested apparmor was the causing problems, so I tried removing that....but that didn't solve the problem, though putting it back it did work once....but rebooting again to see if it was a fluke, seemed to say that it was. So, stick with /etc/rc.local as the more reliable way to make sure these things are running..... :**:

Wonder if there'll be a time where I remove this kluge to see if things are fixed...or not. :??:

OTOH, with box on a PowerSource 400, I kind of hope that it'll never go down during typical power outages. Of course, who knows if there'll be another extreme one, like the icepocalypse.

  02:53:14 pm, by The Dreamer   , 219 words  
Categories: Software, Computer, Networking

Upgrading box to karmic

With a couple hours to kill this morning, I decided to see about upgrading 'box' to karmic. Ideally it should've been LTS, but that's another story....

It gave an estimate of one hour to download. Well, it ended up taking those couple of hours. And, then a couple hours more to actually install the updates.

The upgrade was pretty straight forward...I didn't realize that server kernels were gone now, so at first it caught me off guard, guess I didn't pay attention when I upgraded the server at work.

The only problem during the upgrade was the it stopped named, and left things in a state where it could not be restarted. So, things were a bit quirky on my network without DNS, and the box had some issues...not being able to resolve its own name. For some reason during the original install, it had created /etc/hosts with my FQDN but no entry for just the hostname.

Then things went strange....rebooting the box, no DNS running. 'sudo /etc/init.d/bind9 start' and it would start fine. Reboot again....again no DNS.

So, remove and reinstall the package....reboot again, still no DNS. It starts fine by hand after things have booted, but not during boot for some reason. Well, add a line to /etc/rc.local to start DNS. Guess that does it for now.

Now instead of subjecting some poor random forum to a long rambling thought, I will try to consolidate those things into this blog where they can be more easily ignored profess to be collected thoughts from my mind.

Latest Poopli Updaters -- http://lkc.me/poop

bloglovin

There are 20 years 2 months 1 day 7 hours 46 minutes and 56 seconds until the end of time.
And, it has been 4 years 10 months 27 days 6 hours and 16 minutes since The Doctor saved us all from the end of the World!

Search

November 2017
Mon Tue Wed Thu Fri Sat Sun
 << <   > >>
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
Google

Linkblog

  XML Feeds

Who's Online?

  • Guest Users: 0
This seal is issued to lawrencechen.net by StopTheHacker Inc.
powered by b2evolution

hosted by
Green Web Hosting! This site hosted by DreamHost.

monitored by
Monitored by eXternalTest
SiteUptime Web Site Monitoring Service
website uptime