Now it started working after a day of not working. It just started responding. I am not sure why. I suspect we were not notified that ldap had maintenance or something like that. Its the only thing I can think of because I was working on the copy of trac on the new server and had not made changes to the old server.
Thank you for your help. And this highlights my need to upgrade and I think I will try it on the new server. That may be the best way for me to do it safely anyway. On Friday, August 7, 2015 at 12:59:20 PM UTC-10, teter808 wrote: > It turns out that the only reason for the new server is to try to get the > old trac instance to work again. The old server is still up and running, it > just stopped dishing out pages. So that is the "stopped working out of the > blue". > > I will read those links. > > The part I don't understand is in step 2, if I have version 0.12 installed > with easy_install, then that is the easiest way to upgrade. I did not do an > easy_install, but the easy_install program is available. Then the page > talks about a manual install, which I may have done and if I did that then > take trac offline. But then how do I do a manual upgrade or do I do an > easy_install upgrade even if I did a manual install? And does this apply to > version 1.0.1 to 1.0.8 upgrades? > > Thank you very much for the help. > > I did see that the past post the night before things went south was an > update to a ticket (#542). I also figured that the place where I usually > see session type information when it was working is where the server might > be stopping. So, would it be "safe" to delete all the roles in the > sessions table in MySQL? Should I try to delete the last few inserts into > the ticket_change table for the ticket? > > I still need to figure out how to do an upgrade though. I want to get to > 1.0.8 just to keep current. > > > > On Friday, August 7, 2015 at 12:41:21 PM UTC-10, RjOllos wrote: > >> On Friday, August 7, 2015 at 12:35:09 PM UTC-7, teter808 wrote: >>> >>> Yes, the old server has the PATH_INFO but the new one does not. I will >>> try to fix that. I also see that there is a version difference in the old >>> (1.0.1) and new (1.0.2) servers. The new server was existing and running >>> another instance of trac that was a sandbox. I wonder if an upgrade to >>> 1.0.8 will fix things. I would have to do the upgrade and learn how to do >>> the easy_install. >>> >> >> Yeah, I would focus on the Apache configuration. The scenario you >> describe now of a server move is a bit different than "Trac stopped working >> out of the blue". >> >> There have been a number of MySQL performance improvements in 1.0.x. You >> also want to be sure that your storage engine is not MyISAM, but we should >> see an error if that was the case. >> http://trac.edgewall.org/ticket/12097 >> >> The MySqlDb page is worth reading: >> http://trac.edgewall.org/wiki/MySqlDb >> >> >>> I don't think I used easy_install to install it so I am not sure what to >>> do based on the tracupgrade wiki on the edgewall site. >>> >> >> Which part of the document do you find unclear? >> http://trac.edgewall.org/wiki/TracUpgrade#Instructions >> >> >> > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
