Failed CarbonLink query
Hello,
I am getting many of this message "Failed CarbonLink query"
How can I start debugging/ fix this?
The machine is, Its a centos 6.5 64bit. on top of a supermicro, 2 X xeon 2650, 64GB of RAM.
The load avg. os 1-2.
I have used the instructions from http://
Graphite seems to stop collecting data from time to time and works slow, though the carbon process is running at all time.
always the same lines,
Mon Aug 11 09:03:52 2014 :: Failed CarbonLink query 'la.origin.
Traceback (most recent call last):
File "/opt/graphite/
cachedResults = CarbonLink.
File "/opt/graphite/
results = self.send_
File "/opt/graphite/
result = self.recv_
File "/opt/graphite/
len_prefix = recv_exactly(conn, 4)
File "/opt/graphite/
data = conn.recv( num_bytes - len(buf) )
I also get,
[Mon Aug 11 14:06:23 2014] [error] /usr/lib/
[Mon Aug 11 14:06:23 2014] [error] "use STATIC_URL instead.", DeprecationWarning)
[Mon Aug 11 14:06:23 2014] [error] /usr/lib/
[Mon Aug 11 14:06:23 2014] [error] DeprecationWarning
[Mon Aug 11 14:06:37 2014] [error] /usr/lib/
[Mon Aug 11 14:06:37 2014] [error] "use STATIC_URL instead.", DeprecationWarning)
Thanks so much,
Meir
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Graphite Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- meir
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Hello again Meir,
Did you install master or 0.9.x branch ?
Could you please put your configs here? You can skip comments from them, values only is enough.
BTW wikidot docs is ooooold - please use https:/
But the main question is - did you run only one (single) carbon daemon and that's all?
If yes - then you just ran out of it's capability.
How many metrics/minutes do you have?
Problem that Graphite is written in Python, so, any graphite daemon can't consume more than one core of CPU (it's oversimplification, but true for Graphite). That's why graphite has relay daemon - you can reroute metric to many carbon-cache daemons (on same host) - http://
You also can check that magnificent blog post http://
Also storage is very important for Graphite. Where's your whisper files located (/opt/graphite/
Revision history for this message
|
#2 |
Hello,
Thanks so much for helping!
I have followed the instructions from,
http://
# 0.9.x (stable) branch
git clone https:/
cd graphite-web
git checkout 0.9.x
cd ..
git clone https:/
cd carbon
git checkout 0.9.x
cd ..
git clone https:/
cd whisper
git checkout 0.9.x
cd ..
etc....
one, daemon,
cd /opt/graphite/
./bin/carbon-
I have a much older Graphite machine and I have migrated the data and dashboards to the new machine, the old one is much weaker and it handles the request, I guess that its something else, its a very strong machine. very strong cores....
The storage is sas 15k drives, it should be fast
cpu core load on the machine,
Cpu0 : 26.9%us, 19.7%sy, 0.0%ni, 53.1%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu1 : 8.4%us, 6.4%sy, 0.0%ni, 85.1%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.7%us, 1.3%sy, 0.0%ni, 98.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 : 9.8%us, 5.4%sy, 0.0%ni, 84.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu4 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu5 : 1.3%us, 1.3%sy, 0.0%ni, 97.3%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu6 : 0.7%us, 0.3%sy, 0.0%ni, 99.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu7 : 0.7%us, 0.7%sy, 0.0%ni, 98.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu8 : 36.9%us, 23.0%sy, 0.0%ni, 40.1%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu9 : 26.7%us, 16.7%sy, 0.0%ni, 56.6%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu10 : 17.6%us, 11.4%sy, 0.0%ni, 71.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu11 : 10.0%us, 5.8%sy, 0.0%ni, 84.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu12 : 3.0%us, 2.0%sy, 0.0%ni, 95.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu13 : 1.3%us, 0.7%sy, 0.0%ni, 97.7%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu14 : 36.4%us, 27.8%sy, 0.0%ni, 35.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu15 : 4.7%us, 2.0%sy, 0.0%ni, 93.3%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu16 : 1.3%us, 1.0%sy, 0.0%ni, 97.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu17 : 0.0%us, 0.3%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu18 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu19 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu20 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu21 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu22 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu23 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu24 : 7.3%us, 5.3%sy, 0.0%ni, 87.4%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu25 : 6.8%us, 4.7%sy, 0.0%ni, 88.5%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu26 : 2.0%us, 1.0%sy, 0.0%ni, 97.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu27 : 1.7%us, 1.0%sy, 0.0%ni, 97.4%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu28 : 0.3%us, 0.0%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu29 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu30 : 2.6%us, 0.3%sy, 0.0%ni, 97.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu31 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
The conf was copied from the old machine, local was all commented out.
How do you suggest proceeding?
Thanks so much,
Meir
Revision history for this message
|
#3 |
You can change your setup to one-relay / four-caches for start and also increase timeout, e.g.:
/opt/graphite/
=======
[relay]
LINE_RECEIVER_
LINE_RECEIVER_PORT = 2003
PICKLE_
PICKLE_
RELAY_METHOD = consistent-hashing
REPLICATION_FACTOR = 1
DESTINATIONS = 127.0.0.1:2014:1, 127.0.0.1:2024:2, 127.0.0.1:2034:3, 127.0.0.1:2044:4
[cache]
LINE_RECEIVER_
PICKLE_
CACHE_QUERY_
[cache:1]
LINE_RECEIVER_PORT = 2013
PICKLE_
CACHE_QUERY_PORT = 7012
[cache:2]
LINE_RECEIVER_PORT = 2023
PICKLE_
CACHE_QUERY_PORT = 7022
[cache:3]
LINE_RECEIVER_PORT = 2033
PICKLE_
CACHE_QUERY_PORT = 7032
[cache:4]
LINE_RECEIVER_PORT = 2043
PICKLE_
CACHE_QUERY_PORT = 7042
/opt/graphite/
=======
CARBONLINK_HOSTS = ['127.0.0.1:7012', '127.0.0.1:7022', '127.0.0.1:7032', '127.0.0.1:7042']
CARBONLINK_TIMEOUT = 3.0
It's a config snippets, nor ready to run configs, just edit values your config.
Then you need to run relay daemon and 4 caches:
Instead of running:
bin/carbon-cache.py start
You would run:
bin/carbon-relay.py start
bin/carbon-cache.py --instance=1 start
bin/carbon-cache.py --instance=2 start
bin/carbon-cache.py --instance=3 start
bin/carbon-cache.py --instance=4 start
Revision history for this message
|
#5 |
I dont get the errors any more, I have routed the traffic to the old Graphite machine. should redirecting the traffic again to the new machine change? can the error show up once the change is done or it has nothing to do with it?
Thanks
Revision history for this message
|
#6 |
also, the following errors shouldnt matter, right?
[Tue Aug 12 10:15:18 2014] [error] /usr/lib/
[Tue Aug 12 10:15:18 2014] [error] "use STATIC_URL instead.", DeprecationWarning)
[Tue Aug 12 10:15:18 2014] [error] /usr/lib/
[Tue Aug 12 10:15:18 2014] [error] DeprecationWarning
[Tue Aug 12 10:15:22 2014] [error] /usr/lib/
[Tue Aug 12 10:15:22 2014] [error] "use STATIC_URL instead.", DeprecationWarning)
[Tue Aug 12 10:15:22 2014] [error] /usr/lib/
[Tue Aug 12 10:15:22 2014] [error] DeprecationWarning
[Tue Aug 12 10:15:26 2014] [error] /usr/lib/
[Tue Aug 12 10:15:26 2014] [error] "use STATIC_URL instead.", DeprecationWarning)
[Tue Aug 12 10:15:26 2014] [error] /usr/lib/
[Tue Aug 12 10:15:26 2014] [error] DeprecationWarning
[Tue Aug 12 10:15:38 2014] [error] /usr/lib/
[Tue Aug 12 10:15:38 2014] [error] "use STATIC_URL instead.", DeprecationWarning)
[Tue Aug 12 10:15:38 2014] [error] /usr/lib/
[Tue Aug 12 10:15:38 2014] [error] DeprecationWarning
[Tue Aug 12 10:15:56 2014] [error] /usr/lib/
[Tue Aug 12 10:15:56 2014] [error] "use STATIC_URL instead.", DeprecationWarning)
[Tue Aug 12 10:15:56 2014] [error] /usr/lib/
Revision history for this message
|
#7 |
Seems some deprecation warnings, never saw that. Looks harmless IMO.
I do not understand old/new machine that you saying, but tuning Graphite is quite tricky topic. If you hit some limits again you may need to increase number of cache daemons, number of relays, put faster disk/RAID/SSD etc.
Revision history for this message
|
#8 |
Thanks so much, what I meant to ask was, will streaming traffic again to the Graphite may cause the reappearance of the errors and issue that I was having?
Thank you
Revision history for this message
|
#9 |
Still do not understand you question, sorry, Meir.
If you have no errors on non-loaded server - then yes, it's still possible that you will get errors on loaded server.
Your machine is quite strong, but if you're run only one carbon cache it will not use more than 1 core and starts choking. Please check http://
Revision history for this message
|
#10 |
Thanks so much Denis, I will redirect traffic to the Carbon with in the next couple of days and I will update you afterwards.
Revision history for this message
|
#11 |
Denis, can I send the Graphite traffic to two different machines (IPs)? Thanks
Revision history for this message
|
#12 |
Yes, you can use another relay with REPLICATION_
[relay]
LINE_RECEIVER_
PICKLE_
[relay0]
LINE_RECEIVER_PORT = 2003
PICKLE_
RELAY_METHOD = consistent-hashing
REPLICATION_FACTOR = 2
DESTINATIONS = 127.0.0.1:3004, IP2:2003
[relay1]
LINE_RECEIVER_PORT = 3003
PICKLE_
RELAY_METHOD = consistent-hashing
REPLICATION_FACTOR = 1
DESTINATIONS = 127.0.0.1:2014:1, 127.0.0.1:2024:2, 127.0.0.1:2034:3, 127.0.0.1:2044:4
then you need to run two relays
bin/carbon-relay.py --instance=0 start
bin/carbon-relay.py --instance=1 start
Relay0 will copy metrics both to 127.0.0.1:3004 and IP2:2003.
On 127.0.0.1:3004 relay1 will push metrics to carbon caches.
IP2:2003 - IP and port of another Graphite.
Revision history for this message
|
#13 |
Sorry for not being clear. you are really awesome Denis!
Can the graphite client send metrics to two different graphite servers (different machine and different IPs)?
Thanks so much ;-)
Revision history for this message
|
#14 |
It really depends on client. It's quite simple but I didn't heard about any clients which doing that.
Revision history for this message
|
#15 |
Hello Denis,
I am sending traffic to the Graphite and it is much stable ever since using
4 cache processes behind 1 relay as you have suggested.
I still see the error in the exceptions log file from time to time. the
error follows...
1. Can it be related to the fact that I have copied the webapp directory
from an older version?
2. When ever I am trying to use Graph operation -> breakout the graphs
appear blank, broken image.
How can I solve this?
Thanks so much,
Meir
exception.log
[root@ny-db-010 webapp]# Sun Aug 17 09:11:55 2014 :: Failed CarbonLink
query 'ny.origin.
Traceback (most recent call last):
File "/opt/graphite/
fetchData
cachedResults = CarbonLink.
File "/opt/graphite/
results = self.send_
File "/opt/graphite/
send_request
result = self.recv_
File "/opt/graphite/
recv_response
len_prefix = recv_exactly(conn, 4)
File "/opt/graphite/
recv_exactly
data = conn.recv( num_bytes - len(buf) )
timeout: timed out
error.log
[Sun Aug 17 13:46:36 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:36 2014] [error] DeprecationWarning
[Sun Aug 17 13:46:36 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:36 2014] [error] DeprecationWarning
[Sun Aug 17 13:46:37 2014] [error]
/usr/lib/
DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use
STATIC_URL instead.
[Sun Aug 17 13:46:37 2014] [error] "use STATIC_URL instead.",
DeprecationWarning)
[Sun Aug 17 13:46:37 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:37 2014] [error] DeprecationWarning
On Tue, Aug 12, 2014 at 3:07 PM, Denis Zhdanov <
<email address hidden>> wrote:
> Your question #252963 on Graphite changed:
> https:/
>
> Denis Zhdanov posted a new comment:
> It really depends on client. It's quite simple but I didn't heard about
> any clients which doing that.
>
> --
> You received this question notification because you asked the question.
>
Revision history for this message
|
#16 |
Sorry, Meir, but now I'm totally lost in your setup... Are you has two Graphite installations - one is working and another is not, right?
1. Why you copied webapp dir from previous version? Which previous version? webapp dir contains graphite-web itself, if you mix two versions it teoretically could cause varous troubles, but I do not think that it's your case.
If tou still got lot of that errors then you still facing similar problems - your Graphite is still overloaded, try to increrase number of caches to 8.
2. When you got broken image try to copy it's URL and open it on sepatate tab - then you get error message inside that image.
Revision history for this message
|
#17 |
Thanks so much Denis, I copied the entire webapps for the dashboards. *how
can I copy the dashboards only? I have the original webapps directory saved
I can return it*.
1. I will enlarge the number of cache processes to 8.
2. It worked at a new tab, all of the images. funny! maybe returning the
old webapps would solve this?
Thank you,
Meir
On Sun, Aug 17, 2014 at 5:42 PM, Denis Zhdanov <
<email address hidden>> wrote:
> Your question #252963 on Graphite changed:
> https:/
>
> Status: Open => Needs information
>
> Denis Zhdanov requested more information:
> Sorry, Meir, but now I'm totally lost in your setup... Are you has two
> Graphite installations - one is working and another is not, right?
> 1. Why you copied webapp dir from previous version? Which previous
> version? webapp dir contains graphite-web itself, if you mix two versions
> it teoretically could cause varous troubles, but I do not think that it's
> your case.
> If tou still got lot of that errors then you still facing similar problems
> - your Graphite is still overloaded, try to increrase number of caches to 8.
> 2. When you got broken image try to copy it's URL and open it on sepatate
> tab - then you get error message inside that image.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#18 |
Sorry, I copied the entire storage and not the webapps. my bad.
On Sun, Aug 17, 2014 at 5:49 PM, Meir Hazon <email address hidden> wrote:
> Thanks so much Denis, I copied the entire webapps for the dashboards. *how
> can I copy the dashboards only? I have the original webapps directory saved
> I can return it*.
> 1. I will enlarge the number of cache processes to 8.
> 2. It worked at a new tab, all of the images. funny! maybe returning the
> old webapps would solve this?
> Thank you,
> Meir
>
>
> On Sun, Aug 17, 2014 at 5:42 PM, Denis Zhdanov <
> <email address hidden>> wrote:
>
>> Your question #252963 on Graphite changed:
>> https:/
>>
>> Status: Open => Needs information
>>
>> Denis Zhdanov requested more information:
>> Sorry, Meir, but now I'm totally lost in your setup... Are you has two
>> Graphite installations - one is working and another is not, right?
>> 1. Why you copied webapp dir from previous version? Which previous
>> version? webapp dir contains graphite-web itself, if you mix two versions
>> it teoretically could cause varous troubles, but I do not think that it's
>> your case.
>> If tou still got lot of that errors then you still facing similar
>> problems - your Graphite is still overloaded, try to increrase number of
>> caches to 8.
>> 2. When you got broken image try to copy it's URL and open it on sepatate
>> tab - then you get error message inside that image.
>>
>> --
>> To answer this request for more information, you can either reply to
>> this email or enter your reply at the following page:
>> https:/
>>
>> You received this question notification because you asked the question.
>>
>
>
Revision history for this message
|
#19 |
I can return the original storage if required..... How can I copy the
dashboards only then?
Thanks
On Sun, Aug 17, 2014 at 5:50 PM, Meir Hazon <email address hidden> wrote:
> Sorry, I copied the entire storage and not the webapps. my bad.
>
>
>
> On Sun, Aug 17, 2014 at 5:49 PM, Meir Hazon <email address hidden>
> wrote:
>
>> Thanks so much Denis, I copied the entire webapps for the dashboards. *how
>> can I copy the dashboards only? I have the original webapps directory saved
>> I can return it*.
>> 1. I will enlarge the number of cache processes to 8.
>> 2. It worked at a new tab, all of the images. funny! maybe returning the
>> old webapps would solve this?
>> Thank you,
>> Meir
>>
>>
>> On Sun, Aug 17, 2014 at 5:42 PM, Denis Zhdanov <
>> <email address hidden>> wrote:
>>
>>> Your question #252963 on Graphite changed:
>>> https:/
>>>
>>> Status: Open => Needs information
>>>
>>> Denis Zhdanov requested more information:
>>> Sorry, Meir, but now I'm totally lost in your setup... Are you has two
>>> Graphite installations - one is working and another is not, right?
>>> 1. Why you copied webapp dir from previous version? Which previous
>>> version? webapp dir contains graphite-web itself, if you mix two versions
>>> it teoretically could cause varous troubles, but I do not think that it's
>>> your case.
>>> If tou still got lot of that errors then you still facing similar
>>> problems - your Graphite is still overloaded, try to increrase number of
>>> caches to 8.
>>> 2. When you got broken image try to copy it's URL and open it on
>>> sepatate tab - then you get error message inside that image.
>>>
>>> --
>>> To answer this request for more information, you can either reply to
>>> this email or enter your reply at the following page:
>>> https:/
>>>
>>> You received this question notification because you asked the question.
>>>
>>
>>
>
Revision history for this message
|
#20 |
Meir, plase describe your setup and your problem once and in great detail - it will help a lot, sending many emails without info doesn't help at all.
Revision history for this message
|
#21 |
Thanks Denis,
I have started 4 more cache processes. now I have 8.
1. There are the log errors but I dont know what impact they have. maybe its nothing important. the logs follow.
2. When ever I am trying to use Graph operation -> breakout the graphs
appear blank, broken image. when copying the URL as you suggested to a new tab it works!
3.
exception.log
[root@ny-db-010 webapp]# Sun Aug 17 09:11:55 2014 :: Failed CarbonLink
query 'ny.origin.
Traceback (most recent call last):
File "/opt/graphite/
fetchData
cachedResults = CarbonLink.
File "/opt/graphite/
results = self.send_
File "/opt/graphite/
send_request
result = self.recv_
File "/opt/graphite/
recv_response
len_prefix = recv_exactly(conn, 4)
File "/opt/graphite/
recv_exactly
data = conn.recv( num_bytes - len(buf) )
timeout: timed out
error.log
[Sun Aug 17 13:46:36 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:36 2014] [error] DeprecationWarning
[Sun Aug 17 13:46:36 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:36 2014] [error] DeprecationWarning
[Sun Aug 17 13:46:37 2014] [error]
/usr/lib/
DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use
STATIC_URL instead.
[Sun Aug 17 13:46:37 2014] [error] "use STATIC_URL instead.",
DeprecationWarning)
[Sun Aug 17 13:46:37 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:37 2014] [error] DeprecationWarning
On Tue, Aug 12, 2014 at 3:07 PM, Denis Zhdanov <
<email address hidden>> wrote:
Revision history for this message
|
#22 |
Thanks Denis,
I have started 4 more cache processes. now I have 8.
1. There are the log errors but I dont know what impact they have. maybe its nothing important. the logs follow.
2. When ever I am trying to use Graph operation -> breakout the graphs
appear blank, broken image. when copying the URL as you suggested to a new tab it works!
How can I fix this?
3. How can I copy the dashboards from an old installation to a new one?
I have copied the entire storage directory, is it an issue? I can restore the old directory.
Thanks so much,
Meir
exception.log
[root@ny-db-010 webapp]# Sun Aug 17 09:11:55 2014 :: Failed CarbonLink
query 'ny.origin.
Traceback (most recent call last):
File "/opt/graphite/
fetchData
cachedResults = CarbonLink.
File "/opt/graphite/
results = self.send_
File "/opt/graphite/
send_request
result = self.recv_
File "/opt/graphite/
recv_response
len_prefix = recv_exactly(conn, 4)
File "/opt/graphite/
recv_exactly
data = conn.recv( num_bytes - len(buf) )
timeout: timed out
error.log
[Sun Aug 17 13:46:36 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:36 2014] [error] DeprecationWarning
[Sun Aug 17 13:46:36 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:36 2014] [error] DeprecationWarning
[Sun Aug 17 13:46:37 2014] [error]
/usr/lib/
DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use
STATIC_URL instead.
[Sun Aug 17 13:46:37 2014] [error] "use STATIC_URL instead.",
DeprecationWarning)
[Sun Aug 17 13:46:37 2014] [error]
/usr/lib/
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
[Sun Aug 17 13:46:37 2014] [error] DeprecationWarning
On Tue, Aug 12, 2014 at 3:07 PM, Denis Zhdanov <
<email address hidden>> wrote:
Revision history for this message
|
#23 |
1. Not sure about errors in error.log, looks like deprecation errors from Django.
2. Looks like symptom of overload to me, try to increase CARBONLINK_TIMEOUT - try 5.0 instead of 3.0 if 8 caches didn't help.
3. AFAIK dashboards are stored in DB, if you are using sqlite it's enough to copy graphite.db only.
Revision history for this message
|
#24 |
Thanks so much Denis!
On Sun, Aug 17, 2014 at 8:07 PM, Denis Zhdanov <
<email address hidden>> wrote:
> Your question #252963 on Graphite changed:
> https:/
>
> Denis Zhdanov posted a new comment:
> 1. Not sure about errors in error.log, looks like deprecation errors from
> Django.
> 2. Looks like symptom of overload to me, try to increase
> CARBONLINK_TIMEOUT - try 5.0 instead of 3.0 if 8 caches didn't help.
> 3. AFAIK dashboards are stored in DB, if you are using sqlite it's enough
> to copy graphite.db only.
>
> --
> You received this question notification because you asked the question.
>