Discovery rolled over to the VAB

The NASA Vehicle Assembly Building (VAB)
I just read on the NASA space shuttle homepage:

Sept. 23 at 5:30 p.m. EDT
The orbiter Discovery is parked in the transfer aisle of the Vehicle Assembly Building after rolling over from the Orbiter Processing Facility bay 3. First motion was at 12:22 p.m. EDT. This marks a prelaunch milestone.

Overnight Discovery will be rotated to a vertical position, hoisted and attached to its external fuel tank and two solid rocket boosters for its upcoming mission, STS-120, to the International Space Station.

Space Shuttle Discovery will roll out to Launch Pad 39A approximately one week after rollover. The launch of STS-120 is currently targeted for Oct. 23.

This is excellent news. Looks like my reservations are still right.

But what does this all mean? And why was it necessary?

Orbiters are parked in special, smaller buildings called “orbiter processing facility” or OPF. This is where the majority of work is being done on them. For example, the strut repair happened there. As far as I know, orbiters are immediately moved to the OPF when they have arrived in Kennedy Space Center. Then they are checked, repairs conducted and prepared for the next mission. They are not, mated to either the tank or the solid rocket boosters – the OPF is simply too small to do that.

Instead, that is done in the “Vehicle Assembly Building”, or VAB for short. This is a gigantic building (see picture), where the boosters and tank are mounted and the shuttle is then mated to them. As I have now learned, shuttles are typically moved over to the VAB roughly a month before launch. There the mate happens and, I assume, also some further checks.

I requires good weather to move a shuttle from the OPF to the VAB. Thus this movement can easily be delayed, especially at this time of the year (just think about Florida’s frequent afternoon thunderstorms…). This time, we obviously had no or at least very little delay – which is, why we are still on the timeline.

Kennedy Space Center Webcams…

NASA Webcams in Kennedy Space Center (KSC)
I just did a quick search on Google to view webcam of the Kennedy Space Center (KSC) complex. I have to admit I did not expect anything real interesting to pop up – wrong! There is actually a bunch of webcams run by NASA itself, and they seem to over interesting content.

BTW: I need to say “seem”, because it is night in Florida as I blog this. So I rely on the captions.

But see yourself:

I’ll be on the hunt for more related webcams. If you happen to know some, I’d appreciate if you let me know (just use a comment).

What’s going on with rsyslog?

I’ve not posted much the past days. That doesn’t mean nothing has happened. I wanted to post a work log today, but I have to admit I have forgotten it on a machine I right now can not access. OK, first thing tomorrow morning…

In short words, we are still on the bug hunt. I am now again back to reviewing code, this time on a functional basis. I am checking everything based on the message flow, looking at functions as they are called. Today, I completed the review of the reception part (up to the point when it gets into the main message queue). Unfortunately, no serious problem found. I used the review, however, to clean out some nits, add a large number of new comments and even found a memory leak. The later one would currently most probably never occur in practice, but when syslog-protocol gets adopted, it would have hit.

Tomorrow, and probably then next two or three days I’ll review the code that is executed once the message leaves to main queue. There is probably more meat for a bug in that part (its by far more complex).

I also think I’ll release the cleaned-up version sometime soon – after all, it’s better then what is currently released.

I keep you posted. Comments are always welcome.

Discovery still in for October, 23rd launch…

Discovery with repaired strut (STS-120)
The guys at NASA and its suppliers are fantastic. As you can see on the picture, the strut is re-assembled and even the tires are mounted again. NASA is very optimistic to even launch on the 23rd, as originally planned.

Listen to what these fantastic guys have to say:

With space shuttle Discovery’s right landing gear reassembled following the replacement of its four hydraulic seals, technicians now are carrying out a series of tests on the system. Once these tests are concluded on Saturday and the repairs have been determined successful, the way would be cleared for Discovery’s move on Sunday from its processing hangar at NASA’s Kennedy Space Center to the Vehicle Assembly Building. Depending on how processing operations go, rollout to the launch pad could take place one week later.

One of Discovery’s struts, which act as shock absorbers during the shuttle’s landing, began leaking hydraulic fluid last week.

Once Discovery is in the Vehicle Assembly Building, it will be attached to its external fuel tank and two solid rocket boosters for its upcoming mission, STS-120, to the International Space Station.

While NASA managers will continue to assess the progress, the ongoing preparations would still support Discovery’s Oct. 23 target launch date.

Source: http://www.nasa.gov/mission_pages/shuttle/main/index.html

Shuttle Discovery probably back on schedule

Shuttle Discovery with re-assembled strut
On the picture, you can see the shuttle strut being reassembled. That’s actually a great relief to me.

This article does a full wrap-up and analysis of the current state:

http://www.nasaspaceflight.com/content/?cid=5234

As it looks, the launch date for Discovery’s STS-120 mission will only slip nominally, if at all. The engineers have done superb work today, managed the repair that was scheduled for a few days in just one morning – congrats!

To me, that means my travel plans are so far unaffected. However, there is now no buffer time left, so everything else is on the critical path. But, hey, why should something else go wrong? :-D

I see that it was right not to panic, even while a larger launch slip was in question. I guess I’ll manage to keep cool on other occasions, too (at least this is my current school of thinking ;)).

OK, enough good news for the evening.

Shuttle Discovery is being repaired…


I have just read that the repairs on Discovery’s strut are well under way.

I also found the nice picture showing how the landing gear is being disassembled. If you look closely, you can see the bottom part (right at the floor), where the tires normally sit. And right behind the head of the worker in front of the picture is the upper part of the strut, that one that is still connected to the space shuttle.

I am very glad to see these pictures, because they provide evidence that the repair seems to be on good track. I assume that there are now all needed spare parts available and work can continue to be carried out.

In the mean time, several space forums on the web report that there will probably be a slip in the launch date, but it is not expected to be extreme. So maybe I loose a day or two of “my launch” window, but I think chances are still pretty high I’ll make it. When I first heard about all that, I wondered if I should change my travel plans. Especially air travel to Orlando is a bit problematic. But today everything is unclear. If I move the dates, I’ll probably miss the launch when it is on time (and as of NASA’s official site, there still is a chance). I stay tuned…

Update: I found some new pictures, find them at http://www.gerhards.net/Gallery-sts_120_strut_repair.phtml (thumbs below).


a dedicated shuttle blog

Ah, the joys of blogging. When I started this blog a few years ago, I kept it focussed on one topic – and thus had a few other blogs for other topics. Then, these nice labels appeared in blogger. That looked like an ultimate solution to me: just put everything in a single blog and then use the labels (or tags, as others would call them) to generate topic-specific feeds. Now is the the first time that I really did this. And, guess what, it doesn’t seem to work as nicely as I initially thought.

Mixing rsyslog/logging and a field trip to the space shuttle launch causes some confusion. I do not like confusion ;) So I have created another blog for my space shuttle launch viewing trip today.

I hope this will work out. I sincerely think it is in the best interest of all readers. The next days (as time permits, its obviously not a priority task…), I’ll create some useful links to get the different pieces together if you are interested in the big picture. Also, I’ll remove the shuttle posts here and change them to redirects.

space shuttle troubles…

Space Shuttle Strut Repair
Yesterday, some info leaked that the shuttle … well, leaked ;) To be serious, there were reports that there is an unacceptable leak at a shuttle strut – hydraulics fluid seems to have been leaking. But yesterday the decision was made that a repair is actually needed.

Of course, it didn’t take long for all sorts of rumors to appear. Some sources even said that the October mission would be canceled and moved to January – which is as far from being true as it only can be. In fact, the NASA source quoted above does not outrule there is a change in the launch date, but it is expected to be not a major hit. As far as I understand it, things may be moved a few days at most. There seem to be buffers all along the process, so I do not yet begin to panic ;)

… but I have to admit that this triggers bad memories. As I said, I flew in into Orlando last year to see the STS-115 launch (which I finally didn’t make due to its long delay). With STS-115, all the trouble also started with launch delays, that time caused by a lightning strike. That, too, was quite some time before launch, at least if I correctly remember. It was not that early as the current problem, which leaves me with the firm hope that there is enough buffer time available even to launch on the target date of October, 23rd. Let’s see…

Photo: In the Orbiter Processing Facility at NASA’s Kennedy Space Center, workers secure the tool storage assembly unit into Discovery’s payload bay. Photo credit: NASA/Amanda Diller

paid services for rsyslog

As with a lot of open source projects, rsyslog funding is problematic. Of course, rsyslog currently is funded by my interest in it. And I am glad that Adiscon, my company, permits me to work on. The actual funding for all that action, kind of funny, mostly stems from closed source projects in the Windows world.

However, I’d like to see that over the years rsyslog can fund itself. In my point of view, funding should be provided by those that benefit most from it. So obviously, I do not expect any funding from private folks, people like you and me. Of course, everyone is invented to contribute and new code, doc and bug hunting is definitely a pro. On the other hand, companies (and other organizations, namely the government) take financial advantage of using it. Some of them also contribute in terms of time and code. This is great and much appreciated :)

For the others, I have begun to offer donations. Not surprisingly, this is not a real source of funding ;) But now I have taken an offer from sourceforge.net, which I think is interesting. They begin to offer a marketplace for open source services. So those folks that actually need help can be brought in contact with those that have experience. Sounds like a good idea to me and a fair way to fund projects.

I have created two test service offerings for rsyslog. One is to write a nice custom-created rsyslog configuration file. Well, with rsyslog’s relative ease of use, I do not expect that many folks use that. But you never know and I am always curios.

The other one is especially targeted towards organizations who must prove they have “official” support for all software they use (I guess this includes at least a number of government agencies). For them, I have created a email support option for rsyslog. It guarantees responses to support questions and this is often needed for auditing and other purposes. Of course, we still answer all support emails and do not plan to stop that.

I have added one real goody, though: and that is that we will provide patches for past releases of rsyslog. As you may know, developers hate to fumble with old releases. And so there is very little motivation to look at an older release when there is a new one out. With the paid support option, however, there is some motivation to do that. So, again, I think this is fair: we are just offering a service that would otherwise never appear. It doesn’t hurt any of the other users.

I am very interested to see how this works out. I would also be interested in feedback from the field. How do you like this idea? Do you have any other/additional suggestions?