virtual syslog appliance

I’ve just recently blogged about my syslog appliance idea. Now this has become reality. There is the first 0.0.1 version of rsyslog and phplogcon as a virtual appliance.

For starters, I have created a very simple system. While I have a number of options for the operating platform, I started to Ubuntu JeOS mainly because it had good guides for getting started with an appliance quickly. Being based based on Debian also was a plus. Some may argue that the downside is that the log appliance currently requires VMWare. While I agree this may be an issue, it is not an extremely big one especially as VMWare server runs quite well under Linux and is free to use.

I will investigate Red Hat’s AOS, but I think I need to get some results from the app point of view first and JeOS looks quite promising in this regard.

For now, I have even started with the stock rsyslog package, which is quite outdated on that platform. However, I’ll do a couple of iterations in the next days and so will come up to the current release soon. But for what the appliance currently needs, the older version is not really a problem.

I am now very interested in feedback on this new offering. The appliance can be downloaded from

http://www.rsyslog.com/Downloads-req-viewdownloaddetails-lid-136.phtml

One of my next actions is to set up a dedicated site, which will make finding (and providing!) information on the appliance much easier. But one thing after the other…

Oh, and one thing on the licensing: the appliance is free for non-commercial use. However, we intend to request a moderate fee for commercial use, which I think is a fair policy. Of course, all appliance components are freely available.

If you try out the appliance, please provide feedback!. I have set up a dedicated forum at

syslog appliance forum

As I said, the initial version will probably not as “plug and play” as I hope, but I am very positive we are on a good path. Besides, it is an exciting project.

India is going to the moon…

Everybody seems to want to go the moon these days. Russia does, China does, Europe, as usual, “says” it does (if someone else provides the ferry ship ;)) and the US, of course, will, too.

Today, India has launched a moon mission, just to tell us they, too, are serious about this topic. A rocket carrying the Chandrayaan-1 probe rocketed into the skies at India’s spaceport Sriharikota. Chandrayaan-1’s mission will last two years. It is tasked to create a detailed map of minerals and chemical properties of the moon surfaces, as well as general surface structures.

The moon seems to promise big business. It is also politically quite important. With the US right in front of a very important election, it will be very interesting to see which direction the new administration will take. NASA’s constellation program is underfunded and has unrealistic goals if being worked on at the current (finance-dictated) pace.

Will the US be among the last folks to go back to the moon? The Russians are on a good path already and seem to have funding and a commercial vision. Or will a new moon race start, where the US demonstrates technical leadership? Interesting question, time will tell. At least we have a new player who seems to be serious inside this game…

Hubble partly restored, Atlantis heading back…

The Hubble repairs go well, but unfortunately not too well. As NASA reports, the restoration succeeded only partly, some systems are still defunctional:


On Wednesday, October 14, engineers at NASA’s Goddard Space Flight Center reconfigured six components of the Hubble Data Management System and five components in the Science Instrument Command and Data Handling (SIC &DH) system to use their redundant (or B) sides. This was done to work around a failure that occurred on September 27 in the Side A Science Data Formatter in the SIC&DH and resulted in the cessation of all science observations except for astrometry with the Fine Guidance Sensors.

The reconfiguration proceeded nominally and Hubble resumed the science timeline at Noon ET on Thursday, October 16. The first activities out of that on-board science timeline were the commanding of the science instruments from their safe to operate modes. This occurred nominally for Wide Field Planetary Camera 2 and the Near Infrared Camera and Multi Object Spectrometer. However, an anomaly occurred during the last steps of the commanding to the Advanced Camera for Surveys. At 1:40 pm, when the low voltage power supply to the ACS Solar Blind Channel was commanded on, software running in a microprocessor in ACS detected an incorrect voltage level in the Solar Blind Channel and suspended ACS. Then at 5:14 pm, the Hubble spacecraft computer sensed the loss of a “keep alive” signal from the NASA Standard Spacecraft Computer in the SIC&DH and correctly responded by safing the NSSC-I and the science instruments. It is not yet known if these two events were related.

The investigation into both anomalies is underway. All data has been collected and is being analyzed. The science instruments will remain in safe mode until the NSSC-I issue is resolved. All other subsystems on the spacecraft are performing nominally and astrometry observations continue.

But at least some observations can be carried on.

At the same time, Space Shuttle Atlantis is heading back to the VAB to get to a save haven while the Hubble repair mission is postponed. Unfortunately, a rod struck parts of Atlantis while it was removed from the launch pad. It is now investigated whether or not repairs are necessary. From what I have read, the external tank probably needs some attention, the rest of the space shuttle stack seems to have not been damaged. Thankfully, there is enough time left until mid-February, which is considered the earliest launch date.

A German rsyslog forum…

Some of you may know that I am a native German speaker. I thought I started an interesting experiment: the “deutsches rsyslog forum” (which means “german-language rsyslog forum” ;)). It is targeted to those who prefer to express themselves in German language.

The interesting question, though, is if this forum will actually attract much attention. In German IT, there is a tendency to think that almost everyone speaks sufficiently well English so that he or she can obtain enough information to get the job done. If that proves true, there would be very little benefit in localizing any of the documentation into German language. So before seriously considering that, it is probably a good idea to do some testing. For the very same reason, my buddy Tom Bergfeld currently translates the rsyslog home page, mainly the announcements, into German. We will do a similar experiment to phpLogCon and evaluate both together after some time has progressed.

Please drop me a note if you have an opinion on this, or on localization at all.

Thanks,
Rainer

NASA’s Ares I Rocket Passes Review To Reach Critical Milestone

NASA has taken a major step toward building the nation’s next generation launch vehicle with Wednesday’s successful completion of the Ares I rocket preliminary design review.

Starting in 2015, the Ares I rocket will launch the Orion crew exploration vehicle, its crew of four to six astronauts, and small cargo payloads to the International Space Station. The rocket also will be used for missions to explore the moon and beyond in the coming decades.

The preliminary design review is the first such milestone in more than 35 years for a U.S. rocket that will carry astronauts into space. The review was conducted at NASA’s Marshall Space Flight Center in Huntsville, Ala. It examined the current design for the Ares I launch vehicle to assess that the planned technical approach will meet NASA’s requirements for the fully integrated vehicle. That ensures all components of the vehicle and supporting systems are designed to work together.

“This is a critical step for development of the Ares I rocket,” said Rick Gilbrech, associate administrator of the Exploration Systems Mission Directorate in Washington. “Completing the preliminary design review of the integrated vehicle demonstrates our engineering design and development are on sound footing, and the Ares I design work is taking us another step closer to building America’s next mode of space transportation.”

The preliminary design review included more than 1,100 reviewers from seven NASA field centers and multiple industry partners. The review is the final step of this design process. Teams representing each major part of the Ares I rocket — the upper stage engine, first stage and upper stage — all have conducted similar reviews during the past year.

The preliminary design review is one of a series of reviews that occurs before actual flight hardware can be built. As the review process progresses, more detailed parts of the vehicle design are assessed to ensure the overall system can meet all NASA requirements for safe and reliable flight. This process also identifies technical and management challenges and addresses ways to reduce potential risks as the project goes forward.

“Risk assessment is a very important part of the process,” said Steve Cook, manager of the Ares I rocket at Marshall. “It allows us to identify issues that might impact the Ares I rocket. For example, we identified thrust oscillation – vibration in the first stage – as a risk. In response to this issue, we formed an engineering team. The team conducted detailed analyses and reviewed previous test data, and then recommended options to correct the problem.”

“We intend to hold a limited follow-up review next summer to fully incorporate the thrust oscillation recommendations into the stacked vehicle design,” Cook added. “Identifying risks that can impact the project and resolving them is a necessary and vital part of the development process.”

With the completion of this review, each element of the Ares I rocket will move to the detailed design phase. A critical design review will mark the completion of the detailed design phase and allows for a more thorough review of each system element to ensure the vehicle design can achieve requirements of the Ares program.

This week, the J-2X engine will be the first Ares I element to kick off the critical design review process. The engine will power the Ares I upper stage to orbit after separation from the first stage.

“We’re excited about getting into full system engine tests with the new J-2X engine,” Cook said. “This will be one of the safest, most affordable and highest performing rocket engines ever built, and testing is critical as we begin preparation for future flights.”

Marshall manages the Ares projects and is responsible for design and development of the Ares I rocket and Ares V heavy cargo launch vehicle. NASA’s Johnson Space Center in Houston manages the Constellation Program, which includes the Ares I rocket, the Ares V vehicle, the Orion crew capsule and the Altair lunar lander. NASA’s Kennedy Space Center in Florida is responsible for ground and launch operations. The program also includes multiple project element teams at NASA centers and contract organizations around the U.S.

For more information about the Ares rockets, visit:

http://www.nasa.gov/ares

For more information about NASA’s Constellation Program, visit:

http://www.nasa.gov/constellation

a logging appliance

The IT world is increasingly turning towards appliances: pre-configured systems, which do exactly one job an do it well. Like a household appliance, all you need to do is plug it into your infrastructure, maybe change a setting or two and you are ready to go. While previously appliances always had a co-notation of a hardware box being delivered, the increasing popularity of virtualization enables to build pure software appliances.

One of the things we intend to investigate is create a logging appliance, using VMWare tools. We will set up a standard Linux, use MySQL and Apache with it and install rsyslog and phpLogCon. That in a “ready to use” fashion where only the devices need to be pointed to the right IP address of this virtual box.

This is one of my next projects and feedback on such an effort is very much appreciated.

Software hack e-gold download free

Hey, am I getting spammy? Have I been hacked? Or do I change the profession and become a top-notch e-gold hacker? lol… nice idea. But no, not really. But have a look at this post:


Download now : [some random crappy free webhost]

Send us an e-mail ,we will send you the working copy of software & as soon as you make the payment e-gold $50 1234567.We will give you the password .

Get the copy today

GoldTresor is a known software in E-Gold accessing since 2002. Now our software is very stronger than before. It accesses any E-Gold account in a few minutes and give you some ability such as transfer balance or know passphrase. Generally GoldTresor is used for those who forgot their passphrase. Also in new feature of E-Gold site that named AccSent, if you forgot your e-mail or you can’t access e-mail account, this software helps you to find your e-mail address or transfer balance to other account.

Thank you very much
[some random gmail address]


In a conversation I had with a friend of mine who runs the syslog.org forum He pointed me to his site statistics: http://www.syslog.org/forum/index.php?action=stats. While we were talking about site usage, the top notch content item of this deeply technical site drew my attention. It is the spam you can see above.

Mutex, the site owner, once decided keep a sample of the what the forum spammer left for him. Very interestingly, over time this seems to have been evolved into a the top page for egold hack downloads. At least if you do a google search “hack egold download”, his syslog site is right there in the top spot of the search results.

And what I find really interesting is that this spam accounts for nearly 10% of a quality site’s traffic – a leftover just to show off the spammers. And, no, I don’t think he gains much from that traffic, at least I tend to think that folks looking to break into e-gold suddenly turn out to be interested in the beauty of syslog ;)

Hubble “Repair” looks good

It looks good for the Hubble space telescope. According to the NASA web site (quote below), the switch to a backup system looks promising. With that, hubble could operate while the ground folks prepare final repair plans. Repairs are scheduled to be carried out as part of the space shuttle’s hubble servicing missing, which now tenatively has been moved to mid-February (some sources say Feb, 17th 2009).

From the NASA site:

The Hubble Space Telescope team completed switching the required hardware modules to their B-sides about 9:30 a.m. this morning and received telemetry that verified they had good data. Everything at this point looks good.

The 486 computer on Hubble was reloaded with data around noon and successfully performed a data dump back to the ground to verify all the loads were proper. At 1:10 p.m. this afternoon the team brought Hubble out of safe mode and placed the 486 computer back in control. Late this afternoon, Gyro #4 (which was needed for safe mode) will be turned off.

The team will reconfigure Side B of the Science Instrument Command & Data Handling (SIC&DH) computer later today and verify it is functioning properly.

Around 6 p.m. this evening the spacecraft will begin executing a pre-science command load, which involves sending normal commands to control the spacecraft and resume communications satellite tracking with the HST high gain antennas.

“We won’t know if we’ve been completely successful until around midnight Wednesday when we demonstrate that the SIC&DH Side B is talking to the instruments and able to pass data to the ground,” said HST Operations Deputy Project Manager Keith Kalinowski at NASA’s Goddard Space Flight Center in Greenbelt, Md.

Expedition 18 on the Way to ISS

A new crew that will live and work aboard the International Space Station rocketed into orbit early Sunday aboard a Soyuz spacecraft. U.S. astronaut E. Michael Fincke, Russian cosmonaut Yury Lonchakov and Richard Garriott, a U.S. computer game developer, lifted off from the Baikonur Cosmodrome in Kazakhstan at 2:01 a.m. CDT.

Fincke, the only American to launch twice on a Soyuz, will serve as commander of the six-month Expedition 18 mission. The mission’s main focus will be preparing the station to house six crew members on long-duration missions.

The Expedition 18 crew is scheduled to arrive at the station Tuesday, with docking to the Zarya module scheduled for 3:33 a.m. After the hatches are opened, Expedition 17 Commander Sergey Volkov and spaceflight participant Garriott will become the first children of previous space fliers to greet each other in orbit. Garriott is the son of former NASA astronaut Owen Garriott, who was a member of the Skylab-3 crew in 1973. Volkov is the son of veteran cosmonaut Alexander Volkov, who flew three Soyuz missions.

Garriott will spend nine days on the station under a commercial agreement with the Russian Federal Space Agency. He will return to Earth on Oct. 23 with Volkov and Expedition 17 Flight Engineer Oleg Kononenko, who have worked aboard the station since April 10.

Expedition 17 Flight Engineer Greg Chamitoff, who arrived at the station in June, will be replaced in November by NASA astronaut Sandra Magnus. Space shuttle Endeavour will deliver Magnus and return Chamitoff to Earth.

Endeavour’s November STS-126 mission also will deliver equipment to the station necessary for supporting a six-member crew, including a water recycling system, sleeping quarters, a new kitchen, a second toilet, and an advanced exercise device.

Although they will be in space on Election Day, Chamitoff and Fincke have arranged for the chance to cast their ballots from the station.


Reproduced from JSC News. To obtain it directly, follow the procedure outlined below:

NASA Johnson Space Center Mission Status Reports and other information are available automatically by sending an Internet electronic mail message to listserv@listserver.jsc.nasa.gov. In the body of the message (not the subject line) users should type “subscribe hsfnews” (no quotes). This will add the e-mail address that sent the subscribe message to the news release distribution list. The system will reply with a confirmation via e-mail of each subscription. Once you have subscribed you will receive future news releases via e-mail. To unsubscribe, send an e-mail to listserv@listserver.jsc.nasa.gov with the following command in the body of your e-mail message: “unsubscribe hsfnews” (no quotes) or from another account, besides the account used to subscribe: “unsubscribe hsfnews youremail@yourdomain.com” (no quotes).