Ooops, instead of tei-roma/roma.php I meant tei-roma/roma/roma.php. On 15-07-27 02:45 PM, Martin Holmes wrote:

Hi Kevin, Sebastian et al,

I've just done a quick bugfix for the Roma PHP webapp:

https://sourceforge.net/p/tei/bugs/724/

and tested it locally and it seems to work fine.

As far as I can tell from browsing around the projects/tei/web/Vault directory, the current deployed version of Roma on tei-c is 4.15; the new build is 4.18. The system looks similar to the setup for P5, where the "current" symlink points to whatever should be the current version. I think (but I'm not sure) that we can get a new version deployed like this:

- Create new 4.18 directory

- Get the latest build from Jenkins: http://teijenkins.hcmc.uvic.ca/job/Roma/lastSuccessfulBuild/artifact/tei-rom...

and unzip it into there.

- Change the "current' symlink to point at it.

However, there's something slightly odd going on. As far as I understand it, tei-roma/roma.php requires a file called config.php in the same directory. That file is (I thought) created by copying the file config-dist.php to config.php and then customizing it as necessary for the local install. roma/roma.php contains this:

require_once( 'config.php' );

so it it's definitely expected to be available. But in current/tei-roma/roma, there is no config.php; there are various versions of config-dist.php resulting from what appears to be an svn conflict, where the differences amount only to the version number and date.

So my question is: am I wrong about the fact that config.php is expected to be created from config-dist.php? That is what I did on my local test install, and it worked fine.

If I'm right, that would seem to suggest that Roma on tei-c.org has been running slightly misconfigured, and managing without the missing config.php somehow (perhaps error messages are being suppressed).

Does anybody know anything about this? I'm not seeing any documentation on how to deploy the PHP Roma, so I've started a new section on the wiki page:

http://wiki.tei-c.org/index.php/Roma#Getting_the_Roma_server_running

Cheers, Martin

On 15-07-27 01:44 PM, Kevin Hawkins wrote:

...

As you've probably seen by now, we did in fact get a notification from Uptime Robot, and it's already back up.

This is the first time I've seen the TEI site go down while I'm at my computer. The ADHO site remained up during that time, and given how often I've seen notifications that that site goes down while the TEI site stays up, it appears that these two sites function independently despite sharing a hosting service.

Nick, I'm going to turn off the Uptime Robot notifications for the ADHO site for now.

Kevin

On 7/27/15 3:42 PM, Martin Holmes wrote:

...

Hi Kevin,

I was just working on Roma on tei-c when it stopped responding. I then went to try tei-c.org, and the site doesn't seem to be responding. If you ping it, the ping is returned by digitalhumanities.org, so tei-c appears to be up for services like isup.me, but wget requests never get a response, and I see this proxy error message eventually in my browser:

Proxy Error

The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /index.xml.

Reason: Error reading from remote server

Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request.

Just letting you know, because I don't know whether uptimerobot will notice it.

Cheers, Martin