Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SkyWalking Web Page shows no data #4432

Closed
3 tasks
Heyman90 opened this issue Mar 2, 2020 · 20 comments
Closed
3 tasks

SkyWalking Web Page shows no data #4432

Heyman90 opened this issue Mar 2, 2020 · 20 comments
Labels
question End user question and discussion.
Milestone

Comments

@Heyman90
Copy link

Heyman90 commented Mar 2, 2020

Please answer these questions before submitting your issue.

  • Why do you submit this issue?
  • Question or discussion
  • [√] Bug
  • Requirement
  • Feature or performance improvement

Bug

  • Which version of SkyWalking, OS and JRE?
    6.6.0, Linux, Binary Distribution for ElasticSearch 7
  • What happen?
    After running SkyWalking for three days, SkyWalking Web Page shows no data. Response infos of the WebPage is 'We're sorry but SkyWalking doesn't work properly without JavaScript enabled. Please enable it to continue'. I ensure javascript of myweb view is enabled.
@wu-sheng
Copy link
Member

wu-sheng commented Mar 2, 2020

Do you keep using h2 as storage?

@wu-sheng wu-sheng added this to the 7.0.0 milestone Mar 2, 2020
@wu-sheng wu-sheng added the question End user question and discussion. label Mar 2, 2020
@Heyman90
Copy link
Author

Heyman90 commented Mar 2, 2020

Do you keep using h2 as storage?
I config elasticsearch-7.6.0 as the storage. The elasticsearch cluster include three nodes, every node has master and data roles.
At the same time, I note that the skywalking server print logs such as ’org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient - 388 [I/O dispatcher 1] WARN [] - Bulk [3] executed with failures‘. Get more informations in the picture:

image

@wu-sheng
Copy link
Member

wu-sheng commented Mar 3, 2020

Your ES sever maybe crash. I can't tell why, you have to find out by yourself.

@Heyman90
Copy link
Author

Heyman90 commented Mar 3, 2020

Your ES sever maybe crash. I can't tell why, you have to find out by yourself.

I checked all my es nodes. However, all nodes are in health status and the logs of es show no exception. At the same time, the cpu and memory of the machine are both in a good range.
Maybe should I check something other?

@wu-sheng
Copy link
Member

wu-sheng commented Mar 3, 2020

No clue, are your ES supporting to create index through template?

@Heyman90
Copy link
Author

Heyman90 commented Mar 3, 2020

No clue, are your ES supporting to create index through template?

The es support create index through template. I can get the indexes by template:
image

Do you keep using h2 as storage?
I config elasticsearch-7.6.0 as the storage. The elasticsearch cluster include three nodes, every node has master and data roles.
At the same time, I note that the skywalking server print logs such as ’org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient - 388 [I/O dispatcher 1] WARN [] - Bulk [3] executed with failures‘. Get more informations in the picture:

image

In addition, the logs of skywalking show the library use elasticsearch client while the storage use elasticsearch7 client. Will it influence the data interaction and lead to this result?

@wu-sheng
Copy link
Member

wu-sheng commented Mar 3, 2020

In addition, the logs of skywalking show the library use elasticsearch client while the storage use elasticsearch7 client. Will it influence the data interaction and lead to this result?

Which es client you are using, base on your binary chosen and YAML config. I don't know what you choose.

@wu-sheng wu-sheng closed this as completed Mar 3, 2020
@Heyman90
Copy link
Author

Heyman90 commented Mar 3, 2020

In addition, the logs of skywalking show the library use elasticsearch client while the storage use elasticsearch7 client. Will it influence the data interaction and lead to this result?

Which es client you are using, base on your binary chosen and YAML config. I don't know what you choose.

SkyWalking Version: 6.6.0, Linux, Binary Distribution for ElasticSearch 7;
ElasticSearch Version: 7.6.0.
The picture shows my YAML config:
image

@wu-sheng
Copy link
Member

wu-sheng commented Mar 3, 2020

Look normal. Sorry, can't tell what happens.

@Heyman90
Copy link
Author

Heyman90 commented Mar 3, 2020

Look normal. Sorry, can't tell what happens.

Whatever, thanks for your reply very much.
I will add es nodes to try to reduce pressure of the cluster. Perhaps three nodes can't keep a long time to support skywalking.

@wu-sheng
Copy link
Member

wu-sheng commented Mar 3, 2020

@Heyman90 Next time, please discuss this kind of thing in the mail list, rather than github issue. Today, too many discussions mixed in real issues.

@Heyman90
Copy link
Author

Heyman90 commented Mar 3, 2020

@Heyman90 Next time, please discuss this kind of thing in the mail list, rather than github issue. Today, too many discussions mixed in real issues.

OK,sorry about that.

@Heyman90
Copy link
Author

Heyman90 commented Mar 9, 2020

It is seemly solved by reinstall es and skywalking. However, one week later,the same error appears while es clean records at the TTL time(7days).

@CadenOf
Copy link

CadenOf commented Mar 12, 2020

It is seemly solved by reinstall es and skywalking. However, one week later,the same error appears while es clean records at the TTL time(7days).

Hi @Heyman90, did you make it working now ? I have the same issue like yours in my cluster

@wu-sheng
Copy link
Member

TTL makes the indexes deleted at that moment, 7days in your case.
It requires more resources when doing this. So, likely, your eS cluster crashed.

@CadenOf
Copy link

CadenOf commented Mar 12, 2020

@wu-sheng
It seems that skywalking had created lots of indexs after the TTL time(7 days), I found some logs in my elasticsearch cluster as follow , I'm not sure why skywalking creating these indexs at that time
image
after that, the es health status turn to green
image
but, the oap log still has warning: executed with failures
image

@CadenOf
Copy link

CadenOf commented Mar 12, 2020

It seems that skywalking created so much indices in elasticsearch7 at 00:00 everyday,I delete some older indices then restart skywalking oap resolved this problem.
With defautl configuration in ES, the skwwalking TTL time seems cannot use the default config as 7 days, otherwise there will be more and more indexes in ES then cause this problem.

@wu-sheng
Copy link
Member

No discussion will continue here. Discuss should happen on the official mail list.

@haanyip
Copy link

haanyip commented Mar 25, 2022

Please answer these questions before submitting your issue.

  • Why do you submit this issue?
  • Question or discussion
  • [√] Bug
  • Requirement
  • Feature or performance improvement

Bug

  • Which version of SkyWalking, OS and JRE?
    6.6.0, Linux, Binary Distribution for ElasticSearch 7
  • What happen?
    After running SkyWalking for three days, SkyWalking Web Page shows no data. Response infos of the WebPage is 'We're sorry but SkyWalking doesn't work properly without JavaScript enabled. Please enable it to continue'. I ensure javascript of myweb view is enabled.

it is because of your wrong SW_OAP_ADDRESS when you setup the oap-ui, don't use 127.0.0.1 or localhost, pls fix it and try again~

@Superskyyy
Copy link
Member

Please answer these questions before submitting your issue.

  • Why do you submit this issue?
  • Question or discussion
  • [√] Bug
  • Requirement
  • Feature or performance improvement

Bug

  • Which version of SkyWalking, OS and JRE?

6.6.0, Linux, Binary Distribution for ElasticSearch 7

  • What happen?

After running SkyWalking for three days, SkyWalking Web Page shows no data. Response infos of the WebPage is 'We're sorry but SkyWalking doesn't work properly without JavaScript enabled. Please enable it to continue'. I ensure javascript of myweb view is enabled.

it is because of your wrong SW_OAP_ADDRESS when you setup the oap-ui, don't use 127.0.0.1 or localhost, pls fix it and try again~

Please open a discussions thread and post a Q&A style post there. It will be easier for search for others with the same issue. I will mark your answer as accepted. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question End user question and discussion.
Projects
None yet
Development

No branches or pull requests

5 participants