Hello,
I startet testing base jobs, and I found a very strange behaviour on mysql,
while on postgres everything seems to be fine:
What I did:
I configured one base job, and a "normal" job which depends on this base job:
On a freshly installed and created mysql database, I first ran the base job,
and afterwards the depending job.
Everything works fine until the second job is ready, Then, the mysql proces
starts to run for 100% for **hours**, but it comes to an end.
This is what mysql is doing:
mysqladmin -v processlist
+----+--------+-----------+--------+---------+------+----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Id | User | Host | db | Command | Time | State |
Info
|
+----+--------+-----------+--------+---------+------+----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 18 | bacula | localhost | bacula | Query | 1755 | Copying to tmp table |
INSERT INTO BaseFiles (BaseJobId, JobId, FileId, FileIndex) SELECT B.JobId AS
BaseJobId, 2 AS JobId, B.FileId, B.FileIndex FROM basefile2 AS A,
new_basefile2 AS B WHERE A.Path = B.Path AND A.Name = B.Name ORDER BY B.FileId
|
| 20 | bacula | localhost | bacula | Sleep | 1755 | |
|
| 26 | root | localhost | | Query | 0 | |
show full processlist
|
+----+--------+-----------+--------+---------+------+----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
When I do the same with postgres as database, everything works fine, and the
database only works for about a minute after the second job is ready.
I guess we are missing some index?
Versions:
OS: SUSE Linux Enterprise Server 10 (i586)
VERSION = 10
PATCHLEVEL = 2
bacula : Version: 5.0.0 (26 January 2010)
mysql : mysql Ver 14.12 Distrib 5.0.26, for suse-linux (i686) using readline
5.1
postgres: psql (PostgreSQL) 8.1.19
Hardware: Dual 1GHz P3 with 2.5 G RAM
What information can I provide or what can I do to find the problem?
Regards,
Philipp
Configured Jobs
-------------------
# base job
Job {
Level = Base
Name = "bacula-old-basejob"
Client = "bacula-old-fd"
JobDefs = "DefaultJob"
FileSet = "sles10-32-base-fs"
enabled = no
}
# Zusatz zu Base Job
Job {
Name = "bacula-old-zu-basejob"
Base = "bacula-old-basejob"
Accurate = yes
Client = "bacula-old-fd"
JobDefs = "DefaultJob"
FileSet = "root"
}
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
