• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by TorstenS

  1. T

    Table broker with name 'ServiceNodes' not found // Failures after system crash

    I know this, but not recognized, that Debian Stretch only supports php7+. So I managed and installed a custom php5.6 handler ... for php5.3 I'll take an vserver, cause only 3 domains require this and I think it's time to upgrade for the customers ;o)
  2. T

    Question Logfile Location

    Installed today onyx 17.8.11 and now I want to debug some websites ... I looked in /var/www/vhosts/<DOMAIN>/logs ... directories are empty! Checked the httpd.conf of some domains and recognized, that the location is /var/www/vhosts/system/<DOMAIN/logs ... is this correct for this version? So...
  3. T

    Table broker with name 'ServiceNodes' not found // Failures after system crash

    @Peter Debik Yes it is! Absolute horrible ... managed to reinstall the server and about 70% of the domains are back online. For the rest I'm searching for a solution, cause they need an old PHP version :confused:
  4. T

    Table broker with name 'ServiceNodes' not found // Failures after system crash

    Decided to make a new install and recover the backup *hopefully*. Stay tuned ...
  5. T

    Table broker with name 'ServiceNodes' not found // Failures after system crash

    I've done this already about 4 times cause of foreign keys constraint failed in some db's, now I've got no more errormessages from this. __ci_last_regenerate|i:1526845388;logged_in|b:1; Checking the Plesk database using the native database server tools .. [OK] Checking the structure of the...
  6. T

    Table broker with name 'ServiceNodes' not found // Failures after system crash

    Hi there, today our server was dropped down due a power failure in the datacenter and after that the file system found some orphaned inodes - damn. After I've recognized that the files belongs to the databases I've dumped them and imported them successfully ... mysql is now running fine...
Back
Top