search for: polling_interv

Hello, I downloaded the latest cruisecontrol.rb from github and tried configuring a schedule for building every 24 hours. Below is my project specific cruise_config.rb. What''s happening is, cruisecontrol.rb is not honoring the polling_interval of 1.day and it keeps building continuously (true to it''s nautre of continuous buids), which I assume it''s using the default polling interval of 5 minutes. Am I missing any other configuration options to make it build only on the specified time period? Also, another question...

...is in the svn repo) and ?rake metrics:all? (let?s say every 24 hours). how do i have to configure cruisecontrol.rb? both rake tasks work. however, when i configure cruisecontrol.rb as described on the metric_fu website, i.e. add ''project.rake_task = ?metrics:all? project.scheduler.polling_interval = 24.hours? to the projects cruise_config.rb, only the metrics:all task is executed, but not the tests. how do i configure cruisecontrol.rb so that both are run?

...ltipath.conf: defaults { user_friendly_names no find_multipaths yes prio weightedpath prio_args "hbtl 0:.:.:.* 1 [1-9]:.:.:.* 10" path_grouping_policy group_by_prio path_selector "service-time 0" failback immediate polling_interval 5 no_path_retry 12 } The setting for prio_args fails to set the correct path map topology and priority against an HBA as I can't predict what HBA is what. Consistently iSCSI claims the lowest number but I can't say if that's going to be 0 or 1 a this stage. Does anyone know...

...rr_min_io 100 path_checker tur } - but our actual multipathing as shown by multipath -ll , and multipath -ll -v 3 looks as though for the HSV400 it is using the defaults rather than these settings. The defaults are #defaults { # udev_dir /dev # polling_interval 10 # selector "round-robin 0" # path_grouping_policy multibus # getuid_callout "/sbin/scsi_id -g -u -s /block/%n" # prio_callout /bin/true # path_checker readsector0 # rr_min_io...

...uration for CruiseControl.rb Project.configure do |project| project.email_notifier.emails = [''mongrel-development at rubyforge.org'', ''rubyinstaller-devel at rubyforge.org''] project.rake_task = ''clobber compile test'' project.scheduler.polling_interval = 5.minutes end

...v/sd* /dev/sda /dev/sda2 /dev/sda5 /dev/sdb /dev/sdb2 /dev/sdb5 /dev/sda1 /dev/sda3 /dev/sda6 /dev/sdb1 /dev/sdb3 /dev/sdb6 ===================================================== The multipath.conf is as follows: defaults { multipath_tool "/sbin/multipath -v0" udev_dir /dev polling_interval 10 default_selector "round-robin 0" default_path_grouping_policy multibus default_getuid_callout "/sbin/scsi_id -g -u -s /block/%n" default_prio_callout "/bin/true" default_features "0" rr_wmin_io 100 failback immediate } devnode_blacklist { devno...

...Open Connected Clear Readonly : No Sectors : 41941688 # After, I have configured the device-mapper multipath by commenting the "blacklist" section in /etc/multipath.conf and adding this "defaults" section: defaults { user_friendly_names yes polling_interval 5 #path_grouping_policy failover path_grouping_policy multibus rr_min_io 1 failback immediate #failback manual no_path_retry fail #no_path_retry queue } Now I have the mpath device configured correctly (IMHO): # multipath -ll...

The most recent message is: [3108269.919256] sd 2:0:1:0: timing out command, waited 1080s [3108269.919528] sd 2:0:1:0: [sdb] Unhandled error code [3108269.919535] sd 2:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK [3108269.919540] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 00 01 21 47 00 00 08 00 [3108269.919586] EXT4-fs error (device sdb1): ext4_find_entry: reading directory #2 offset 0

...rr_min_io 100 path_checker tur } - but our actual multipathing as shown by multipath -ll , and multipath -ll -v 3 looks as though for the HSV400 it is using the defaults rather than these settings. The defaults are #defaults { # udev_dir /dev # polling_interval 10 # selector "round-robin 0" # path_grouping_policy multibus # getuid_callout "/sbin/scsi_id -g -u -s /block/%n" # prio_callout /bin/true # path_checker readsector0 # rr_min_io...

...tgtd start''. The config on the initiator needed to reproduce this is default to the best of my recollection. Xen was compiled with ''make world XEN_TARGET_X86_PAE=y vmxassist=n''. /etc/multipath.conf is as follows: defaults { udev_dir /dev polling_interval 2 selector "round-robin 0" path_grouping_policy multibus # getuid_callout "/sbin/scsi_id -g -u -s /block/%n" prio_callout /bin/true path_checker readsector0 rr_min_io...

Are folks in the Centos community succesfully using device-mapper-multipath? I am looking to deploy it for error handling on our iSCSI setup but there seems to be little traffic about this package on the Centos forums, as far as I can tell, and there seems to be a number of small issues based on my reading the dm-multipath developer lists and related resources. -geoff Geoff Galitz Blankenheim