Hey all, Just another weekly update on GeoNode developments: First in my mind among this week's GeoNode news is the further delay of the 1.0.1 release - it's been delayed again. As discussed on the development list we have deployed a candidate for GeoNode 1.0.1 to the demo server at http://demo.geonode.org/ for some "field" testing to see if some prospective reliability improvements actually improved uptime. Things do indeed look better, but we did have some failure this weekend and again on Monday. I have tweaked the Java configuration on the server and added a robots.txt file (one of the outages was the result of simultaneously being crawled by Googlebot and MSN) but since that didn't happen until late Monday we are only at 4 days of uptime at this point. So, hopefully GeoNode 1.0.1 will be released next week. The second big development in GeoNode this week is a call for architecture review. In particular, deployments of GeoNode such as Risiko and Harvard Worldmap rely on GeoNode not just as a tool, but as a base for further customization and implementation of new tools. If you are working on such a project and running into problem points in your customization of GeoNode, or just running a basic GeoNode site, we are interested in your ideas about how we can make it easier for you to make your customizations and avoid integration problems when integrating new improvements from the base GeoNode project. We invite you to discuss such ideas on the GeoNode development list, hosted on Google Groups at https://groups.google.com/a/opengeo.org/group/geonode-dev/ -- David Winslow OpenGeo - http://opengeo.org/
Hello ,
I had stopped using geonode for sometime because of the previous bugs
I used to get like the "500 internal server error" . So is the bug fixed yet
? Should I go for a fresh installation of Geonode ?
On Sat, Apr 23, 2011 at 3:46 AM, David Winslow <dwinslow@opengeo.org> wrote:
> Hey all,
>
> Just another weekly update on GeoNode developments:
>
> First in my mind among this week's GeoNode news is the further delay of the
> 1.0.1 release - it's been delayed again. As discussed on the development
> list we have deployed a candidate for GeoNode 1.0.1 to the demo server at
> http://demo.geonode.org/ for some "field" testing to see if some
> prospective reliability improvements actually improved uptime. Things do
> indeed look better, but we did have some failure this weekend and again on
> Monday. I have tweaked the Java configuration on the server and added a
> robots.txt file (one of the outages was the result of simultaneously being
> crawled by Googlebot and MSN) but since that didn't happen until late Monday
> we are only at 4 days of uptime at this point. So, hopefully GeoNode 1.0.1
> will be released next week.
>
> The second big development in GeoNode this week is a call for architecture
> review. In particular, deployments of GeoNode such as Risiko and Harvard
> Worldmap rely on GeoNode not just as a tool, but as a base for further
> customization and implementation of new tools. If you are working on such a
> project and running into problem points in your customization of GeoNode, or
> just running a basic GeoNode site, we are interested in your ideas about how
> we can make it easier for you to make your customizations and avoid
> integration problems when integrating new improvements from the base GeoNode
> project. We invite you to discuss such ideas on the GeoNode development
> list, hosted on Google Groups at
> https://groups.google.com/a/opengeo.org/group/geonode-dev/
>
> --
> David Winslow
> OpenGeo - http://opengeo.org/
>
--
*Satyajit Sarangi*
"500 internal server error" is a very generic error and doesn't tell much about what went wrong. It may indicate a configuration problem, or a bug in GeoNode, or something external to your software (such as a failing hard drive.) So I can't say with any confidence whether the cause of your particular error has been resolved. Issues have definitely been resolved between GeoNode 1.0 and 1.0.1, but there are also definitely some bugs remaining. If you are interested in resolving your issues, I would recommend discussing the specific problems you're seeing on this mailing list rather than waiting for the next release and hoping that someone else has discovered and resolved your specific issue (which might turn out to be a configuration problem specific to your system and not a general GeoNode issue in the first place.) -- David Winslow OpenGeo - http://opengeo.org/ On Mon, Apr 25, 2011 at 1:42 AM, Satyajit Sarangi <writetosatyajit@gmail.com > wrote: > Hello , > > I had stopped using geonode for sometime because of the previous > bugs I used to get like the "500 internal server error" . So is the bug > fixed yet ? Should I go for a fresh installation of Geonode ? > > > On Sat, Apr 23, 2011 at 3:46 AM, David Winslow <dwinslow@opengeo.org>wrote: > >> Hey all, >> >> Just another weekly update on GeoNode developments: >> >> First in my mind among this week's GeoNode news is the further delay of >> the 1.0.1 release - it's been delayed again. As discussed on the >> development list we have deployed a candidate for GeoNode 1.0.1 to the demo >> server at http://demo.geonode.org/ for some "field" testing to see if >> some prospective reliability improvements actually improved uptime. Things >> do indeed look better, but we did have some failure this weekend and again >> on Monday. I have tweaked the Java configuration on the server and added a >> robots.txt file (one of the outages was the result of simultaneously being >> crawled by Googlebot and MSN) but since that didn't happen until late Monday >> we are only at 4 days of uptime at this point. So, hopefully GeoNode 1.0.1 >> will be released next week. >> >> The second big development in GeoNode this week is a call for architecture >> review. In particular, deployments of GeoNode such as Risiko and Harvard >> Worldmap rely on GeoNode not just as a tool, but as a base for further >> customization and implementation of new tools. If you are working on such a >> project and running into problem points in your customization of GeoNode, or >> just running a basic GeoNode site, we are interested in your ideas about how >> we can make it easier for you to make your customizations and avoid >> integration problems when integrating new improvements from the base GeoNode >> project. We invite you to discuss such ideas on the GeoNode development >> list, hosted on Google Groups at >> https://groups.google.com/a/opengeo.org/group/geonode-dev/ >> >> -- >> David Winslow >> OpenGeo - http://opengeo.org/ >> > > > > -- > *Satyajit Sarangi* > >