Re: [Bacula-users] ERR=20:"unable to get local issuer certificate"

On 1/23/21 5:46 PM, Dan Langille wrote: > On Tue, Nov 10, 2020, at 2:11 PM, David Newman wrote: >> Director: FreeBSD 12.2, bacula-server-9.6.6 from pkgs >> Client: OpenBSD 6.8, bacula-client-9.6.5 from pkgs >> >> After upgrading a bacula client's OS from OpenBS

[Bacula-users] ERR=20:"unable to get local issuer certificate"

Director: FreeBSD 12.2, bacula-server-9.6.6 from pkgs Client: OpenBSD 6.8, bacula-client-9.6.5 from pkgs After upgrading a bacula client's OS from OpenBSD 6.7 to 6.8, nightly backups run successfully but throw this warning: ERR=20:"unable to get local issuer certificate" This setup uses self-sig

Re: [Bacula-users] Could not connect to Storage daemon

On 10/9/14, 9:53 AM, Ana Emília M. Arruda wrote: > Hi David, > > Could you clarify some points? > > 1) your storage daemon is running on backups.networktest.com:9103 > .? > 2) who is listening on the 3 ports bellow? > $ sudo netstat -an -f inet | grep 910 > tc

Re: [Bacula-users] Could not connect to Storage daemon

On 10/6/14, 9:20 PM, David Newman wrote: > On 10/3/14, 7:47 AM, Ana Emília M. Arruda wrote: >> Hi David, >> >> Have you tried to schedule the job at another time? Just for checking if >> the problem is at the scheduled time you're trying to run the job or not. &

Re: [Bacula-users] Could not connect to Storage daemon

console could not connect. After a reboot, the rescheduled incremental backup worked for the first few hosts. It's still running. When it's done, I'll change bacula-dir.conf back to the original time, restart everything, and report back. dn > > Regards, > Ana > >

Re: [Bacula-users] Could not connect to Storage daemon

d. The same setup worked for years with FreeBSD 8.x and 9.x; the only difference is that it doesn't work with FreeBSD 10.x. Puzzling that manual backups work, but automated ones don't. dn > > Regards, > Ana > > On Thu, Oct 2, 2014 at 2:01 PM, David Newman <mailto:dne

[Bacula-users] Could not connect to Storage daemon

Bacula 5.2.12 installed as a pkg on FreeBSD 10.0-RELEASE-p9 Nightly backups fail with "Connection refused" errors like those pasted below. However: - backups succeed when run manually from bconsole; and - the Bacula server can telnet to the backups.networktest.com address on port 9103. I've al

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

SD startup script. Thanks in advance for additional troubleshooting clues. Also, should I instead file a FreeBSD PR for this? dn On 11/10/13, 5:12 PM, David Newman wrote: > On 11/10/13 12:09 PM, Dan Langille wrote: >> >> On Nov 10, 2013, at 2:02 PM, David Newman wrote: >&g

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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:

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

gt; The second file is named something like bactrace and is not > interesting for this particular problem. > > Best regards, > Kern > > On 11/10/2013 08: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

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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-rele

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

: - debugging is enabled - btraceback and the bsmtp directory are manually copied into /usr/local/sbin - the bsmtp permissions are set to 777 dn > -- > Dan Langille > http://langille.org/ > > >>>> On Nov 8, 2013, at 7:51 PM, David Newman wrote: >>>> &g

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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 >> >> >>

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

tes at 29030318 from runscript.c:51 o-fd: smartall.c:404 Orphaned buffer: o-fd 272 bytes at 2905d418 from runscript.c:203 o-fd: smartall.c:404 Orphaned buffer: o-fd 24 bytes at 290303d8 from bpipe.c:76 > > On Nov 4, 2013, at 5:44 PM, David Newman wrote: > >> On 10/29/13 12:42 PM, Dan Lan

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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: >>

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

rticularly the > pthreads routines. Perhaps they are using a signal 0 internally, > and somehow that leaked back to Bacula. > > Best regards, > Kern > > On 10/18/2013 01:29 AM, David Newman wrote: >> On 10/17/13 5:33 AM, Martin Simmons wrote: >>>>>>>&

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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: >>>> >

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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

Re: [Bacula-users] bacula-fd crashes on FreeBSD 9.2

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-users] bacula-fd crashes on FreeBSD 9.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

Re: [Bacula-users] catalog pg_dump fails after 5.2.2 upgrade

On 12/23/11 5:27 PM, Thomas Lohman wrote: > The update postgres script for 5.2.x is missing these two lines which > you can run manually from within psql (connect to the bacula db as your > Postgres admin db user): > > grant all on RestoreObject to ${bacula_db_user}; > grant select, update on re

Re: [Bacula-users] catalog pg_dump fails after 5.2.2 upgrade

On 12/23/11 2:38 PM, Dan Langille wrote: > > On Dec 23, 2011, at 5:35 PM, David Newman wrote: > >> On 12/23/11 2:21 PM, Dan Langille wrote: >>> On Dec 20, 2011, at 1:19 PM, David Newman wrote: >>> >>>> bacula 5.2.2, FreeBSD 8.2-RELEASE >>>&g

Re: [Bacula-users] catalog pg_dump fails after 5.2.2 upgrade

On 12/23/11 2:21 PM, Dan Langille wrote: > On Dec 20, 2011, at 1:19 PM, David Newman wrote: > >> bacula 5.2.2, FreeBSD 8.2-RELEASE >> >> After upgrading bacula-server from 5.0.3 to 5.2.2 using FreeBSD ports >> and updating the (PostgreSQL) bacula database, all j

[Bacula-users] catalog pg_dump fails after 5.2.2 upgrade

bacula 5.2.2, FreeBSD 8.2-RELEASE After upgrading bacula-server from 5.0.3 to 5.2.2 using FreeBSD ports and updating the (PostgreSQL) bacula database, all jobs run fine except for the final one on the bacula server, the one that dumps the catalog before making a backup. The error looks like this:

Re: [Bacula-users] maximum value for watchdog timer

On 11/16/11 4:23 AM, Dan Langille wrote: > > On Nov 15, 2011, at 2:53 PM, David Newman wrote: > >> bacula-server 5.0.3 running on FreeBSD, installed from ports. >> >> Which knob in Bacula do I twiddle to reduce the length of this watchdog >> timer: >> >&

[Bacula-users] maximum value for watchdog timer

bacula-server 5.0.3 running on FreeBSD, installed from ports. Which knob in Bacula do I twiddle to reduce the length of this watchdog timer: Error: Watchdog sending kill after 518409 secs to thread stalled reading File daemon. I'm aware of this thread, but didn't see a configurable parameter for

Re: [Bacula-users] fixing a 'Cannot find any appendable volumes' problem

On 4/28/11 4:37 AM, Martin Simmons wrote: >>>>>> On Wed, 27 Apr 2011 21:13:53 -0700, David Newman said: >> >> bacula 5.0.3, FreeBSD 8.2 >> >> While running a full backup of a file server, bacula keeps issuing >> 'Cannot find any appendable

[Bacula-users] fixing a 'Cannot find any appendable volumes' problem

bacula 5.0.3, FreeBSD 8.2 While running a full backup of a file server, bacula keeps issuing 'Cannot find any appendable volumes' messages and prompting me to create a new volume. I've done that, three times, and tried rerunning the job but now the NAS unit attached to the bacula box is nearly ful

Re: [Bacula-users] moving from UTF-8 to SQL_ASCII -- SOLVED

On 6/13/09 2:42 PM, Dan Langille wrote: > David Newman wrote: >> bacula-server-3.0.0, postgresql-server-8.2.13 > >> Looking for guidance on moving a database from UTF-8 to SQL_ASCII. > >> I've been getting a bunch of warnings like this since moving to bacu

[Bacula-users] moving from UTF-8 to SQL_ASCII

bacula-server-3.0.0, postgresql-server-8.2.13 Looking for guidance on moving a database from UTF-8 to SQL_ASCII. I've been getting a bunch of warnings like this since moving to bacula 3.x: bacula-dir JobId 0: Warning: Encoding error for database "bacula". Wanted SQL_ASCII, got UTF8 I am apparen

Re: [Bacula-users] preserving ownership of restored files

On 5/14/09 8:29 AM, Martin Simmons wrote: >>>>>> On Thu, 14 May 2009 06:26:00 -0700, David Newman said: >> On 5/14/09 4:56 AM, Martin Simmons wrote: >>>>>>>> On Wed, 13 May 2009 18:57:43 -0700, David Newman said: >>>> A server

Re: [Bacula-users] preserving ownership of restored files

On 5/14/09 4:56 AM, Martin Simmons wrote: >>>>>> On Wed, 13 May 2009 18:57:43 -0700, David Newman said: >> A server crashed here after an upgrade/reboot. Much mayhem and sleep >> deprivation ensued. Ugh. >> >> Bacula came through with most of the f

[Bacula-users] preserving ownership of restored files

A server crashed here after an upgrade/reboot. Much mayhem and sleep deprivation ensued. Ugh. Bacula came through with most of the files needed, but restored everything as root:wheel. This was from running bconsole, running restore, picking the Job IDs, and selecting files. The UID/GIDs did not e