Hello,
Yes, Martin, that is surely the problem. Bacula has a handler for
SIGUSR1 and if it gets a 0 for a signal number, Bacula will die.
Kern
On 11/25/2013 07:43 PM, Martin Simmons wrote:
> Looks like a recently discovered bug in FreeBSD:
>
> http://thread.gmane.org/gmane.os.freebsd.devel.hack
Looks like a recently discovered bug in FreeBSD:
http://thread.gmane.org/gmane.os.freebsd.devel.hackers/51832
__Martin
> On Sun, 24 Nov 2013 17:36:50 -0800, David Newman said:
>
> Apologies for top posting. Kern and Dan asked for more information on
> this issue awhile back, and I'd provid
Hello David,
I have been on vacation since 4 November (in Belgium) and will not
be back home until 1 December. I am busy basically from 8:15am
until 10pm, with only a few pauses, so am not able to look at this.
If the problem is only in the FreeBSD start scripts (not in the ./bacula
script)
then
Apologies for top posting. Kern and Dan asked for more information on
this issue awhile back, and I'd provided it (see below, or the list
archives) in two messages on 10 November.
I'm OK for now by running from the binary, but a backup will crash when
the binary is called from the FreeBSD startup
On 11/10/13 12:09 PM, Dan Langille wrote:
>
> On Nov 10, 2013, at 2:02 PM, David Newman wrote:
>
>> On 11/9/13, 9:33 AM, Dan Langille wrote:
>>> On Nov 8, 2013, at 7:51 PM, David Newman wrote:
>>>
On 11/7/13 6:17 AM, Dan Langille wrote:
> On 2013-11-06 21:05, David Newman wrote:
>>
On 11/10/13 11:54 AM, Kern Sibbald wrote:
> Hello,
>
> It looks like bsmtp is not executable so the gdb output
> is not properly mailed.
It's true that bsmtp was missing from /usr/local/sbin in the FreeBSD
port (not just i386 but also amd64). However I copied a bstmp directory
over there from the
On Nov 10, 2013, at 2:02 PM, David Newman wrote:
> On 11/9/13, 9:33 AM, Dan Langille wrote:
>> On Nov 8, 2013, at 7:51 PM, David Newman wrote:
>>
>>> On 11/7/13 6:17 AM, Dan Langille wrote:
On 2013-11-06 21:05, David Newman wrote:
> On 11/5/13 5:53 PM, Dan Langille wrote:
> You ar
Hello,
It looks like bsmtp is not executable so the gdb output
is not properly mailed. However, Bacula normally will place
two files from the crash in the working directory (whatever it
is configured to be). One of the files, I would like to see --
it is the one named /bacula..traceback,
whe
On 11/9/13, 9:33 AM, Dan Langille wrote:
> On Nov 8, 2013, at 7:51 PM, David Newman wrote:
>
>> On 11/7/13 6:17 AM, Dan Langille wrote:
>>> On 2013-11-06 21:05, David Newman wrote:
On 11/5/13 5:53 PM, Dan Langille wrote:
You are on 9.2-release.
Have you run freebsd-update to g
On Nov 8, 2013, at 7:51 PM, David Newman wrote:
> On 11/7/13 6:17 AM, Dan Langille wrote:
>> On 2013-11-06 21:05, David Newman wrote:
>>> On 11/5/13 5:53 PM, Dan Langille wrote:
>>> You are on 9.2-release.
>>>
>>> Have you run freebsd-update to get the latest security patches?
>>>
>>> Yes
>>>
> On Nov 9, 2013, at 8:12 AM, Dan Langille wrote:
>
> Quick reply from my phone while not at the computer. I think that's it.
> Fixing permissions. Did you install this from ports?
>
Yes, from ports.
It's more than just permissions. The startup script only works if:
- debugging is enabled
-
On 11/7/13 6:17 AM, Dan Langille wrote:
> On 2013-11-06 21:05, David Newman wrote:
>> On 11/5/13 5:53 PM, Dan Langille wrote:
>> You are on 9.2-release.
>>
>> Have you run freebsd-update to get the latest security patches?
>>
>> Yes
>>
>>
>> Did you see the post by Dean E. Weimer today?
>>
>> The m
On 2013-11-06 21:05, David Newman wrote:
> On 11/5/13 5:53 PM, Dan Langille wrote:
> You are on 9.2-release.
>
> Have you run freebsd-update to get the latest security patches?
>
> Yes
>
>
> Did you see the post by Dean E. Weimer today?
>
> The most recent post from Dean to this list (at least
On 11/5/13 5:53 PM, Dan Langille wrote:
> You are on 9.2-release.
>
> Have you run freebsd-update to get the latest security patches?
Yes
>
> Did you see the post by Dean E. Weimer today?
The most recent post from Dean to this list (at least that I have) is
from 4 November at 2030 UTC, saying
You are on 9.2-release.
Have you run freebsd-update to get the latest security patches?
Did you see the post by Dean E. Weimer today?
Second: read below.
On Nov 4, 2013, at 5:44 PM, David Newman wrote:
> On 10/29/13 12:42 PM, Dan Langille wrote:
>> On 2013-10-27 19:33, David Newman wrote:
>>>
On 10/29/13 12:42 PM, Dan Langille wrote:
> On 2013-10-27 19:33, David Newman wrote:
>> On 10/27/13 11:31 AM, Dan Langille wrote:
>>
>> On Oct 22, 2013, at 3:00 PM, David Newman wrote:
>>
>>
>>
>> On 10/19/13 11:40 PM, Kern Sibbald wrote:
>> Hello,
>>
>> From what I can see -- first "signal 0", and
On 11/04/2013 2:01 pm, Dan Langille wrote:
> On Oct 30, 2013, at 4:48 PM, dweimer wrote:
>
>
> I have no idea. But I have one suggestion, just for kicks.
>
> I've long been skeptical of multiple run before/after scripts. I've
> always preferred
> to have just one script. Is it worth combinin
On Oct 30, 2013, at 4:48 PM, dweimer wrote:
> On 10/16/2013 5:43 pm, David Newman wrote:
>> On 10/16/13 12:44 PM, dweimer wrote:
>>> On 10/16/2013 2:13 pm, David Newman wrote:
On 10/14/13 2:44 AM, Martin Simmons wrote:
>> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
>>
On 10/16/2013 5:43 pm, David Newman wrote:
> On 10/16/13 12:44 PM, dweimer wrote:
>> On 10/16/2013 2:13 pm, David Newman wrote:
>>> On 10/14/13 2:44 AM, Martin Simmons wrote:
> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
>
> On 10/9/13 4:41 PM, David Newman wrote:
>>
On 2013-10-27 19:33, David Newman wrote:
> On 10/27/13 11:31 AM, Dan Langille wrote:
>
> On Oct 22, 2013, at 3:00 PM, David Newman wrote:
>
>
>
> On 10/19/13 11:40 PM, Kern Sibbald wrote:
> Hello,
>
> From what I can see -- first "signal 0", and second this
> traceback, this looks a lot like a
On 10/27/13 11:31 AM, Dan Langille wrote:
>
> On Oct 22, 2013, at 3:00 PM, David Newman wrote:
>
>>
>>
>> On 10/19/13 11:40 PM, Kern Sibbald wrote:
>>> Hello,
>>>
>>> From what I can see -- first "signal 0", and second this
>>> traceback, this looks a lot like a FreeBSD pthreads bug.
>>>
>>> Firs
On Oct 22, 2013, at 3:00 PM, David Newman wrote:
>
>
> On 10/19/13 11:40 PM, Kern Sibbald wrote:
>> Hello,
>>
>> From what I can see -- first "signal 0", and second this
>> traceback, this looks a lot like a FreeBSD pthreads bug.
>>
>> First because there is no such thing, at least in userlan
On 10/19/13 11:40 PM, Kern Sibbald wrote:
> Hello,
>
> From what I can see -- first "signal 0", and second this
> traceback, this looks a lot like a FreeBSD pthreads bug.
>
> First because there is no such thing, at least in userland,
> as a signal number 0, which I saw in an earlier
> email.
Hello,
From what I can see -- first "signal 0", and second this
traceback, this looks a lot like a FreeBSD pthreads bug.
First because there is no such thing, at least in userland,
as a signal number 0, which I saw in an earlier
email. Second, as the traceback below
shows, Bacula is waiting on
On 10/18/13 1:15 PM, Dan Langille wrote:
> On Oct 9, 2013, at 7:41 PM, David Newman wrote:
>
>> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
>>
>> Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as soon
>> as bacula-dir starts a backup job. The entry in /var/
On Oct 9, 2013, at 7:41 PM, David Newman wrote:
> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
>
> Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as soon
> as bacula-dir starts a backup job. The entry in /var/log/messages is:
>
> Oct 9 16:25:50 o bacula-fd:
> On Thu, 17 Oct 2013 16:29:22 -0700, David Newman said:
>
> On 10/17/13 5:33 AM, Martin Simmons wrote:
> >> On Wed, 16 Oct 2013 12:13:26 -0700, David Newman said:
> >>
> >> On 10/14/13 2:44 AM, Martin Simmons wrote:
> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
>
On 10/17/13 5:33 AM, Martin Simmons wrote:
>> On Wed, 16 Oct 2013 12:13:26 -0700, David Newman said:
>>
>> On 10/14/13 2:44 AM, Martin Simmons wrote:
On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
On 10/9/13 4:41 PM, David Newman wrote:
> FreeBSD 9.2-RELEASE, bacu
> On Wed, 16 Oct 2013 12:13:26 -0700, David Newman said:
>
> On 10/14/13 2:44 AM, Martin Simmons wrote:
> >> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
> >>
> >> On 10/9/13 4:41 PM, David Newman wrote:
> >>> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
> >>>
On 10/16/2013 05:43 PM, David Newman wrote:
> /usr/local/sbin/btraceback.gdb:1: Error in sourced command file:
> No symbol table is loaded. Use the "file" command.
>
> So, I'm still blocked on debugging this issue.
What it says is if you're attaching to a running process, gdb has no
idea what i
On 10/16/13 12:44 PM, dweimer wrote:
> On 10/16/2013 2:13 pm, David Newman wrote:
>> On 10/14/13 2:44 AM, Martin Simmons wrote:
On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
On 10/9/13 4:41 PM, David Newman wrote:
> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 insta
On 10/16/2013 2:13 pm, David Newman wrote:
> On 10/14/13 2:44 AM, Martin Simmons wrote:
>>> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
>>>
>>> On 10/9/13 4:41 PM, David Newman wrote:
FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
Ever since upgradi
On 10/16/2013 1:21 pm, David Newman wrote:
> On 10/16/13 8:35 AM, dweimer wrote:
>> On 10/09/2013 6:41 pm, David Newman wrote:
>>> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
>>>
>>> Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as
>>> soon
>>> as bacula-di
On 10/14/13 2:44 AM, Martin Simmons wrote:
>> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
>>
>> On 10/9/13 4:41 PM, David Newman wrote:
>>> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
>>>
>>> Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as s
On 10/16/13 8:35 AM, dweimer wrote:
> On 10/09/2013 6:41 pm, David Newman wrote:
>> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
>>
>> Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as soon
>> as bacula-dir starts a backup job. The entry in /var/log/messages is
On 10/09/2013 6:41 pm, David Newman wrote:
> FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
>
> Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as
> soon
> as bacula-dir starts a backup job. The entry in /var/log/messages is:
>
> Oct 9 16:25:50 o bacula-fd: Ba
> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
>
> On 10/9/13 4:41 PM, David Newman wrote:
> > FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
> >
> > Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as soon
> > as bacula-dir starts a backup job. The
Is there a Wireshark decode for Bacula?
I'm still stuck on this problem, and need more info on what's causing
that UNKNOWN SIGNAL error. Wireshark 1.8.6 just shows strings of bytes
for the Bacula stuff.
Thanks.
dn
On 10/9/13 4:41 PM, David Newman wrote:
> FreeBSD 9.2-RELEASE, bacula-client-5.2
FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as soon
as bacula-dir starts a backup job. The entry in /var/log/messages is:
Oct 9 16:25:50 o bacula-fd: Bacula interrupted by signal 0: UNKNOWN SIGNAL
Backups work
39 matches
Mail list logo
