Sles10

Well, after some more refining I think I finally have a script I ain’t never gonna touch again (unless something breaks, which can happen quick as we all know). The script now uses a sysconfig file for the common settings (like sender, receipents, categories to scan for), so it may be deployed en mass. /etc/sysconfig/zypper-update-report 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ## Type: string ## Default: root ## Config: "" # # Sender address for the update report FROM="Yourupdatemonkey " ## Type: string ## Default: root ## Config: "" # # Receiver address for the update report #RECEIPENTS="tehsysadmin@barfoo.org" ## Type: string ## Default: "securty recommended optional" ## Config: "" # # List of groups, to include in the report CLASSES="security recommended optional" /usr/local/sbin/zypper-update-report ...

Well, it’s 7pm. I’m sitting at home and thinking about why in gods name rug isn’t adding my update repository. I can add the service using yast inst_source, but when yast then syncs with ZenWorks, it tells me something like: Failed to get repomd/repodata.xml; Reason: 530 - Access denied So my fellow co-worker turned on the debug-logging and we quickly found out why: rug isn’t using the command line credentials I was passing. ...

Today I was moving a pretty standard SLES10 virtual machine to another host, when the migration dialog showed me this: fault.MemorySizeNotRecommended And if you now think, the virtual machine is something special take a look at those settings: Virtual machine configuration I don’t know what to think about that error message. Googling for it doesn’t reveal that much about it. If anyone out there got an idea, I’m open for suggestions.

Since I do happen to be in the situation pretty often where the kernel inside a VM is newer than what VMware currently has in their tools (as in the SUSE kernel is newer than the binary modules built by VMware), here’s a quick reminder for myself on how to to fix the .ko symlinks. 1 2 3 4 5 for file in /lib/modules/$( uname -r )/misc/*.ko ; do rm $file && ln -s /lib/modules/$( uname -r )/misc/${file/.ko/.o} $file done

Well, it turns out that my thought was ultimativly flawed. When defining the hostgroup_members in the lower tiers, nagios is association the checks from the lower tier with the upper tiers. Thus propagandating all checks upwards, and me ending up with ~250 checks instead of ~150. Gonna have to try to define the dependency backwards, maybe that’ll help. But that’s a topic for Monday. Guess I’ll finish viewing Ghost in the Shell - Stand Alone Complex first.

Well, it seems to be getting a “trend” for me, to integrate stuff into our Active Directory. Now that I know why, and how easy that is, I expect to add more stuff. The good thing about the integration is, that you only need to maintain a single source for authorization. The bad thing about that is, that stuff becomes dependent on the Active Directory (we do have four domain controllers, so that should be fine). ...

Recently I got the task, to implement unixODBC/freetds on one (well, it’s really three) of our web servers, as someone wanted to use Microsoft SQL Server 2005 with PHP (without using the MSSQL functions, which PHP provides soo nicely; don’t ask me why). With that I also got a set of " instructions" on how to install freetds from source (remember, I was a Gentoo dev, so I know my way around, when it comes to building from source), as well as a small set of instructions on how to create the connection. ...

Okay, so I ended up toying with subversion via WebDAV on SLES today (I know, I know .. it’s bloody Sunday). It wasn’t much of a hassle though, after reading this. Sure, I made a few errors at first (simply confused the logic behind " Location" and " Directory"), but after that plain subversion commits via WebDAV (thus utilizing Apache) worked fine. For POC or as a hint to myself, here’s where and what I needed to add/change: ...

Remember, I talked about building RPM’s on SLES10SP2 on ppc64 ? Well, turns out I was rather stupid .. and it was rather simple (don’t ask me why I didn’t think of that). I tried asking solar, I used Google (apparently with the wrong search parameters), nothing though. Not a clue. Today it bugged me again, so I used Google again. This time with " ppc64 suse rpmbuild", and guess what I saw within the preview of the second hit .. ...

Here I am, preparing our environment for the first (of hopefully many) tester for our upcoming VTL project. So I ended up installing the ISC and Administration Center for Tivoli Storage Manager on a 64bit guest (that is SLES10 for AMD64), just because I forgot to include support for later versions with our current running one. Guess what, na- na na na na. Exactly, didn’t work, the same errors I got while trying it before in a virtual environment. “Portlet is not available.” ...