Forumsregeln
RUNALYZE started as one-man-project with only one user and has grown to an app with around 15.000 users of our official online version. Server requirements and complexity of the app and its configuration grow with the feature list. Please understand that our main focus is on implementing new features and serving a performant online version. Therefore, support for local installations is limited and we cannot guarantee any support.

Please always provide log files (and screenshots, activity files if it makes sense) and all other needed information: https://docs.runalyze.com/en/latest/support.html

We spend our leisure time to make RUNALYZE as good as possible and we still have tons of great ideas, but time is scarce and after a hard training we first need some fruits or a smoothie. You can support the development of RUNALYZE with every financial contribution — We highly appreciate every grant.
https://blog.runalyze.com/donate/
Friedi1970
Neuling
Beiträge: 16
Registriert: Mo 19. Dez 2016, 04:51

Update auf 4.1.2 unmöglich

Fr 25. Aug 2017, 16:24

Hallo zusammen,

ich versuche gerade verzweifelt auf v. 4.1.2 upzudaten und bin am Verzweifeln.

Wenn ich das Update aufrufe, erhalte ich folgende Meldung:
RUNALYZE Migrations


Migrating up to 20170430165002 from 20170311194530

++ migrating 20170320194525

-> CREATE TABLE IF NOT EXISTS `runalyze_notification` (
`id` INT UNSIGNED AUTO_INCREMENT NOT NULL,
`messageType` tinyint unsigned NOT NULL,
`createdAt` INT UNSIGNED NOT NULL,
`expirationAt` INT UNSIGNED DEFAULT NULL,
`data` TINYTEXT NOT NULL,
`wasRead` tinyint(1) unsigned NOT NULL DEFAULT 0,
`account_id` INT UNSIGNED NOT NULL,
INDEX IDX_F99B51889B6B5FBA (account_id),
PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE = InnoDB

-> ALTER TABLE runalyze_notification ADD CONSTRAINT FK_F99B51889B6B5FBA FOREIGN KEY (account_id) REFERENCES runalyze_account (id)
Migration 20170320194525 failed during Execution. Error An exception occurred while executing 'ALTER TABLE runalyze_notification ADD CONSTRAINT FK_F99B51889B6B5FBA FOREIGN KEY (account_id) REFERENCES runalyze_account (id)':

SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint


[Doctrine\DBAL\Exception\DriverException]
An exception occurred while executing 'ALTER TABLE runalyze_notification AD
D CONSTRAINT FK_F99B51889B6B5FBA FOREIGN KEY (account_id) REFERENCES runaly
ze_account (id)':
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint



[Doctrine\DBAL\Driver\PDOException]
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint



[PDOException]
SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint


doctrine:migrations:migrate [--write-sql] [--dry-run] [--query-time] [--allow-no-migration] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] []
Über Github habe ich dann herausgefunden, dass auf einmal die Inno-DB vorgeschrieben und nicht mehr optional ist :shock: Ich habe dann versucht, das über phpmyadmin und diesem Script zu lösen: https://github.com/Runalyze/Runalyze/bl ... ucture.sql

Leider verursacht das einen Fehler:
Fehler

Es scheint einen Fehler in Ihrer MySQL-Abfrage zu geben. Die MySQL-Fehlerausgabe, falls vorhanden, kann Ihnen auch bei der Fehleranalyse helfen.

ERROR: Unbekannte Interpunktion @ 1623
STR: //
SQL: -- phpMyAdmin SQL Dump
-- version 4.2.11
-- http://www.phpmyadmin.net
--
-- Host: localhost
-- Erstellungszeit: 08. Sep 2015 um 16:59
-- Server Version: 5.6.21
-- PHP-Version: 5.6.3

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";# MySQL lieferte ein leeres Resultat zurück (d. h. null Zeilen).


--
-- Datenbank: `runalyze`
--

-- --------------------------------------------------------

--
-- Tabellenstruktur für Tabelle `runalyze_account`
--

CREATE TABLE IF NOT EXISTS `runalyze_account` (
`id` int(10) unsigned NOT NULL,
`username` varchar(60) NOT NULL,
`name` varchar(50) NOT NULL DEFAULT '',
`mail` varchar(100) NOT NULL,
`language` varchar(5) NOT NULL DEFAULT '',
`timezone` smallint(5) unsigned NOT NULL DEFAULT '0',
`password` varchar(64) NOT NULL DEFAULT '',
`salt` char(64) NOT NULL DEFAULT '',
`registerdate` int(10) unsigned DEFAULT NULL,
`lastaction` int(10) unsigned DEFAULT NULL,
`changepw_hash` char(32) DEFAULT NULL,
`changepw_timelimit` int(10) unsigned DEFAULT NULL,
`activation_hash` char(32) DEFAULT NULL,
`deletion_hash` char(32) DEFAULT NULL,
`allow_mails` tinyint(1) unsigned NOT NULL DEFAULT '1',
`allow_support` tinyint(1) unsigned NOT NULL DEFAULT '0',
`role` tinyint(3) unsigned NOT NULL DEFAULT '1',
`gender` tinyint(1) unsigned NOT NULL DEFAULT '0',
`birthyear` int(4) unsigned DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;# MySQL lieferte ein leeres Resultat zurück (d. h. null Zeilen).


--
-- Trigger `runalyze_account`
--
DROP TRIGGER IF EXISTS `del_tr_train`;# MySQL lieferte ein leeres Resultat zurück (d. h. null Zeilen).

DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;
DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
FOR EACH ROW BEGIN
DELETE FROM runalyze_conf WHERE accountid = OLD.id;


SQL-Befehl:

DELIMITER // CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account` FOR EACH ROW BEGIN DELETE FROM runalyze_conf WHERE accountid = OLD.id;

MySQL meldet: Dokumentation
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DELIMITER //
CREATE TRIGGER `del_tr_train` AFTER DELETE ON `runalyze_account`
F' at line 1
Ich komme hier einfach nicht mehr weiter :( Weiß jemand Rat?
0 x

Lennetaler
Neuling
Beiträge: 8
Registriert: Mo 8. Jan 2018, 08:38

Re: Update auf 4.1.2 unmöglich

Di 9. Jan 2018, 13:12

Hatte das gleiche Problem und die gleichen Meldungen wie oben im ersten Beitrag.
Lag daran, dass das Update nicht sauber durchlief, wenn man es über den Browser aufrief.
Da ich bei meinem Webspace bei all-inkl. aber keinen Konsolenzugriff habe, habe ich die Verarbeitung einmalig verpackt in ein Php-Script aufrufen lassen.
0 x

Friedi1970
Neuling
Beiträge: 16
Registriert: Mo 19. Dez 2016, 04:51

Re: Update auf 4.1.2 unmöglich

Di 9. Jan 2018, 13:26

Kannst du das evtl. mal genauer beschreiben? Evtl. mit Script ...
0 x

Lennetaler
Neuling
Beiträge: 8
Registriert: Mo 8. Jan 2018, 08:38

Re: Update auf 4.1.2 unmöglich

Di 9. Jan 2018, 14:52

Code: Alles auswählen

<?php
exec("/www/htdocs/all-inkl KdNr/Pfad/runalyze/bin/console doctrine:migrations:migrate  2>&1", $out, $result);
echo "Returncode: " .$result ."<br>";
echo "Ausgabe des Scripts: " ."<br>";
echo "<pre>"; print_r($out);
?>
Das oben ist jetzt Beispielhaft für das Hosting bei all-inkl.com, den absolten Pfad musst Du entsprechend anpassen.
Das folgende mag jetzt vielleicht Quatsch sein, aber auf Basis meines gefährlichen Halbwissens war ich mir nicht sicher, ob es zB für die Laufzeiten einen Unterschied macht, ob ich die PHP-Datei im Browser aufrufe oder ob es durch den Server geschieht. Daher habe ich einfach das Script einmal als Cronjob aufrufen lassen.

Viele Grüsse

Thomas
0 x

Friedi1970
Neuling
Beiträge: 16
Registriert: Mo 19. Dez 2016, 04:51

Re: Update auf 4.1.2 unmöglich

Di 9. Jan 2018, 18:42

Vielen Dank :-)
0 x

Lennetaler
Neuling
Beiträge: 8
Registriert: Mo 8. Jan 2018, 08:38

Re: Update auf 4.1.2 unmöglich

Mi 10. Jan 2018, 16:12

Ich ruder mal ein Stück zurück, ich weiß nicht, ob es wirklich hilft, bzw. warum das Update in der Variante dann plötzlich durchlief.
Auf jeden Fall habe ich jetzt beim Update auf 4.2 fast das gleiche Problem, nur lässt es sich nicht auf diese Weise lösen.

Die Fehlermeldung:
ALTER TABLE runalyze_notification ADD CONSTRAINT FK_F99B51889B6B5FBA FOREIGN KEY (account_id) REFERENCES runalyze_account (id)
Migration 20170320194525 failed during Execution. Error An exception occurred while executing 'ALTER TABLE runalyze_notification ADD CONSTRAINT FK_F99B51889B6B5FBA FOREIGN KEY (account_id) REFERENCES runalyze_account (id)':

SQLSTATE[HY000]: General error: 1005 Can't create table 'd0160304.#sql-adf_76c6d' (errno: 150)


Was wohl bedeutet, dass es ein Problem zwischen der Referenzierung zwischen der account_id in der Tabelle runalyze_notification und der id in runalyze_account gibt.
Beide Datentypen sind auch gleich definiert, allerdings sind für beide Tabellen unterschiedliche Engines eingetragen. Da frage ich mich, ob ggf bei einer vorherigen Migration schon was schief ging, oder ob das so ok ist...
show table runalyze_notification.jpg
show table runalyze_notification.jpg (46.3 KiB) 81 mal betrachtet
show table runalyze_account.jpg
show table runalyze_account.jpg (68.96 KiB) 81 mal betrachtet
0 x

Lennetaler
Neuling
Beiträge: 8
Registriert: Mo 8. Jan 2018, 08:38

Re: Update auf 4.1.2 unmöglich

Mi 10. Jan 2018, 16:53

Eine Umstellung aller Tabellen auf InnoDB brachte mich nun ein Stückchen weiter. Die Migration der meisten Tabellen lief nun durch der Fehler
ALTER TABLE runalyze_notification ADD CONSTRAINT FK_F99B51889B6B5FBA FOREIGN KEY (account_id) REFERENCES runalyze_account (id)
[20] => Migration 20170320194525 failed during Execution. Error An exception occurred while executing 'ALTER TABLE runalyze_notification ADD CONSTRAINT FK_F99B51889B6B5FBA FOREIGN KEY (account_id) REFERENCES runalyze_account (id)':
[21] =>
[22] => SQLSTATE[HY000]: General error: 1005 Can't create table 'd0160304.#sql-adf_76c97' (errno: 150)
erschien nun nicht mehr...

Dafür hängt es noch an andere Stelle, aber häppchenweise komme ich weiter... ;)

Aktuelle Meldung:
RUNALYZE Migrations


Migrating up to 20170715090403 from 20170424080000

++ migrating 20170424090000

-> CREATE UNIQUE INDEX unique_key ON `runalyze_dataset` (`accountid`, `keyid`)
Migration 20170424090000 failed during Execution. Error An exception occurred while executing 'CREATE UNIQUE INDEX unique_key ON `runalyze_dataset` (`accountid`, `keyid`)':

SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-24' for key 'unique_key'


[Doctrine\DBAL\Exception\UniqueConstraintViolationException]
An exception occurred while executing 'CREATE UNIQUE INDEX unique_key ON `r
unalyze_dataset` (`accountid`, `keyid`)':
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-24
' for key 'unique_key'



[Doctrine\DBAL\Driver\PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-24
' for key 'unique_key'



[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-24
' for key 'unique_key'
0 x

Lennetaler
Neuling
Beiträge: 8
Registriert: Mo 8. Jan 2018, 08:38

Re: Update auf 4.1.2 unmöglich

Mi 10. Jan 2018, 17:13

Nachdem ich die doppelten Einträge entfernt habe, kommt nur folgende Meldung:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /www/htdocs/xxxxxxxx/xxxxxxxx/runalyze/vendor/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php on line 592
0 x

Benutzeravatar
mipapo
Administrator
Beiträge: 948
Registriert: Mo 29. Jul 2013, 20:26
Wohnort: Kiel
Kontaktdaten: Website Facebook Twitter

Re: Update auf 4.1.2 unmöglich

Mi 10. Jan 2018, 17:15

Lennetaler hat geschrieben:
Mi 10. Jan 2018, 17:13
Nachdem ich die doppelten Einträge entfernt habe, kommt nur folgende Meldung:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /www/htdocs/xxxxxxxx/xxxxxxxx/runalyze/vendor/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php on line 592
Sollte ja selbsterklärend sein: Zu wenig Memory/RAM, der für den PHP Prozess zur Verfügung steht
0 x
###Donate to RUNALYZE###
Erste Schritte - Höhenmeter (Korrektur & Berechnung) - Nutzerhilfe/User help - Admin docs-

Run Happy!,
Michael
P.S. Ich antworte gerne kurz und knackig ;)
Bild

Lennetaler
Neuling
Beiträge: 8
Registriert: Mo 8. Jan 2018, 08:38

Re: Update auf 4.1.2 unmöglich

Do 11. Jan 2018, 08:05

Ja, klar! Eigentlich sollte da auch stehen "...kommt nur noch folgende Meldung...". Ich habe das Wörtchen noch vergessen.... ;)
Scheint zumindest, dass die DB-Probleme damit gelöst sind. Wenn ich das Speicherproblem bei all-inkl. nicht gelöst bekomme, spiele ich das DB-Backup in eine XAMPP-Installation ein und hieve es dann auf 4.2.
Wie auf Twitter schon geschrieben gehts mir ja primär darum, Daten raus zu ziehen, die ich auf runalyze.de einspielen kann. Das Ding ist mittlerweile einfach zu komplex für simplen Webspace - und auch für mich... :D
0 x

Zurück zu „Runalyze v4.1.x“

Advertisement

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 1 Gast