#1 Le 07/05/2018, à 21:54
- alinthda
[Ubuntu server 16.04 LTS & Plesk Onyx] Server Error 500 Db_Table_Excep
Bonjour a tous, j'espère vraiment que quelqu'un pourra m'aider, je suis désespéré!
J'utilise depuis quelques années un serveur dédié (kimsufi) pour mes besoins perso.
Livré à l'origine sous Ubuntu 14.04 & plesk 12.5, il a tourné des années sans autres modifs que les maj systèmes & plesk. Hier encore il tournait sous ubuntu 14.04 & Plesk onyx 17.8.11.
Mais voila, face à l'accumulation d'erreur de php j'ai effectué la migration vers ubuntu 16.04. Dans l'ensemble tout fonctionné hormis le webmail Horde.
J'ai donc suivi un tutoriel qui m'a amené à supprimer deux dossiers:
- /usr/share/psa-horde
- /usr/share/psa-pear
Et la tout se complique, erreur sql sur la main page de plesk (les autres sites web fonctionne encore), je lance donc en ssh la commande de réparation:
# plesk repair all -y
Et depuis plus rien, tous les sites sont down, plus de synchro caldav/cardav, plus de mail...etc etc
Je ne sais plus quoi faire, j'ai vraiment besoin de récupérer mes sites aussi bien personnellement que professionnellement.
Merci d'avance pour toute aide.
PJ 1: Main page plesk
PJ 2 : Rapport du script de réparation plesk
https://image.noelshack.com/fichiers/20 … -34-04.png
# plesk repair all -y
Reconfiguring the Plesk installation
Reconfiguring the Plesk installation ............................
[FAILED]
- Started bootstrapper repair procedure (fast mode). This may
take a while.
- Certain actions may be skipped if not applicable.
-
- Finishing up upgrade procedures and rerunning previously
failed upgrade actions...
- ===> Cumulative APS controller database (apsc) upgrade and
repair has been started.
- ===> Cumulative upgrade and repair of APS controller database
has been completed.
- ===> Cumulative APS controller upgrade and repair (final stage)
has been started.
- ===> Cumulative upgrade and repair of APS controller (final
stage) has been completed.
- ===> Cumulative Plesk database upgrade and repair (revertable
stage) has been started.
- ===> Preparing Plesk database upgrade (revertable stage).
- ===> Cumulative upgrade and repair of Plesk database
(revertable stage) has been completed.
- ===> Plesk database scheme upgrade has been started.
- Applying migrations from:
/opt/psa/bootstrapper/pp17.8.11-bootstrapper/migrations/
- ===> Plesk database scheme upgrade has been completed.
- ===> Cumulative Plesk upgrade and repair (final stage) has been
started.
- ===> Preparing Plesk upgrade (final stage).
- Stopping sw_engine service... done
- sed: can't read /etc/postfix/master.cf: No such file or
directory
- ===> Plesk was not upgraded completely. See installation log
for details.
-
- **** Product repair started.
-
- ===> Checking for previous installation ... found.
- Started bootstrapper repair procedure (fast mode). This may
take a while.
- Certain actions may be skipped if not applicable.
-
- Trying to start service mysql... /usr/sbin/mysqld (pid 15926)
is running...
- done
- Trying to establish test connection... connected
- done
- Trying to find psa database... version is 017008011
- Trying to backup MySQL database... done
- MySQL databases are dumped to
/var/lib/psa/dumps/mysql.preupgrade.17.8.11-17.8.11.20180507-224925.dump.gz
- Finishing up upgrade procedures and rerunning previously
failed upgrade actions...
- Checking for the group 'lock-manager'...
- Trying to add supplementary group 'lock-manager' for user
'psaadm'... already there
- ===> Cumulative APS controller database (apsc) upgrade and
repair has been started.
- Upgrade or repair for 'apsc' (stage 'prep') is not required
- Trying to backup MySQL database... done
- MySQL databases are dumped to
/var/lib/psa/dumps/mysql.preupgrade.apsc.17.8.11-17.8.11.20180507-224932.dump.gz
- ===> Cumulative upgrade and repair of APS controller database
has been completed.
- Connection to APSC DB is possible
- ===> Cumulative APS controller upgrade and repair (final stage)
has been started.
- Upgrade or repair for 'apsc' (stage 'post') is not required
- ===> Cumulative upgrade and repair of APS controller (final
stage) has been completed.
- Trying to reset database user password for
'pma_bdIK5JlbUNog@'... done
- ===> Cumulative Plesk database upgrade and repair (revertable
stage) has been started.
- Upgrade or repair for 'core' (stage 'prep') is not required
- ===> Preparing Plesk database upgrade (revertable stage).
- Trying to resolve hostname 'ns3059948.ip-91-121-179.eu' and
validate its IP address... done
-
- Trying to set psa database version to 017008011... done
- ===> Cumulative upgrade and repair of Plesk database
(revertable stage) has been completed.
- ===> Plesk database scheme upgrade has been started.
- ===> Plesk database scheme upgrade has been completed.
- done
- ===> Cumulative Plesk upgrade and repair (final stage) has been
started.
- ===> Preparing Plesk upgrade (final stage).
- After end of upgrade for 'core' (stage 'post') following
actions are registered as failed:
20171214123200-set_recipient_address_mapper_17_8_9
20171214123200-set_recipient_address_mapper_17_8_9
20171214123200-set_recipient_address_mapper_17_8_9
20171214123200-set_recipient_address_mapper_17_8_9.
- ===> Plesk was not upgraded completely. See installation log
for details.
- Trying to upgrade and repair Roundcube webmail
configuration... Upgrade or repair for 'roundcube' (stage
'files') is not required
- done
- Upgrade of Roundcube Web Based mail client configs and DB is
not required - already on '1.3.5'
- Trying to upgrade and repair Horde webmail configuration...
- ERROR while trying to act on PEAR packages - description
directory is not specified or does not exist
- Check the error reason(see log file:
/var/log/plesk/install/plesk_17.8.11_repair.log), fix and try
again
-
- ***** problem report *****
- ERROR while trying to act on PEAR packages - description
directory is not specified or does not exist
- Check the error reason(see log file:
/var/log/plesk/install/plesk_17.8.11_repair.log), fix and try
again
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database ........................ [OK]
Checking the consistency of the Plesk database ...................... [OK]
Checking system users ............................................... [OK]
Checking Linux system files ......................................... [OK]
Checking virtual hosts' file system
There are incorrect permissions on some items in the root directory
of the domain 'ns3059948.ip-91-121-179.eu' ........................ [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................. [FAILED]
- Unable to load object of type SysUser with id=1: SysUser:
unable to select: No such row in the table
There is incorrect ownership on some items in the WWW root directory
of the domain 'ns3059948.ip-91-121-179.eu' ........................ [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect ownership ................................... [FAILED]
- Unable to load object of type SysUser with id=1: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the WWW root
directory of the domain 'ns3059948.ip-91-121-179.eu' .............. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................. [FAILED]
- Unable to load object of type SysUser with id=1: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the system
directory for the domain 'ns3059948.ip-91-121-179.eu' ............. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................. [FAILED]
- Unable to load object of type SysUser with id=1: SysUser:
unable to select: No such row in the table
Unable to load object of type SysUser with id=1: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
Unable to load object of type SysUser with id=1: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
There are incorrect permissions on some items in the root directory of
the domain 'alinthda.com' ........................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There is incorrect ownership on some items in the WWW root directory
of the domain 'alinthda.com' ........................................ [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect ownership ..................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the WWW root
directory of the domain 'alinthda.com' .............................. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the system directory
for the domain 'alinthda.com' ....................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
There are incorrect permissions on some items in the root directory of
the domain 'forum.alinthda.com' ..................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There is incorrect ownership on some items in the WWW root directory
of the domain 'forum.alinthda.com' .................................. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect ownership ..................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the WWW root
directory of the domain 'forum.alinthda.com' ........................ [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the system directory
for the domain 'forum.alinthda.com' ................................. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
There are incorrect permissions on some items in the root directory of
the domain 'dev.alinthda.com' ....................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There is incorrect ownership on some items in the WWW root directory
of the domain 'dev.alinthda.com' .................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect ownership ..................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the WWW root
directory of the domain 'dev.alinthda.com' .......................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the system directory
for the domain 'dev.alinthda.com' ................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
There are incorrect permissions on some items in the root directory of
the domain 'cloud.alinthda.com' ..................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There is incorrect ownership on some items in the WWW root directory
of the domain 'cloud.alinthda.com' .................................. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect ownership ..................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the WWW root
directory of the domain 'cloud.alinthda.com' ........................ [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the system directory
for the domain 'cloud.alinthda.com' ................................. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
There are incorrect permissions on some items in the root directory of
the domain 'wiki.alinthda.com' ...................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There is incorrect ownership on some items in the WWW root directory
of the domain 'wiki.alinthda.com' ................................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect ownership ..................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the WWW root
directory of the domain 'wiki.alinthda.com' ......................... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
There are incorrect permissions on some items in the system directory
for the domain 'wiki.alinthda.com' .................................. [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................... [FAILED]
- Unable to load object of type SysUser with id=3: SysUser:
unable to select: No such row in the table
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
Unable to load object of type SysUser with id=3: SysUser: unable to select: No such row in the table
The database is inconsistent. You can try to repair it with "plesk repair db".
Checking Plesk version .............................................. [OK]
Checking for custom configuration templates ......................... [OK]
Checking the JkWorkersFile directive in the Apache configuration .... [OK]
Checking associations between domains and IP addresses .............. [OK]
Checking for corrupted reference between IP collections and
IPaddresses ......................................................... [OK]
Checking for links between APS applications and subscriptions ....... [OK]
Checking for the Zend extension declaraion in php.ini ............... [OK]
Check symbolic links for latest virtual host config files ........... [OK]
Checking for system users home directories consistency
There is missing system user's login or home directory for
sys_user_id of hosting with www_root in
/var/www/vhosts/ns3059948.ip-91-121-179.eu/httpdocs of domain
ns3059948.ip-91-121-179.eu ........................................ [WARNING]
There is missing system user's login or home directory for
sys_user_id of hosting with www_root in
/var/www/vhosts/alinthda.com/httpdocs of domain alinthda.com ..... [WARNING]
There is missing system user's login or home directory for
sys_user_id of hosting with www_root in
/var/www/vhosts/alinthda.com/forum.alinthda.com of domain
forum.alinthda.com ................................................ [WARNING]
There is missing system user's login or home directory for
sys_user_id of hosting with www_root in
/var/www/vhosts/alinthda.com/dev.alinthda.com/wordpress of domain
dev.alinthda.com .................................................. [WARNING]
There is missing system user's login or home directory for
sys_user_id of hosting with www_root in
/var/www/vhosts/alinthda.com/cloud.alinthda.com of domain
cloud.alinthda.com ................................................ [WARNING]
There is missing system user's login or home directory for
sys_user_id of hosting with www_root in
/var/www/vhosts/alinthda.com/wiki.alinthda.com of domain
wiki.alinthda.com ................................................. [WARNING]
There are some inconsistencies in the Parallels Plesk system users
Please check http://kb.plesk.com/113490 for solution and log file
/var/log/plesk/webserver_configuration_issues.log for details ..... [WARNING]
Checking for records with empty name field in the Configurations table
................................................................... [OK]
Checking for nginx ULIMIT value ..................................... [OK]
Checking for extra configurations in database not owned by any object
................................................................... [OK]
Checking the configuration of Apache modules ........................ [OK]
Repairing web server configuration
Reinstalling SSL/TLS certificates ............................... [OK]
Applying the default SSL/TLS certificate to all IP addresses .... [OK]
File not found: ns3059948.ip-91-121-179.eu.conf
File not found: alinthda.com.conf
File not found: forum.alinthda.com.conf
File not found: dev.alinthda.com.conf
File not found: cloud.alinthda.com.conf
File not found: wiki.alinthda.com.conf ............................ [ERROR]
Repairing server-wide configuration parameters for web servers .. [2018-05-07 22:52:51.105] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/httpdmng' '--reconfigure-server'] with exit code [1]
[FAILED]
- httpdmng failed: [2018-05-07 22:52:50.340] ERR [util_exec]
proc_close() failed ['/opt/psa/admin/bin/apache-config' '-t']
with exit code [1]
[2018-05-07 22:52:50.782] ERR [util_exec] proc_close() failed
['/opt/psa/admin/bin/apache-config' '-t'] with exit code [1]
[2018-05-07 22:52:50.783] ERR [panel] Apache config
(15257263690.54957600) generation failed: Template_Exception:
AH00543: apache2: bad user name admin_plesk
file:
/opt/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0
AH00543: apache2: bad user name admin_plesk
Updating the file of sharing passwords and permissions of users
according to actual information ................................. [OK]
Repairing web server configuration for all domains. This aspect
can be used with individual domains ("plesk repair web
example.com"), and on the server level ("plesk repair web") ..... [2018-05-07 22:52:56.385] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/httpdmng' '--reconfigure-all'] with exit code [1]
[FAILED]
- httpdmng failed: Execution failed.
Command: httpdmng
Arguments: Array
(
[0] => --reconfigure-domains
[1] =>
alinthda.com,cloud.alinthda.com,dev.alinthda.com,forum.alinthda.com,ns3059948.ip-91-121-179.eu,wiki.alinthda.com
)
Details: [2018-05-07 22:52:54.614] ERR [panel] No data.
[2018-05-07 22:52:54.618] ERR [panel] No data.
[2018-05-07 22:52:54.642] ERR [panel] No data.
[2018-05-07 22:52:54.655] ERR [panel] No data.
[2018-05-07 22:52:54.658] ERR [panel] No data.
[2018-05-07 22:52:54.661] ERR [panel] No data.
[2018-05-07 22:52:54.664] ERR [panel] No data.
[2018-05-07 22:52:55.255] ERR [util_exec] proc_close() failed
['/opt/psa/admin/bin/apache-config' '-t'] with exit code [1]
[2018-05-07 22:52:56.156] ERR [util_exec] proc_close() failed
['/opt/psa/admin/bin/apache-config' '-t'] with exit code [1]
[2018-05-07 22:52:56.156] ERR [panel] Apache config
(15257263730.69076300) generation failed: Template_Exception:
AH00543: apache2: bad user name admin_plesk
file:
/opt/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0
AH00543: apache2: bad user name admin_plesk
Checking the usage of PHP handlers .................................. [OK]
Repairing the mail server configuration
Reconfiguring all domains and mailboxes ......................... [2018-05-07 22:53:14.152] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/mchk'] with exit code [1]
[FAILED]
- mchk failed: ==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_handlers_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: mail_imap_restore... ok
==> Checking for: mail_spam_restore... not found, skipped
==> Checking for: mail_grey_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_dmarc_restore... ok
==> Checking for: mail_drweb_restore... ok
==> Checking for: mail_outgoing_restore... fail
==> Checking for: mail_transport_restore... ok
Errors occured in mail restore procedure
Some utilities have exited with errors:
/usr/lib/plesk-9.0/remote_mail_restore/mail_outgoing_restore
Checking the DNS configuration file ................................. [OK]
Restoring DNS server configuration
Synchronizing DNS zones with the DNS server ..................... [OK]
Checking MySQL database servers ..................................... [OK]
Repair databases on available servers ............................... [OK]
Repair database users on available servers .......................... [OK]
Error messages: 25; Warnings: 7; Errors resolved: 0
exit status 1
Modération : merci d'utiliser des images de petite taille (300x300) ou des miniatures pointant sur ces images (Des hébergeurs comme Toile Libre, TDCT'Pix le permettent).
Dernière modification par cqfd93 (Le 07/05/2018, à 22:36)
Il n'existe que deux choses infinies, l'univers et la bêtise humaine... mais pour l'univers, je n'ai pas de certitude absolue.
- Albert Einstein -
Hors ligne
#2 Le 08/05/2018, à 00:56
- krodelabestiole
Re : [Ubuntu server 16.04 LTS & Plesk Onyx] Server Error 500 Db_Table_Excep
le premier truc qui ressemble à une erreur c'est ça :
- After end of upgrade for 'core' (stage 'post') following
actions are registered as failed:
20171214123200-set_recipient_address_mapper_17_8_9
20171214123200-set_recipient_address_mapper_17_8_9
20171214123200-set_recipient_address_mapper_17_8_9
20171214123200-set_recipient_address_mapper_17_8_9.
- ===> Plesk was not upgraded completely. See installation log
for details.
mais ça donne absolument zéro détail compréhensible, tu devrais peut-être trouver des infos plus complète comme indiqué dans "l'installation log".
aucune idée d'où tu peux le trouver, j'ai jamais déployé plesk.
et un peu plus loin
ERROR while trying to act on PEAR packages - description directory is not specified or does not exist
qui correspond clairement au fait que tu as supprimé pear de manière bourrine.
je te conseille déjà d'essayer de restaurer un backup des répertoires que tu as supprimé (ne jamais supprimer, surtout en suivant un tuto au pif sans bien le comprendre, un mv ça coûte pas plus cher qu'un rm), ou alors tu récupères d'une manière ou d'une autre ces répertoires depuis une version de plesk correspondant à la tienne.
et au pire si ton plesk est effectivement pété et que tu as seulement 2 ou 3 sites à remonter ça devrait pourvoir se faire avec un lamp standard.
horde utilise encore pear !? les 3/4 des packages pear sont abandonnés...
nouveau forum ubuntu-fr on en parle là : refonte du site / nouveau design
profil - sujets récurrents - sources du site
Hors ligne
#3 Le 08/05/2018, à 09:56
- alinthda
Re : [Ubuntu server 16.04 LTS & Plesk Onyx] Server Error 500 Db_Table_Excep
merci pour ta réponse.
L'erreur qui reviens le plus dans les logs c'est l'absence de l'utilisateur "admin" dans la base de données "smb_users".
Cette erreur empêche lamp de tourner.
Je n'ai pourtant pas touché au serveur sql, à moins que le script autorepair de plesk la modifier lui même...
Il n'existe que deux choses infinies, l'univers et la bêtise humaine... mais pour l'univers, je n'ai pas de certitude absolue.
- Albert Einstein -
Hors ligne
#4 Le 08/05/2018, à 17:31
- alinthda
Re : [Ubuntu server 16.04 LTS & Plesk Onyx] Server Error 500 Db_Table_Excep
problème résolu via les sauvegardes.
Merci
Il n'existe que deux choses infinies, l'univers et la bêtise humaine... mais pour l'univers, je n'ai pas de certitude absolue.
- Albert Einstein -
Hors ligne