On Sun, 13 Nov 2011 13:01:58 -0800
pchilingirov bacula-fo...@backupcentral.com wrote:
Just for information:
Finally I found a solution that seems to work so far.
I compiled storage daemon version 5.0.3 and replaced it with the one
from 5.2.1. But I'm not sure that they are completely
pchilingirov wrote:
Just for information:
Finally I found a solution that seems to work so far.
I compiled storage daemon version 5.0.3 and replaced it with the one from
5.2.1.
But I'm not sure that they are completely compatible!
Are you saying you were using 5.2.1 director with 5.0.3
Just for information:
Finally I found a solution that seems to work so far.
I compiled storage daemon version 5.0.3 and replaced it with the one from 5.2.1.
But I'm not sure that they are completely compatible!
Peter
+--
|This
I think that the problem is not in communication. When i tried to change the
password with wrong one it said that the password is not correct.
So i is suppose that the are visible to each other via tcp ports!
+--
|This was sent
On Sat, Nov 12, 2011 at 4:41 AM, pchilingirov
bacula-fo...@backupcentral.com wrote:
I think that the problem is not in communication. When i tried to change the
password with wrong one it said that the password is not correct.
So i is suppose that the are visible to each other via tcp ports!
here is the output from debug
srvlog2-dir: bnet.c:708-0 who=client host=192.168.109.72 port=9101
srvlog2-dir: job.c:1331-0 wstorage=File
srvlog2-dir: job.c:1340-0 wstore=File where=Job resource
srvlog2-dir: job.c:1031-0 JobId=0 created Job=-Console-.2011-11-12_16.11.27_02
srvlog2-dir:
On Sat, Nov 12, 2011 at 9:27 AM, pchilingirov
bacula-fo...@backupcentral.com wrote:
here is the output from debug
srvlog2-dir: bnet.c:708-0 who=client host=192.168.109.72 port=9101
srvlog2-dir: job.c:1331-0 wstorage=File
srvlog2-dir: job.c:1340-0 wstore=File where=Job resource
srvlog2-dir:
Here is gdb output it doesn't look well
(gdb) run -s -f -c /etc/bacula//bacula-sd.conf
Starting program: /sbin/bacula-sd -s -f -c /etc/bacula//bacula-sd.conf
[New LWP1]
warning: Lowest section in /usr/lib/libpthread.so.1 is .dynamic at 0074
[New Thread 1 (LWP 1)]
[New LWP2
Hi All,
I'm having bacula 5.2.1 installed on Solaris 10 SPARC with postgres database.
The problem is that i'm not able to run any kind of backup job.
Here is the error that i have received after running one of the default bacula
jobs:
11-Nov 16:52 srvlog2-dir JobId 8: No prior Full backup Job
On Nov 11, 2011, at 10:12 AM, pchilingirov wrote:
Hi All,
I'm having bacula 5.2.1 installed on Solaris 10 SPARC with postgres database.
The problem is that i'm not able to run any kind of backup job.
Here is the error that i have received after running one of the default
bacula jobs:
I compiled it from package bacula-5.2.1 so i suppose that the version is the
same!
Is there any chance to be different versions?
Regards
+--
|This was sent by fal...@abv.bg via Backup Central.
|Forward SPAM to
On 11/11/11, pchilingirov bacula-fo...@backupcentral.com wrote:
Hi All,
I'm having bacula 5.2.1 installed on Solaris 10 SPARC with postgres
database.
The problem is that i'm not able to run any kind of backup job.
Here is the error that i have received after running one of the default
bacula
Here is the output
*status storage
Automatically selected Storage: File
Connecting to Storage daemon File at srvlog2:9103
srvlog2-sd Version: 5.2.1 (30 October 2011) sparc-sun-solaris2.10 solaris 5.10
Daemon started 12-Nov-11 00:23. Jobs: run=0, running=0.
Heap: heap=90,112 smbytes=15,164
fyi - when I upgraded bacula from 5.0.3 to 5.2.1 I upgraded the Director
and then ran a backup
of a 5.0.3 client just out of curiosity, and it backed up just fine. So
I strongly doubt it is a version
problem, as also your log says is the latest version:
1-Nov 16:52 srvlog2-dir JobId 8: Fatal
Does anyone what any idea what this error means?
13-Aug 23:10 backup-dir: RunBefore: mysqldump:
mysqldump: Couldn't execute 'show fields from
`BaseFiles`': Got error 28 from storage engine (1030)
13-Aug 23:10 backup-dir: RunBefore: mysqldump:
mysqldump: Couldn't execute 'SHOW TRIGGERS LIKE
On Mon, Aug 14, 2006 at 08:50:11AM -0700, Zakai Kinan wrote:
Does anyone what any idea what this error means?
13-Aug 23:10 backup-dir: RunBefore: mysqldump:
mysqldump: Couldn't execute 'show fields from
`BaseFiles`': Got error 28 from storage engine (1030)
The result is that I can't back
I see the error with show warnings; as well in the
mysql cli, but I am still not sure what it means
because I have space on the hardrive. The storage
engine can sometimes refer to myisam or innodb. The
maximum storage on these are in the terabytes so that
is why I am still confused.
any more
On Mon, 14 Aug 2006, Frank Sweetser wrote:
You can use the perror command to translate mysql error codes:
tty/1 1011 erwin 11:45:48 $ perror 28
OS error code 28: No space left on device
Or an oversize database.
The default maximum is about 4Gb for MyISAM.
You can set flags to make it
Hello,
Michael Reith wrote:
There isn't very much outputted to the logs, infact nothing that would
indicate the problem.. below pasted is the error message I recieve, and
a brief description of the problem is quite simple.. While preforming a
full restoration it errors out near the end, and
19 matches
Mail list logo
