You are here
Basil Kurian - Tue, 2010/08/24 - 10:15
Home URL :http://www.cacti.net/
Cacti is a complete network graphing solution designed to harness the power of RRDTool's data storage and graphing functionality. Cacti provides a fast poller, advanced graph templating, multiple data acquisition methods, and user management features out of the box. All of this is wrapped in an intuitive, easy to use interface that makes sense for LAN-sized installations up to complex networks with hundreds of devices.
Admin username : admin
Admin pasword :admin
Base : Turnkey LAMP Lucid
Forum:
Tags:
Patch tested
Working !
Redirecting HTTP to HTTPS
default virtualhost need to
default virtualhost need to be changed to
New patch attached
Tested, working !!
Excellent + Diff
Thanks Basil, this takes care of it. For others who are reading the thread I'm including the diff to show how this is done:
My first try!
Ok, so here I am, trying to patch for my first time, I've downloaded the LAMP appliance ISO and then I've made:
tklpatch turnkey-lamp-2009.10-2-hardy-x86.iso Cacti.tar.gz
This is the output:
Two things I love: Linux and my sax
This patch is for TKL beta (Lucid) - Not TKL stable (Hardy)
So you'll need to get the TKL-Core-Lucid, patch it with Basil's LAMP TKLPatch. The resulting ISO will in effect be TKL-LAMP-Lucid and you may wish to keep a copy of that somewhere if you plan on trying some of the other patches (many of them - especially Basil's ones, rely on TKL-LAMP-Lucid). Then patch that ISO with this patch.
A little bit of mucking around but hopefully worth it! Another option is to patch the file system rather than the ISO. Personally I don't really recommend that as problems can sometimes occur (it will error if any of the services the patch patches are running) but its an option. Have a look at the bottom of this page for details.
OK, second try...
I see now, well, sounds a bit f a hassle to "patch the patched" but I'm trying it now with the right versions.
I've successfully patched the lucid beta core ISO with the LAMP patch, now I have the LAMP ISO and I've also saved it aside for future use.
Now I'm trying to apply the Cacti patch to the LAMP ISO and this is what I've got:
Sooo, what now?
BTW, how can I attach a file here? I saw others did...
Two things I love: Linux and my sax
Hmm, not sure...
I'm guessing from what you've posted that something went wrong.
We really need Basil here to have a look at this, he'd be in a much better position to offer useful suggestions. Some of the stuff towards the end suggests to me that there may be some issues with his patch (rather than other possible issues) but I'm too much of a LInux newb to be sure.
Out of interest what is your patching environment? Are you running TKLPatch inside a VM of TKL-Core-Lucid? Or have you got it installed in something else?
You need to start a new thread to attach a file (only first posts in a new thread allow attachments).
>> socket
>> socket turnkey-LAMP-lucid-x86.rootfs/var/spool/postfix/private/uucp ignored
This kind of warning occurs in some machines when a patch consisting of postfix package (in lucid), is executed. We can ignore this warning, the ISO creation will be successfull. All the patches which i submitted is tested only in this scenario
or
I never tried any patch in running instances by
These days I'm too busy with a project in my company :(
TuxSax - Perhaps just try installing patched ISO?
If you have 5 mins to spare, perhaps try installing from your new (Cactii) ISO and see if it works. You never know your luck?!
Keep us posted on how you go.
shows that you are patching the ISO so we can rule that out as an issue. Also the above line answers my last question too ("root@core" - suggests to me that you're working inside TKL-Core-Lucid - which is good).
Ok good to know that the warnings at the top can be safely ignored then.
The last few warnings seem almost like the startup scripts in the patch aren't upstart compliant? I can't check that without lookng at the patch (which I don't have time for at the moment either). But if you want to get your hands dirty TuxSax then have a look at the conf file in the patch and do some research around upstart in Ubuntu 10.04 (some services now use a different way of starting and stopping called Upstart). Be warned though I'm only guessing really, hopefully I'm not sending you off on a wild goose chase :)
Maybe you didn't understand
I've forgotten to point that there is no patched ISO at the end of the process, actually the process didn't end successfully. It's just quitting on me like that, all I have after that is the unpacked folders but no ISO file is created.
I'm running a VirtualBox machine installed w/ tkl core, inside this box I'm trying to perform all the patching, the first one went fine, I have a LAMP ISO, now I've only tried to patch that LAMP with the Cacti patch.
Perhaps I need to run it on a real box instead of a VM?
Two things I love: Linux and my sax
Hmm, no ISO is a big problem!
Sorry I missed that bit! From what I can gather, you're doing everything fine...
I'm pretty sure that some of the commands in this patch are incompatible with Lucid (due to upstart). I've just had a quick look and despite the fact that Basil said this patch is for Lucid, I think it may be for TKL-LAMP stable (so you were on the right track initially - although I still have no idea about your original error).
This leaves you with a number of possible ways forward (not sure which is best, or even if any/all of them will actually work):
I tried that patch on my TKL lucid LAMP
In my case , though inclusion of postfix package produced some warning during patching , the patching was sucessfull.... I don't know what went wrong in your case :( It would be nice, if someone else also try that patch. ..
Let me help a bit on this
Hi, I can see the errors and I'll try to help here:
What's happening is a problem of not stoping services in the patches. As mysql was not stoped in the previous patch, it's unable to start in the Cacti patch.
In the LAMP_lucid patch, Basil forgot to stop services. You must add at the end of the patch:
That way, those services are stoped and you won't get the initial errors.
To prevent this warning:
Rather than invoking init scripts through /etc/init.d, use the service(8)
Is easy, insted of calling services using "/etc/init.d/servicename action", in Ubuntu 10.04 you should use the more standarized form "service servicename action". This is a safe error to skip, but it's nice to start using the standar way of doing things, to be sure that in the future everything would work.
So instead of "/etc/init.d/mysql start" use "service mysql start" and so on.
Also, a recommendation: it's not a good practice to create files directly in /etc/apache2/sites-enabled. You should create or symlink files in /etc/apache2/sites-available, and then use the apache commands to enable/disable sites: "aeensite nameofsite" to enable and "a2dissite nameofsite" to disable.
You shouldn't ignore any errors in the patching process, as this could lead to future problems in the appliance. So be sure to stop the services again in the cacti patch at the end. (only the one started, mysql in this case)
Basil, what's that hostname service you use in LAMP patch? I also noted that you added mod_rails to the LAMP, I think LAMP should only include PHP, but as the official also includes Python and Pearl support, maybe the name should change to something like "Apache application server" or something like that.
That's my 2 cents...
Then it should be named
Then it should be named LAMPPP, maybe...
Two things I love: Linux and my sax
Thanks Adrian
Changes applied on both LAMP and Cacti patches. Thanks !
Politeness goes a long way and costs very little...
Considering that this is a community developed appliance TKLPatch (produced by an unpaid volunteer) then I don't think that Basil (or anyone else) should do anything for you!
Perhaps it would be nice if he did or helpful for you if he did, but IMO if you want more information you need to make a polite request rather than what appears to be a demand, or at least an expectation of minimum requirements. Is that you you speak to others that give you gifts? If someone gave you a birthday present that you didn't know how to work would you tell them that they should have provided better instructions? Or would you politely ask them for help?
Besides, if you read the full thread (above) I think that there is enough information for you to have a search (top right) and you will find the documentation for TKLPatch (and how to apply them). Although bottom line is, considering this patch is two and a half years old and applies to a beta version of a previous TKL appliance (which is no longer even available) I suspect that it is too out of date to be applied as is anyway. I strongly suspect that it would need some serious tweaks before being immediately usable...
Add new comment