- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi All,
I am a new user and I am testing BART setup for our development servers. I find it strange that the EDB Bart manual instructions say to run the ./bart-scanner command manually and it appears to be essential for the operation of BART. Why is bart-scanner not set up as linux service or something like that? There are no further instructions about how to keep it running in the install manual.
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.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
The BART WAL scanner is used by invoking the bart-scanner program.
The WAL scanner processes can run in either the foreground or background depending upon the usage of the --daemon option.
• If the --daemon option is omitted, then the WAL scanner process runs in the foreground. All output messages can be viewed from the terminal running the program as well as in the BART log file. See Section 4.1 for information on the logfile parameter in the BART configuration file.
• If the --daemon option is specified, then the WAL scanner process runs in the background. All output messages can be viewed in the BART log file.
Please refer to the URL for more details.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
The BART WAL scanner is used by invoking the bart-scanner program.
The WAL scanner processes can run in either the foreground or background depending upon the usage of the --daemon option.
• If the --daemon option is omitted, then the WAL scanner process runs in the foreground. All output messages can be viewed from the terminal running the program as well as in the BART log file. See Section 4.1 for information on the logfile parameter in the BART configuration file.
• If the --daemon option is specified, then the WAL scanner process runs in the background. All output messages can be viewed in the BART log file.
Please refer to the URL for more details.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: BART scanner
Thanks for the information , Rohit,
I think the point still remaining is whether the daemon restarts automatically at server reboot or does the user have to make a point of restarting manually every time?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: BART scanner
Hi Ivor,
Currently, there is no functionality of run-level settings for bart-scanner daemon.
An end-user has to start the daemon after every event of the server reboot.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: BART scanner
Good point!
One can create an init script or a use System Manager (Systemd).
HTH