On Mon, Aug 1, 2011 at 3:39 PM, Anoop Thomas Mathew <atm...@gmail.com>wrote:
> Hi, > > Thank you all for your suggestions, Especially, Cal and Sam. > I'd go with Debian Squeeze. That seems to be the best choice for now. > +1 on Sams comments. > > To be clear about the question, I'm using linux operating systems for the > past 7 years. The errors are not specific nor recurring, nor even device > specific. Just gets stuck in between. I've never checked the log, as you > said, that might have helped. Same OS on a server with a specific app > running, might run stable for years. The time gap would be 2-3 months > between screen freezes. And nothing in specific would be there to note. I > just want an OS which is a Juggernaut, that's it. > Screen freezes can sometimes be relates to the OOM-killer entering into an unrecoverable loop (this happens when certain drivers are loaded at run time, as they cause the oom_score to act crazily). They can also be related to the server hitting swap (which I went into detail on earlier). Could possibly be faulty memory (try running memtest86+ from boot). Or, it could even be something causing the kernel to seg fault (certain file systems, such as OCFS2, can cause this to happen). Hope this helps, and good luck! > > Compare this to a rolling release or distro with releases every 6-12 > months where kernel is changing and OS has bleeding edge versions and > you will have a larger gaumet of issues. Concequently you will have to > know more and be better at problem solving. Will you have a rollback > plan when the dist-upgrade finishes and something breaks in a new > exciting way? > > > > I'd seriously consider a rollback plan if it breaks. > Personally, I keep all our installs separated by means of LXC (google for 'lxc cgroup'). Meaning, there is a host OS and a guest container. The host OS is on LTS with security updates only, whilst the guest OS is on more frequent updates. This makes repair a lot easier if something breaks in the guest OS. (LXC isn't virtualisation, it uses cgroups in the kernel, but you need to know your way around the kernel compile quite well to get it working properly. On top of this, I personally don't use 'dist-upgrade' and much prefer to do a system re-install where possible. As we use LXC, once the host is re-installed, it's just simply a case of copying over the guest container, and placing into initd. If we had iSCSI, it would be even simpler. And if you had an auto deploy image, that would be even simpler still. But it's taken us almost 5 years to get to the point where we are comfortable with our processes. It's really a self learning curve to find what suits you best :) > So Thanks again, > > Anoop > > atm > ___ > Life is short, Live it hard. > > > > > On 1 August 2011 18:55, Sam Walters <mr.sam...@gmail.com> wrote: > >> If a modern linux OS is crashing then it will likely /var/log whats >> going wrong. The phrasing of this issue seems to indicate lack of >> experience or familiarity with the linux os or unix model of os. >> Thats no problem if you are keen to learn the principles of the OS you >> will get better at using the OS and identifying issues. >> >> Now to answer your question specifically: >> debian stable branch is a good idea. I assume you will stick to >> something and keep it so go for a distro with long term support/longer >> release cycle. >> >> http://en.wikipedia.org/wiki/Debian#Stable_ports >> >> Good documentation, forums, community support. >> >> I would avoid rapid release cycle stuff unless you know what you're >> doing. Eg: i use apto-sid which is an unstable branch of debian for >> some servers but i know what im getting myself into. >> >> I say debian because the package management, runs nearly all the >> dependencies that django and a lot of its addons require. Also once >> you have built a server stack... eg: nginx+fcgi+django+memcached+mysql >> or any web server stack of your choice on a stable distro you will >> reduce the pool of possible issues with any of these aformentioned >> components to a minimum and the problems can be googled with ease. And >> keep doing this for ~5 years until they stop the LTS and it stops >> getting security patches. eg: debian etch 2010 >> >> Compare this to a rolling release or distro with releases every 6-12 >> months where kernel is changing and OS has bleeding edge versions and >> you will have a larger gaumet of issues. Concequently you will have to >> know more and be better at problem solving. Will you have a rollback >> plan when the dist-upgrade finishes and something breaks in a new >> exciting way? >> >> Obviously you can develop on any flavour of linux shouldnt matter. >> Managing a production server is different ballgame. >> >> >> good luck and i hope this advice helps >> >> >> >> On Mon, Aug 1, 2011 at 6:27 PM, Anoop Thomas Mathew <atm...@gmail.com> >> wrote: >> > Hi All, >> > Firstly, I am not here for a distro war. >> > I was using ubuntu 9.10, and then switched to fedora 14 and then to >> fedora >> > 15. >> > IMHO, It seems that they all were quite unstable. (Many times it hung up >> on >> > my Dell and HP machines - may be driver issues, still I don't want that >> > too.) >> > I would really like some recommendation for a linux distro which is much >> > stable, but still can support all relevant packages. >> > Top recommendations I found around was Debian and OpenSuse. >> > Please revert with your suggestions. >> > Thanks, >> > Anoop Thomas Mathew >> > atm >> > ___ >> > Life is short, Live it hard. >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "Django users" group. >> > To post to this group, send email to django-users@googlegroups.com. >> > To unsubscribe from this group, send email to >> > django-users+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/django-users?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To post to this group, send email to django-users@googlegroups.com. >> To unsubscribe from this group, send email to >> django-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-users?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
