common problem

4214 error

ua file problem, modify the dll file or global-metadata.dat by yourself (the international server and the national server should be distinguished)

4206 Error

Most of these errors are that the proxy is not configured correctly, you can try

Double-check all proxy/server configurations

Restart agent/restart server

Run the game after enabling the proxy, check the logs of the server and proxy, if the proxy is in

There is no request for the mihoyo.com / hoyoverse.com subdomain or no logs are flushed, the client proxy is misconfigured

If there is a request for the mihoyo.com / hoyoverse.com subdomain, but TLS handshake failed is reported, the client has not installed the certificate of the corresponding server, or the server cannot connect to the corresponding domain name

There is a request for the mihoyo.com / hoyoverse.com subdomain, but an error such as connection refused is reported. It may be a network problem on the server side that prevents the Mihoyo server from being connected.

If the proxy does not report an error, it should be a server-side problem, check the server-side configuration or update the server-side

If you still can’t solve it, try the following:

Turn off the proxy and start the game normally. After checking the update, turn on the proxy and enter the game again.

Modify server.dispatch.accessAddress in config.json to dispatchcnglobal.yuanshen.com

To confirm the configuration is correct, try to modify server.dispatch.accessAddress in config.json to dispatchcnglobal.yuanshen.com and enter the game again. If you can enter, you can restore this configuration

Click to log in to circle and then no response

If there is a successful login prompt in the server log after clicking, close the login window to enter the game (for bugs in the mobile version)

If not, please check whether the server proxy is running correctly and whether it is suspended (try restarting)

502 / 4301 / Unable to connect to server

Not configured correctly, please check by yourself

Check for updates after login failed

If there is a request for the mihoyo.com / hoyoverse.com subdomain in the proxy log, but an error such as connection refused is reported, it may be a network problem on the server side that prevents the Mihoyo server from being connected.

After opening the agent, I still log in to the official server

There are other proxy conflicts; the server is not running correctly

4201

Check that the certificate is properly installed and trusted

9203

Generally, it is a proxy problem. It is known that iOS uses a small rocket to have this problem.

Card check for updates

Try to enter the game normally once and then connect to the proxy; check the server network problem, if there is no problem, please try to restart the proxy/replace the proxy port/restart the server

Connection timed out after entering the door

Check UDP 22102 or your configuration file has only changed one ip, you need to change both together

white screen when entering

not connected to database

———————————————

No. suddenly exploded no attack icon character information

I have said many times not to go to Yaoyao, Naked Man and other Kate, these few have no models, and there will be ghosts if they don’t blow up.

the problem i’m having

In the case of CentOS 7 + JDK 18 + lawn mower compiled by others, it was found that the abnormal situation of memory and log writing was very obvious, and the integration packaged too many plug-ins.

After compiling it myself, I adjusted the run method (screen) and got some relief. The current memory situation basically starts from 480M and increases by 1M per minute. At the same time, the speed of memory expansion can be suppressed by XX:MaxMetaspaceSize.

The minimalist tutorial of compilation + manual installation will be discussed in the next issue.

crazy log

When running in the background, there will be a lot of logs in /root/genshin/grasscutter/logs. One of the temporary solutions is to lock this directory.

Command reference (unlock is + change -)

 chattr -i /root/genshin/grasscutter/logs

After the log is locked, the startup effect is as shown in the figure

run method

run directly in the foreground

Generally no problem, there is a slight memory expansion problem

Supervisor process daemon

Exit directly, unable to process guard

Pagoda Application Manager

The startup file of the java environment is set to /usr/local/java/bin/java, and the environment parameter is set to -jar

There are a large number of EOF errors, and the log is directly bombed

Nohup run

There are also a lot of error reports, while eating memory + writing logs (in severe cases, tens of megabytes of logs per second + memory expansion of several megabytes per second), but it is better than the Supervisor process guardian and the pagoda application manager, at least it can move

Screen runs

Generally, there is no problem. There is a slight memory expansion problem. The current memory situation basically starts from 480M and increases by 1M per minute. At the same time, the speed of memory expansion can be suppressed by XX:MaxMetaspaceSize.

run command

 java -jar -Xmx512M -XX:MaxMetaspaceSize=512M grasscutter.jar

 java -jar -XX:MaxMetaspaceSize=512M grasscutter.jar

Screen Quick Teaching

Install

 yum install -y screen

Create a session named ys

 screen -S ys

Hold Ctrl and then press A, then D to switch sessions

returns a session named ys

 screen -r ys

List conversations

 screen -ls

Spam log sample

2022-09-18T13:10:38Z <ERROR:emu.grasscutter.Grasscutter> An IO error occurred.

java.io.IOError: java.io.IOException: Bad file descriptor

at org.jline.keymap.BindingReader.readCharacter(BindingReader.java:170)

at org.jline.keymap.BindingReader.readBinding(BindingReader.java:110)

at org.jline.keymap.BindingReader.readBinding(BindingReader.java:61)

at org.jline.reader.impl.LineReaderImpl.doReadBinding(LineReaderImpl.java:923)

at org.jline.reader.impl.LineReaderImpl.readBinding(LineReaderImpl.java:956)

at org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:651)

at org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:468)

at emu.grasscutter.Grasscutter.startConsole(Grasscutter.java:364)

at emu.grasscutter.Grasscutter.main(Grasscutter.java:208)

Caused by: java.io.IOException: Bad file descriptor

at java.base/java.io.FileInputStream.read0(Native Method)

at java.base/java.io.FileInputStream.read(FileInputStream.java:228)

at org.jline.utils.NonBlockingInputStreamImpl.run(NonBlockingInputStreamImpl.java:216)

at java.base/java.lang.Thread.run(Thread.java:833)

There is also an EOF error

16:06:16 < [34mINFO[0;39m:[1;30mGrasscutter[0;39m> EOF detected.

and many more

This article is reprinted from https://www.blueskyxn.com/202209/6596.html
This site is for inclusion only, and the copyright belongs to the original author.