ERROR: logfile path '/tmp/bart-auto.log' is not valid

Highlighted
Silver Adventurer

ERROR: logfile path '/tmp/bart-auto.log' is not valid

seeing this when attempting to run the bart command as the postgres user,  it works when running as root.

 

regards

 

Matt

Archived Discussions


Effective March 31st, we will no longer engage on PostgresRocks.


How to engage with us further?


  • Thought Leadership: EDB Blogs

  • Tips and Tricks: Postgres Tutorials

  • Customer Support: Create a Case Please note: Only customers with an active EDB support subscription and support portal authorization can create support ticket

  • Engage on Stackoverflow While engaging on Stackoverflow tag the question with EDB or EnterpriseDB.

2 REPLIES 2
Highlighted
EDB Team Member

Re: ERROR: logfile path '/tmp/bart-auto.log' is not valid

Hi Matt,

Could you please share the Bart configuration file to look further into your query.

Please if you can also check the ownership and the permissions on the logfile mentioned as /tmp/bart-auto.log.

Highlighted
EDB Team Member

Re: ERROR: logfile path '/tmp/bart-auto.log' is not valid

Hi MattGorham,
 
The reason for getting the below error while running the bart command as postgres user is, earlier the bart command was ran as "root" user, so it as created a logfile path with '/tmp/bart-auto.log' and it as root ownership currently, now when you switch it to postgres user and then ran the bart command you will get below error.
 
ERROR: logfile path '/tmp/bart-auto.log' is not valid
 
To avoid above issue remove the logfile path i.e, '/tmp/bart-auto.log' which was created with "root" ownership and then run the bart command with postgres user, it will create a logfile path with '/tmp/bart-auto.log' with postgres ownership. 
 
So any bart command executed from any user it will create a logfile path with '/tmp/bart-auto.log' with that particlular user and it blocks the the bart command to execute from another user.
 
Hope this helps you.

© 2019 EnterpriseDB Corporation. All rights reserved.   |   Privacy Policy   |  Terms of Use   |   Trademarks