On Wednesday 04 January 2017 07:15:42 Josh Fisher wrote:
> > Now the job that WAS running (and all ones after it) are Error.
>
> Yes. So you cannot trust the job that was running. I would probably
> restart all daemons and erase that tape and start over.
Thanks. Was hoping for a more elegant way, but since none appeared I tried
that and it worked.
Bacula did some backups, I've started running all the full backup jobs, which
went okay until right now, where it suddenly decided to die:
=========================
trooper log # bconsole
Connecting to Director trooper:9101
1000 OK: 102 trooper-dir Version: 7.4.3 (18 June 2016)
Enter a period to cancel a command.
*messages
05-Jan 23:16 trooper-dir JobId 0: Error: sql_create.c:514 Create DB Client
record INSERT INTO Client (Name,Uname,AutoPrune,FileRetention,JobRetention)
VALUES ('trooper-fd','7.4.3 (18Jun16) x86_64-pc-linux-
gnu,gentoo,',1,5184000,15552000) failed. ERR=no connection to the server
05-Jan 23:16 trooper-dir JobId 0: Warning: Error updating Client record.
ERR=sql_create.c:514 Create DB Client record INSERT INTO Client
(Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES ('trooper-fd','7.4.3
(18Jun16) x86_64-pc-linux-gnu,gentoo,',1,5184000,15552000) failed. ERR=no
connection to the server
05-Jan 23:16 trooper-dir JobId 0: Error: sql_create.c:514 Create DB Client
record INSERT INTO Client (Name,Uname,AutoPrune,FileRetention,JobRetention)
VALUES ('trooper-fd','',1,5184000,15552000) failed. ERR=no connection to the
server
05-Jan 23:17 trooper-dir JobId 0: Fatal error: Could not create Client record.
ERR=Query failed: INSERT INTO Log (JobId, Time, LogText) VALUES (0,'2017-01-05
23:16:39','trooper-dir JobId 0: Error: sql_create.c:514 Create DB Client
record INSERT INTO Client (Name,Uname,AutoPrune,FileRetention,JobRetention)
VALUES (''trooper-fd'','''',1,5184000,15552000) failed. ERR=no connection to
the server
'): ERR=no connection to the server
==============================
The messages do not say WHICH server, I presume Director? But it is
running....
trooper log # ps ax | grep bacula
3316 ? Ssl 42:25 /usr/sbin/bacula-fd -u root -g bacula -c
/etc/bacula/bacula-fd.conf
3341 ? Ssl 0:21 /usr/sbin/bacula-dir -u root -g bacula -c
/etc/bacula/bacula-dir.conf
17055 pts/4 S+ 0:00 grep --colour=auto bacula
as is postgres:
trooper log # ps ax | grep postgres
3285 ? S 0:02 /usr/lib64/postgresql-9.5/bin/postgres -D
/etc/postgresql-9.5 --data-directory=/var/lib/postgresql/9.5/data
11669 ? Ss 0:00 postgres: checkpointer process
11670 ? Ss 0:00 postgres: writer process
11671 ? Ss 0:00 postgres: wal writer process
11672 ? Ss 0:00 postgres: autovacuum launcher process
11673 ? Ss 0:00 postgres: stats collector process
17843 pts/4 S+ 0:00 grep --colour=auto postgres
I did not update an software today, so can't understand why it would suddenly
develop these issues, when earlier backups today ran fine.
Any suggestions gratefully received :)
Thanks, Ian
--
ian AT zti.co DOT za http://www.zti.co.za
Zero 2 Infinity - The net.works
Phone +27-21-975-7273
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
