# Observer: timeout notification from cluster service. timeout setting \[1m\], time since start \[1m\] **URL:** \ **Category:** Elasticsearch\ **Created:** [June 2, 2015, 12:33am UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676 "2015-06-02T00:33:17Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ccrivelli](https://avatars.discourse-cdn.com/v4/letter/c/f1d935/32.png) [@ccrivelli](https://discuss.elastic.co/u/ccrivelli)\ **Post date:** [June 2, 2015, 12:33am UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676/1 "2015-06-02T00:33:17Z")
Hi guys, is there someone able to clarify what does this Error mean? Can it potentially cause other problems? `observer: timeout notification from cluster service. timeout setting [1m], time since start [1m]` Thanks ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 2, 2015, 11:13am UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676/2 "2015-06-02T11:13:59Z")
Generally this means a node could not be contacted, for whatever reason. It could mean network issues, or GC problems, or high load. It's a little hard to say. ---
**Author:** ![oranciog](https://avatars.discourse-cdn.com/v4/letter/o/e19b73/32.png) [@oranciog](https://discuss.elastic.co/u/oranciog)\ **Post date:** [July 6, 2015, 2:00pm UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676/3 "2015-07-06T14:00:47Z")
Hi, Thank you for your response, but can you be more specific please? "Generally this means a node could not be contacted". How can we find the node that is causing these problems? Is the master, is the node that writes down these messages or it's just an unknown node from cluster? "It could mean network issues, or GC problems, or high load. It's a little hard to say." How can we debug to see exactly what is the problem? Thank you, ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 6, 2015, 9:01pm UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676/4 "2015-07-06T21:01:49Z")
You need to look at the log that has this, there should be more information in it associated with this event. Without that context there's very little else to go on. ---
**Author:** ![vaniaravinda](https://avatars.discourse-cdn.com/v4/letter/v/7993a0/32.png) [@vaniaravinda](https://discuss.elastic.co/u/vaniaravinda)\ **Post date:** [December 7, 2015, 11:05am UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676/5 "2015-12-07T11:05:27Z")
I'm also facing the same issue. Please find below which is logged in log file. [2015-12-07 11:56:48,346][DEBUG][action.bulk] [Betty Ross Banner] observer: timeout notification from cluster service. timeout setting [1m], time since start [1m] Can you please help me how to solve this. I'm using Elasticsearch 1.6.0 version. Thanks, Vani Aravinda ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 8, 2015, 1:41am UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676/6 "2015-12-08T01:41:29Z")
Please start your own thread 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:32pm UTC](https://discuss.elastic.co/t/observer-timeout-notification-from-cluster-service-timeout-setting-1m-time-since-start-1m/1676/7 "2017-07-05T23:32:53Z")