On 01/15/2014 02:54 PM, Wolfgang Denk wrote:
> Dear Dimitri,
>>> Basically whay I did is dumping the DB
>>> under MySQL
>>
>>> and then importing the dump into PostgreSQL.
>>
>> That's why the sequences didn't get reinitialized properly.
>
> Would there have been a better way to do that?
Nope.
Dear Thomas,
In message <52d6a29a.6010...@mtl.mit.edu> you wrote:
>
> > I ran this under "bconsole", i. e. as user bacula - is this not the
> > right thing to do?
...
> As someone I think already pointed out, it sounds like the owner of your
> bacula database sequences is another user - more than
Dear Dimitri,
In message <52d5c764.4050...@bmrb.wisc.edu> you wrote:
>
> > I didn't use any precanned procedure (is there one? I mean a
> > recommended/working one?). Basically whay I did is dumping the DB
> > under MySQL=20
>
> > and then importing the dump into PostgreSQL.
>
> That's why the
> I tried that, but it fails:
>
> Enter SQL query: alter sequence fileset_filesetid_seq restart with 76;
> Query failed: ERROR: must be owner of relation fileset_filesetid_seq
>
> I ran this under "bconsole", i. e. as user bacula - is this not the
> right thing to do?
Wolfgang,
As some
On 01/14/2014 04:57 PM, Wolfgang Denk wrote:
> I didn't use any precanned procedure (is there one? I mean a
> recommended/working one?). Basically whay I did is dumping the DB
> under MySQL
> and then importing the dump into PostgreSQL.
That's why the sequences didn't get reinitialized properl
Dear Thomas,
In message <52d59d74.6000...@mtl.mit.edu> you wrote:
>
> > Do you have any idea why this would happen? Is this something I can
> > influence?
> > Are there any other variables that might hit by similar issues?
>
> I can't say exactly why it happened to you but my guess would be tha
On 01/14/2014 02:26 PM, Thomas Lohman wrote:
> I can't say exactly why it happened to you but my guess would be that
> this problem could hit anyone porting from mysql to postgres.
At a guess migration scripts don't translate mysql's "autoincrement" (or
"identity" or whatever they call it) to po
Wolfgang,
> Dear Thomas,
>
> In message <52d555c5.9070...@mtl.mit.edu> you wrote:
>> My guess is that during the migration from MySQL to Postgres, the
>> sequences in Bacula did not get seeded right and probably are starting
>> with a seed value of 1.
>
> Do you have any idea why this would happen
Dear Thomas,
In message <52d555c5.9070...@mtl.mit.edu> you wrote:
> My guess is that during the migration from MySQL to Postgres, the
> sequences in Bacula did not get seeded right and probably are starting
> with a seed value of 1.
Do you have any idea why this would happen? Is this something
My guess is that during the migration from MySQL to Postgres, the
sequences in Bacula did not get seeded right and probably are starting
with a seed value of 1.
the filesetid field in the fileset table is automatically populated by
the fileset_filesetid_seq sequence.
Run the following two quer
Hello,
I've tried to switch a bacula configuration that has been running for
years using from MySQL to PostgreSQL. Everything worked apparently
fine (I did the same before with two other instalations, where the
very same steps worked, too), but when trying to run jobs in the new
PostgreSQL enviro
Hi,
then the database connection is not your problem. With 'netstat -tulpn' you can
check if the mysqld listens on 127.0.0.1:3306. Do you have executed all mysql
create scripts. The output of mysql -u root bacula -e "show tables;" It should
look like this:
+--+
| Tables_in_bacul
> bacula database exists, bacula user have ALL PRIVILEGES.
Then I stand corrected.
I am definitely not a mysql guru, so I will leave the matter to the
other posters.
> What you mean with database schema? What command I need to run?
I *really* think you should stop, take a deep breath and try to
Reynier Perez Mira wrote:
>> You may need to specify the MySQL socket
>>
>
> With socket you mean this line in my.cnf:
> socket = /var/run/mysqld/mysqld.sock
>
Yes, that is the Unix socket mysqld listens on.
>
>> or you can try to connect to 127.0.0.1
>>
> Catalog {
> Name =
Hello,
It is in the documentation, just like the answers to every other
question you asked:
http://www.bacula.org/rel-manual/Installing_Configurin_MySQL.html#mysql_phase2
You need to read the documentation.
Bacula is complex, you need to read the documentation BEFORE you ask
the list questions.
Hi Andrea:
> Generally speaking, opening two threads for the same problem
> is not going to get you an answer any sooner. Having said that,
Soury for that, is not my intention open and reopen the same problem.
> My guess is that you did not create a 'bacula' database
> within mysql, and/or tha
Hello,
Generally speaking, opening two threads for the same problem is not
going to get you an answer any sooner. Having said that,
> MySQL isn't the problem because I do this: mysql -u bacula -p and I can
> connect withouth any problem.
My guess is that you did not create a 'bacula' database
> You may need to specify the MySQL socket
With socket you mean this line in my.cnf:
socket = /var/run/mysqld/mysqld.sock
> or you can try to connect to 127.0.0.1
Catalog {
Name = MyCatalog
dbname = bacula;
user = bacula;
password = "baculadmin"
DB Address = 127.0.0.1
}
This?
Ing.
Reynier Perez Mira wrote:
> Hi Arjen:
>
>
>> Please post the relevant part of you bacula-dir.conf.
>>
>
> Catalog {
> Name = MyCatalog
> dbname = bacula;
> user = bacula;
> password = "baculadmin"
> }
>
You may need to specify the MySQL socket ( DB socket option in
bacula-dir.
Hi Mathias:
> if the mysql server just listens on a unix socket give it a
> try to listen to tcp/ip localhost. You have to comment the
> skip-networking option in your my.cnf file.
I can't find that in my.cnf file. I just see that refer to skip-networking:
#
# Instead of skip-networking the de
Hi,
if the mysql server just listens on a unix socket give it a try to
listen to tcp/ip localhost. You have to comment the skip-networking
option in your my.cnf file.
On Tue, Jan 08, 2008 at 08:41:55AM -0500, Reynier Perez Mira wrote:
> Hi every:
> After some headaches configuring bacula-dir I ha
Hi Arjen:
> Please post the relevant part of you bacula-dir.conf.
Catalog {
Name = MyCatalog
dbname = bacula;
user = bacula;
password = "baculadmin"
}
Ing. Reynier Pérez Mira
-
Check out the new SourceForge.net
08 03:03 pm
Para: Reynier Perez Mira
CC: Bacula Users
Asunto: Re: [Bacula-users] Catalog problem
Have you checked the password on the bacula-dir.conf ?
cheers!
Orlando.
On Jan 8, 2008 7:
Reynier Perez Mira wrote:
> Hi every:
> After some headaches configuring bacula-dir I have another problem. When I
> try to test if bacula-dir.conf file is OK I get this message:
>
> bacula-dir -t -c bacula-dir.conf
> 08-ene 08:43 bacula-dir: Fatal error: Could not open Catalog "MyCatalog",
> d
Have you checked the password on the bacula-dir.conf ?
cheers!
Orlando.
On Jan 8, 2008 7:41 AM, Reynier Perez Mira <[EMAIL PROTECTED]> wrote:
> Hi every:
> After some headaches configuring bacula-dir I have another problem. When I
> try to test if bacula-dir.conf file is OK I get this message:
Hi every:
After some headaches configuring bacula-dir I have another problem. When I try
to test if bacula-dir.conf file is OK I get this message:
bacula-dir -t -c bacula-dir.conf
08-ene 08:43 bacula-dir: Fatal error: Could not open Catalog "MyCatalog",
database "bacula".
08-ene 08:43 bacula-di
26 matches
Mail list logo
