First of all I am new to TURNKEY and to bugzilla. I have setup this Bugzilla solution ( and got the system running in a ec2 micro.

When I went in to setup email using a gmail account I've set these settings in bugzilla administration-> parameters

I can send emails out with bugzilla but I cant figuire out how to file bugs via email

can anyone point me in the right direction on how to accomplish this?


Jeremy Davis's picture

I'm guessing that perhaps you are using the old appliance from the Amazon marketplace? I didn't work on it myself, but AFAIK the latest version of TurnKey Bugzilla (v14.1) includes this OOTB (although is not yet available on the MarketPlace - it's coming but not sure when). If you are happy using a micro server then you can launch TurnKey micro servers on AWS from the Hub for free.

Please let us know how it goes.

thanks for the reply jeremy

I'm using version 13.1 that's in aws market place. I thought that was the latest one, didn't know that a newer version available in turnkey site. 

Are there any downsides to using the older 13.1 version?

if so how do I update to latest version?

I'm not that knowledgeable in linux so getting thigs done has been somewhat of an uphill battle for me.

but google is always your friend right? ;)

anyways, hope you could shed some light on what I should do next

Jeremy Davis's picture

We are in the process of getting newer images uploaded there but I'm not sure when it will be...

The downside is that it is an older base operating system (v13.x was based on Debian Wheezy aka 7.x; v14.x is based on Debian Jessie aka 8.x). It also includes quite an old version of Bugzilla too. The final factor, is that our newer images are built in the new Amazon format and so can be run on the newer server types/sizes that Amazon offer.

Because we build our images fr0om scratch and update the build code when we update the images; it isn't really that easy to update the whole server to the latest version. Also because of the way Amazon do things there is a nasty bug that will make your server unbootable if you do a "normal" Debian OS update (I don't recall the workaround, but there is one...).

Another option is to just update the Bugzilla software itself (i.e. leave the OS be as is - it is still supported by Debian so still gets security updates). I have updated our Bugzilla appliance previously; but as I mentioned above, the process is a bit different to manually updating it on an actual installed server.

Also sometimes you can run into issues with the available versions of software (from the Debian repos i.e. installed via apt) being too old for newer versions of software like bugzilla. I don't know if that will be an issue or not... You may find our appliance build code somewhat useful (or perhaps not!?) Regardless you can find that here:

What sort of traffic are you expecting? Like I said the new version is available via our Hub (free Hub plan supports AWS t2.micro servers). That would be by far the easiest option. Alternatively if you want to test the newer version first (of course for free), you could download the OVA (download the "VM" from the Bugzilla appliance page). Then use VirtualBox (or similar) to host it locally - at least to test it out.

Yeah google is always your friend! :) If you keep in mind that TurnKey is based on Debian (as is Ubuntu - although TurnKey is much closer to Debian than Ubuntu) you'll find plenty of relevant info. What can be a little confusing sometimes is that some Linux stuff (i.e. ideas/concepts/commands/etc) is totally generic and will work on pretty much any 'nix (sometimes even including OSX!) whereas other things are very distro specific. Although like I said there should be plenty of Debian info so stick to that where you can and you shouldn't go wrong!

Let me know how you go with it all... I can't guarantee that I'll be able to help out, but I'll try! :)

Thanks for the reply jeremy. very thorough and thoughtful answer. 

I'm thinking of launching a new instance from turnkey hub with the new version of bugzilla(v 14)

Is there a difference between launching from turnkey hub as opposed to launching from aws marketplace?

are there any added charges if it is launched from turnkey hub?

sorry if I'm asking a noob question but I don't know anything about turnkey appliaces or turnkey hub

hope you could help

Jeremy Davis's picture

I've been caught up dealing with issues related to some last minute bug hunting on our brand new shiny v14.1 release.

TBH I actually thought that I had already relied but I must have clicked "preview" instead of "save"... :( So please don't apologise about being noob! We've all been there at some point and even after years of posting on these forums I still sometimes do dumb stuff like that! :)

To answer your question though; the images on the Amazon MarketPlace are essentially the same as the Hub images, however the current images on the MarketPlace are really old (v13.0); whereas the images on the Hub are the latest ones (v14.1).

Everything about the v13.0 images is old; the underlaying operating system, the TurnKey components and the version of Bugzilla installed on top.

As I mentioned in the blog post we are in the process of upgrading the images on the MarketPlace but we have not ETA on them. As we control the Hub ourselves we can upload new images there as soon as we build them. OTOH Amazon control their MarketPlace so we need to wait while they go through their process. We did originally plan to upload our v14.0 images there but we'll be going straight to the v14.1 images now...

Personally I recommend that you use the Hub as it's a more pleasant experience IMO; although I'm obviously biased! :)

Regardless good luck with it all and let me know if you have any further issues. PS obviously it's polite to be a little patient but in future please do not hesitate to bump a thread if you aren't getting a timely response

thanks for the reply jeremy, and I'm happy to say that I've followed your advice and switched to the new version.

couldn't be happier with the new version, which was easier to setup in my opinion (maybe because I've gone through the same thing with the previous version so I kinda had an idea on what to do) and mail works fine as of now.

Its a big learning curve but I'm kind of getting the hang of things so thanks for all your help

can you please tell me what are the limitations of t2 micro instance? how many bugs / concurrent users can the micro instance handle? at which point would I run out of resources prompting for a upgrade?

hope you could help and I really appreciate taking time out of your busy schedule to answer these questions


Jeremy Davis's picture

Thanks for your feedback. Unfortunately I can't give you a clear and reliable indication of what you can expect from micro. Some users are really happy; others find them useless.

IMO, as a general rule a micro is really only good for a very small user base. It shouldn't be too much of an issue with regard to how many bugs you have; it's more concurrent users that will be the issue. Also over time you may find that resources get exhausted.

I recommend that you enable Amazon CloudWatch. According to the pricing page it's free for basic usage on your first few servers. Then you'll know if there's issues.

The thing that is most likely to happen is that the MySQL DB backend will crash (that's the most common result of running out of RAM). Then your site will usually give you an error message but restarting MySQL (service mysql start) will fix it. If it runs out of CPU it will usually stop responding altogether.

If your site isn't mission critical and you want to minimise your spend, then you may be willing to put up with the occasion outage. You can just restart MySQL or reboot the server to resolve it. However if it happens regularly it's time to upgrade to a bigger server.

If you want to upgrade to a bigger server then the best way to go is to do a TKLBAM backup and restore the backup to a new server.

Add new comment