purepennons / gss

Automatically exported from code.google.com/p/gss
Other
0 stars 0 forks source link

Files not showing in GUI #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. login without authentication to http://localhost:8080/pithos/login?
next=http://localhost:8080/pithos/

What is the expected output? What do you see instead?

List of files and folders

What version of the product are you using? On what operating system?

I am using CentOS 5.4 x64, Jboss AS 5.1.0, HornetQ 2.0

Please provide any additional information below.

I am seeing lot of HornetQ errors about passing messages, and I cannot seem 
to build solr neither patch it with rich patch. I am using versions that 
are listed on Building and Deploying in wiki. Could you please help me out.
I installed hornetq for jboss as5 - I ran build.sh as5. 

I am attaching server.log file showing errors from solr and hornetq.

Files count and total size is shown in bottom left corner. GUI complains 
that it can not get file information.

Regards,
Nikola

Original issue reported on code.google.com by ngara...@gmail.com on 22 Apr 2010 at 1:57

Attachments:

GoogleCodeExporter commented 8 years ago
Edit:

What is the expected output? What do you see instead?

Expected is list of files and folders. I do not see any files in provided 
window in 
interface. Only totals in bottom left corner.

Original comment by ngara...@gmail.com on 22 Apr 2010 at 1:59

GoogleCodeExporter commented 8 years ago
From your log I assume that you try to deploy Solr inside JBoss. This should 
work, but it is something we haven't 
tried. Try running solr standalone with jetty as specified in its 
documentation, to try and debug this. However, a 
missing Solr is not going to affect the service much, despite the errors in the 
log. At most you will not be able to 
index and search files. I assume that you have already created some folders and 
uploaded some files that you 
expect to appear in the web client, correct? Can you attach a screenshot of the 
web client in its "empty" state that 
you describe? It will help me see what you actually see.

Original comment by past...@gmail.com on 22 Apr 2010 at 5:05

GoogleCodeExporter commented 8 years ago
Dear Sirs,

I have trouble building solr with ant, I ran ant dist and got some files in 
dist 
foldet that I copied to jboss server. I am looking for guide to install solr as 
standalone. Hope I will work it out.

I have uploaded files and created some folders. And yes, I expect them to 
appear in 
web client. Everything actually appears for about a second and then disappears 
with 
error: "Unable to retrieve file details". Does it have anything to do with 
hornetq? 
Concerning hornetq, is it only used for building gss or does it have to be 
"installed" to jboss? I found some guide and installed hornetq to jboss, but it 
also 
outputs errors (hope that you saw some of them in log).

Screenshots attached show web client with "missing" files, but note that bottom 
left 
statistics show 4 files and their total space. Other screenshot shows webdav, 
that 
seems to be working, at least it shows files and folders.

Regards,
Nikola

Original comment by ngara...@gmail.com on 23 Apr 2010 at 6:57

Attachments:

GoogleCodeExporter commented 8 years ago
HornetQ error messages are not related to your problem. HornetQ is a messaging 
queue that receives a new 
message every time a file is uploaded or deleted. When acting upon these 
messages it tries to contact Solr to 
add or remove an entry from the index. Since Solr is not functioning properly 
HornetQ reports an error when 
trying to connect. So, these errors concern file indexing and searching. As I 
said you should be able to work 
with the system without that functionality.

The error in your screenshot is caused by the server responding with an error 
in a client request to receive a 
file or folder metadata. I have gone through your log file a few times already 
and I can't find any relevant 
messages from the server. Perhaps enabling debug-level logging will reveal more 
info for this error. Update to 
the latest tip from the repository and run "ant install" to update the log4j 
configuration. I assume any 
configuration modifications for your particular environment (like 
gss.properties) are in the source tree, 
otherwise copy your modified files over again. Afterwards run the jboss startup 
script with the additional 
parameter "-Djboss.server.log.threshold=DEBUG", i.e.:

run.sh -b 0.0.0.0 -Djboss.server.log.threshold=DEBUG

Then try to reproduce the error and attach the new log file so I can take a 
look.

Original comment by past...@gmail.com on 23 Apr 2010 at 12:02

GoogleCodeExporter commented 8 years ago
I'm closing this issue since there has been no feedback in two months.

Original comment by past...@gmail.com on 22 Jun 2010 at 10:17