Beiträge von CLIPPER

CLIPPER · 14. Mai 2018

This looks really really damn good.

CLIPPER · 12. Mai 2018

Tausend dank für die Vorlagen, sieht alles mega aus!

CLIPPER · 12. Mai 2018

Nacht zusammen,

bin gerade auf folgenden Fehler gestoßen;

Code

FUNCTION warp(tbl)
FUNCTION get_warpneedstrings(tbl)
FUNCTION check_warpneeds(tbl)
FUNCTION remove_warpneeds(tbl)
FUNCTION check_and_remove_warpneeds(tbl)
FUNCTION get_warpnames(tbl)
FUNCTION showwarps(tbl)
Calls undeclared function! :
warpring.check_and_remove_warpneeds
warpring.check_warpneeds
warpring.get_warpnames
warpring.get_warpneedstrings
warpring.remove_warpneeds
warpring.showwarps
warpring.warp
Error occured on compile Warpquests/warpneu.lua

Alles anzeigen

Jetzt dachte ich mir, füge ich die fehlenden Funktionen einfach mal in die quest_functions.lua ein so wie sie mir ausgegeben wurden, hilft aber nichts, gibt es da noch mehr was man da beachten sollte ?

Liebe Grüße,
CLIPPER

CLIPPER · 2. Mai 2018

Zitat von Sanii

os.system('chgrp quest object')

Sieht auch nicht ganz richtig aus merke ich grade. Schau dir mal die Makefile aus anderen Files an, solange ich noch nicht daheim bin

#Edit:

Konnte grade durch mein Git, von der Arbeit fix meine make.py rausziehen:

Python: make.py

#!/usr/local/bin/python

import pre_qc

import os

os.system('rm -rf object')

os.system('mkdir object')

os.system('rm -rf pre_qc')

os.system('mkdir pre_qc')

for line in file('quest_list'):

line = line.rstrip()

if len(line) == 0:

continue

if line[0] == '#':

continue

r = pre_qc.run (line)

if r == True:

filename = "pre_qc/{0}".format(line)

else:

filename = line

if os.system("./qc_x64 {0}".format(filename)):

print "Error occured on compile {0}".format(line)

os.system('chmod -R 770 object')

import sys

sys.exit(-1)

os.system('chmod -R 770 object')

Alles anzeigen

Damit kannst du auch Quests in der quest_list mit # auskommentieren und Leerzeilen führen auch nichtmehr zu Fehlern.

#Edit2:

Wer auch immer damals den pre_qc machen durfte, hatte keinen Spaß scheinbar:
print "fucking"

Alles anzeigen

Danke, teste ich sofort mal.

Zu Edit2; habe ich mir auch gedacht, und genau so geht es mir jetzt damit haha.

EDIT; bist ein Gott! Funktioniert alles wieder, frage mich nur noch wieso der Fehler so plötzlich ohne sichtlichen Grund kam.

CLIPPER · 2. Mai 2018

Zitat von Sanii

Hab sie mal etwas umgebaut und das \r entfernt.
Könnte evtl Probleme geben wenn er das letzte Zeichen entfernt und es nicht sein sollte.
Berichte einfach, was es für Auswirkungen hat, konnt's grade auf der Arbeit nicht testen.

Python: make.py

#!/usr/local/bin/python

import pre_qc

import os

os.system('rm -rf object')

os.system('mkdir object')

os.system('rm -rf pre_qc')

os.system('mkdir pre_qc')

os.system('chgrp quest object')

for line in file('quest_list'):

line = line[:-1] # This line removes the last character (\r)

r = pre_qc.run(line)

if r == True:

filename = "pre_qc/{0}".format(line)

else:

filename = line

if os.system("./qc_x64 {0}".format(filename)):

print "Error occured on compile {0}".format(line)

os.system('chmod -R 770 object')

import sys

sys.exit(-1)

os.system('chmod -R 770 object')

Alles anzeigen

Habe es dir ja schon über die PN gesagt, aber hier noch für die Anderen die evtl. mitlesen;
Fehler bleibt;

Spoiler anzeigen

CLIPPER · 2. Mai 2018

Zitat von Aiceal

poste mal deine make.py rein eventuell liegt da ein fehler

Spoiler anzeigen

Edit; hier noch die pre_qc.py

Spoiler anzeigen

# -*- coding: 949 -*-
# 말 그대로 pre qc.
# 우리 퀘스트 언어에는 지역 변수만이 있고,
# state나, 심지어 when, function을 아우르는 전역 변수를 사용할 수 없다.
# 전역 '변수'의 사용은 언어의 구조상 사용이 불가하고, 별 의미가 없다.
# 하지만 전역 '상수'의 사용은 퀘스트 view 상으로 꼭 필요하기 때문에,
# fuction setting () 과 같은 함수를 이용하여,
# 매번 테이블을 생성하여 전역 상수를 흉내내어 사용하였다.
# 이는 매우 비효율적이므로,
# c의 preprocesser와 같이 pre qc를 만들어 전역 상수를 사용할 수 있도록 하였다.
# 퀘스트를 qc로 컴파일 하기 전에 pre_qc.py를 통과하면,
# pre_qc.py는 define 구문을 처리하고, 그 결과를
# pre_qc/filename에 저장한다.

import sys

def split_by_quat (buf):
p = False
l = list (buf)
l.reverse()
s = ""
res = []
while l:
c = l.pop()
if c == '"':
if p == True:
s += c
res += [s]
s = ""
else:
if len (s) != 0:
res += [s]
s = '"'
p = not p
elif c == "\\" and l[0] == '"':
s += c
s += l.pop()
else:
s += c
if len (s) != 0:
res += [s]
return res

def AddSepMiddleOfElement (l, sep):
l.reverse()
new_list = [l.pop()]
while l:
new_list.append (sep)
new_list.append (l.pop())
return new_list

def my_split_with_seps(s, seps):
res = [s]
for sep in seps:
new_res = []
for r in res:
sp = r.split (sep)
sp = AddSepMiddleOfElement (sp, sep)
new_res += sp
res = new_res
new_res = []
for r in res:
if r != '':
new_res.append (r)
return new_res

def my_split(s, seps):
res = [s]
for sep in seps:
new_res = []
for r in res:
sp = r.split (sep)
new_res += sp
res = new_res
new_res = []
for r in res:
if r != '':
new_res.append (r)
return new_res
def MultiIndex (list, key):
l = []
i = 0
for s in list:
if s == key:
l.append (i)
i = i + 1
return l

def Replace (lines, parameter_table, keys):
r = []
for string in lines:
l = split_by_quat (string)
for s in l:
if s[0] == '"':
r += [s]
else:
tokens = my_split_with_seps (s, ["\t", ",", " ", "=", "[", "]",'-','<','>','~','!','.','(',')'])
for key in keys:
try:
idices = MultiIndex(tokens, key)
for i in idices:
tokens[i] = parameter_table[key][0]
except:
pass
r += tokens
return r

def MakeParameterTable(lines, parameter_table, keys):
names = []
values = []
group_names = []
group_values = []
idx = 0
for line in lines:
idx += 1
line = line.strip("\n")
if (-1 != line.find("--")):
line = line[0:line.find("--")]

tokens = my_split(line, ["\t", ",", " ", "=", "[", "]", "\r", "\n"])
if len(tokens) == 0:
continue
if cmp (tokens[0], "quest") == 0:
start = idx
break
if cmp (tokens[0], "define") == 0:
if cmp (tokens[1], "group") == 0:
group_value = []
for value in tokens[3:]:
if parameter_table.get(value, 0) != 0:
value = prameter_table[value]
group_value.append (value)
parameter_table [tokens[2]] = group_value
keys.append(tokens[2])
elif len(tokens) > 5:
print "%d %s" % (idx, "Invalid syntax")
print "define [name] = [value]"
print "define group [name] = \"[\"[v0],[v1], ... \"]\""
else :
if tokens[1] == "rgd_kill_num":
print "fucking"
value = tokens[2]
if parameter_table.get(value, 0) != 0:
value = prameter_table[value]
parameter_table[tokens[1]] = [value]
keys.append (tokens[1])
parameter_table = dict (zip (group_names, group_values))
return start

def run(filename):
parameter_table = dict()
keys = []

filename = filename.strip("\n")
if filename == "":
return
lines = open (filename).readlines()
start = MakeParameterTable (lines, parameter_table, keys)
if len (keys) == 0:
return False

lines = lines [start-1:]
r = Replace (lines, parameter_table, keys)
f = file ("pre_qc/"+filename, "w")
for s in r:
f.write(s)
return True

CLIPPER · 2. Mai 2018

Zitat von Darisil

remove '/r' at the end of the quest's name inside the index file.

sadly there is no "/r" in the quest list

CLIPPER · 2. Mai 2018

Mahlzeit zusammen,

bin gestern Abend auf einen komischen Quest Fehler gestoßen und bin jetzt relativ unschlüssig wie ich das ganze beheben kann.

[cbox]root@root602902:/usr/home/game/share/locale/germany/quest # python make.py
mkdir: pre_qc: File exists
chgrp: quest: illegal group name[/cbox]

chgrp deutet für mich auf einen Berechtigungsfehler.. aber der Quest Ordner "gehört" root-mysql und hat komplette 777 Rechte.

Sobald ich auch nur versuche eine Quest in die quest_list zu packen kommt sofort

[cbox]IOError: [Errno 2] No such file or directory: 'Events/Heirats.quest\r'[/cbox]

obwohl nichts an der Quest / Pfad / Name verändert wurde.

Eventuell könnt ihr mir ja Lösungsansätze vorschlagen.

CLIPPER · 18. April 2018

Sieht imho richtug gut aus. Vorallem die Lila / Pinken Bäume.

CLIPPER · 16. April 2018

Zitat von CLIPPER

nein, ich lösche natürlich nicht über Filezilla. Es dauert bei mir nur, weil meine Bandbreite zurzeit etwas schlapp macht. Da kann es schon mal etwas dauern bis alles aktualisiert ist und ich die Daten vom Server empfange.

warum auch immer läuft MYSQL jetzt wieder. mysql is running as pid 1879.
So, wenn ich jetzt meine Backups von den Tables einfügen möchte muss ich da noch irgend etwas bestimmtes beachten an das ich evtl. nicht gedacht habe? Normal müsste das ja einfach über FileZilla möglich sein oder liege ich da falsch ?

CLIPPER · 16. April 2018

Zitat von Sanii

Ach grade nochmal den Fehler genauer angeschaut.
Created with MySQL 50092 dein MySQL Backup ist einfach von ner uralten Version.
Speichere dir die "mysql.users"-Dateien, lösch den mysql-Ordner (also die Tabelle) und starte den MySQL-Service, er sollte den Ordner nun neu generieren.
Schiebe dann deine gespeicherte "mysql.users" wieder in den neuen mysql-Ordner und starte neu.

Falls das nicht hilft, kann ich's mir später mal ansehen.

Du löscht den Ordner doch nicht etwa über FileZila/WinSCP oder? Hört sich an als würde das Löschen bei dir dauern.
cd /var/db && rm -rf mysql

Alles anzeigen

nein, ich lösche natürlich nicht über Filezilla. Es dauert bei mir nur, weil meine Bandbreite zurzeit etwas schlapp macht. Da kann es schon mal etwas dauern bis alles aktualisiert ist und ich die Daten vom Server empfange.

CLIPPER · 16. April 2018

Zitat von Sanii

Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50092, now running 50639. Please use mysql_upgrade to fix this error.

Auf die Zeile wurde ja schon Verwiesen.

Welche MySQL Version hast du installiert? 5.6 oder 5.7?

Ab 5.7 haben sich die MySQL-eigenen Tabellen etwas geändert. Darum musst du das upgrade laufen lassen.

Alles anzeigen

Habe MYSQL5.6 am laufen, upgrade möchte er nicht durchführen, bin jetzt gerade dabei das gesamte Verzeichnis MYSQL in /var/db zu löschen und danach die .tar.gz neu zu entpacken, eventuell hilft das ja was.

CLIPPER · 16. April 2018

Zitat von Ranighte

Achso hab was überlesen, vergiss was ich geschrieben habe

Uhm, okay, alles klar haha.

CLIPPER · 16. April 2018

Zitat von Ranighte

mach nen advanced check deiner tabellen in Navicat und mach ggf. repair

Sorry, aber wie mache ich das ?

Die richtige MYSQL Version habe ich, es ging bis dato ja alles.
Habe nun einfach mal die quest.list wieder zurück gesetzt aber mysql56-server lässt sich dennoch nicht starten.

CLIPPER · 16. April 2018

Zitat von StreetFight

steht genau da : 2018-04-16 02:23:16 710 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50092, now running 50639. Please use mysql_upgrade to fix this error.

Hast du da zwei ColumS hinzugefügt ? Wenn ja lösch se wieder oder nimm mal ein backup von der tabelle?

Ansonsten benutzt du vielleicht eine Datenbank die von einer anderen MySQL version stammt dann würde ich mal deine derzeigte MySQL version deinstallieren und die richtige für die Fliege Files DB installieren.

Danke für deine Antwort. Ich habe schon auf den Fehler geschaut bevor ich gepostet habe, jedoch habe ich zuletzt um 02:19:39 die quest.list verändert und ansonsten nichts an den Tables gemacht, ansonsten hätte ich es eventuell schon selbst gelöst. Irgendwelche Vorschläge ?

CLIPPER · 16. April 2018

Hallo zusammen,

ich bräuchte mal ein paar Anreize für eine möglichst leichte Lösung.
Folgendes Problem;

MYSQL startet beim booten der Fliege Files nicht und ist auch laut service mysql-server status nicht aktiv.

Die Logs sagen man solle ein mysql_upgrade durchführen, dafür habe ich jedoch trotz mysql_upgrade -uroot -p --force keinerlei Berechtigung.

Via mysql_safe --skip-grant-tables & habe ich es ebenfalls schon versucht, ohne Erfolg.

Neustarten lässt sich MYSQL auch nicht.

Der Fehler ist aufgetreten nachdem ich die CONFIG Files in Channel 1 Kern1, 2 & 3, Reiche und Neutraler_Channel (ch99) auf lvl 99 gestellt habe. Auch nach rückgängig machen keine Veränderung.

Mittlerweile bekomme ich folgende Fehlermeldung und weiß jetzt nicht mehr weiter, hoffe ihr könnt aushelfen.

Spoiler anzeigen

2018-04-16 01:42:04 708 [Note] Server hostname (bind-address): '*'; port: 3306
2018-04-16 01:42:04 708 [Note] IPv6 is available.
2018-04-16 01:42:04 708 [Note] - '::' resolves to '::';
2018-04-16 01:42:04 708 [Note] Server socket created on IP: '::'.
2018-04-16 01:42:05 708 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50092, now running 50639. Please use mysql_upgrade to fix this error.
2018-04-16 01:42:05 708 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2018-04-16 01:42:05 708 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.39' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2018-04-16 01:43:12 708 [Note] /usr/local/libexec/mysqld: Normal shutdown

2018-04-16 01:43:12 708 [Note] Giving 0 client threads a chance to die gracefully
2018-04-16 01:43:12 708 [Note] Shutting down slave threads
2018-04-16 01:43:12 708 [Note] Forcefully disconnecting 0 remaining clients
2018-04-16 01:43:12 708 [Note] Binlog end
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'partition'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_METRICS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_CMP'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'INNODB_TRX'
2018-04-16 01:43:12 708 [Note] Shutting down plugin 'InnoDB'
2018-04-16 01:43:12 708 [Note] InnoDB: FTS optimize thread exiting.
2018-04-16 01:43:12 708 [Note] InnoDB: Starting shutdown...
2018-04-16 01:43:13 708 [Note] InnoDB: Shutdown completed; log sequence number 1949980
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'BLACKHOLE'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'ARCHIVE'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'MRG_MYISAM'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'MyISAM'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'MEMORY'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'CSV'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'sha256_password'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'mysql_old_password'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'mysql_native_password'
2018-04-16 01:43:13 708 [Note] Shutting down plugin 'binlog'
2018-04-16 01:43:13 708 [Note] /usr/local/libexec/mysqld: Shutdown complete

180416 01:43:13 mysqld_safe mysqld from pid file /var/db/mysql/root602778.kms4.cc.pid ended
180416 01:43:13 mysqld_safe Logging to '/var/db/mysql/root602778.kms4.cc.err'.
180416 01:43:13 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2018-04-16 01:43:14 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-16 01:43:14 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.39) starting as process 963 ...
2018-04-16 01:43:14 963 [Note] Plugin 'FEDERATED' is disabled.
2018-04-16 01:43:14 963 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-16 01:43:14 963 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-16 01:43:14 963 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-16 01:43:14 963 [Note] InnoDB: Memory barrier is not used
2018-04-16 01:43:14 963 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-04-16 01:43:14 963 [Note] InnoDB: Using CPU crc32 instructions
2018-04-16 01:43:14 963 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-16 01:43:14 963 [Note] InnoDB: Completed initialization of buffer pool
2018-04-16 01:43:14 963 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-16 01:43:15 963 [Note] InnoDB: 128 rollback segment(s) are active.
2018-04-16 01:43:15 963 [Note] InnoDB: Waiting for purge to start
2018-04-16 01:43:15 963 [Note] InnoDB: 5.6.39 started; log sequence number 1949980
2018-04-16 01:43:15 963 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2018-04-16 01:43:15 963 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2018-04-16 01:43:15 963 [Note] Server hostname (bind-address): '*'; port: 3306
2018-04-16 01:43:15 963 [Note] IPv6 is available.
2018-04-16 01:43:15 963 [Note] - '::' resolves to '::';
2018-04-16 01:43:15 963 [Note] Server socket created on IP: '::'.
2018-04-16 01:43:15 963 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50092, now running 50639. Please use mysql_upgrade to fix this error.
2018-04-16 01:43:15 963 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2018-04-16 01:43:15 963 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.39' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2018-04-16 01:52:56 963 [Warning] Host name 'social10.cayopesystems.com' could not be resolved: hostname nor servname provided, or not known
2018-04-16 02:22:28 963 [Note] /usr/local/libexec/mysqld: Normal shutdown

2018-04-16 02:22:28 963 [Note] Giving 45 client threads a chance to die gracefully
2018-04-16 02:22:28 963 [Note] Shutting down slave threads
2018-04-16 02:22:30 963 [Note] Forcefully disconnecting 27 remaining clients
2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 13 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 14 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 15 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 16 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 17 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 18 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 19 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 20 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 21 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 22 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 23 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 24 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 25 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 26 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 27 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 28 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 29 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 30 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 31 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 32 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 33 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 34 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 35 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 36 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 37 user: 'core'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 47 user: 'root'

2018-04-16 02:22:30 963 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 48 user: 'root'

2018-04-16 02:22:30 963 [Note] Binlog end
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'partition'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_METRICS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_CMP'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'INNODB_TRX'
2018-04-16 02:22:30 963 [Note] Shutting down plugin 'InnoDB'
2018-04-16 02:22:30 963 [Note] InnoDB: FTS optimize thread exiting.
2018-04-16 02:22:30 963 [Note] InnoDB: Starting shutdown...
2018-04-16 02:22:32 963 [Note] InnoDB: Shutdown completed; log sequence number 1949990
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'BLACKHOLE'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'ARCHIVE'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'MRG_MYISAM'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'MyISAM'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'MEMORY'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'CSV'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'sha256_password'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'mysql_old_password'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'mysql_native_password'
2018-04-16 02:22:32 963 [Note] Shutting down plugin 'binlog'
2018-04-16 02:22:32 963 [Note] /usr/local/libexec/mysqld: Shutdown complete

180416 02:22:32 mysqld_safe mysqld from pid file /var/db/mysql/root602778.kms4.cc.pid ended
180416 02:23:14 mysqld_safe Logging to '/var/db/mysql/root602778.kms4.cc.err'.
180416 02:23:14 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2018-04-16 02:23:15 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-16 02:23:15 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.39) starting as process 710 ...
2018-04-16 02:23:15 710 [Note] Plugin 'FEDERATED' is disabled.
2018-04-16 02:23:15 710 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-16 02:23:15 710 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-16 02:23:15 710 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-16 02:23:15 710 [Note] InnoDB: Memory barrier is not used
2018-04-16 02:23:15 710 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-04-16 02:23:15 710 [Note] InnoDB: Using CPU crc32 instructions
2018-04-16 02:23:15 710 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-16 02:23:15 710 [Note] InnoDB: Completed initialization of buffer pool
2018-04-16 02:23:16 710 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-16 02:23:16 710 [Note] InnoDB: 128 rollback segment(s) are active.
2018-04-16 02:23:16 710 [Note] InnoDB: Waiting for purge to start
2018-04-16 02:23:16 710 [Note] InnoDB: 5.6.39 started; log sequence number 1949990
2018-04-16 02:23:16 710 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2018-04-16 02:23:16 710 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2018-04-16 02:23:16 710 [Note] Server hostname (bind-address): '*'; port: 3306
2018-04-16 02:23:16 710 [Note] IPv6 is available.
2018-04-16 02:23:16 710 [Note] - '::' resolves to '::';
2018-04-16 02:23:16 710 [Note] Server socket created on IP: '::'.
2018-04-16 02:23:16 710 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50092, now running 50639. Please use mysql_upgrade to fix this error.
2018-04-16 02:23:16 710 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2018-04-16 02:23:16 710 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.39' socket: '/tmp/mysql.sock' port: 3306 Source distribution
180416 03:16:58 mysqld_safe mysqld restarted
2018-04-16 03:17:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-16 03:17:02 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.39) starting as process 1272 ...
2018-04-16 03:17:03 1272 [Note] Plugin 'FEDERATED' is disabled.
2018-04-16 03:17:03 1272 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-16 03:17:03 1272 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-16 03:17:03 1272 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-16 03:17:03 1272 [Note] InnoDB: Memory barrier is not used
2018-04-16 03:17:03 1272 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-04-16 03:17:03 1272 [Note] InnoDB: Using CPU crc32 instructions
2018-04-16 03:17:03 1272 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-16 03:17:03 1272 [Note] InnoDB: Completed initialization of buffer pool
2018-04-16 03:17:04 1272 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-16 03:17:04 1272 [Note] InnoDB: The log sequence numbers 1949990 and 1949990 in ibdata files do not match the log sequence number 1950000 in the ib_logfiles!
2018-04-16 03:17:04 1272 [Note] InnoDB: Database was not shutdown normally!
2018-04-16 03:17:04 1272 [Note] InnoDB: Starting crash recovery.
2018-04-16 03:17:04 1272 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-16 03:17:04 1272 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace account/server_settings which uses space ID: 5 at filepath: ./account/server_settings.ibd
2018-04-16 03:17:04 803616000 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./account/server_settings.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
180416 03:17:04 mysqld_safe mysqld from pid file /var/db/mysql/root602778.kms4.cc.pid ended
180416 03:36:52 mysqld_safe Logging to '/var/db/mysql/root602778.kms4.cc.err'.
180416 03:36:53 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2018-04-16 03:36:55 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-16 03:36:55 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.39) starting as process 714 ...
2018-04-16 03:36:55 714 [Note] Plugin 'FEDERATED' is disabled.
2018-04-16 03:36:55 714 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-16 03:36:55 714 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-16 03:36:55 714 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-16 03:36:55 714 [Note] InnoDB: Memory barrier is not used
2018-04-16 03:36:55 714 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-04-16 03:36:55 714 [Note] InnoDB: Using CPU crc32 instructions
2018-04-16 03:36:55 714 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-16 03:36:55 714 [Note] InnoDB: Completed initialization of buffer pool
2018-04-16 03:36:55 714 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-16 03:36:55 714 [Note] InnoDB: The log sequence numbers 1949990 and 1949990 in ibdata files do not match the log sequence number 1950000 in the ib_logfiles!
2018-04-16 03:36:55 714 [Note] InnoDB: Database was not shutdown normally!
2018-04-16 03:36:55 714 [Note] InnoDB: Starting crash recovery.
2018-04-16 03:36:55 714 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-16 03:36:56 714 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace account/server_settings which uses space ID: 5 at filepath: ./account/server_settings.ibd
2018-04-16 03:36:56 803616000 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./account/server_settings.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
180416 03:36:56 mysqld_safe mysqld from pid file /var/db/mysql/root602778.kms4.cc.pid ended
180416 03:41:31 mysqld_safe Logging to '/var/db/mysql/root602778.kms4.cc.err'.
180416 03:41:31 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2018-04-16 03:41:32 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-16 03:41:32 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.39) starting as process 700 ...
2018-04-16 03:41:33 700 [Note] Plugin 'FEDERATED' is disabled.
2018-04-16 03:41:33 700 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-16 03:41:33 700 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-16 03:41:33 700 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-16 03:41:33 700 [Note] InnoDB: Memory barrier is not used
2018-04-16 03:41:33 700 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-04-16 03:41:33 700 [Note] InnoDB: Using CPU crc32 instructions
2018-04-16 03:41:33 700 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-16 03:41:33 700 [Note] InnoDB: Completed initialization of buffer pool
2018-04-16 03:41:33 700 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-16 03:41:33 700 [Note] InnoDB: The log sequence numbers 1949990 and 1949990 in ibdata files do not match the log sequence number 1950000 in the ib_logfiles!
2018-04-16 03:41:33 700 [Note] InnoDB: Database was not shutdown normally!
2018-04-16 03:41:33 700 [Note] InnoDB: Starting crash recovery.
2018-04-16 03:41:33 700 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-16 03:41:33 700 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace account/server_settings which uses space ID: 5 at filepath: ./account/server_settings.ibd
2018-04-16 03:41:33 803616000 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./account/server_settings.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
180416 03:41:33 mysqld_safe mysqld from pid file /var/db/mysql/root602778.kms4.cc.pid ended
180416 03:43:31 mysqld_safe Logging to '/var/db/mysql/root602778.kms4.cc.err'.
180416 03:43:31 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2018-04-16 03:43:31 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-16 03:43:31 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.39) starting as process 949 ...
2018-04-16 03:43:31 949 [Note] Plugin 'FEDERATED' is disabled.
2018-04-16 03:43:31 949 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-16 03:43:31 949 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-16 03:43:31 949 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-16 03:43:31 949 [Note] InnoDB: Memory barrier is not used
2018-04-16 03:43:31 949 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-04-16 03:43:31 949 [Note] InnoDB: Using CPU crc32 instructions
2018-04-16 03:43:31 949 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-16 03:43:31 949 [Note] InnoDB: Completed initialization of buffer pool
2018-04-16 03:43:32 949 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-16 03:43:32 949 [Note] InnoDB: The log sequence numbers 1949990 and 1949990 in ibdata files do not match the log sequence number 1950000 in the ib_logfiles!
2018-04-16 03:43:32 949 [Note] InnoDB: Database was not shutdown normally!
2018-04-16 03:43:32 949 [Note] InnoDB: Starting crash recovery.
2018-04-16 03:43:32 949 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-16 03:43:32 949 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace account/server_settings which uses space ID: 5 at filepath: ./account/server_settings.ibd
2018-04-16 03:43:32 803616000 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./account/server_settings.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
180416 03:43:32 mysqld_safe mysqld from pid file /var/db/mysql/root602778.kms4.cc.pid ended

Beiträge von CLIPPER

Summer 2018

Vorstellungsdesign, Patcher + Serverlogo

quest_functions, fehler beim Compilen

Quest Fehler

Quest Fehler

Quest Fehler

Quest Fehler

Quest Fehler

Erste Farmmap

MYSQL startet nicht

MYSQL startet nicht

MYSQL startet nicht

MYSQL startet nicht

MYSQL startet nicht

MYSQL startet nicht

MYSQL startet nicht