No website display

[Jeff Mitchell]

Hello All,

Last week we had a VMHost crap out.  I was able to move the vm of dspace to another host.  I thought everything was good but now my site won't display at all.  I have checked IP, Apache, Tomcat services but nothing displays.  I can ping the ip address internally and externally both resolve. However, no site will display.

I'm not sure which logs to look at so if someone could kick me in the right direction that would greatly be appreciated.

Thanks,

Jeff

[Javier Távara]

Did you checked your firewall configuration?

[Jeff Mitchell]

It doesn't work inside or outside. My firewall doesn't cover traffic inside. I'm restoring from backup to a test host now. If that works I'll restore to the production host to see if that changes anything.

--
You received this message because you are subscribed to a topic in the Google Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-tech/Szm4vmpLh9s/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dspace-tech...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[Jeff Mitchell]

Restoring from backup didn't change anything.  Not sure what the issue is as it was working on Thursday for sure.

[Javier Távara]

What errors are you getting?

Check your Tomcat and DSpace logs.

[Jeff Mitchell]

It is basically a 404 error but both tomcat and apache are running.

http://essays.wls.wels.net

Looking at the logs now.

[Javier Távara]

So you are running Apache HTTP as a proxy? What OS are you running?

Again, disable the OS firewall to discard it.

Check if there is something running on port 80.

You can do 

sudo netstat -plnt | grep ':80'

You should see httpd.

https://support.rackspace.com/how-to/checking-listening-ports-with-netstat/

[Jeff Mitchell]

Output:

tcp6       0      0 127.0.0.1:8005          :::*                    LISTEN      2478/java       

tcp6       0      0 :::8009                 :::*                    LISTEN      2478/java       

tcp6       0      0 :::80                   :::*                    LISTEN      2573/apache2    

tcp6       0      0 :::8080                 :::*                    LISTEN      2478/java  

--

You received this message because you are subscribed to a topic in the Google Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-tech/Szm4vmpLh9s/unsubscribe.

To unsubscribe from this group and all its topics, send an email to dspace-tech+unsubscribe@googlegroups.com.

[Jeff Mitchell]

Sorry - Running Debian 7

Jeff

On Monday, February 20, 2017 at 1:46:02 PM UTC-6, Jeff Mitchell wrote:

Output:

tcp6       0      0 127.0.0.1:8005          :::*                    LISTEN      2478/java       

tcp6       0      0 :::8009                 :::*                    LISTEN      2478/java       

tcp6       0      0 :::80                   :::*                    LISTEN      2573/apache2    

tcp6       0      0 :::8080                 :::*                    LISTEN      2478/java  

[Jeff Mitchell]

If I am looking at the output correctly Java is listening on 8080 but tomcat should be.  Is that right, or do I need to switch something?

If I need to switch something, how would that get changed?

Jeff

[Jeff Mitchell]

A restore has fixed nothing, I look through the logs and nothing stands out.  Would now be the time to just build a new server?  If so, can I just do a DB dump and then rebuild?

Any benefit to going to 6.x now?  Or should I stay with 5.x - I was on 5.1 but was holding off upgrading until 6 was released.  Which I missed my opportunity :(

Thanks in Advance,

Jeff

[George Kozak]

Jeff:

I don't know if this is helpful, but I had a similar problem when I moved our Test instance to a new Development server when I was planning on upgrading from DSpace 5.5 to DSpace 6.0.  The Development server was running a different version of Tomcat, and I discovered that I needed to change how I defined my site in the tomcat conf/server.xml file.

On my test and production machines, I defined my tomcat root as:

<Context path="" docBase="(path to tomcat)/webapps/xmlui" />

but on my development server that it did not work and created a blank page.  I discovered that I had to change the context path by adding a "/" on my development server:

<Context path="/" docBase="(path to tomcat)/webapps/xmlui" />

This may not be your problem, but you may want to check out how DSpace is defined in your tomcat's server.xml file.

George Kozak

Cornell University

--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscribe@googlegroups.com.

To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

--

***************************
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924

gs...@cornell.edu

[Jeff Mitchell]

I am running dspace 5.1 on Debian 7.

If I look at /etc/tomcat7/server.xml - I don't see anything for context path. Am I not looking in the right location?

Jeff

To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.

To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[Javier Távara]

Jeff, take a look in /etc/tomcat7/conf/Catalina/localhost/

[Jeff Mitchell]

Javier,

Nothing in that file.

Jeff

[George Kozak]

Jeff:

 In general, in server.xml, is where you define what is the root for tomcat and what webapps are activated and how to get to them.  I'm surprised that nothing is showing up.  Maybe that's the problem, or the definitions could be somewhere else, like <tomcat>/bin/setenv.sh.  Somewhere in tomcat the path to the webapps and what is the root webapp and what the DSpace instance is called has to be defined.  Anyway, here is how the pertinent part of my server.xml is set up on my production server:

     <Host name="localhost"  appBase="webapps" unpackWARs="true" autoDeploy="true">

        <Alias>(my ip goes here)</Alias>

        <Alias>(my DSpace site name goes here)</Alias>

       (I am skipping a bunch of stuff that I didn't change, then further in the definition, I added)        

       <Context path="" docBase="(path to tomcat)/webapps/xmlui" />

       <Context path="/oai" docBase="(path to tomcat)/webapps/oai" />

       <Context path="/jspui" docBase="(path to tomcat)/webapps/jspui" />

       <Context path="/rdf" docBase="(path to tomcat)/webapps/rdf" />

      <Context path="/rest" docBase="(path to tomcat)/webapps/rest" />

       

       <Context path="/solr" docBase="(path to tomcat)/webapps/solr" />

       <Context path="/sword" docBase="(path to tomcat)/webapps/sword" />

  

       <Context path="/swordv2" docBase="(path to tomcat)/webapps/swordv2" />

    </Host>

I hope this is of some help.

George Kozak

Cornell University

To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscribe@googlegroups.com.

To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.