Hello,
I installed Bacula Community on a AlmaLinux 9.2 server + Postgresql 15 :
List of rpms :
postgresql15-libs-15.4-1PGDG.rhel9.x86_64
postgresql15-15.4-1PGDG.rhel9.x86_64
postgresql15-server-15.4-1PGDG.rhel9.x86_64
bacula-postgresql-13.0.3-23050308.el9.x86_64
bacula-libs-13.0.3-23050308.el9.x
> On Mon, 18 Jul 2022 10:06:50 -0500, Larry Rosenman said:
>
> I'll just keep using the DEBUG build for now, but sounds like this
> should be picked up
> upstream.
I've reported it here:
https://bugs.bacula.org/view.php?id=2655
__Martin
___
Bac
> On Mon, 18 Jul 2022 10:06:50 -0500, Larry Rosenman said:
>
> On 07/18/2022 10:00 am, Martin Simmons wrote:
> >> On Mon, 18 Jul 2022 09:18:17 -0500, Larry Rosenman said:
> >>
> >> On 07/18/2022 8:22 am, Martin Simmons wrote:
> >> >> On Sat, 16 Jul 2022 17:00:33 -0500, Larry Rosenman
On 07/18/2022 10:00 am, Martin Simmons wrote:
On Mon, 18 Jul 2022 09:18:17 -0500, Larry Rosenman said:
On 07/18/2022 8:22 am, Martin Simmons wrote:
>> On Sat, 16 Jul 2022 17:00:33 -0500, Larry Rosenman said:
>>
>> (gdb) bt full
>> #0 kill () at kill.S:4
>> No locals.
>> #1 0x00088ad66
> On Mon, 18 Jul 2022 09:18:17 -0500, Larry Rosenman said:
>
> On 07/18/2022 8:22 am, Martin Simmons wrote:
> >> On Sat, 16 Jul 2022 17:00:33 -0500, Larry Rosenman said:
> >>
> >> (gdb) bt full
> >> #0 kill () at kill.S:4
> >> No locals.
> >> #1 0x00088ad660a0 in __fail (
> >>
OK. I just saw that dird/fd_cmds.c includes findlib/find.h and that
findlib/find_one.c was significantly changed in 13.0. It is one of the
few places alloca() is used. It might not even be related to alloca(),
but that is a likely candidate for a stack-protector overflow detection.
The detectio
On 07/18/2022 8:22 am, Martin Simmons wrote:
On Sat, 16 Jul 2022 17:00:33 -0500, Larry Rosenman said:
(gdb) bt full
#0 kill () at kill.S:4
No locals.
#1 0x00088ad660a0 in __fail (
msg=0x88ac6d34f "stack overflow detected; terminated")
at /usr/src/lib/libc/secure/stack_protector.
> On Sat, 16 Jul 2022 17:00:33 -0500, Larry Rosenman said:
>
> (gdb) bt full
> #0 kill () at kill.S:4
> No locals.
> #1 0x00088ad660a0 in __fail (
> msg=0x88ac6d34f "stack overflow detected; terminated")
> at /usr/src/lib/libc/secure/stack_protector.c:130
> sa = {__sig
I don't see how it can be related to find_one_file.
The crash is happening in the director, but find_one_file is called in the
client.
__Martin
> On Mon, 18 Jul 2022 08:33:30 -0400, Josh Fisher said:
>
> So, v. 13.0 calls alloca() in the following source files:
>
> findlib/mkpath.c
> find
So, v. 13.0 calls alloca() in the following source files:
findlib/mkpath.c
findlib/find_one.c
lib/bnet_server.c
lib/parse_conf.c
tools/bsmtp.c
tools/bsmtp.c
win32/compat/compat.h
win32/compat/compat.cpp
win32/compat/compat.cpp
win32/libwin32/statusDialog.cpp
and that list is unchanged from the 9
On 7/17/22 18:25, Larry Rosenman wrote:
> full build log for the DEBUG version:
>
https://home.lerctr.org:/data/live-host-ports/2022-07-16_17h45m44s/logs/bacula13-server-13.0.0.log
>
> full build log for the NON-DEBUG version:
>
https://home.lerctr.org:/data/live-host-ports/2022-07-15
On 07/17/2022 9:16 am, Andrea Venturoli wrote:
On 7/17/22 15:34, Josh Fisher wrote:
Bacula has had false-positive issues with similar buffer overrun
protections before,
Hmm... -fstack-protector just put canaries around the stack and
verifies they are still there and intact.
If the stack canar
On 7/17/22 15:34, Josh Fisher wrote:
Bacula has had false-positive issues with similar buffer overrun
protections before,
Hmm... -fstack-protector just put canaries around the stack and verifies
they are still there and intact.
If the stack canary is corrupt, then IMO an overrun has defini
On 7/17/22 06:10, Andrea Venturoli wrote:
On 7/16/22 19:07, Larry Rosenman wrote:
msg=0x88ac6d34f "stack overflow detected; terminated")
at /usr/src/lib/libc/secure/stack_protector.c:130
#2 0x00088ad66010 in __stack_chk_fail ()
at /usr/src/lib/libc/secure/stack_protector.c
On 7/16/22 19:07, Larry Rosenman wrote:
msg=0x88ac6d34f "stack overflow detected; terminated")
at /usr/src/lib/libc/secure/stack_protector.c:130
#2 0x00088ad66010 in __stack_chk_fail ()
at /usr/src/lib/libc/secure/stack_protector.c:137
#3 0x00252e69 in send_include_
On 07/16/2022 5:00 pm, Larry Rosenman wrote:
On 07/15/2022 6:08 pm, Larry Rosenman wrote:
On 07/15/2022 5:42 pm, Larry Rosenman wrote:
On my 14-current system with bacula13-{client,server}, bacula-dir is
crashing when I try to run one of my jobs:
[SNIP]
if I undo the above bacula-dir.conf ch
On 07/15/2022 6:08 pm, Larry Rosenman wrote:
On 07/15/2022 5:42 pm, Larry Rosenman wrote:
On my 14-current system with bacula13-{client,server}, bacula-dir is
crashing when I try to run one of my jobs:
[SNIP]
if I undo the above bacula-dir.conf changes it runs.
Ideas what I did to cause it g
On 07/15/2022 5:42 pm, Larry Rosenman wrote:
On my 14-current system with bacula13-{client,server}, bacula-dir is
crashing when I try to run one of my jobs:
<10>1 2022-07-15T17:36:29.513796-05:00 borg.lerctr.org bacula-dir
36370 - - stack overflow detected; terminated
<6>1 2022-07-15T17:36:29.627
: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] bacula-dir 9.4.4 runnig on Centos 6.4 host and
bacula-fd 9.4.4 running on Centos 7.8.
Hi folks,
I'm running CentOS 7.7 in the Bacula server and have also got one client
running CentOS 7.7. Never had any problems with fire
Hi folks,
I'm running CentOS 7.7 in the Bacula server and have also got one client
running CentOS 7.7. Never had any problems with firewalld. Just keep
firewalld running, and make sure the appropriate ports are allowed
(default 9101, 9102, 9103), plus other ports you need. Using firewalld
or
On 4/23/2020 7:45 AM, Martin Simmons wrote:
Check if the Centos 7.8 host is running a firewall (e.g. run iptables -L -v).
Centos 7 installs firewalld by default. Disable it (don't remove it) and
install iptables-services instead.
Dima
___
Bacula-
Check if the Centos 7.8 host is running a firewall (e.g. run iptables -L -v).
__Martin
> On Thu, 23 Apr 2020 10:55:24 +, "Shaligram Bhagat, Yateen (Nokia said:
>
> Hello
>
> I have bacula-dir 9.4.4 runnig on Centos 6.4 host and bacula-fd 9.4.4 running
> on client host with Centos 7.8
Hello
I have bacula-dir 9.4.4 runnig on Centos 6.4 host and bacula-fd 9.4.4 running
on client host with Centos 7.8.
(I assume this should not be an issue)
On the director when I execute console command "status client=" I get
error
*status client=CLIENT-fd
Connecting to Client
On 01/25/2018 05:19 PM, Tilman Schmidt wrote:
> If your bacula-dir runs fine when started directly but fails when
> started through systemd then you're most likely encountering a problem
> with Bacula's systemd integration.
FWIW 7.0.5 from Simone's RPMs works fine on Centos 7.
--
Dimitri Maziuk
If your bacula-dir runs fine when started directly but fails when
started through systemd then you're most likely encountering a problem
with Bacula's systemd integration. This is not unheard of. Systemd
itself is still very new and immature, and systemd integration of most
software packages even m
On 01/25/2018 01:19 PM, Ben Wong wrote:
> Is there any way to make sure it's
> running?
Yes: figure out why it's crashing and fix that.
You can use nagios, net-snmp, or mon if that's still available, to send
you an alert if bacula-dir is not running, and then you can go in and
fix whatever's cau
Hi all,
I'm setting up Bacula 9.0.6 on a CentOS 7.4.1708 server. The director,
storage daemon, and file daemon have all been configured with the same
hashed password. I first noticed an issue when I ran bconsole and the
system had trouble connecting to port 9101.
[root@backup3 ~]# bacula status
That should be it then. Thanks for the help.
On Wed, Oct 25, 2017 at 7:28 PM, Gary R. Schmidt
wrote:
> On 25/10/2017 21:34, Davide Franco wrote:
>
>> Hi,
>>
>> As far as I know, both sd and director needs to be on same version.
>>
>> I can’t find it in Bacula documentation yet, but feel free to
On 25/10/2017 21:34, Davide Franco wrote:
Hi,
As far as I know, both sd and director needs to be on same version.
I can’t find it in Bacula documentation yet, but feel free to have a
look at the main manual.
>
The Rule is:
(DIR == SD) >= FD.
The Director and Storage Daemon have to b
Hi,
As far as I know, both sd and director needs to be on same version.
I can’t find it in Bacula documentation yet, but feel free to have a look
at the main manual.
Regards
Davide
On Wed, 25 Oct 2017 at 11:44, Gi Dot wrote:
> On Wed, Oct 25, 2017 at 5:20 PM, Davide Franco wrote:
>
>> Hi,
>
On Wed, Oct 25, 2017 at 5:27 PM, Heitor Faria wrote:
>
> Hi,
>
>
> Hello,
>
>
>
> I've setup bacula-dir on Ubuntu, and bacula-sd on Freenas.
>
>
> Why? Isn't iSCSI easier?
>
I'm not used to Freenas (or any NAS). I will look into it.
>
> Problem is the director can't connect to the storage.
>
>
>
Hi,
Does both director and storage daemon are running the same version ?
Regards
Davide
On Wed, 25 Oct 2017 at 11:11, Gi Dot wrote:
> Hi,
>
> I've setup bacula-dir on Ubuntu, and bacula-sd on Freenas. Problem is the
> director can't connect to the storage. Error below:
>
> *message
> 25-Oct
On Wed, Oct 25, 2017 at 5:20 PM, Davide Franco wrote:
> Hi,
>
> Does both director and storage daemon are running the same version ?
>
No. I missed to check on that. Storage daemon runs on bacula 5.2.12 and
director runs on 7.4.4. Supposed that's the issue?
>
> Regards
>
> Davide
>
> On Wed, 25
Hi,Hello,I've setup bacula-dir on Ubuntu, and bacula-sd on Freenas. Why? Isn't iSCSI easier?Problem is the director can't connect to the storage. Probably different Director and SD versions?Error below:*message25-Oct 16:52 foo-dir JobId 0: Fatal error: authenticate.c:122 Director unable to authenti
Hi,
I've setup bacula-dir on Ubuntu, and bacula-sd on Freenas. Problem is the
director can't connect to the storage. Error below:
*message
25-Oct 16:52 foo-dir JobId 0: Fatal error: authenticate.c:122 Director
unable to authenticate with Storage daemon at "xx.xx.xx.yy:9103". Possible
causes:
Pass
Good luck in resolving your database disconnections ...
On 05/18/2017 08:16 AM, Andrey
Mursenkov wrote:
Got it, thank you for explanation.
I wondered why this connect was running. I know that it is
better to use filesystem sockets
Got it, thank you for explanation.
I wondered why this connect was running. I know that it is better to
use filesystem sockets on local machine, just got the same behavior on
file sockets and gave a try to tcp setup, but saw this permanent connect.
Thought it was a bacula bug but guess it is
In looking at your output, I see that you are using a TCP
connection. That is not the optimal way or the default way to run
Bacula with a local database. On my server:
netstat -nap|grep bacula-dir
I get:
tcp 0 0 0.0.0.0:9101
0.0
Well, first, you should not be getting database disconnects. If you
are, either something is configured incorrectly, or perhaps you are
running your database on a machine other than where the Director is,
which is possible but not really recommended for performance reasons.
The only time that
Hello, thank you for reply.
But Heartbeat interval is a socket option, and is not what I need.
Let me be more precise:
after completion job in bacula-console:
# netstat -nap|grep ESTABLISHED|grep bacula-dir
tcp0 0 127.0.0.1:55336 127.0.0.1:5432 ESTABLISHED
10244/bacula-d
Hello Andrey
As Kern said in that bugreport, "Every job that starts opens a new
connection (sometimes during the job additional connections will be
opened)."
But is not persistent.
If you are running a command "list files jobid=XXX" of a job with some
million of files and you have connection prob
Hello,
what connection type does bacula-dir use while connecting to database,
permanent or not?
If bacula-dir uses permanent connection does it support reconnect?
Here what I can see:
When I launch bacula-console and run job manually, bacula-dir
establishes network connection to database and
On 08/09/2016 09:12 PM, Erwan RIGOLLOT
wrote:
Hello,
I have to migrate and update my bacula
director to a new server.
So I will copy configurations files and
database.
I w
Hello,
I have to migrate and update my bacula director to a new server.
So I will copy configurations files and database.
I will run update script for database.
After all steps, can I change my bacula director’s name if I update all
configurations files on all servers (dir, fd and sd) ?
Thanks
ok, fixed
Somehow the bacula-dir startup file was old
Pulled a copy, I am running now
Thanks for all help
Phil
+--
|This was sent by p...@isone.biz via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+---
ok, tried a restore:
[root@bkpcentos6 mysql]# mysql -u root -D bacula -p <
/root/bacula/bin/working/bacula.sql
Enter password:
[root@bkpcentos6 mysql]# cp /dev/null /var/log/bacula/bacula.log
cp: overwrite `/var/log/bacula/bacula.log'? y
[root@bkpcentos6 mysql]# /etc/init.d/bacula-dir start
Star
>I think its the other way around: sometimes between reboots MySQL got
>upgraded to version 15, but not restarted, so the old version of MySQL
>was still running. Then after the reboot new version of MySQL was
>loaded in the memory, causing bacula to emit this error.
Ok, I stopped mysql, and start
So after a bit more reading.
The dtabase is v15, why would bacula-dir look for v12?
It is the same date as the bacula-fd, -sd, and bconsole
bconsole -v shows 7.2
+--
|This was sent by p...@isone.biz via Backup Central.
|Forward
hi
The actual version is 7.2
I did the upgrade way back in January, and have run 400+ jobs since then. I
did a new install of 7.2 and started over back then
I run bconsole -v, it does show v7.2
I run bconsole -l and it does show the bacula-dir that is defined
Is the catalog dump you talk of,
On Tue, Jun 21, 2016 at 11:41:18AM -0300, Heitor Faria wrote:
> > Hello
>
> > You can try stop mysql, and move the directory /var/lib/mysql/bacula to
> > another
> > safe directory.
>
> > Then you can try run mysql and see if it works.
>
> > If you have a dump of mysql you just mysql -u root <
> Hello
> You can try stop mysql, and move the directory /var/lib/mysql/bacula to
> another
> safe directory.
> Then you can try run mysql and see if it works.
> If you have a dump of mysql you just mysql -u root < catalog.dump, or you need
> to use BLS and BEXTRACT to get catalog.dump from vol
Hello
You can try stop mysql, and move the directory /var/lib/mysql/bacula to
another safe directory.
Then you can try run mysql and see if it works.
If you have a dump of mysql you just mysql -u root < catalog.dump, or you
need to use BLS and BEXTRACT to get catalog.dump from volumes.
Best Re
More info
Bacula 7.0.5
Mysqld is running
I can get into database using credentials and mysql command
Question. How do I restore the catalog if the db is hosed (If that is the
problem)?
Any way to debug this would be appreciated.
+--
Hello
You said you just reboot the server. You didn't restore the mysql database?
It seems you have an newer version of catalog and restored an older one.
Atenciosamente
*Wanderlei Hüttel*
http://www.huttel.com.br
2016-06-21 10:56 GMT-03:00 philhu :
> Hi,
>
> I was backing up an NFS volume fr
More info
Bacula 7.0.5
+--
|This was sent by p...@isone.biz via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
Hi,
I was backing up an NFS volume from a NAS, when the NAS crashed, and the backup
aborted.
The next backup got a database error, so I reboot, and started up bacula-fd,
bacula-sd without problem, but starting up bacula-dir, it dies with:
[root@bkpcentos6 bacula]# cat /var/log/bacula/bacula.lo
Hi,
I had "TLS Verify" Peer disabled in bacula-dir.conf so why to define
allowed CN's?
Nevertheless, I added TLS Allowed CN, switched to TLS Verify = yes and
also added the TLS Certificate / TLS Key in bconsole.conf (don't think
that they are mandatory either).
However, the behavior is exactly the
> Hello Heitor,
> root@bacula-dir:/etc/bacula# bacula-dir -t
> root@bacula-dir:/etc/bacula# echo $?
> 0
>
> There seems to be no syntax error in configuration because after
> restart everything is ok again. After reloading, I get the following
> messages:
>
> 22-Dec 13:02 bacula-dir.grnet.gr-dir
Hello Heitor,
root@bacula-dir:/etc/bacula# bacula-dir -t
root@bacula-dir:/etc/bacula# echo $?
0
There seems to be no syntax error in configuration because after
restart everything is ok again. After reloading, I get the following
messages:
22-Dec 13:02 bacula-dir.grnet.gr-dir JobId 0: Fatal error
>>> Hello,
>>> we are on Linux Debian Wheezy and we use version bacula-director-mysql
>>> 5.2.6+dfsg-9. We experience a faulty communication between bconsole
>>> and director daemon after reloading bacula-dir. Specifically, when
>>> everything is ok and without TLS configuration we get the followi
Hi Ana,
exactly. After restarting the daemon, bconsole is connected
sucessfully until the next reload
Regards,
Kostis
On 22 December 2015 at 11:30, Ana Emília M. Arruda
wrote:
> Hello Kostis,
>
> When you say "If we restart bacula-dir service, everything is ok again", you
> mean that bacula-dir
Hello Kostis,
When you say "If we restart bacula-dir service, everything is ok again",
you mean that bacula-dir service is running and you successfully enter
bconsole with SSL/TLS configured?
Best regards,
Ana
On Tue, Dec 22, 2015 at 10:05 AM, Kostis Fardelas
wrote:
> Hello,
> we are on Linux
Hello,
we are on Linux Debian Wheezy and we use version bacula-director-mysql
5.2.6+dfsg-9. We experience a faulty communication between bconsole
and director daemon after reloading bacula-dir. Specifically, when
everything is ok and without TLS configuration we get the following:
{code}
*root@bacu
On 9/7/2014 4:33 AM, Kern Sibbald wrote:
> It is not a question that I will not document something, why would I
> write code and discuss it if I did not want to document it? It *was* a
> question that I incorrectly thought it was already documented.
>
> What some people tend to forget is that I a
Hello,
It is not a question that I will not document something, why would I
write code and discuss it if I did not want to document it? It *was* a
question that I incorrectly thought it was already documented.
What some people tend to forget is that I am doing this for free, I
volunteer for thi
On 9/6/2014 2:59 PM, Kern Sibbald wrote:
...
> perhaps I am overly sensitive
I've been dealing with other people's software for a living for close to
two decades now and familiarity brings contempt. So yeah, I don't like
software -- with very few exceptions, and bacula isn't one of them, I am
j
Hello,
Yes, I likely chimed in with the statement you said, and it seems like
most everything you say is correct -- I cannot find the documentation on
these features.
I now remember why I didn't answer you the last time and why I probably
won't this time either. It is because when I read what yo
On 9/6/2014 3:10 AM, Kern Sibbald wrote:
> Can you tell me what my explanation of the disk autochanger was and why
> it did not make sense to you?
The goal was to write file volumes -- same pool, same backup set, to a
set of filesystems (hosted on removable disks). The thread went on a for
a co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/2014 09:16 PM, Dimitri Maziuk wrote:
> On 09/05/2014 01:41 PM, Josh Fisher wrote:
>>
>> On 9/5/2014 1:48 PM, Dimitri Maziuk wrote:
>>> I've another bacula setup that writes to a single filesystem. It's been
>>> running with about zero problem
On 09/05/2014 03:10 PM, Josh Fisher wrote:
>> With vchanger I
>> - need to manually fix the catalog every time I sneeze,
>
> Fix the catalog??
Run 'update slots' after 'delete volume'. My impression is "cartridges"
in "magazines" are completely disconnected from "volumes" in the media
catalog; e
On 9/5/2014 3:16 PM, Dimitri Maziuk wrote:
> On 09/05/2014 01:41 PM, Josh Fisher wrote:
>> On 9/5/2014 1:48 PM, Dimitri Maziuk wrote:
>>> I've another bacula setup that writes to a single filesystem. It's been
>>> running with about zero problems (knock on wood) and zero maintenance
>>> for years:
On 09/05/2014 01:41 PM, Josh Fisher wrote:
>
> On 9/5/2014 1:48 PM, Dimitri Maziuk wrote:
>> I've another bacula setup that writes to a single filesystem. It's been
>> running with about zero problems (knock on wood) and zero maintenance
>> for years: auto-labelling works, volume recycling works,
On 9/5/2014 1:48 PM, Dimitri Maziuk wrote:
> I've another bacula setup that writes to a single filesystem. It's been
> running with about zero problems (knock on wood) and zero maintenance
> for years: auto-labelling works, volume recycling works, the only
> problems are spinning rust and lsi's ug
On 09/05/2014 12:52 PM, John Drescher wrote:
>>> There are several ways to control what volumes bacula use. Although I
>>> am uncertian how you got in the situation you were in.
>>
>> That makes two of us. I
>> 1. deleted some volumes and didn't run 'update slots',
>
> I am curious to why you are
>> There are several ways to control what volumes bacula use. Although I
>> am uncertian how you got in the situation you were in.
>
> That makes two of us. I
> 1. deleted some volumes and didn't run 'update slots',
I am curious to why you are deleting volumes. I mean for my vchanger
usage (for 4+
On 09/05/2014 12:16 PM, John Drescher wrote:
> There are several ways to control what volumes bacula use. Although I
> am uncertian how you got in the situation you were in.
That makes two of us. I
1. deleted some volumes and didn't run 'update slots',
2. got an 'intervention needed' e-mail a day
> 2. Bacula's clever volume selection algorithm is completely unsuitable
> for vchanger. If you have multiple disk "magazines" online you probably
> want to fill up one disk, then the next. What bacula did here is pick a
> volume from the next disk when the "current" one's only 20% full.
There are
On 09/05/2014 11:59 AM, Dimitri Maziuk wrote:
>
> So 'update slots kicked' some sense into bacula-dir and it started writing.
duh. 'update slots' kicked...
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital s
So 'update slots kicked' some sense into bacula-dir and it started writing.
Summary:
1. You'd think media manipulation commands like delete volume would
update bacula's inventory when done. You'd be wrong. You have to
manually run 'update slots' every time. This might be documented
someplace (do
On 9/4/2014 3:57 PM, Dimitri Maziuk
wrote:
On 09/04/2014 02:23 PM, Josh Fisher wrote:
...
One possibility is that you need to do a 'update slots' command to bring Bacula
into sync. If anything has changed with regard to which volumes are currently
On 09/04/2014 02:57 PM, Dimitri Maziuk wrote:
...
>> Current Volume "vchanger_0007_0011" not acceptable because:
>> 1998 Volume "vchanger_0007_0011" status is Full, volume has recycling
>> disabled.
>> 04-Sep 13:26 holstein-sd JobId 5431: 3307 Issuing autochanger "unload slot
>> 293, drive 0"
On 09/04/2014 02:23 PM, Josh Fisher wrote:
...
> One possibility is that you need to do a 'update slots' command to bring
> Bacula
> into sync. If anything has changed with regard to which volumes are currently
> online, then the update slots command is necessary to bring Bacula back into
> syn
On 9/4/2014 1:35 PM, Dimitri Maziuk
wrote:
So after making sure every disk fsck's fine, has free space, etc., and
restarting the server, I got this again:
... Warning: Director wanted Volume "vchanger_0008_0011".
Current Volume "vchanger_0007_0011" not accepta
So after making sure every disk fsck's fine, has free space, etc., and
restarting the server, I got this again:
... Warning: Director wanted Volume "vchanger_0008_0011".
Current Volume "vchanger_0007_0011" not acceptable because:
1998 Volume "vchanger_0007_0011" status is Full, volume has
Subject: Re: [Bacula-users] bacula-dir dead but subsys locked
You didn't read the documents I told you earlier, did you?
[root@localhost ~]# cd /usr/share/doc/bacula-common-7.0.4/
[root@localhost bacula-common-7.0.4]# ls -al
total 60
drwxr-xr-x. 2 root root 4096 Jun 19 16:33 .
drwxr-xr-x
age-
> From: John Drescher [mailto:dresche...@gmail.com]
> Sent: Thursday, June 19, 2014 6:55 PM
> To: More, Ankush
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] bacula-dir dead but subsys locked
>
> > I have installed Bacula-7.0.4 on CentOS 6.5 w
To: More, Ankush
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] bacula-dir dead but subsys locked
> I have installed Bacula-7.0.4 on CentOS 6.5 with RPM successfully.
> Bacula-dir,sd,fd start successfully, but when I try access bconsole.
> Bacula-dir daemon show "
> I have installed Bacula-7.0.4 on CentOS 6.5 with RPM successfully.
> Bacula-dir,sd,fd start successfully, but when I try access bconsole.
> Bacula-dir daemon show " bacula-dir dead but subsys locked"
>
> Below is daemon staus:
> root@bacula7 bacula]# service bacula-dir start
> Starting bacula-dir
Hi Team,
I have installed Bacula-7.0.4 on CentOS 6.5 with RPM successfully.
Bacula-dir,sd,fd start successfully, but when I try access bconsole.
Bacula-dir daemon show " bacula-dir dead but subsys locked"
Below is daemon staus:
root@bacula7 bacula]# service bacula-dir start
Starting bacula-dir:
Hello,
A priori this has nothing to do with high resources, unless there
is some sort of unknown Bacula memory corruption problem (unlikely
at this point). This is clearly a segfault. However, it does not
make any sense.
I think you should su
Good morning.
I've got Bacula 7.0.2 on CENTOS6 and when doing a long backup, resources can be
really high (load average 10+). Trying to cancel a job using bconsole,
bacual-dir crashed with the following trace.
Can anyone give me guidance to see if there is anything I can do and/or change
o
Bacula documentation helped me out [Embarassed]
An important thing to know is that Bacula treats disks like tape drives as
much as it can. This means that you can only have a single Volume mounted at
one time on a disk as defined in your Device resource in the Storage daemon's
conf file. You
Hey ,
I cannot get a new File storage device to be used. I can create the volumes and
the volumes appear on the newly added SAN hard disk, but writing to the volumes
fail and change the volume to Error. The Status window of the File-SAN storage
device shows that the job is attempting to run on t
On 3/26/2014 10:52 PM, James Harper wrote:
> I have a new server running Windows 2012R2 with Hyper-V for running Windows
> VM's. Rather than buy a separate server for running Bacula on, I'm thinking
> we can use a SAN with an iSCSI connection to a Linux VM and run the director
> and sd on that.
I have a new server running Windows 2012R2 with Hyper-V for running Windows
VM's. Rather than buy a separate server for running Bacula on, I'm thinking we
can use a SAN with an iSCSI connection to a Linux VM and run the director and
sd on that.
Is anyone doing this and could comment on the perf
On 8/3/2013 2:52 AM, lst_ho...@kwsoft.de wrote:
>
> Zitat von uhog-v...@spamex.com:
>
>> Hi folks,
>>
>> For what it's worth, I tried compiling Bacula 5.0.3 on Ubuntu 12.0.4
>> today. I currently have Bacula 5.0.3 running on Ubuntu 10.0.4 on
>> another server. The compilation failed on 12.0.4 f
Zitat von uhog-v...@spamex.com:
> Hi folks,
>
> For what it's worth, I tried compiling Bacula 5.0.3 on Ubuntu 12.0.4
> today. I currently have Bacula 5.0.3 running on Ubuntu 10.0.4 on
> another server. The compilation failed on 12.0.4 for the director
> though the SD and FD both compiled. I
Hi folks,
For what it's worth, I tried compiling Bacula 5.0.3 on Ubuntu 12.0.4 today. I
currently have Bacula 5.0.3 running on Ubuntu 10.0.4 on another server. The
compilation failed on 12.0.4 for the director though the SD and FD both
compiled. I played around a bit but then decided just for k
On 8/1/2013 10:12 AM, Martin Simmons wrote:
>> On Wed, 31 Jul 2013 13:52:10 -0400, uhog-v9e4 said:
>>
>> On 7/31/2013 10:33 AM, Martin Simmons wrote:
>>>
On Tue, 30 Jul 2013 11:55:43 -0400, uhog-v9e4 said:
Hi folks,
I'm trying to build and run Bacula 5.2.13 on U
> On Wed, 31 Jul 2013 13:52:10 -0400, uhog-v9e4 said:
>
> On 7/31/2013 10:33 AM, Martin Simmons wrote:
> >
> >> On Tue, 30 Jul 2013 11:55:43 -0400, uhog-v9e4 said:
> >>
> >> Hi folks,
> >>
> >> I'm trying to build and run Bacula 5.2.13 on Ubuntu server 12.04.02. I
> >> have downloaded s
1 - 100 of 374 matches
Mail list logo
