Fatal NI connect error 12170, connecting to:
(DESCRIPTION...
VERSION INFORMATION:
TNS for Linux: Version 19.0.0.0.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 19.0.0.0.0 - Production
Version 19.19.0.0.0
Time: 13-JUN-2023 11:21:02
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: Message 12535 not found; No message file for product=network, facility=TNS
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Message 505 not found; No message file for product=network, facility=TNS
nt secondary err code: 0
nt OS err code: 0Fatal NI connect error 12170, connecting to:
(DESCRIPTION=...
VERSION INFORMATION:
TNS for Linux: Version 19.0.0.0.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 19.0.0.0.0 - Production
Version 19.19.0.0.0
Time: 13-JUN-2023 14:59:34
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: Message 12535 not found; No message file for product=network, facility=TNS
ns secondary err code: 12579
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0db:
image: mysql:5.7
command:
- "--character-set-server=utf8"
- "--collation-server=utf8_general_ci"mysql -u root -p --database=redmine -B -N -e "SHOW TABLES" | awk '{print "SET foreign_key_checks = 0; ALTER TABLE", $1, "CONVERT TO CHARACTER SET utf8 COLLATE utf8_unicode_ci; SET foreign_key_checks = 1; "}' | mysql -u root -p --database=redminerake aborted!
ActiveRecord::ConnectionNotEstablished: Unsupported charset: '"utf8mb4_unicode_ci"'FROM postgres:14.3
RUN localedef -i de_DE -c -f UTF-8 -A /usr/share/locale/locale.alias de_DE.UTF-8
ENV LANG de_DE.utf8# This file is auto-generated from the current state of the database. Instead
# of editing this file, please use the migrations feature of Active Record to
# incrementally modify your database, and then regenerate this schema definition.
#
# This file is the source Rails uses to define your schema when running `bin/rails
# db:schema:load`. When creating a new database, `bin/rails db:schema:load` tends to
# be faster and is potentially less error prone than running all of your
# migrations from scratch. Old migrations may fail to apply correctly if those
# migrations use external dependencies or application code.
#
# It's strongly recommended that you check this file into your version control system.
ActiveRecord::Schema.define(version: 2022_02_24_194639) do
create_table "attachments", id: :integer, charset: "latin1", force: :cascade do |t|
...
create_table "auth_sources", id: :integer, charset: "latin1", force: :cascade do |t|
...
create_table "boards", id: :integer, charset: "latin1", force: :cascade do |t|
...root@kube2:/data/tmp# svn2git http://192.168.1.2:13000/svn/bgpbo/ --authors ./authors.txt --username sync
command failed:
git checkout -f master
root@kube2:/data/tmp# git checkout -f master
error: pathspec 'master' did not match any file(s) known to git
root@kube2:/data/tmp# git status
On branch master
No commits yet
Untracked files:
(use "git add <file>..." to include in what will be committed)
authors.txt
nothing added to commit but untracked files present (use "git add" to track)
root@kube2:/data/tmp# git commit -m "Initial commit" --allow-empty
[master (root-commit) a15dd94] Initial commit
root@kube2:/data/tmp# git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
authors.txt
nothing added to commit but untracked files present (use "git add" to track)
root@kube2:/data/tmp# git checkout -f master
Already on 'master'
root@kube2:/data/tmp##!/bin/sh
# Set _HERE_ name of the new virtual machine
new=$1
if [ "$new" != "" ]
then
# Create folder for new virtual machine
mkdir /vmfs/volumes/DS2/$new
# Clone virtual disk from prepared template
# and move two created files (.vmdk and -flat.vmdk) to the new location
cd /vmfs/volumes/DS2/susetmp
vmkfstools -i susetmp.vmdk $new.vmdk -d thin
mv /vmfs/volumes/DS2/susetmp/$new* /vmfs/volumes/DS2/$new
# Copy .vmx file to the new location
# and replase template name "susetmp" to the new name of the new virtual machine
cp /vmfs/volumes/DS2/susetmp/susetmp.vmx /vmfs/volumes/DS2/$new/$new.vmx
sed -i 's/susetmp/'$new'/g' /vmfs/volumes/DS2/$new/$new.vmx
else
echo
echo This script copies new virtual machine from prepared template.
echo The template should be located at /vmfs/volumes/DS2/susetmp
echo
echo Example of using:
echo ./clone_suse.sh [new_vm_name]
echo ./clone_suse.sh suse5
echo
echo After run script you should "Register an existing virtual machine" in the ESXi console
echo
fi
# Now you should "Register an existing virtual machine" in the ESXi console
# from the new .vmx file (/vmfs/volumes/DS2/$new/$new.vmx)
# https://kb.vmware.com/s/article/1029513
Переключимся на мониторинг инфраструктуры, в первую очередь сетевого соединения.
Оно достаточно многохоповое и не в нашем ведении, придется обращаться к коллегам извне.
Спасибо.