You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by "fritz-net (via GitHub)" <gi...@apache.org> on 2023/05/13 12:22:07 UTC
[GitHub] [skywalking] fritz-net opened a new issue, #10798: [Bug] OAP keeps restarting using h2 and helm
fritz-net opened a new issue, #10798:
URL: https://github.com/apache/skywalking/issues/10798
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues.
### Apache SkyWalking Component
OAP server (apache/skywalking)
### What happened
I tried to setup minimal Skywalking via helm for the first time however I cannot reach UI which which seems to be caused by OAP not starting.
k8s tells me: `Readiness probe failed: dial tcp 172.17.0.22:12800: connect: connection refused`
```
2023-05-13 12:15:52,783 com.zaxxer.hikari.HikariDataSource 82 [main] INFO [] - HikariPool-1 - Start completed.
2023-05-13 12:15:52,786 org.apache.skywalking.oap.server.core.storage.model.ModelInstaller 43 [main] INFO [] - table: alarm_record does not exist. OAP is running in 'no-init' mode, waiting... retry 3s later.
2023-05-13 12:15:55,787 org.apache.skywalking.oap.server.core.storage.model.ModelInstaller 43 [main] INFO [] - table: alarm_record does not exist. OAP is running in 'no-init' mode, waiting... retry 3s later.
2023-05-13 12:15:58,788 org.apache.skywalking.oap.server.core.storage.model.ModelInstaller 43 [main] INFO [] - table: alarm_record does not exist. OAP is running in 'no-init' mode, waiting... retry 3s later.
```
however init job seem to be run fine
```
2023-05-13 12:15:15,402 org.apache.skywalking.oap.server.library.server.grpc.GRPCServer 131 [main] INFO [] - Bind handler MetricServiceGRPCHandlerV3 into gRPC server 0.0.0.0:11800
2023-05-13 12:15:15,404 org.apache.skywalking.oap.server.library.server.grpc.GRPCServer 131 [main] INFO [] - Bind handler AccessLogServiceGRPCHandler into gRPC server 0.0.0.0:11800
2023-05-13 12:15:15,409 org.apache.skywalking.oap.server.library.server.grpc.GRPCServer 131 [main] INFO [] - Bind handler AccessLogServiceGRPCHandlerV3 into gRPC server 0.0.0.0:11800
2023-05-13 12:15:15,410 org.apache.skywalking.oap.server.library.server.grpc.GRPCServer 131 [main] INFO [] - Bind handler SatelliteAccessLogServiceGRPCHandlerV3 into gRPC server 0.0.0.0:11800
2023-05-13 12:15:15,506 com.linecorp.armeria.common.util.SystemInfo 237 [main] INFO [] - hostname: skywalking-oap-init-ghwpw (from /proc/sys/kernel/hostname)
2023-05-13 12:15:16,216 com.linecorp.armeria.server.Server 807 [armeria-boss-http-*:12800] INFO [] - Serving HTTP at /0.0.0.0:12800 - http://127.0.0.1:12800/
2023-05-13 12:15:16,218 org.apache.skywalking.oap.server.core.storage.PersistenceTimer 58 [main] INFO [] - persistence timer start
2023-05-13 12:15:16,221 org.apache.skywalking.oap.server.core.cache.CacheUpdateTimer 46 [main] INFO [] - Cache updateServiceInventory timer start
2023-05-13 12:15:16,659 org.apache.skywalking.oap.server.starter.OAPServerBootstrap 53 [main] INFO [] - Version of OAP: 9.2.0-cb8845a
2023-05-13 12:15:16,660 org.apache.skywalking.oap.server.starter.OAPServerBootstrap 56 [main] INFO [] - OAP starts up in init mode successfully, exit now...
```
### What you expected to happen
OAP to just start up without manual intervention on first install
### How to reproduce
Just run the following command against a 1 node k8s minikube cluster
```
helm upgrade --install "skywalking" oci://registry-1.docker.io/apache/skywalking-helm \
--set oap.image.tag=9.2.0 \
--set oap.storageType=h2 \
--set oap.replicas=1 \
--set ui.image.tag=9.2.0 \
--set ui.replicas=1 \
--set elasticsearch.enabled=false
```
### Anything else
I found the same error in issues, however it seemed to be fixed in 9.1.0 and also was related to elastic not h2
related:
https://github.com/apache/skywalking/issues/9486
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [skywalking] wu-sheng closed issue #10798: [Bug] OAP keeps restarting using h2 and helm
Posted by "wu-sheng (via GitHub)" <gi...@apache.org>.
wu-sheng closed issue #10798: [Bug] OAP keeps restarting using h2 and helm
URL: https://github.com/apache/skywalking/issues/10798
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [skywalking] wu-sheng commented on issue #10798: [Bug] OAP keeps restarting using h2 and helm
Posted by "wu-sheng (via GitHub)" <gi...@apache.org>.
wu-sheng commented on issue #10798:
URL: https://github.com/apache/skywalking/issues/10798#issuecomment-1546648503
Don't use H2 for helm deployment. SkyWalking helm is only designed for product use, but the default H2 setup is only in-memory, which is conflicting.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org