Re: [Bacula-users] Can't connect to FD after upgrade to 3.
Am Samstag 27 März 2010 02:57:17 schrieb Roland Roberts: Any suggestions on what's happening here? Maybe some problems with Fedora Firewall or SELinux? Does the fd listen to any interfaces? Does the fd just listen to IPv6 or IPv4? Nameresolution or DNS problems? Julian -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Problem establishing ssh tunnel in Run before script
Hi there,
to one of my clients I'm trying to connect via a ssh tunnel like this:
---
bacula-dir.conf:
Client {
Name = majestix-fd
Address = localhost
FDPort = 9202
Catalog = MyCatalog
Password = xyz # password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired Jobs/Files
}
# [...]
Job {
Name = Majestix Daily Backup On LTO1 Tapes
Type = Backup
Client = majestix-fd
FileSet = MajestixAll
Schedule = DailyFileBackup
Storage = TapeStorageLTO1
Pool = DailyBackupLTO1
Messages = Standard
Run Before Job = /usr/bin/ssh -fC2 -R 9101:localhost:9101 -R
9103:localhost:9103 -L 9202:localhost:9102 majestix sleep 60 sleep 10
# sleep 10 to give ssh some time to settle
SpoolData = yes
Rerun Failed Levels = yes
}
---
majestix's bacula-fd.conf:
FileDaemon { # this is me
Name = majestix-fd
FDport = 9102 # where we listen for the director
FDaddress = localhost
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run
Maximum Concurrent Jobs = 20
Heartbeat Interval = 300
}
---
With this configuration I'm getting the following error:
---
2010-03-27 17:47:06 fileserver-dir Start Backup JobId 601,
Job=Majestix_Daily_Backup_On_LTO1_Tapes.2010-03-27_17.45.53_05 Using Device
TapeStorageLTO1
2010-03-27 17:47:06 fileserver-sd JobId=601
Job=Majestix_Daily_Backup_On_LTO1_Tapes.2010-03-27_17.45.53_05 marked to be
canceled.
2010-03-27 17:47:06 fileserver-dir Fatal error: No Job status returned from
FD.
---
The ssh tunnel is up and running, I'm able to connect to the tunnel end points
with telnet on each side of the connection.
If I - instead of using the Run before statement - establish the ssh tunnel
on the console right before starting the backup job with accurately the same
command line
/usr/bin/ssh -fC2 -R 9101:localhost:9101 -R 9103:localhost:9103 -L
9202:localhost:9102 majestix sleep 60
the backup job runs without any error.
What's the difference between establishing the ssh tunnel on the console
versus the Run before statement?
Thx for reading ;)
--
mit freundlichen Grüßen / best regards
Johannes Studt
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 5.0.1 dir is trying to connect to Postgresql as root and is driving me nuts
Bruno Et all, Yea as I looked at it the problem was well defined and the solution popped out. It was the local line in pg_hba and authentication changed from ident to md5 fixed the problem. Mehma === On Sat, Mar 27, 2010 at 2:23 AM, Bruno Friedmann br...@ioda-net.ch wrote: On 03/25/2010 01:35 AM, mehma sarja wrote: Mehma Hi Mehma, just take a long breathe, and check with postgresql documentation how about interact pg_hba.conf and pg_ident.conf to check manually issue a su bacula and try a psql -U bacula -d bacula type the password when requested and see if you can connect. After you will have a valid connection, bacula-dir can also. I'm thinking your are mixing normal authorization in pg_hba.conf and mapping users in pg_ident.conf -- Bruno Friedmann -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problem establishing ssh tunnel in Run before script
On 27.3.2010 22:11, Johannes Studt wrote:
Hi there,
to one of my clients I'm trying to connect via a ssh tunnel like this:
---
bacula-dir.conf:
Client {
Name = majestix-fd
Address = localhost
FDPort = 9202
Catalog = MyCatalog
Password = xyz # password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired Jobs/Files
}
# [...]
Job {
Name = Majestix Daily Backup On LTO1 Tapes
Type = Backup
Client = majestix-fd
FileSet = MajestixAll
Schedule = DailyFileBackup
Storage = TapeStorageLTO1
Pool = DailyBackupLTO1
Messages = Standard
Run Before Job = /usr/bin/ssh -fC2 -R 9101:localhost:9101 -R
9103:localhost:9103 -L 9202:localhost:9102 majestix sleep 60 sleep 10
# sleep 10 to give ssh some time to settle
SpoolData = yes
Rerun Failed Levels = yes
}
---
majestix's bacula-fd.conf:
FileDaemon { # this is me
Name = majestix-fd
FDport = 9102 # where we listen for the director
FDaddress = localhost
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run
Maximum Concurrent Jobs = 20
Heartbeat Interval = 300
}
---
With this configuration I'm getting the following error:
---
2010-03-27 17:47:06 fileserver-dir Start Backup JobId 601,
Job=Majestix_Daily_Backup_On_LTO1_Tapes.2010-03-27_17.45.53_05 Using Device
TapeStorageLTO1
2010-03-27 17:47:06 fileserver-sd JobId=601
Job=Majestix_Daily_Backup_On_LTO1_Tapes.2010-03-27_17.45.53_05 marked to be
canceled.
2010-03-27 17:47:06 fileserver-dir Fatal error: No Job status returned from
FD.
---
The ssh tunnel is up and running, I'm able to connect to the tunnel end
points
with telnet on each side of the connection.
If I - instead of using the Run before statement - establish the ssh tunnel
on the console right before starting the backup job with accurately the same
command line
/usr/bin/ssh -fC2 -R 9101:localhost:9101 -R 9103:localhost:9103 -L
9202:localhost:9102 majestix sleep 60
the backup job runs without any error.
What's the difference between establishing the ssh tunnel on the console
versus the Run before statement?
Thx for reading ;)
I can't think now fully, but what I see wrong that you use sleep and
sleep in your command. Those are not valid arguments to ssh
executable, but shell constructs. You many need to run sh -c with all
those arguments in order to get it work.
--
http://www.iki.fi/jarif/
You are a bundle of energy, always on the go.
signature.asc
Description: OpenPGP digital signature
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Can't connect to FD after upgrade to 3.
On 03/27/2010 08:41 AM, Julian Golderer wrote: Am Samstag 27 März 2010 02:57:17 schrieb Roland Roberts: Any suggestions on what's happening here? Maybe some problems with Fedora Firewall or SELinux? Does the fd listen to any interfaces? Does the fd just listen to IPv6 or IPv4? Nameresolution or DNS problems? Well, from the part of the message just before my question Note that the configuration files were working just fine before the upgrade and they're really still there. I've trying running client in the foreground but get no indication that it gets anything. I can telnet to the client port and connect, but have no idea if there is a text protocol to ask the FD its status; anything I type seems to just get me disconnected. So no, I don't think there is a firewall or SELinux issue or I wouldn't be able to telnet from the server to the FD. Plus I get no avc warning and have tried with permissive settings. It used to work, before the upgrade, with enforcing turned on. When I telnet to the FD, is there something I could type to talk to it, an equivalent to smtp or http? roland -- PGP Key ID: 66 BC 3B CD Roland B. Roberts, PhD RL Enterprises rol...@rlenter.com6818 Madeline Court rol...@astrofoto.org Brooklyn, NY 11220 -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
