So you'll need to get the, patch it with Basil's. 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.
This all assumes that you have Cacti installed. If you need help installing Cacti, see the article: Install Cacti on CentOS 6. This articl will help you Monitor VMware ESXi Hosts with Cacti. Enable SNMP Service in VMware ESXi. The first step is to enable the SNMP service in your VMware ESXi host.
Have a look at the bottom of page for details. 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 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 tklpatch lucid-core.iso LAMPpatch or tklpatch LAMP.iso cactipatch I never tried any patch in running instances by tklpatch / LAMPpatch.iso These days I'm too busy with a project in my company:(. 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. Root@core # tklpatch turnkey-LAMP-lucid-x86.iso Cacti.tar.gz 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 (' - 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:). 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? 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):. Backtrack go with your original plan of patching TKL-LAMP stable. Note that this has to be done inside TKL-Core stable (Or Ubuntu Hardy - not TKL-Core-Lucid). Not sure about the error you had, perhaps try install and see what happens.
Install the TKL-LAMP-Lucid ISO (patched with Basil's LAMP patch) that you have and patch the file system using the tklpatch-apply command. You'll need to stop the LAMP services from running first.
Service apache2 stop and service mysql stop. Get your hands dirty and manually create the ISO. If you look in the (scroll down to Command Syntax) and take each step at a time. After extracting the root filesystem, copy the contents of overlay from the patch over your root folder. Run the command apt-get update && apt-get install cacti and then build the ISO. Install and configure Cacti yourself (on top of TKL-LAMP stable, or the TKL-LAMP-Lucid ISO you've made). Wait for Basil to have time to have a closer look.
Wait for the TKL devs to produce the official TKL-Cacti appliance. Some other option I haven't thought of.
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 LAMPlucid patch, Basil forgot to stop services. You must add at the end of the patch: service apache2 stop service mysql stop service postfix stop 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 modrails 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. 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.
Installation Process To install the OVF, you must first download it from and save it to disk. Then, you must import it into your virtualization platform. The process for this varies. On VMware Player, choose File-Open a Virtual Machine from the menu and select the cw-aio.ova file you downloaded.
On the Import Virtual Machine dialog that appears, the defaults are normally fine, so you can just click Import. On VirtualBox, choose File-Import Appliance from the menu. In the Appliance Import Wizard, click Choose, select the cw-aio.ova file you downloaded and click Next. On the next tab, you can view the settings and then click Import. On VMware ESXi, using the VMware vSphere Client, choose File-Deploy OVF Template from the menu.
![Cacti Cacti](/uploads/1/2/5/6/125612471/548429768.png)
Select the cw-aio.ova file you downloaded and click through assigning it a suitable name, location and attached network (which must support DHCP) before finally clicking Finish to create the virtual machine. Running and Using the Image Once you’ve installed the virtual machine, you should start it in the usual way for your virtualization platform. If you attach to the console, you should see an Ubuntu loading screen and then be dropped at a cw-aio login prompt.
![Cacti Vmware Image Cacti Vmware Image](http://www.unixmen.com/wp-content/uploads/2015/02/cacti5.png)
The username is ubuntu and the password is cw-aio. Note that the console is hard-coded to use a US keyboard, so if you have a different keyboard you might find that keys are remapped - in particular the - key. The OVF provides 3 network services. SSH - username is ubuntu and password is cw-aio.
HTTP to ellis for subscriber management - sign-up code is secret. You will probably want to change this to a more secure value - see for how to do this. SIP to bono for call signaling - credentials are provisioned through ellis. How these network services are exposed can vary depending on the capabilities of the platform. VMware Player sets up a private network between your PC and the virtual machine and normally assigns the virtual machine IP address 192.168.28.128.
To access ellis, you’ll need to point your browser at. To register over SIP, you’ll need to configure an outbound proxy of 192.168.28.128 port 5060. VirtualBox uses NAT on the local IP address, exposing SSH on port 8022, HTTP on port 8080 and SIP on port 8060. To access ellis, you’ll need to point your browser at. To register over SIP, you’ll need to configure an outbound proxy of localhost port 8060. VMware ESXi runs the host as normal on the network, so you can connect to it directly. To find out its IP address, log in over the console and type hostname -I.
To access ellis, just point your browser at this IP address. To register over SIP, you’ll need to configure an outbound proxy for this IP address. Once you’ve successfully connected to ellis, try - just remember to configure the SIP outbound proxy as discussed above.