These are chat archives for inuitwallet/ALP-Server

10th
Apr 2016
Cybnate
@Cybnate
Apr 10 2016 06:07
Now stuck with the following:
File "/home/alp/code/ve/local/lib/python2.7/site-packages/psycopg2/init.py", line 164, in connect
conn = _connect(dsn, connection_factory=connection_factory, async=async)
psycopg2.OperationalError: FATAL: password authentication failed for user "alp"
FATAL: password authentication failed for user "alp"
This is in the alp.log
There is something wrong with supervisord setup I suspect, but can't get my head around it. How does ALP user get their authentication? Inherited from root through supervisor? Where is that setup?
supervisor is very elusive to me, never got it to work properly. Not sure why not as I don't understand how it works probably
inuitwallet
@inuitwallet
Apr 10 2016 06:12
Psycopg is the database connector. If that is appearing in the alp log it indicates that the password in the alp config for the database is wrong.
Has that been altered at a all?
(morning/evening by the way)
I didn't have any joy on the log search. There was nothing more to identify the user that wasn't already known.
Cybnate
@Cybnate
Apr 10 2016 06:13
Morning, haven't touched it
inuitwallet
@inuitwallet
Apr 10 2016 06:13
(for the 990)
Weird.
If you run the ansible again it should set the password again and the config.
Cybnate
@Cybnate
Apr 10 2016 06:15
Ok, will try that.
inuitwallet
@inuitwallet
Apr 10 2016 06:15
Failing that, you could use psql and alter the password manually on the database, then copy the same password to the alp config
Cybnate
@Cybnate
Apr 10 2016 06:16
Sounds like I might just start over again as well.....
inuitwallet
@inuitwallet
Apr 10 2016 06:17
For me it did just install from 0 to full with no intervention. It's worth a go I thibk
Cybnate
@Cybnate
Apr 10 2016 06:24
It is running....
inuitwallet
@inuitwallet
Apr 10 2016 06:25
:thumbsup:
Cybnate
@Cybnate
Apr 10 2016 06:28
Two fatal issues, one with supervisor! And a problem with UFW-init which I haven't seen before.
It says: another program is already running on a port that one of our HTTP servers is configured to use. Should I just deinstall supervisor first and then try again?
inuitwallet
@inuitwallet
Apr 10 2016 06:32
Shouldn't need to uninstalling (although that will work too). Just killing the supervisord process should work
Cybnate
@Cybnate
Apr 10 2016 06:38
Firewall issue is because I'm using another port. Supervisor issue sorted, something is running under ALP user for the first time!
Other port for ssh
But after a restart it fails again :-( Will dive into the logs again
inuitwallet
@inuitwallet
Apr 10 2016 06:42
Does sudo supervisorctl start all do anything?
Cybnate
@Cybnate
Apr 10 2016 06:45
Haven't checked that yet, but in alp.log the following:
File "/home/alp/code/ve/local/lib/python2.7/site-packages/psycopg2/init.py", line 164, in connect
conn = _connect(dsn, connection_factory=connection_factory, async=async)
psycopg2.OperationalError: could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
inuitwallet
@inuitwallet
Apr 10 2016 06:45
Postgres not running
Cybnate
@Cybnate
Apr 10 2016 06:45
There is also this:
16-04-10 08:40:26 - ERROR - Exchange config check failed: There is no reverse parameter for ccedk.usd
16-04-10 08:40:26 - ERROR - Exchange config check failed: There is no reverse parameter for test_exchange.ppc
inuitwallet
@inuitwallet
Apr 10 2016 06:45
Ah, I added that recently. Is the alp code the latest?
(it allows for reverse pairs to have their tolerance calculated correctly)
Cybnate
@Cybnate
Apr 10 2016 06:47
Just started 'all' and I do have ALP and postgres running!
ALP code from a week ago
This message was deleted
Weird that supervisorctl still don't work automatically on startup
At least I have now running processes to look at :-)
inuitwallet
@inuitwallet
Apr 10 2016 06:52
:) cool. Yeah weird about the autostart. May need to poke the init script.
Cybnate
@Cybnate
Apr 10 2016 06:52
What code or config needs to be changed for the config error?
inuitwallet
@inuitwallet
Apr 10 2016 06:53
If you switch to the alp user sudo -u alp -i then cm code you can git pull to update the codw
Cm =cd
Cybnate
@Cybnate
Apr 10 2016 06:54
It says already up to date
inuitwallet
@inuitwallet
Apr 10 2016 07:22
Hmmm. In /home/alp/code/config/exchanges/test_exchange.json is there a reverse parameter? If not create on with true or false
Cybnate
@Cybnate
Apr 10 2016 07:28
No, there is not
Not sure what to create and where in the config file, do you have an example file? reverse=true?
reverse : true ?
"reverse" : true?
maybe
inuitwallet
@inuitwallet
Apr 10 2016 07:51
It'll be just below the "target" line. It would be "reverse" : true,
Have a look in the "heroku_config" directory. It should be in one of those files.
Cybnate
@Cybnate
Apr 10 2016 10:13
A bit off-topic, but have some trouble with broadcasting liquidity with ALPv1. Not sure why that suddenly happened. The error is:
2016/04/10-12:05:41 ERROR: NuRPC: unable to send liquidity: Failed to process info.
Any ideas what this could be?
Everything else appears to be working fine. Have restarted Nud and the server a few times to no avail. Moved from v203 to v211, not helping. The next step is reverting to an old backup
inuitwallet
@inuitwallet
Apr 10 2016 10:19
I'd have to dig through the code a bit. Creon built his own rpc connector so it's a bit of a black box.
Cybnate
@Cybnate
Apr 10 2016 19:37
Problem has solved itself after upgrade to nudv211. Weird, but saves you a dig. Suspect it was somehow fallen behind with sync, can't find anything useful in the logs.