Morning all, after some 10+ years in the (functional) SAP-arena I thought it might be worth trying something new. I've choosen Tiny, because it is build close to where I live (somewhat) and has some MRP functionalities.
Now, following the installation instructions I set it up on a SuSE 10.0 system. Postgres is up and running: [EMAIL PROTECTED]:> ps ax | grep postgr 10035 ? S 0:00 postgres: logger process 10037 ? S 0:00 postgres: writer process 10038 ? S 0:00 postgres: stats buffer process 10039 ? S 0:00 postgres: stats collector process 11378 pts/1 S 0:00 su postgres 11523 ? S 0:00 postgres: postgres terp [local] idle 11524 ? S 0:00 postgres: postgres terp [local] idle 11534 pts/2 R+ 0:00 grep postgr After starting the server with [EMAIL PROTECTED]:/home/axel/TinyERP/tinyerp-server-4.0.1/bin> python tinyerp-server.py -d terp --without-demo=all -n 127.0.0.1 Thu, 11 Jan 2007 08:41:03 INFO:objects:initialising distributed objects services Thu, 11 Jan 2007 08:41:03 INFO:init:connecting to database Thu, 11 Jan 2007 08:41:03 INFO:init:addon:base:registering classes [...] it looks that it connected to Postgres properly. Further down: Thu, 11 Jan 2007 08:41:03 INFO:init:addon:profile_service:registering classes Thu, 11 Jan 2007 08:41:03 INFO:web-services:starting XML-RPC services, port 8069 Thu, 11 Jan 2007 08:41:03 INFO:web-services:You are not using the SSL layer Thu, 11 Jan 2007 08:41:03 INFO:web-services:the server is running, waiting for connections... it claims to be listening on port 8069, but a client on the same machine can't connect to that server. This is similar to the problem discussed in this thread (http://tinyerp.org/forum/viewtopic.php?t=2495), but I couldn't find really an answer to the problem. Can anyone provide me with guidance how to solve this? Thanks Axel PS: is the terp-server process just killed (as it stays open in the terminal), or is there a way to shut down the server? _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
