You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by la...@talktalk.net on 2012/06/11 12:39:40 UTC
Keep getting message alarm_handler:
{set,{system_memory_high_watermark,[]}}
Hello,
I'm newbie to couchdb
I have just installed it on my PC which is running Windows 7
I'm using a Dell Vostro with Intel(R) core(TM) i5-2400 CPU @ 3.1 GHz and 2.0GB memory
I'm getting errors on the erlang console with frequent "alarm_handler: {set,{system_memory_high_watermark,[]}} "
When I run the verify test it passes.
When I run the test suite though it fails as shown below:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Name
Status
Elapsed Time
Details
basics
success
4849ms
all_docs
success
172ms
attachments
error
218ms
Run with debugger
Assertion failed: xhr.responseText == lorem
Exception raised: {}
attachments_multipart
success
101ms
attachment_names
success
30ms
attachment_paths
success
121ms
attachment_ranges
success
44ms
attachment_views
success
146ms
auth_cache
success
254ms
batch_save
success
594ms
bulk_docs
success
352ms
changes
success
2063ms
coffee
success
200ms
compact
success
2403ms
config
success
88ms
conflicts
success
132ms
content_negotiation
success
21ms
cookie_auth
success
192ms
copy_doc
success
42ms
delayed_commits
success
17571ms
design_docs
success
27616ms
design_options
success
97ms
design_paths
success
78ms
erlang_views
success
719ms
etags_head
success
52ms
etags_views
success
5252ms
form_submit
success
19ms
http
success
38ms
invalid_docids
success
68ms
jsonp
success
51ms
large_docs
success
53ms
list_views
failure
401ms
Run with debugger
Assertion 'xhr.status == 200, "standard get should be 200"' failed: standard get should be 200
Assertion failed: /head0123456789tail/.test(xhr.responseText)
lots_of_docs
success
187ms
method_override
success
37ms
multiple_rows
success
42ms
oauth
success
1324ms
oauth_users_db
success
116ms
proxyauth
success
73ms
purge
success
207ms
reader_acl
success
2421ms
recreate_doc
success
177ms
reduce
success
1655ms
reduce_builtin
success
2397ms
reduce_false
success
65ms
reduce_false_temp
success
34ms
replication
success
94105ms
replicator_db
failure
67550ms
Run with debugger
Assertion failed: copy === null
Assertion failed: expected 'null', got '{"_id":"foo666","_rev":"1-8f008c4354eb07d5fbfc399a84bc88a1","value":666}'
replicator_db_security
success
382ms
rev_stemming
failure
259ms
Run with debugger
Assertion failed: db.open("bar", {revs: true})._revisions.ids.length == newLimit + 1
Assertion failed: db.open("bar", {revs: true})._revisions.ids.length == newLimit + 1
rewrite
success
173ms
security_validation
success
786ms
show_documents
success
285ms
stats
success
6656ms
update_documents
success
335ms
users_db
success
110ms
users_db_security
success
277ms
utf8
success
67ms
uuids
success
153ms
view_collation
success
171ms
view_collation_raw
success
192ms
view_conflicts
success
108ms
view_compaction
failure
1005ms
Run with debugger
Assertion failed: resp.view_index.disk_size < disk_size_before_compact
view_errors
success
880ms
view_include_docs
success
219ms
view_multi_key_all_docs
success
65ms
view_multi_key_design
success
163ms
view_multi_key_temp
success
81ms
view_offsets
success
614ms
view_pagination
success
149ms
view_sandboxing
success
125ms
view_update_seq
success
5190ms
view_xml
success
45ms
Does anyone know how to get over this problem?
Re: Keep getting message alarm_handler: {set,{system_memory_high_watermark,[]}}
Posted by Robert Newson <ro...@gmail.com>.
The alarms can be ignored, they're a side-effect of a new feature in couchdb that monitors disk consumption.
The test suite failures below look like the usual ones caused by browser cache issues. Clear your cache and try again.
B.
On 11 Jun 2012, at 11:39, laurie.turpin@talktalk.net wrote:
> Hello,
>
>
> I'm newbie to couchdb
> I have just installed it on my PC which is running Windows 7
> I'm using a Dell Vostro with Intel(R) core(TM) i5-2400 CPU @ 3.1 GHz and 2.0GB memory
> I'm getting errors on the erlang console with frequent "alarm_handler: {set,{system_memory_high_watermark,[]}} "
> When I run the verify test it passes.
> When I run the test suite though it fails as shown below:
>
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>
>
>
>
>
> Name
> Status
> Elapsed Time
> Details
>
>
>
> basics
> success
> 4849ms
>
>
>
> all_docs
> success
> 172ms
>
>
>
> attachments
> error
> 218ms
>
> Run with debugger
> Assertion failed: xhr.responseText == lorem
> Exception raised: {}
>
>
>
> attachments_multipart
> success
> 101ms
>
>
>
> attachment_names
> success
> 30ms
>
>
>
> attachment_paths
> success
> 121ms
>
>
>
> attachment_ranges
> success
> 44ms
>
>
>
> attachment_views
> success
> 146ms
>
>
>
> auth_cache
> success
> 254ms
>
>
>
> batch_save
> success
> 594ms
>
>
>
> bulk_docs
> success
> 352ms
>
>
>
> changes
> success
> 2063ms
>
>
>
> coffee
> success
> 200ms
>
>
>
> compact
> success
> 2403ms
>
>
>
> config
> success
> 88ms
>
>
>
> conflicts
> success
> 132ms
>
>
>
> content_negotiation
> success
> 21ms
>
>
>
> cookie_auth
> success
> 192ms
>
>
>
> copy_doc
> success
> 42ms
>
>
>
> delayed_commits
> success
> 17571ms
>
>
>
> design_docs
> success
> 27616ms
>
>
>
> design_options
> success
> 97ms
>
>
>
> design_paths
> success
> 78ms
>
>
>
> erlang_views
> success
> 719ms
>
>
>
> etags_head
> success
> 52ms
>
>
>
> etags_views
> success
> 5252ms
>
>
>
> form_submit
> success
> 19ms
>
>
>
> http
> success
> 38ms
>
>
>
> invalid_docids
> success
> 68ms
>
>
>
> jsonp
> success
> 51ms
>
>
>
> large_docs
> success
> 53ms
>
>
>
> list_views
> failure
> 401ms
>
> Run with debugger
> Assertion 'xhr.status == 200, "standard get should be 200"' failed: standard get should be 200
> Assertion failed: /head0123456789tail/.test(xhr.responseText)
>
>
>
> lots_of_docs
> success
> 187ms
>
>
>
> method_override
> success
> 37ms
>
>
>
> multiple_rows
> success
> 42ms
>
>
>
> oauth
> success
> 1324ms
>
>
>
> oauth_users_db
> success
> 116ms
>
>
>
> proxyauth
> success
> 73ms
>
>
>
> purge
> success
> 207ms
>
>
>
> reader_acl
> success
> 2421ms
>
>
>
> recreate_doc
> success
> 177ms
>
>
>
> reduce
> success
> 1655ms
>
>
>
> reduce_builtin
> success
> 2397ms
>
>
>
> reduce_false
> success
> 65ms
>
>
>
> reduce_false_temp
> success
> 34ms
>
>
>
> replication
> success
> 94105ms
>
>
>
> replicator_db
> failure
> 67550ms
>
> Run with debugger
> Assertion failed: copy === null
> Assertion failed: expected 'null', got '{"_id":"foo666","_rev":"1-8f008c4354eb07d5fbfc399a84bc88a1","value":666}'
>
>
>
> replicator_db_security
> success
> 382ms
>
>
>
> rev_stemming
> failure
> 259ms
>
> Run with debugger
> Assertion failed: db.open("bar", {revs: true})._revisions.ids.length == newLimit + 1
> Assertion failed: db.open("bar", {revs: true})._revisions.ids.length == newLimit + 1
>
>
>
> rewrite
> success
> 173ms
>
>
>
> security_validation
> success
> 786ms
>
>
>
> show_documents
> success
> 285ms
>
>
>
> stats
> success
> 6656ms
>
>
>
> update_documents
> success
> 335ms
>
>
>
> users_db
> success
> 110ms
>
>
>
> users_db_security
> success
> 277ms
>
>
>
> utf8
> success
> 67ms
>
>
>
> uuids
> success
> 153ms
>
>
>
> view_collation
> success
> 171ms
>
>
>
> view_collation_raw
> success
> 192ms
>
>
>
> view_conflicts
> success
> 108ms
>
>
>
> view_compaction
> failure
> 1005ms
>
> Run with debugger
> Assertion failed: resp.view_index.disk_size < disk_size_before_compact
>
>
>
> view_errors
> success
> 880ms
>
>
>
> view_include_docs
> success
> 219ms
>
>
>
> view_multi_key_all_docs
> success
> 65ms
>
>
>
> view_multi_key_design
> success
> 163ms
>
>
>
> view_multi_key_temp
> success
> 81ms
>
>
>
> view_offsets
> success
> 614ms
>
>
>
> view_pagination
> success
> 149ms
>
>
>
> view_sandboxing
> success
> 125ms
>
>
>
> view_update_seq
> success
> 5190ms
>
>
>
> view_xml
> success
> 45ms
>
>
>
> Does anyone know how to get over this problem?
>
>
Re: Keep getting message alarm_handler: {set,{system_memory_high_watermark,[]}}
Posted by Dave Cottlehuber <da...@muse.net.nz>.
On 11 June 2012 12:39, <la...@talktalk.net> wrote:
> Hello,
>
>
> I'm newbie to couchdb
> I have just installed it on my PC which is running Windows 7
Doubly welcome :-).
> I'm using a Dell Vostro with Intel(R) core(TM) i5-2400 CPU @ 3.1 GHz and 2.0GB memory
> I'm getting errors on the erlang console with frequent "alarm_handler: {set,{system_memory_high_watermark,[]}} "
> When I run the verify test it passes.
> When I run the test suite though it fails as shown below:
I'd not get too concerned around these, it seems often we are testing
the browser rather than CouchDB. Also make sure you're testing with
Firefox, rather than IE. More notes on that here
http://wiki.apache.org/couchdb/Windows_Binary_Packages#Testing.
A+
Dave
A+
Dave