Beiträge von AceWavee

    Keine Ahnung was guild_gold sein soll, aber downloade dir doch einfach fliege/marty und zieh dir die sql´s daraus.

    Denke aber nicht das dein Problem mit dem Char erstellen daher kommt, schau am besten einfach mal in deine Syssers da wird sicherlich drin stehen weshalb du den char nicht erstellen kannst.

    SYSERR: Aug 22 20:31:36 :: Start: TABLE_POSTFIX not configured use default

    SYSERR: Aug 22 20:32:29 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Field 'bank_money' doesn't have a default value

    query: INSERT INTO player (id, account_id, name, level, st, ht, dx, iq, job, voice, dir, x, y, z, hp, mp, random_hp, random_sp, stat_point, stamina, part_base, part_main, part_hair, part_acce, gold, playtime, skill_level, quickslot) VALUES(0, 1, 'test', 1, 6, 4, 3, 3, 0, 0, 0, 957227, 255287, 0, 760, 260, 0, 0, 0, 800, 0, 0, 0, 0, 0, 0, '\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0

    SYSERR: Aug 22 20:32:29 :: __QUERY_PLAYER_CREATE: QUERY_ERROR: UPDATE player_index SET pid1=0 WHERE id=1



    das ist meine syserr und ka was da los ist >.<

    ich suche der zeit guild_gold und guild_log.sql weil bei meiner db sind die kaputt und ich weiß nicht wo ich die her bekomme hoffe das ich da etwas hilfe bekomme


    denke mal des wegen kann ich mir keinen Charakter erstellen den bei mir kommt permanent Du kannst diesen charakter nicht erstellen aber die Player Table ist gleich wie die Delete


    mit freundlichen grüßen

    AveWavee

    mysql Server gefixt


    aber homepage kann zu mysql57-server keine verbindung aufbauen keine ahnung warum.


    Server läuft nur unter Freebsd 13 und mysql57-server


    mfg AceWavee

    Guten Abend,


    hat wer eine warum die Mysql nicht startet bin grade irgendwie plan los...


    hier mal die error log


    220818 22:25:47 mysqld_safe Logging to '/var/db/mysql/localhost.err'.

    220818 22:25:47 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql

    2022-08-18 22:25:47 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

    2022-08-18 22:25:47 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 1834 ...

    2022-08-18 22:25:47 1834 [Note] Plugin 'FEDERATED' is disabled.

    /usr/local/libexec/mysqld: Unknown storage engine 'InnoDB'

    2022-08-18 22:25:47 1834 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

    2022-08-18 22:25:47 1834 [Note] InnoDB: Using atomics to ref count buffer pool pages

    2022-08-18 22:25:47 1834 [Note] InnoDB: The InnoDB memory heap is disabled

    2022-08-18 22:25:47 1834 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

    2022-08-18 22:25:47 1834 [Note] InnoDB: Memory barrier is not used

    2022-08-18 22:25:47 1834 [Note] InnoDB: Compressed tables use zlib 1.2.11

    2022-08-18 22:25:47 1834 [Note] InnoDB: Using CPU crc32 instructions

    2022-08-18 22:25:47 1834 [Note] InnoDB: Initializing buffer pool, size = 128.0M

    2022-08-18 22:25:47 1834 [Note] InnoDB: Completed initialization of buffer pool

    2022-08-18 22:25:47 1834 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!

    2022-08-18 22:25:47 1834 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB

    2022-08-18 22:25:47 1834 [Note] InnoDB: Database physically writes the file full: wait...

    2022-08-18 22:25:48 1834 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB

    2022-08-18 22:25:48 1834 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB

    2022-08-18 22:25:48 1834 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0

    2022-08-18 22:25:48 1834 [Warning] InnoDB: New log files created, LSN=45781

    2022-08-18 22:25:48 1834 [Note] InnoDB: Doublewrite buffer not found: creating new

    2022-08-18 22:25:48 1834 [Note] InnoDB: Doublewrite buffer created

    2022-08-18 22:25:48 1834 [Note] InnoDB: 128 rollback segment(s) are active.

    2022-08-18 22:25:48 1834 [Warning] InnoDB: Creating foreign key constraint system tables.

    2022-08-18 22:25:48 1834 [Note] InnoDB: Foreign key constraint system tables created

    2022-08-18 22:25:48 1834 [Note] InnoDB: Creating tablespace and datafile system tables.

    2022-08-18 22:25:48 1834 [Note] InnoDB: Tablespace and datafile system tables created.

    2022-08-18 22:25:48 1834 [Note] InnoDB: Waiting for purge to start

    2022-08-18 22:25:48 1834 [Note] InnoDB: 5.6.51 started; log sequence number 0

    /usr/local/libexec/mysqld: Error on delete of './auto.cnf' (Errcode: 2 - No such file or directory)

    2022-08-18 22:25:48 1834 [Warning] World-writable config file './auto.cnf' has been removed.


    2022-08-18 22:25:48 1834 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: f24e29b2-1f33-11ed-83a9-005056002308.

    2022-08-18 22:25:48 1834 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.

    2022-08-18 22:25:48 1834 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.

    2022-08-18 22:25:48 1834 [Note] Server hostname (bind-address): '*'; port: 3306

    2022-08-18 22:25:48 1834 [Note] IPv6 is available.

    2022-08-18 22:25:48 1834 [Note] - '::' resolves to '::';

    2022-08-18 22:25:48 1834 [Note] Server socket created on IP: '::'.

    2022-08-18 22:25:48 1834 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.

    2022-08-18 22:25:48 1834 [Warning] 'user' entry 'mysql.session@localhost' has both a password and an authentication plugin specified. The password will be ignored.

    2022-08-18 22:25:48 1834 [Warning] 'user' entry 'mysql.sys@localhost' has both a password and an authentication plugin specified. The password will be ignored.

    2022-08-18 22:25:48 1834 [Warning] 'user' entry '[email protected]' has both a password and an authentication plugin specified. The password will be ignored.

    2022-08-18 22:25:48 1834 [Warning] 'user' entry 'root@%' has both a password and an authentication plugin specified. The password will be ignored.

    2022-08-18 22:25:48 1834 [Warning] 'user' entry 'root@localhost' has both a password and an authentication plugin specified. The password will be ignored.

    2022-08-18 22:25:48 1834 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format.

    220818 22:25:48 mysqld_safe mysqld from pid file /var/db/mysql/localhost.pid ended

    220818 22:27:44 mysqld_safe Logging to '/var/db/mysql/localhost.err'.

    220818 22:27:44 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql

    2022-08-18 22:27:45 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

    2022-08-18 22:27:45 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 1973 ...

    2022-08-18 22:27:45 1973 [Note] Plugin 'FEDERATED' is disabled.

    /usr/local/libexec/mysqld: Unknown storage engine 'InnoDB'

    2022-08-18 22:27:45 1973 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

    2022-08-18 22:27:45 1973 [Note] InnoDB: Using atomics to ref count buffer pool pages

    2022-08-18 22:27:45 1973 [Note] InnoDB: The InnoDB memory heap is disabled

    2022-08-18 22:27:45 1973 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

    2022-08-18 22:27:45 1973 [Note] InnoDB: Memory barrier is not used

    2022-08-18 22:27:45 1973 [Note] InnoDB: Compressed tables use zlib 1.2.11

    2022-08-18 22:27:45 1973 [Note] InnoDB: Using CPU crc32 instructions

    2022-08-18 22:27:45 1973 [Note] InnoDB: Initializing buffer pool, size = 128.0M

    2022-08-18 22:27:45 1973 [Note] InnoDB: Completed initialization of buffer pool

    2022-08-18 22:27:45 1973 [Note] InnoDB: Highest supported file format is Barracuda.

    2022-08-18 22:27:45 1973 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463

    2022-08-18 22:27:45 1973 [Note] InnoDB: Database was not shutdown normally!

    2022-08-18 22:27:45 1973 [Note] InnoDB: Starting crash recovery.

    2022-08-18 22:27:45 1973 [Note] InnoDB: Reading tablespace information from the .ibd files...

    2022-08-18 22:27:45 1973 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 17 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace account/blocked_hwids which uses space ID: 17 at filepath: ./account/blocked_hwids.ibd

    2022-08-18 22:27:45 801784000 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/blocked_hwids.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.

    220818 22:27:45 mysqld_safe mysqld from pid file /var/db/mysql/localhost.pid ended



    ka was ich da falsch mache >.<


    lg AceWavee

    Guten Abend,


    Ich habe da mal eine frage bei mir funktioniert keinerlei Homepage meine DB Connection läuft über einen SSH-Tunnel und ich weiß halt nicht wo ran der Fehler liegt entweder ist die Homepage Weiß oder es kommt HTTP ERROR 500 ich weiß nicht mehr weiter.


    Könnte mir da eventuell jemand helfen?


    Mit freundlichen Grüßen

    AceWavee

    Alles mit Tabs und keine Leerzeichen?


    ReadSpecialDropItemFile: ReadSpecialDropItemFile : there is no item 88901 --> Das item gibt es nicht.


    Außerdem würde ich keine Sonderzeichen wie Klammern in die Gruppen Namen machen.

    88901 habe ich ja schon entfernt und die Klammern auch aber dennoch fährt er nicht mehr hoch die Cores verabschieden sich immer und immer wieder wenn ich die raus genommen habe Special item group.txt leer ist startet der server wieder

    Guten Tag,


    habe ein problem mit der Spical Item Group.txt



    Ich weiß nicht warum das so ist habe die meisten sachen schon raus genommen Sennsi truhe findet er nicht ob wohl sie vorhanden ist.


    Bitte hilft mir ;(


    Mit freundlichen Grüßen

    AceWavee

    Habe euch jetzt mal die uicharacter.py reingestellt hoffe ihr könnt mir bei diesen problem weiter helfen das es mit dem status skillen wieder geht.


    Mit freundlichen Grüßen

    AceWavee

    Guten Abend kleine frage kann mir jemand sagen wo dieses Glitzern Definiert ist.


    Wäre echt dankbar wenn mir das wer sagen kann und wie dieses Glitzern heißt.


    Bitte melden Sie sich an, um diesen Link zu sehen.


    Da ich dieses Glitzern raus nehmen muss sobald mann angegriffen wird von den Monstern Glitzert es immer so und es wird immer stärker.


    deswegen möchte ich dieses Entfernen da es auch keine Syserr gibt darüber was dies auslöst.


    Mit freundlichen Grüßen

    AceWavee