Apss Installer generating errors: "Installation_error" for every package!

Understand..here is output:

Code:

root@web2:~# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 1051
Server version: 10.0.23-MariaDB-0+deb8u1 (Debian)

Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> use dbispconfig;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [dbispconfig]> SELECT s.updated AS datalog_processed_until, MAX(sl.datalog_id) datalog_log_until, MAX(sd.datalog_id) datalog_new_max FROM `server` s, sys_log sl, sys_datalog sd;
+-------------------------+-------------------+-----------------+
| datalog_processed_until | datalog_log_until | datalog_new_max |
+-------------------------+-------------------+-----------------+
|                     477 |                 0 |             509 |
+-------------------------+-------------------+-----------------+
1 row in set (0.53 sec)

MariaDB [dbispconfig]>

What now?
Thx

 

Is this server part of a multiserver setup or has it been / did you modify anything like that ( delegate master to slave or vice versa ) ?
Is it a mirrored server or a mirror for something?

What does the following SQL return?

Code:

SELECT count(server_id) as number from sys_datalog WHERE datalog_id > 477 AND server_id = 1;
SELECT server_id FROM `server`;

 

No it isn't..
It is clear installed few days ago and just now builed first site on him..as I said with this tutorial:
https://www.howtoforge.com/tutorial/perfect-server-debian-8-jessie-apache-bind-dovecot-ispconfig-3/
Output is:

Code:

root@web2:~# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 1063
Server version: 10.0.23-MariaDB-0+deb8u1 (Debian)

Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> use dbispconfig;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [dbispconfig]> SELECT count(server_id) as number from sys_datalog WHERE datalog_id > 477 AND server_id = 1;
+--------+
| number |
+--------+
|     29 |
+--------+
1 row in set (0.00 sec)

MariaDB [dbispconfig]> SELECT server_id FROM `server`;
+-----------+
| server_id |
+-----------+
|         1 |
+-----------+
1 row in set (0.00 sec)

MariaDB [dbispconfig]>

Thx for helping me..

 

Hmm everything's looking alright so far, maybe it's time to try some dirty hacks.

disable the cronjob like I described on page 1
Make a backup of /usr/local/ispconfig/server/server.php and do the following modification:
you should look for

Code:

        $tmp_num_records = $tmp_rec['number'];

it's near line 168.
make it look like this

Code:

        $app->log('computed last_datalog_id: '.$conf['last_datalog_id'], LOGLEVEL_DEBUG);
        $app->log('computed server_id: '.$conf['server_id'], LOGLEVEL_DEBUG);
        $tmp_rec = $app->dbmaster->queryOneRecord("SELECT count(server_id) as number from sys_datalog WHERE datalog_id > 477 AND server_id = 1");

        $tmp_num_records = $tmp_rec['number'];

        unset($tmp_rec);

Then run /usr/local/ispconfig/server/server.sh from termina, what does it say?
After running this, please restore the file from the backup first before reenabling the cronjob. And Please only run it once!
It could break your current setup run twice ... well nothing which can't be fixed and it doesn't seem to work anyway for some reason so....

 

I do as you said..
Here is output of ssh terminal:

Code:

root@web2:~# /etc/init.d/cron restart
[ ok ] Restarting cron (via systemctl): cron.service.
root@web2:~# /etc/init.d/cron restart
[ ok ] Restarting cron (via systemctl): cron.service.
root@web2:~# ps aux | grep server.sh
root     26885  0.0  0.2  12728  2056 pts/0    S+   15:01   0:00 grep server.sh
root@web2:~# /usr/local/ispconfig/server/server.sh
18.03.2016-10:01 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
18.03.2016-10:01 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
18.03.2016-10:01 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
18.03.2016-10:02 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
18.03.2016-10:02 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
18.03.2016-10:02 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
18.03.2016-10:02 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
18.03.2016-10:02 - DEBUG - There is already a lockfile set. Waiting another 10 seconds...
^C
root@web2:~#

Btw I have 377 pages of log in last 24h:


And I still have this queue:

 

No I didn't..
I just follow tutorial instruction from link very carefully step by step:
https://www.howtoforge.com/tutorial/perfect-server-debian-8-jessie-apache-bind-dovecot-ispconfig-3/

Here is the output:

Code:

root@web2:~# ls -la /usr/local/ispconfig/server/plugins-enabled/
total 92
drwxr-s---  2 root root 4096 Feb 26 15:27 .
drwxr-s--- 13 root root 4096 Mar 18 15:04 ..
lrwxrwxrwx  1 root root   68 Feb 26 15:27 apache2_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/apache2_plugin.inc.php
lrwxrwxrwx  1 root root   71 Feb 26 15:27 apps_vhost_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/apps_vhost_plugin.inc.php
lrwxrwxrwx  1 root root   64 Feb 26 15:27 aps_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/aps_plugin.inc.php
lrwxrwxrwx  1 root root   67 Feb 26 15:27 backup_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/backup_plugin.inc.php
lrwxrwxrwx  1 root root   65 Feb 26 15:27 bind_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/bind_plugin.inc.php
lrwxrwxrwx  1 root root   73 Feb 26 15:27 cron_jailkit_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/cron_jailkit_plugin.inc.php
lrwxrwxrwx  1 root root   65 Feb 26 15:27 cron_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/cron_plugin.inc.php
-rwxr-x---  1 root root   45 Feb 26 15:27 empty.dir
lrwxrwxrwx  1 root root   69 Feb 26 15:27 firewall_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/firewall_plugin.inc.php
lrwxrwxrwx  1 root root   73 Feb 26 15:27 ftpuser_base_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/ftpuser_base_plugin.inc.php
lrwxrwxrwx  1 root root   68 Feb 26 15:27 getmail_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/getmail_plugin.inc.php
lrwxrwxrwx  1 root root   72 Feb 26 15:27 maildeliver_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/maildeliver_plugin.inc.php
lrwxrwxrwx  1 root root   68 Feb 26 15:27 mailman_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/mailman_plugin.inc.php
lrwxrwxrwx  1 root root   65 Feb 26 15:27 mail_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/mail_plugin.inc.php
lrwxrwxrwx  1 root root   75 Feb 26 15:27 mysql_clientdb_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/mysql_clientdb_plugin.inc.php
lrwxrwxrwx  1 root root   77 Feb 26 15:27 network_settings_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/network_settings_plugin.inc.php
lrwxrwxrwx  1 root root   75 Feb 26 15:27 postfix_filter_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/postfix_filter_plugin.inc.php
lrwxrwxrwx  1 root root   75 Feb 26 15:27 postfix_server_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/postfix_server_plugin.inc.php
lrwxrwxrwx  1 root root   75 Feb 26 15:27 shelluser_base_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/shelluser_base_plugin.inc.php
lrwxrwxrwx  1 root root   78 Feb 26 15:27 shelluser_jailkit_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/shelluser_jailkit_plugin.inc.php
lrwxrwxrwx  1 root root   76 Feb 26 15:27 software_update_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/software_update_plugin.inc.php
root@web2:~#

What now?
Thx for helping me!

 

If you think that I need to do a clean install from begining with some modification of that tutorial..
I will do, just tell me what to do.
Thx

 

Please repeat my steps again, it didn't do anything since there was a .lock file.
Before running the modified script, make sure cronjob is disabled, no other process is running and delete the .lock file ( all as explained on page 1)
Btw. it is sufficient to just edit the crontab, no need to restart the deamon.

 

I do it.
Here is the output:

Code:

root@web2:~# ps aux | grep server.sh
root      9026  0.0  0.2  12728  2152 pts/0    S+   21:11   0:00 grep server.sh
root@web2:~# /usr/local/ispconfig/server/server.sh
18.03.2016-16:11 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
18.03.2016-16:11 - DEBUG - computed last_datalog_id: 477
18.03.2016-16:11 - DEBUG - computed server_id: 1
root@web2:~#

 

Sure strange issue.
It seems to break at

Code:

        //** Load required base-classes
        $app->uses('modules,plugins,file,services,system');
        //** Load the modules that are in the mods-enabled folder
        $app->modules->loadModules('all');
        //** Load the plugins that are in the plugins-enabled folder
        $app->plugins->loadPlugins('all');

        $app->plugins->raiseAction('server_plugins_loaded', '');

which is highly unlikely

I haven't let you set the number

Code:

        $tmp_num_records = $tmp_rec['number'];

to the result of the above query ( 29 ) which would look like

Code:

        $tmp_num_records = 29;

this. If you're feelin lucky, you can try that.


It shouldexecute

Code:

                $app->log("Found $tmp_num_records changes, starting update process.", LOGLEVEL_DEBUG);

if the number in $tmp_num_records is above 0 - which it should :/

I don't know if there's a hidden issue with your database server, ISPConfig files ( I guess you already did the manual forced update ) or the downloaded packages from APS ( however they're used after the cron echoed how many changes it has to process ).

So yepp - it's really guessing - and my best guess would be some issue with php and mariadb, which I also don't really can imagine.
I'd do try/error/hacking code to death until I sorted that issue out ... however it takes probably too long to do this in a board...

You could try setting $tmp_num_records to 29 with the instructions as above, wait a little - I'm trying to reproduce this ( setting up ISPConfig using mariadb and trying to install APS packages ) or do a reinstall of ISPConfig - maybe only hell knows what went wrong :/

Also I doubt this is an issue but, disable the cronjob, try deleting *.zip files at /usr/local/ispconfig/interface/web/sites/aps_meta_packages
refresh APS data in ISPConfig and rerun the cron.
Edit, ok this is what you have done already...
One last chance would be .... well jut to skip the installation of the packages in the datalog, however if there has been some entries to the database already - it could potentially mess up things.

 

Hmm..
So if I correctly understood you suggest to change in original

Code:

/usr/local/ispconfig/server/server.php

file only the 168 line:

Code:

$tmp_num_records = $tmp_rec['number'];

to be as:

Code:

$tmp_num_records = 29;

??
Before that I need to disable crond line (as I before) kill server.sh proccess and make this changes then start server.sh proccess and enable crond?
If you produce this error and found some solution for me I will be very happy.
Thx again for helping me!

 

Yes, that's exactly what I meant.

 

I had no issue setting up websites / databases and installing a few APS packages on a fresh debian 8 install 100% according to the howto including mariadb :/

According to your log, there are 2 outstanding server changes, do you remember what they were about? We could try to skip them maybe.

 

I do it..
Here is the output:

Code:

root@web2:~# /usr/local/ispconfig/server/server.sh
18.03.2016-19:43 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
root@web2:~# ps -e | grep server.sh
root@web2:~# ps aux | grep server.sh
root     17287  0.0  0.1  12728  1984 pts/0    S+   00:45   0:00 grep server.sh
root@web2:~#

Nothing happend..
I do not start more than once you said..because to not mess my ispconfig.
What now?
If I try instalation from begining what part need to change or omit from installation tutotrial?

 

if you are going to start over installtion everything, you can just do as the howto suggests - feel free to leave out what you don't need
( suphp, mailman, squirrelmail for example won't hurt if you skip those except you/your clients needs it ).

If you do so, you could give it a last try, login to your datbase and switch to dbispconfig ( or use it as param as described earlier in this thread ) and just skip the two server config changes:

Code:

use dbispconfig;
UPDATE server SET updated=479;

You might need to redo the changes you wanted to make.

 

Yes I do before and again. Delete all zip files in /usr/local/ispconfig/interface/web/sites with crond disabled and refreshed apps and try to install it.
But nothing..if I want to install it on root of sites I receive error:

but if I chose some folder then after 15 minutes I still have message:

Code:

Installation_task

You said:

What do you mean exactly? What is datalog? And which step of installation is that?

 

OK..
I will try now to make a clean install as you suggested..
And try to add those two line after if not working:

Code:

use dbispconfig;
UPDATE server SET updated=479;

 

you won't need the two lines of sql code if you do a clean install, this was an attempt to make the cronjob skip the 2 system changes before your APS install tasks!

 

it would require some changes in your database to fix all the issues, it's not impossible but would require more details about your database entries, ping pong posts ect.
For example you could set the updated field to "datalog_new_max" as gathered from the SQL above - then you would need to do some cleaning up like removing the entries of the installed APS in ispconfig database, users/databases which has been created, files from web folder and probably a few other things in ispconfig database.

But if you haven't done anything special yet or it would be no big deal to just do a fresh setup, this is probably the best / easiest solution to go on and forget about this issue.
It's not very common this kind of stuff happens.