The same error, yes. Permissions are not relevant as FD runs under root
and the script generates the dump file just fine.
I now changed the dump location to /srv, touched /srv/mysqldump.sql file
too and now the error was:
JobId 54542: Error: /srv/mysqldump.sql mtime changed during backup.
JobId 54542: Error: bpipe-fd: Error closing for file /srv/mysqldump.sql:
268435583
...
Termination: Backup OK -- with warnings
--
Silver
On 22.01.2016 10:56, Ana Emília M. Arruda wrote:
Hello Silver,
The same error? Have you checked permissions?
Best regards,
Ana
On Fri, Jan 22, 2016 at 9:19 AM, Silver Salonen
<silver.salo...@gmail.com <mailto:silver.salo...@gmail.com>> wrote:
After creating those folders, those errors still appeared. Any
other ideas?
--
Silver
On 21.01.2016 13:43, Silver Salonen wrote:
Aha, I indeed didn't have /mysql directory. Thanks a bunch! :)
PS. Script permissions are correct as otherwise the dump wouldn't
have been created.
--
Silver
On 21.01.2016 12:21, Heitor Faria wrote:
Hello Silver,
Does the /mysql directory exist? It must.
Make sure also bacula-fd daemon OS user has proper permissions
to run the scripts
Regards,
===========================================================================
Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems
Certified Administrator II
Do you need Bacula training? http://bacula.us/video-classes/
+55 61 8268-4220 <tel:%2B55%2061%208268-4220>
Site: http://bacula.us FB: heitor.faria
===========================================================================
Enviado por TypeApp <http://www.typeapp.com/r>
Em 21 de jan de 2016, pelo 06:37, Silver Salonen
<silver.salo...@gmail.com <mailto:silver.salo...@gmail.com>>
escrito:
Hi.
I'm backing up MySQL databases from several servers with Fileset line:
Plugin =
"bpipe:/mysql/mysqldump.sql:/etc/bacula/scripts/mysqldump.sh <http://mysqldump.sh>
mydb:/etc/bacula/scripts/mysqldump.sh <http://mysqldump.sh> -R"
FD on some of those servers give the following error:
Warning: Cannot stat file /mysql/mysqldump.sql: ERR=No such file
or
directory
I've confirmed that actually the MySQL database is still backed up and
can be restored too. So why the error? Anybody knows or can guess?
--
Silver
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
