*Sorry if this post is a bit chatty, but I wanted it to be helpful to
anybody else who runs into the same problems.*
I had some initial success and was able to complete the 'ant
fresh_install'. Tomcat didn't display the default page but
I think that may be because I installed it with yum rather
Thanks for clarifying. Tomcat is the dspace "user" accessing the database
on behalf of a person
searching our repository online, so everything is local as far as the
database is concerned.
To clarify my side, I didn't add that 'trust' authorization rule and 6543
was a typing-in-the-dark
typo
Your PostgreSQL database is not aware of any users that are logged in into
or connected to your DSpace web application. It is the Tomcat process
itself (which serves the DSpace web app) that connects to your database and
since both are on the same host, you should only have the rule "host
dspace
I've previously only interacted with DSpace as a user so please pardon the
'newb' questions. I'm trying to (re)create a repository that anyone can
search
via a website but only certain authorized local users can modify.
Given these authentication rules:
host dspace dspace
Thank you Tom.
1) I have the md5 line in the pg_hba.conf file
3) Changed dspace.hostname to "localhost" then later to localhost (no
quotes) since that's the default
4) Postgres complained with I tried to reset dspace's attributes
postgres=# alter role dspace NOSUPERUSER CREATEDB
Hi Tom,
It was a very complete answer, you should put it in a wiki page as a
troubleshooting.
Best
Luiz Claudio Santos
http://luizclaudiosantos.me/
On Tue, Jan 31, 2017 at 4:03 PM, Tom Desair wrote:
> Hi Walter,
>
> You need to make sure of the following:
>
>1.
Hi Walter,
You need to make sure of the following:
1. *Allow the "dspace" PostgreSQL user to connect using a password:* This
means having the following line to the pg_hba.conf file:
- "hostdspace dspace 127.0.0.1 255.255.255.255
md5"
- This tells the
Hi Walter,
Are you sure the database is available outside of the server, did you
try to use db.url = jdbc:postgresql://localhost:5432/dspace, and more the
Dspace dspace it should be something like baseUrl =
http://${dspace.hostname}:80/
or dspace.baseUrl = http://${dspace.hostname}:8080/, but
I remember having some difficulty during the database part of the
installation. I'm tempted to rip out the
database down to reinstalling Postgres and starting over. But before I do,
should the dspace user have
an special privileges? I didn't see where any should be set in the
instructs so it
Thanks Mark and Luiz. Unless I'm misunderstanding how it reads variables
I'm using almost the default
values in our local.cfg file::
dspace.hostname = "irtest.library.uaf.edu"
dspace.baseUrl = http://${dspace.hostname}:5432/
db.url = jdbc:postgresql://${dspace.hostname}:5432/dspace
With
Hi Walter,
I was clarify some points of Mark's e-mail... About you issue, I guess
it is something with config/installation of your database, but I don't have
idea how to solve it, but review the connection info in the
dspace.cfg/local.cfg as Mark said is always a good idea.
Best regards
Postgres is running as a Linux service if that's what you mean.
--
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
Hi Mark,
Maybe I lost that part, but he said that the database is local, right?
if he is using the Dspace 6, he should use local.cfg, it is not an option,
right? The wierd thing here is that he said, he can connect with the linux
user "dspace", but not with others linux user, to me it seem
On Monday, January 30, 2017 at 7:16:53 PM UTC-5, Walter Rutherford wrote:
>
> I think that all makes sense. If I'm logging in from user 'dspace' to
> 'dspace' in posgres it uses
> the peer rule and lets me in without a password. Any other user would have
> to be accessing
> their own
Man, it is really weird, I've not ever faced an issue like that, it is hard
to know what is going on. If I was your shoes I could keep try, but right
now, I don't have any idea to offer to you, sorry!
On Mon, Jan 30, 2017 at 8:56 PM Walter Rutherford
wrote:
>
> Sorry...
Sorry... Correction: "dspace.hostname" not "domain.hostname".
--
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
I tried some of the commented rules in pg_hba.conf. They either wouldn't
allow the postgres server to
restart or there was no obvious change - I continued to get
the java.net.UnknownHostException error
which implies to me that the authentication method isn't the immediate
cause of the ant
I think that all makes sense. If I'm logging in from user 'dspace' to
'dspace' in posgres it uses
the peer rule and lets me in without a password. Any other user would have
to be accessing
their own user/database.
So, how should the pg_hba.conf file be configured to allow any user to
access
Yes and no.
If I'm logged into Linux as user 'dspace' (which is also the name of the
postgres user and database) then
'psql -U dspace' drops me in without a password. If I force a password with
'psql -U dspace -W' I can get
in just fine even with an incorrect password! But if I try from another
This is the output from the 'ant fresh-install' command. I believe the
first error is just a non-fatal WARNing, the fatal
problems come when it tries to access the postgres database. But I can't
tell if the problem stems from postgres,
java, Maven (that created the ant files), ant, DNS, etc..
Thanks Luiz. I didn't recall if I created the user and DB as root so I
dropped them both while logged in as 'dspace'.
I'm still getting the same errors which seem to stem from this:
Caused by: java.net.UnknownHostException:
I've verified the hostname resolves in DNS and even added it to the
21 matches
Mail list logo