[Puppet Users] puppet 3.1.1-1 ignores runinterval (?)

Hi,

i recently updated from puppet 2.x to puppet 3.1.1-1 (centos 6) and
noticed, that my puppet runs heavily increased.

My config:

[...]
     runinterval = 1200
     report = true
     splay = true
     splaylimit = 300
[...]

but instead of running every 1200 seconds it runs every few minutes.


May 19 03:31:01 issum puppet-agent[16435]: Finished catalog run in 6.12
seconds
May 19 03:38:24 issum puppet-agent[17188]: Finished catalog run in 11.84
seconds
May 19 03:41:32 issum puppet-agent[17874]: Finished catalog run in 5.28
seconds
May 19 03:51:05 issum puppet-agent[18745]: Finished catalog run in 6.16
seconds
May 19 03:58:27 issum puppet-agent[19476]: Finished catalog run in 12.57
seconds

the interval changes from server to server. A different server:

May 19 03:38:26 cupertino puppet-agent[15310]: Finished catalog run in
17.42 seconds
May 19 03:50:50 cupertino puppet-agent[16492]: Finished catalog run in 9.60
seconds
May 19 03:51:50 cupertino puppet-agent[17110]: Finished catalog run in 9.82
seconds
May 19 03:58:29 cupertino puppet-agent[17927]: Finished catalog run in
17.20 seconds
May 19 04:10:58 cupertino puppet-agent[19215]: Finished catalog run in
16.31 seconds
May 19 04:11:50 cupertino puppet-agent[19834]: Finished catalog run in 9.18
seconds

also i noticed more processes running at the same time

   745 ? Ss 0:11 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report
  2618 ? Ss 0:11 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report
  5531 ? Ss 0:12 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report
  8371 ? Ss 0:11 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report
11817 ? Ss 0:11 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report
29503 ? Ss 0:11 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report
30903 ? Ss 0:01 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report
31493 ? Ss 0:11 /usr/bin/ruby /usr/bin/puppet agent
--server=puppet.th --report

this all started after upgrading from 2.x to 3.x

Any ideas?

Thanks and best regards
Sebastian