[one-users] oneacctd execution error
Alberto Picón Couselo
alpicon1 at gmail.com
Tue Jan 10 00:10:28 PST 2012
We are using 3.0.0 stable release under Ubuntu LTS. We considered
upgrading to lastest release candidate, but we are afraid of the
consecuencies of using a RC in a production environment...
El 10/01/2012 2:23, Steven Timm escribió:
> What version are you running? We saw a very similar problem in 3.0
> and they say it is fixed in the latest release candidate.
>
> Steve Timm
>
>
> On Tue, 10 Jan 2012, Alberto Picón Couselo wrote:
>
>> Hi everybody:
>>
>> Please, can you help us with the following oneacctd error?. After 10
>> or 15 minutes of oneacctd usage, oneacctd aborts dumping the
>> following data in /var/log/one/acctd.log
>>
>> Tue Jan 10 00:46:41 +0100 2012 OneWatch::VmMonitoring
>> Tue Jan 10 00:51:41 +0100 2012 OneWatch::VmMonitoring
>> Tue Jan 10 00:56:41 +0100 2012 OneWatch::VmMonitoring
>> Tue Jan 10 00:56:42 +0100 2012 OneWatch::HostMonitoring
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/adapters/mysql.rb:175:in
>> `query': Mysql::Error: Duplicate entry '37-0' for key 'PRIMARY'
>> (Sequel::DatabaseError)
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/adapters/mysql.rb:175:in
>> `_execute'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/database/logging.rb:28:in
>> `log_yield'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/adapters/mysql.rb:175:in
>> `_execute'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/adapters/shared/mysql_prepared_statements.rb:23:in
>> `execute'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/connection_pool/threaded.rb:71:in
>> `hold'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/database/connecting.rb:226:in
>> `synchronize'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/adapters/shared/mysql_prepared_statements.rb:23:in
>> `execute'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/database/query.rb:71:in
>> `execute_dui'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/dataset/actions.rb:639:in
>> `execute_dui'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/adapters/mysql.rb:333:in
>> `execute_dui'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/adapters/mysql.rb:321:in
>> `update'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/model/associations.rb:1197:in
>> `_remove_all_samples'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/model/associations.rb:1383:in
>> `send'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/model/associations.rb:1383:in
>> `remove_all_associated_objects'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/model/associations.rb:1212:in
>> `remove_all_samples'
>> from /usr/lib/one/ruby/acct/watch_helper.rb:279:in `fix_size'
>> from /usr/lib/one/ruby/acct/watch_helper.rb:449:in `flush'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/database/query.rb:231:in
>> `_transaction'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/database/query.rb:210:in
>> `transaction'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/connection_pool/threaded.rb:84:in
>> `hold'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/database/connecting.rb:226:in
>> `synchronize'
>> from
>> /usr/lib/ruby/gems/1.8/gems/sequel-3.28.0/lib/sequel/database/query.rb:208:in
>> `transaction'
>> from /usr/lib/one/ruby/acct/watch_helper.rb:446:in `flush'
>> from /usr/lib/one/ruby/acct/monitoring.rb:31:in `insert'
>> from /usr/lib/one/ruby/acct/acctd.rb:77:in `update'
>> from /usr/lib/one/ruby/acct/acctd.rb:59:in `each'
>> from /usr/lib/one/ruby/acct/acctd.rb:59:in `update'
>> from /usr/lib/one/ruby/acct/acctd.rb:57:in `each'
>> from /usr/lib/one/ruby/acct/acctd.rb:57:in `update'
>> from /usr/lib/one/ruby/acct/acctd.rb:129
>> from /usr/lib/one/ruby/acct/acctd.rb:124:in `loop'
>> from /usr/lib/one/ruby/acct/acctd.rb:124
>>
>> We have noticed too that oneacct client dumps old data. We migrated
>> from 2.9.80 to 3.0.0 without problems, but accounting does not work
>> correctly.
>>
>> Thank you very much in advance,
>>
>> Best Regards,
>> Alberto Picón
>>
>>
>>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120110/d1347d06/attachment-0003.htm>
More information about the Users
mailing list