Did "status client=" worked before? And during the backup job? It should
work at all times.
Is the client listend with "status dir"?
Does the backup job run through without plugins?


On 07.02.2018 at 22:19 wrote Vladislav Solovei:
> Director ver: Bareos 17.2.4, Debian.
> Client ver: 17.2.4, SLES.
> 
> I have configured my FD with "Client Initiated Connection", because FD is 
> behind nat.
> 
> 
> After starting the backup job, this job never ends.
> FD started in debug mode. Some last messages:
> ADSERV (100): bfile.c:1101-0 bopen: fname /_mysqlbackups_/bnstat.sql, flags 
> 00000000, mode 0000, rdev 0
> ADSERV (100): python-fd.c:2741-0 python-fd: plugin_io called with 1
> ADSERV (100): python-fd.c:2741-0 python-fd: plugin_io called with 2
> ADSERV (100): python-fd.c:2741-0 python-fd: plugin_io called with 2
> ADSERV (100): python-fd.c:2741-0 python-fd: plugin_io called with 4
> ADSERV (100): python-fd.c:2741-0 python-fd: end_backup_file() entry point in 
> Python called. Returncode: 0
> ADSERV (100): heartbeat.c:153-0 Send kill to heartbeat id
> ADSERV (100): backup.c:185-0 end blast_data ok=1
> ADSERV (100): python-fd.c:2741-0 python-fd: handle_plugin_event called with 
> bEventEndBackupJob
> ADSERV (100): dir_cmd.c:511-0 Quit command loop. Canceled=0
> ADSERV (100): python-fd.c:2741-0 python-fd: handle_plugin_event called with 
> bEventJobEnd
> ADSERV (100): htable.c:84-0 free malloc buf=b3b12020
> Pool   Maxsize  Maxused  Inuse
> NoPool      256        6      2
> NAME        256        4      0
> FNAME      2304       19      6
> MSG         512       11      3
> EMSG       1024        5      0
> BSOCK     65636        6      1
> RECORD      128        0      0
> 
> ADSERV (100): htable.c:590-0 Done destroy.
> ADSERV (100): jcr.c:184-0 write_last_jobs seek to 188
> ADSERV (100): dir_cmd.c:570-0 Done with free_jcr
> 
> Messages from director console:
> 07-Feb 22:59 bareos-dir JobId 4696: Start Backup JobId 4696, 
> Job=Back_ADSERV.2018-02-07_22.59.55_17
> 07-Feb 22:59 bareos-dir JobId 4696: Using Device "FileStorage" to write.
> 07-Feb 22:59 bareos-dir JobId 4696: Using Client Initiated Connection 
> (ADSERV).
> 07-Feb 22:59 bareos-sd JobId 4696: Volume "Full-1" previously written, moving 
> to end of data.
> 07-Feb 22:59 bareos-sd JobId 4696: Ready to append to end of Volume "Full-1" 
> size=192047816238
> 07-Feb 23:02 bareos-sd JobId 4696: Elapsed time=00:02:44, Transfer rate=10.05 
> M Bytes/second
> 
> And... Nothing after that. 
> Job stays in "Running" state infinitely...FD does not respond on "status 
> client=..." command anymore (because heartbeat.c:153-0 Send kill to heartbeat 
> id? :) )
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


-- 
 Jörg Steffens                   joerg.steff...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-91
 http://www.bareos.com           Fax:   +49 221 630693-10

 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer:
 S. Dühr, M. Außendorf, Jörg Steffens, P. Storz

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to