dangmingyang opened a new issue, #35865:
URL: https://github.com/apache/shardingsphere/issues/35865
> The issue contains images for log, which is not conducive to search or
code copying by contributors. Could you please recreate an new issue and
describe it again using text and code?
_Originally posted by @terrymanu in
[#35850](https://github.com/apache/shardingsphere/issues/35850#issuecomment-3028144410)_
When I deploy ShardingSphere-Proxy latest in a single Docker instance, my
global.yaml is configured as follows:
```yaml
mode:
type: Standalone
repository:
type: JDBC
props:
jdbcUrl:
jdbc:mysql://192.168.30.9:23306/lmersV2?serverTimezone=UTC&useSSL=false&characterEncoding=utf8
username: root
password: Lmers@1qaz2wsx
authority:
users:
- user: root@%
password: root
privilege:
type: ALL_PERMITTED
sqlParser:
sqlStatementCache:
initialCapacity: 2000
maximumSize: 65535
parseTreeCache:
initialCapacity: 128
maximumSize: 1024
props:
max-connections-size-per-query: 1
sql-show: false
proxy-default-port: 3307
```
However, after using DISTSQL to write STORAGE UNITS or ENCRYPT RULES
policies, the data in the database at 192.168.30.9:23306/lmersV2 doesn’t change
at all.There are also no related logs or error outputs in the container. Is
there an issue with my usage or configuration?
I’ve also tried using an H2 database and file storage:
```yaml
mode:
type: Standalone
repository:
type: JDBC
props:
jdbcUrl:
jdbc:h2:mem:config;DB_CLOSE_DELAY=0;DATABASE_TO_UPPER=false;MODE=MYSQL
#username: root
#password:
provider: H2
```
but neither works. After restarting the Docker container, the data still
gets lost.
For the above two configurations, only the following lines of logs appear
when starting the Docker container:
```txt
we find java version: java21, full_version=21.0.5,
full_path=/opt/java/openjdk/bin/java
unadapted java version, please notice...
The classpath is
/opt/shardingsphere-proxy/conf:/opt/shardingsphere-proxy/conf:.:/opt/shardingsphere-proxy/lib/*:/opt/shardingsphere-proxy/ext-lib/*
main class org.apache.shardingsphere.proxy.Bootstrap -1
/opt/shardingsphere-proxy/conf 0.0.0.0 false
[INFO ] 2025-07-01 11:58:37.450 [main]
o.a.s.d.p.c.l.PipelineContextManagerLifecycleListener - mode type is not
Cluster, mode type='Standalone', ignore
[INFO ] 2025-07-01 11:58:37.487 [main] o.a.s.p.frontend.ssl.ProxySSLContext
- Proxy frontend SSL/TLS is not enabled.
[INFO ] 2025-07-01 11:58:37.614 [main] o.a.s.p.frontend.ShardingSphereProxy
- ShardingSphere-Proxy Standalone mode started successfully
```
In addition, whether when running distsql or starting the container, there
are no other exceptions.
Or will the program write logs to other paths when starting up instead of
outputting them to the console of docker logs?
--
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-unsubscr...@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
