当前位置：首页 > news >正文

达梦 manager启动报错

news 2025/8/26 6:22:03

通过mobaxterm登录达梦库服务器，
在这里插入图片描述
首先看到X11-forwarding提示红叉
用root修改 /etc/ssh/sshd_config文件中X11Forwarding为 yes

重启sshd服务
systemctl restart sshd
再次登录

在linux上尝试启动manager，但是无法启动，提示一堆信息

[dmdba@dm8monitor ~]$ manager
No protocol specified(Manager:26029): GLib-GObject-WARNING **: 11:16:21.529: invalid (NULL) pointer instance(Manager:26029): GLib-GObject-CRITICAL **: 11:16:21.529: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed(Manager:26029): Gtk-CRITICAL **: 11:16:21.530: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gtk-WARNING **: 11:16:21.538: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window(Manager:26029): Gtk-WARNING **: 11:16:21.538: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window(Manager:26029): Gdk-CRITICAL **: 11:16:21.538: IA__gdk_screen_get_display: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gdk-CRITICAL **: 11:16:21.539: IA__gdk_display_get_pointer: assertion 'GDK_IS_DISPLAY (display)' failed(Manager:26029): Gtk-WARNING **: 11:16:21.539: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window(Manager:26029): Gdk-CRITICAL **: 11:16:21.539: IA__gdk_screen_get_n_monitors: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gtk-WARNING **: 11:16:21.539: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window(Manager:26029): Gdk-CRITICAL **: 11:16:21.539: IA__gdk_screen_get_monitor_geometry: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gdk-CRITICAL **: 11:16:21.539: IA__gdk_screen_get_default_colormap: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gdk-CRITICAL **: 11:16:21.539: IA__gdk_colormap_get_visual: assertion 'GDK_IS_COLORMAP (colormap)' failed(Manager:26029): Gdk-CRITICAL **: 11:16:21.539: IA__gdk_screen_get_default_colormap: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gdk-CRITICAL **: 11:16:21.539: IA__gdk_screen_get_root_window: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gdk-CRITICAL **: 11:16:21.540: IA__gdk_screen_get_root_window: assertion 'GDK_IS_SCREEN (screen)' failed(Manager:26029): Gdk-CRITICAL **: 11:16:21.540: IA__gdk_window_new: assertion 'GDK_IS_WINDOW (parent)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007ff454e15aa7, pid=26029, tid=0x00007ff4701f2700
#
# JRE version: OpenJDK Runtime Environment (8.0_382-b05) (build 1.8.0_382-b05)
# Java VM: OpenJDK 64-Bit Server VM (25.382-b05 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libgdk-x11-2.0.so.0+0x7baa7]  gdk_window_enable_synchronized_configure+0x7
#
# Core dump written. Default location: /home/dmdba/core or core.26029
#
# An error report file with more information is saved as:
# /home/dmdba/hs_err_pid26029.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/dm/tool/manager：行 21: 26029 已放弃               （核心已转储）"$JAVA_HOME/bin/java" -Xms256m -Xmx2048m -XX:+PerfDisableSharedMem -DDM_HOME="$DM_HOME" -Djava.library.path="$DM_HOME/bin" -Ddameng.log.file="$TOOL_HOME/log4j.xml" -Dosgi.nl="$INSTALL_LANGUAGE" -Duse_bak2=true -Dgrant_vti_role=false -Dapp.name=manager -jar "$TOOL_HOME/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar" -os linux -ws gtk -arch x86_64 -showsplash "$TOOL_HOME/manager.bmp" -configuration "$TOOL_WORKSPACE/configuration/manager" -data "$TOOL_WORKSPACE/data/manager" -product com.dameng.manager.product -name Manager

设置DISPLAY 环境变量


[dmdba@dm8monitor ~]$ who am i
dmdba    pts/0        2025-08-19 11:16 (192.168.32.1)
[dmdba@dm8monitor ~]$ export DISPLAY=192.168.32.1:0.0
[dmdba@dm8monitor ~]$ manager