Hello everyone

When I start terp/server here's the first output lines:

[b]cata:/usr/down/tinyerp-server-4.2.0-rc2/bin # python tinyerp-server.py -d terp -r terp
Thu, 13 Sep 2007 17:58:05 INFO:objects:initialising distributed objects services
Thu, 13 Sep 2007 17:58:05 INFO:init:connecting to database
Thu, 13 Sep 2007 17:58:05 INFO:init:could not connect to database 'terp'![/b]

I'tried I guess everything I read... from dropping the terp db and user within PGAdmin from another machine and creating them again, to deal without success with the .conf files.

I have installed Tiny 4.2 on Suse 9.3 and Postgres 8.2.4. Thank you!

Any ideas

Did you tried to create the database from the Tiny eRP client ?

Proposed enhancement: http://tinyforge.org/tracker/index.php?func=detail&aid=155&group_id=13&atid=132

Regards,
Geoff

See
http://tinyerp.org/forum/topic4636.html

Michael

Okay first of all thanks guys. I cannot make it work yet. These are mi news:

Fabien: Yes, tried that, but it (after connect to server) simply says Could not create database, while in the server the output is as follows:

createdb: could not connect to database template1: FATAL: Ident authentication failed for user "terp"
Fri, 14 Sep 2007 14:42:12 ERROR:web-services:Exception in call: Traceback (most recent call last):
File "/usr/down/tinyerp-server-4.2.0-rc2/bin/netsvc.py", line 206, in _dispatch
r=m(*params)
File "/usr/down/tinyerp-server-4.2.0-rc2/bin/service/web_services.py", line 120, in create
raise Exception, "Couldn't create database"
Exception: Couldn't create database


And when I try with a diferent than the default "admin" password asked in TerpClient in order to create a new database, the output on server is the same except for the exception that is in this case "Access denied!".



Geoff:
Great advice, thank you. Based on your post I stopped worrying about that startup message. Now I'm facing the problem that I cannot neither create a database from client nor connect or login at all, altough the ports are wide open and I can see it telneting to that ports (8069 and 8070 in my case).


Michael
I followed your instructions that follow:

First: Sudo su postgres. Then: python2.4 ./bin/tinyerp-server.py
does it with me. If I forget the su postgres then it does not find my databases.

Michael


cata:~ # sudo su postgres
postgres@cata:/root> cd /usr/down/tinyerp-server-4.2.0-rc2/bin/
postgres@cata:/usr/down/tinyerp-server-4.2.0-rc2/bin> python tinyerp-server.py -d terp -r terp


... but as I tell Geoff, it seems I can't go far than this point by now.


Sincerely yours
Martin

Guys... I know you know a lot of this software.
I'm not asking you to solve my problem but as documentation is poor yet, I would really appreciate some guidelines regardin for example:

- do i need to create a linux account named terp so postgres in the identsameuser mode authenticate it?

- why before I follow your suggestions the output on server was "could not connect to database terp" and now is the database template1?

I really thank your help.
Regards

Martin

Once Python and the needed libraries are installed, and postgres is installed in its default state, I found that I needed do almost nothing on a fresh installation of Ubuntu 7.04 to make it all work.

So I just download the server and client files, run

on them, and then in one terminal window

and in another terminal window

So I've not encountered the problems you've run into. No messing with accounts (for single server mode). No messing with terp or template1 databases. No pgadmin III! The client says it's got no database so you create one through File > Databases > New database. That's all I needed.

I know that I'd reinstall Ubuntu and start again (and I have done that a few times). Maybe you're not in a position to be able to do that.

Regards,
Geoff

Thanks Geoff. I'll try with the linux client on the same machine to se what happens.

If I make it work I'll let you know, and also if I dont.

Regards.

Because of a conversation elsewhere, I feel compelled to add that I'm doing this for trial systems not for use in production. For that case I would naturally set up more secure (i.e. less insecure) database users! In this case this is just a simple method of getting it to work.

Regards,
Geoff

Well, after a period of inactivity I could get it work.

After I tried many ways, simply compiled the latest version of Postresql and it worked for me.

Aparently the postgresql that came with suse 9.3 does not like Tiny erp.


Thank you guys, I appreciate your advices that leaded me to the final solution.

I just wanted to add that after wrestling with getting the client to connect with the server this worked like a charm.

Now I am curious on the comment about security. Anyone willing to elaborate?

I'm afraid I don't understand what your question is about. Can you be more precise ?
regards

You would not want to run tinyerp-server as user postgres in a production environment, nor from a command prompt. There are posts on this topic in these forums.

Regards,
Geoff

Ok, I see what was meant. Thank you.
I don't see postgres user as a real threat anyway but I don't use it for other reasons. There are several concerns I would rank far above.
Cheers.