Beiträge von Source

Source · 14. Juli 2019

Zitat von Aze

Bitte melden Sie sich an, um diesen Link zu sehen.
Bist du nach diesem Tutorial vorgegangen?

Ja auf der vm klappt es ja nur auf dem Root nicht

Source · 12. Juli 2019

Ja er ist frisch aufgesetzt

Source · 12. Juli 2019

Könnte mir einer mal helfen? Ich reiß mir langsam die Haare aus.

Bekomme keine syserr und ist ein rootserver auf freebsd 11.0

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

Source · 6. Januar 2017

Zitat von Nero

versuch mysql mal damit zu starten:

mysqld_safe --skip-grant-tables & (Vorrausgesetzr es lässt sich starten)

Mach die gesamte mysql neu. Also die Datenbank "mysql" die ist fehlerhaft. Oder es fehlen Rechte.

probier ich gleich mal aus, an den rechten kann es schlecht liegen

Source · 6. Januar 2017

Zitat von MeragonGER

ab 23 uhr wäre ich auch erreichbar .

Sieht ab 22 Uhr bei mir schlecht aus muss arbeiten um die Uhrzeit..

Source · 6. Januar 2017

Zitat von Premiumlike

Hm komisch schreib mich doch Heute Abend mal bitte in Skype an ich gucke mir das mal an

mach ich

Source · 6. Januar 2017

die daten für den Root

Spoiler anzeigen

hat freebsd 11 64bit und mysql 5.6 alles wie im video halt gemacht..

Source · 6. Januar 2017

bei mir hängt sich der server jedes mal auf, wenn ich versuche zu connecten,, die db stürzt danach auch ab..
ich weiß nicht woran es liegen könnte ist ein root server etc.. selbst nach mehrmaliger neuinstallation

EDIT

Spoiler anzeigen

170106 10:53:03 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2017-01-06 10:53:04 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-06 10:53:04 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-06 10:53:04 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 725 ...
2017-01-06 10:53:04 725 [Note] Plugin 'FEDERATED' is disabled.
2017-01-06 10:53:04 725 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-01-06 10:53:04 725 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-06 10:53:04 725 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-06 10:53:04 725 [Note] InnoDB: Memory barrier is not used
2017-01-06 10:53:04 725 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-06 10:53:04 725 [Note] InnoDB: Using CPU crc32 instructions
2017-01-06 10:53:04 725 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-06 10:53:04 725 [Note] InnoDB: Completed initialization of buffer pool
2017-01-06 10:53:04 725 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-06 10:53:04 725 [Note] InnoDB: The log sequence numbers 2254791 and 2254791 in ibdata files do not match the log sequence number 2254801 in the ib_logfiles!
2017-01-06 10:53:04 725 [Note] InnoDB: Database was not shutdown normally!
2017-01-06 10:53:04 725 [Note] InnoDB: Starting crash recovery.
2017-01-06 10:53:04 725 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-01-06 10:53:04 725 [Note] InnoDB: Restoring possible half-written data pages
2017-01-06 10:53:04 725 [Note] InnoDB: from the doublewrite buffer...
2017-01-06 10:53:05 725 [Note] InnoDB: 128 rollback segment(s) are active.
2017-01-06 10:53:05 725 [Note] InnoDB: Waiting for purge to start
2017-01-06 10:53:05 725 [Note] InnoDB: 5.6.34 started; log sequence number 2254801
2017-01-06 10:53:05 725 [Note] Server hostname (bind-address): '*'; port: 3306
2017-01-06 10:53:05 725 [Note] IPv6 is available.
2017-01-06 10:53:05 725 [Note] - '::' resolves to '::';
2017-01-06 10:53:05 725 [Note] Server socket created on IP: '::'.
2017-01-06 10:53:05 725 [ERROR] Column count of mysql.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50537, now running 50634. Please use mysql_upgrade to fix this error.
2017-01-06 10:53:05 725 [ERROR] Column count of mysql.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50537, now running 50634. Please use mysql_upgrade to fix this error.
2017-01-06 10:53:05 725 [ERROR] Column count of mysql.events_waits_history_long is wrong. Expected 19, found 16. Created with MySQL 50537, now running 50634. Please use mysql_upgrade to fix this error.
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_thread_by_event_name: expected column 'THREAD_ID' at position 0 to have type bigint(20), found type int(11).
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Column count of mysql.file_summary_by_event_name is wrong. Expected 23, found 5. Created with MySQL 50537, now running 50634. Please use mysql_upgrade to fix this error.
2017-01-06 10:53:05 725 [ERROR] Column count of mysql.file_summary_by_instance is wrong. Expected 25, found 6. Created with MySQL 50537, now running 50634. Please use mysql_upgrade to fix this error.
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Incorrect definition of table performance_schema.mutex_instances: expected column 'LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Incorrect definition of table performance_schema.rwlock_instances: expected column 'WRITE_LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50537, now running 50634. Please use mysql_upgrade to fix this error.
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
2017-01-06 10:53:05 725 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
2017-01-06 10:53:05 725 [Note] Event Scheduler: Loaded 0 events
2017-01-06 10:53:05 725 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.34' socket: '/tmp/mysql.sock' port: 3306 Source distribution
170106 10:58:38 mysqld_safe mysqld restarted

CPU-Kerne	2
`Bitte melden Sie sich an, um dieses Bild zu sehen.` Ram	2048 MB
`Bitte melden Sie sich an, um dieses Bild zu sehen.` SSD	40 GB
`Bitte melden Sie sich an, um dieses Bild zu sehen.` Traffic	1000 GB
`Bitte melden Sie sich an, um dieses Bild zu sehen.` Anbindung	10000 MBit/s

Beiträge von Source

Fliege core dumps

Fliege core dumps

Fliege core dumps

Wie richte ich die Premiumlike Files ein

Wie richte ich die Premiumlike Files ein

Wie richte ich die Premiumlike Files ein

Wie richte ich die Premiumlike Files ein

Wie richte ich die Premiumlike Files ein