It's now resolved!
The Fedora DNF update picked up Bacula 7.4.2 yesterday and today all the
servers did their first daily backup for nearly 3 weeks - no changes on my part
were needed.
Thanks all.
+--
|This was sent by bill.da
Hello Bill,
Well, you happen to be quite lucky, because some distros are slow to
release fixes, but I have found that Simone is very reactive and fixes
problems extremely rapidly, so I expect that you will have a solution
shortly.
This kind of problem does unfortunately happen. For example,
Btw, co-maintainers are welcome, I can also sponsor people in Fedora if
they have made all the necessary steps:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer
Regards,
--Simo
Sorry, I've not been reading this list recently, I'm swamped at work.
The Fedora 24 package got built before the release, and I've forgot to test
it. I've no production systems with Bacula on Fedora except one laptop.
There is a new update coming with the workaround, it will be available in
updates
This is a bummer. As you will have gathered I am not really a tinkerer. I am
guessing this will take time to fix, during which I cannot now take any backups.
Is there something which isn't dangerous I can do, or should I wait?
I can see this is no fault at all on Kern or Baculas part. However, a
Hello,
Fedora 23 uses gcc 5.3 and Fedora 24 uses gcc 6.1. Thus it appears that
gcc (or g++) on Fedora 24 is broken -- i.e. it generates incorrect code
for Bacula.
Best regards,
Kern
On 07/04/2016 12:58 PM, bdam wrote:
> [root@sabbath ~]# g++ -v
> bash: g++: command not found...
>
> +-
OK, gcc is not loaded. I will check on the Fedora web site.
Best regards,
Kern
On 07/04/2016 12:58 PM, bdam wrote:
> [root@sabbath ~]# g++ -v
> bash: g++: command not found...
>
> +--
> |This was sent by bill.dam...@yahoo.com vi
[root@sabbath ~]# g++ -v
bash: g++: command not found...
+--
|This was sent by bill.dam...@yahoo.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
Hello Bill,
Can you tell me what version of GNU C Fedora 24 is using using (output
from "g++ -v")?
I am not tuned in to Fedora, but if they are using gcc >= 6.0, it might
be worth while posting a bug report to Fedora. If they are using gcc >=
6.0, then a workaround it to build Bacula with -O0
I read the bug report Kern and I think that is also my problem.
I was running bacula 7.4.1 on Fedora 23 OK, and after the update to 24 it's the
same version, but rebuilt for that platform.
I don't build from sources - everything is official Fedora, so I think anyone
using bacula on Fed 23 who upd
Hello Bill,
OK, thanks for the responses. Unfortunately the traceback is not very
useful because the symbols have been stripped, but it did give me a
rough idea where the seg fault is coming from, and it looks like it may
be the same bug reported in the bugs database bug #2231. If you read
t
Thanks Kern.
Part 2/3
I have to answer in parts because this forum is saying my post contains an SQL
injection attempt!
The problem preventing this post was in the trace file so I put it here:
http://pastebin.com/PAZ3mi9n
+--
Thanks Kern.
Part 2/3
I have to answer in parts because this forum is saying my post contains an SQL
injection attempt!
I commented out the DVD entry but it made no difference. Here is bacula-sd.conf
#
# Default Bacula Storage Daemon Configuration file
#
# For Bacula release 2.4.2 (26 July 200
Thanks Kern.
Part 1/3
I have to answer in parts because this forum is saying my post contains an SQL
injection attempt!
This system has only had the regular Fedora 23->24 update as supplied by their
repos.
This what you meant by g++?
[code]
[root@sabbath bacula]# gcc -v
Using built-in specs.
CO
Another question: what version of g++ are you using?
On 07/04/2016 03:36 AM, Kern Sibbald wrote:
> To proceed, I need to have the .traceback file that is normally in the
> working directory. The bacula-sd.conf file would also be useful.
>
> The fact that you have a DVD device may be causing some
To proceed, I need to have the .traceback file that is normally in the
working directory. The bacula-sd.conf file would also be useful.
The fact that you have a DVD device may be causing some problems since
it is no longer supported.
Best regards,
Kern
On 07/03/2016 09:17 PM, bdam wrote:
> D
Damn.
OK, I knew there was an issue I just was clumsy diagnosing it. Thanks for the
quick responses. Heres what should have posted
[root@sabbath ~]# ps -Af | grep bacula
root 1935 1 0 01:04 ?00:00:00 /usr/sbin/bacula-fd -f -c
/etc/bacula/bacula-fd.conf -u root -g root
bacula
> Whats wrong with this please? I'm guessing something is now incompatible with
> the same config I've used for years. Happens on all 3 servers, all of which
> just got the Fedora 23->24 update.
>
> Here is the error:
>
> [root@sabbath sbin]# ./bacula-sd -d -c /etc/bacula/bacula-fd.conf -u root
Hello
You are using the wrong command.
The correct is:
bacula-sd -d 200 -c /etc/bacula/bacula-sd.conf -u root -g root
Best Regards
Wanderlei Hüttel
Enviado de Motorola Moto X2
Em 3 de jul de 2016 7:18 AM, "bdam"
escreveu:
> Whats wrong with this please? I'm guessing something is now incompatib
Well, that is exactly what is expected. If you execute the storage
daemon and give it a File daemon's conf file, it will get upset.
Best regards,
Kern
On 07/03/2016 12:12 PM, bdam wrote:
> Whats wrong with this please? I'm guessing something is now incompatible with
> the same config I've used
Whats wrong with this please? I'm guessing something is now incompatible with
the same config I've used for years. Happens on all 3 servers, all of which
just got the Fedora 23->24 update.
Here is the error:
[root@sabbath sbin]# ./bacula-sd -d -c /etc/bacula/bacula-fd.conf -u root -g
root
[roo
21 matches
Mail list logo
