Life

What would you figure from the above ? Hopefully the rather obvious, that it’s a really shitty combination. So we figured it would be a nice thing to test our new setup before going into pre-production testing or production, but we don’t have an extra spare box. So we took one of the power4 boxes we have mounted in the rack basically consuming energy all day (that’s about 38kWh a day) and installed SLES10 onto it. Which wasn’t all that bad (at first the box repeatedly started back to AIX, from CD and after convincing the SMS - that’s basically the bios on the power*-boxes also known as System Management Services with a hammer to boot from the first hard disk). ...

So I have one or the other file, that needs to be extracted to a directory. And why not name it as the archive itself .. Only problem with it is the handling of variables with bash … Try it yourself, stuff some directories with a space in inside a variables, and use something like this: 1 2 3 epimetheus tmp [0] $ mkdir files epimetheus tmp [0] $ touch files/"I hate directories.archive" files/"Me luuv you looong time.archive" epimetheus tmp [0] $ for i in $( /bin/ls --color=none files/ ); do mkdir "${i/.archive/}"; done And now take a look at the output of that .. ...

Today I played a bit with our PE Chassis, or more specifically the DRAC/MC (remote management console). One of the things I’ve been experiencing was that the DRAC/MC was rather slow when browsing on the web interface (as in waiting a minute for the jnlp for the KVM to download). So I went ahead, fired up net-misc/atftp on my notebook, put the firmware update provided by Dell in the TFTPROOT and executed this in my telnet session on the DRAC/MC: ...

After today’s adventure with the kernel bonding, I just took a look at the code … 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 if (miimon) { printk(KERN_INFO DRV_NAME ": MII link monitoring set to %d msn", miimon); } else if (arp_interval) { int i; printk(KERN_INFO DRV_NAME ": ARP monitoring set to %d ms, validate %s, with %d target(s):", arp_interval, arp_validate_tbl[arp_validate_value].modename, arp_ip_count); for (i = 0; i < arp_ip_count; i++) printk (" %s", arp_ip_target[i]); printk("n"); } else { /* miimon and arp_interval not set, we need one so things * work as expected, see bonding.txt for details */ printk(KERN_WARNING DRV_NAME ": Warning: either miimon or arp_interval and " "arp_ip_target module parameters must be specified, " "otherwise bonding will not detect link failures! see " "bonding.txt for details.n"); } If I read it right, you only get the KERN_WARNING for “either miimon or arp_interval” only if miimon or arp_interval isn’t set … but at least my config says it is .. 🤷 .. bed time for me :rolling_eyes:

Okay, yet another day passed by blazing fast. I had a good day at work, spent nearly the whole day trying to get my bloody systems hooked up to our SAN (which was interrupted by a non-working SAN-switch, disappearing WWN’s, lunch and my trainees), messing around with our internal network, hacking our Blade Chassis switches to get me what I want and some random paperwork. But first things first .. We installed SLES10 on a pSeries box the other day (I think on Monday), and now I’m trying to get the WWN of it’s Emulex HBA, out of either sysfs or procfs. But whatcha’ thinking ? ...

Yessir, I’m back home. Bought a new bed (god, I forgot how good sleeping can feel) and spent the first two days at work already (yes, it’s Friday afternoon already). I really thought catching up after having a 2 week vacation would take more time, but it just took yesterday morning (till ~9am). I’m surprised by the taste of black tea with milk and sugar (yes, I was like yikes initially, but I like it pretty much now 😀 ) and by the ability to rise at 7am in the morning 😛

On Monday I finally got to do an expanded test drive with my shiny, new car (that is driving it up from Stralsund down to Stuttgart). I really can’t complain, the fuel consumption is like I expected (~6.6l/100km while driving between 160 and 180km/h), the noise while driving that fast is quite low (as in you hear the engine but you don’t really consider it noise) and the acceleration is nearly like the one of a F1-car 😛 (at least I’d wish 😉 ). Spent the evening relaxing from the near 950km nonstop trip (yes, only had one stop to put some fuel back into the car), had nice curry (my cousin’s husband made yummy potato curry!!!). ...

Here’s just a note for you people out there, how’re crazy enough and want something from me in the next week (that’s 18th till 26th June): I’m on vacation … Means I won’t be around to fix anything (as I’m gonna try and relax a bit), so if you encounter something that you want to fix; consult with the herd (that’s apache/hardened/kernel …) and/or fix it YOURSELF. Just make sure you don’t break it more :rolling_eyes:

OK, it turns out that I was rather stupid when configuring the my.cnf. As it turned out, the effect I was seeing was due to the presence of two log-bin lines, which looked like the following: 1 2 3 4 5 6 7 8 9 10 11 12 [mysqld] port = 3306 datadir = /mysql/dbase log = /mysql/logs/dbc-mysql1.log log-error = /mysql/logs/dbc-mysql1.err socket = /var/lib/mysql/mysql.sock bind = 172.16.234.31 # custom paths for binary logs log-bin = /mysql/binlogs/dbc-mysql1 log-bin-index = /mysql/binlogs/dbc-mysql1.idx relay-log = /mysql/binlogs/dbc-mysql1.relay And some lines down there was this: ...

Here I am, sitting at my desk on a Thuesday evening thinking about what happened the last few days. I finally got to play around with our PacketPro 450 Cluster(nifty LoadBalancing appliance) We reworked the network the way we want it (and not that tool of a wannabe sysadmin) We mostly figured out how to do the LoadBalancing right, we just need to find some bugs in the LoadBalancer software (like the thing is failing over to its slave from time to time, but keeping the IP address for himself) or let the guys at teamix do their work and hopefully get a working release within the next week or so I figured out how to setup interface bonding with SLES10 (it was quite straight forward, thanks to the excellent in-kernel documentation), and we’re using an active-backup mode for now I still need to figure out how to do the MySQL Master<->Master replication right .. I’m currently building fresh RPM’s on one of those Dell blades (yes, they ROCK!) which will hopefully be finished till I’m at the office tomorrow. Pt. 5 also includes figuring out how to pass MySQL a custom location for the binary-log, at least that’s what the handbook says in Chapter “5.11.3. The Binary Log” … When started with the –log-bin[=base_name] option, mysqld writes a log file containing all SQL commands that update data. If no base_name value is given, the default name is the name of the host machine followed by -bin. If the basename is given, but not as an absolute pathname, the server writes the file in the data directory. It is recommended that you specify a basename; see Section B.1.8.1, “Open Issues in MySQL”, for the reason. ...