Re: Strange deployment problem

2015-04-02 Thread Miloš Kozák
I have just found, that if I use tmux then everything works perfect... Maybe this might be caused by some system variables forced by my terminal? This problem denies me to use Fabric for DB updates! This is very big constraint. -- You received this message because you are subscribed to the Goo

Re: Strange deployment problem

2015-03-28 Thread Miloš Kozák
Sure, those credentials work. If you look at the last line of the error output you can see that django wants to use user root whereas I am using user demo -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop

Re: Strange deployment problem

2015-03-28 Thread Gergely Polonkai
Hello, do you have command line access on that machine? If so, can you connect to the database using the credentials in the settings file? Best, Gergely On 28 Mar 2015 14:21, "Anderson Resende" wrote: > > I don't used mysql,but in postgres for you write in a database your user > db needs permis

Re: Strange deployment problem

2015-03-28 Thread Anderson Resende
I don't used mysql,but in postgres for you write in a database your user db needs permission to write. Check that! -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email

Strange deployment problem

2015-03-27 Thread Miloš Kozák
Hi, I have rather strange problem with already deployed application. I added some new ACL rules which I need to write to the database, so I wanted to call syncdb --all. However, using the command: ./manage.py syncdb or ./manage.py syncdb --settings=intranet.settings.demo I get this: S