Category Archives: Error

Mac vagrant up Error: VBoxManage: error: Failed to create the host-only adapter VBoxManage: error: Context: “RTEXITCODE handleCreate(HandlerArg *)” at line 95 of file VBoxManageHostonly.cpp

1.Error Messages:
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: [“hostonlyif”, “create”]
Stderr: 0%…
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: “RTEXITCODE handleCreate(HandlerArg *)” at line 95 of file VBoxManageHostonly.cpp

2. Solution:

sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart

Webpack Error: Cannot use [chunkhash] for chunk

error – webpack – Cannot use [chunkhash] for chunk

ERROR in chunk runtime [entry]
[name].[chunkhash].js
Cannot use [chunkhash] for chunk in '[name].[chunkhash].js' (use [hash] instead)

Just comment out the hot replacement plug-ins in plugins. The online config does not need hot replacement:

plugins: [
    //new hotModuleReplacementPlugin(),
]

vue.config.js

local productionstart

 devServer: {
    // set proxy
    hot: process.env.NODE_ENV === 'development',
    ......

Kafka Error: Error while executing topic command : Replication factor: 3 larger than available brokers: 0.

This error occurs when creating topic. Create command:

[hw@node01 bin]$ ./kafka-topics.sh --create --topic first --zookeeper node01:2181 --partitions 3 --replication-factor 1

The error is as follows:;

Error while executing topic command : Replication factor: 3 larger than available brokers: 0.
[2022-02-26 15:55:45,948] ERROR org.apache.kafka.common.errors.InvalidReplicationFactorException: Replication factor: 3 larger than available brokers: 0.
 (kafka.admin.TopicCommand$)

Error reason: the problem occurs because the path stored by Kafka # broker in zookeeper is not the root directory, but the/Kafka # path

You can start the client of zookeeper to view the broker path of Kafka:

$ bin/zkCli.sh

#Go to the client to view the path details
$ ls -R /

Therefore, modify the command that you create Topic:

[hw@node01 bin]$ ./kafka-topics.sh --create --topic first --zookeeper node01:2181/kafka --partitions 1 --replication-factor 3

ERROR: Unable to start the RMI connector for NodeAgent (ArcGIS Server Startup Error)

ArcGIS Server does not start the service properly. Checking the /framework/etc/service/logs log file in the installation directory keeps indicating the following error:

“ERROR: Unable to start the RMI connector for NodeAgent”

The initial judgment is related to the network.

The first step is to check the system network information.

Linux environment: use ip addr or nmcli , where you have to make sure IPv6 is turned off.

Step 2, if IPv6 is not turned off, you can turn it off by modifying sysctl.

Modify the /etc/sysctl.conf file and add the following two lines.

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

Execute sysctl -p to take effect.

Step 3 Start the ArcGIS Server service again.

Connected Redis Execute command Error: (error) MISCONF Redis is configured to save RDB snapshots,

Error reporting when connecting to redis

(error) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

The solution is as follows:

Connect redis and run the config set stop writes on bgsave error no command

Close the configuration item stop writes on bgsave error to solve the problem.

gradle –version Error: ERROR: JAVA_HOME is set to an invalid directory: /usr/local/opt/openjdk

1. Problems

appledeMacBook-Pro:~ apple$ gradle -version

ERROR: JAVA_HOME is set to an invalid directory: /usr/local/opt/openjdk

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

2. Solution
vim /usr/local/bin/gradle

#!/bin/bash
#JAVA_HOME="${JAVA_HOME:-/usr/local/opt/openjdk/libexec/openjdk.jdk/Contents/Home}" exec "/usr/local/Cellar/gradle/7.0/libexec/bin/gradle"  "$@"
JAVA_HOME="${JAVA_HOME:-/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home}" exec "/usr/local/Cellar/gradle/7.0/libexec/bin/gradle"  "$@"

[Solved] SQL Error (3621): String or binary data would be truncated The statement has been terminated.

I. Question

SQLServer database writing error occurred as follows: SQL Error (3621): String or binary data would be truncated The statement has been terminated. */

II. Cause

The length of the field definition in the database table structure is smaller than the actual length of the field content to be written, so it cannot be written.

III. Solution

After modifying the length of the fields in the table structure, it can be written successfully

eg：alter table table name alter column field name nvarchar(100)

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.

This error is because that log4j2.xml file not loaded

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.

View now

pom.xml have this code or not?

If it has, then add the follow code below:

<include>**/**.xml</include>

Just run it again.