Posts by betz0r

Hi, i try to update from imscp1.5.1 to 1.5.3 and get the following error on running perl autoinstaller -d:

How can i solve this problem on Ubuntu 18.04? Thx!

Hi,

my server has latest i-mscp with php-fpm pool per site configuration.

I am tryin to get my php "kind-a" asynchronous by using php exec('bash -c "exec php index.php" > /dev/null 2>&1 &')

I am using successfully php apc cache but the cache of php-pool is obviously not shared with cache of above executed cli command. Is there any possibility to execute a php script with exec() IN the php-fpm pool from which the script is called by exec()?
An option like exec('bash -c "exec php-fpm --pool=domain.tlp index.php" > /dev/null 2>&1 &')

Thx for your help.

Hi,

Ubuntu 14.04, I-MSCP 1.2.0

since update to 1.2.0 i experience the following behaviour: Unknown vhosts but set the server's IP as A-Record in DNS will be forwarded to the first vhost on server. (one.tld.com has DNS A-Record ip 1.2.3.4 but does not exist as an vhost(customer), you are being redirected to first vhost of server 1.2.3.4 (example a-first-domain.tld).
But strangest thing is: no logentries are done about this access/error.

It may not be a bug but with the panel moved to port 8080 this occures now on my setup and i am trying to get rid of it.

Thanks!

hi thx for your answer, but actually i am not looking for help how to migrate, but i need help how to uninstall an missconfigured imscp, and i guess that IS kind of support you wanna give?

dont get me wrong, i am very glad that you are developing i-mscp and i will donate in near future if my system is all stable up and running, but in fact this is a software which cant be uninstalled after an autoinstall i am gettin a lil bit nervous...

if it is not fixable with the auto-uninstaller i would like to purge it manually:
is there a list which contains all i-mscp files to delete manuallly to purge i-mscp? (like an index..)
i tried the git repo, but its only the source and does not contain all information where i-mscp stores all its data.

known directories:
/etc/imscp
/etc/apache2/
/var/www
/var/mail

whats about the daemon?

i copied imscp from one server to another, copied /etc/imscp, /var/www/virtual, /var/mail/virtual and started autoinstaller. first it worked but the changed IP in imscp.conf was not used for the other software like roundcubemail etc, so the whole install is broken now.

first setup run was perfect but configs of addons/tools etc were NOT changed to new IP and hostname. so i tried to rerun setup, which ends suddenly like this:
[error] Modules::Domain::loadData: Domain with ID '4' has not been found or is in an inconsistent state

trying to uninstall there is a inconsistency on sub domains too:
[error] Modules::Subdomain::loadData: Subdomain with ID '6' has not been found or is in an inconsistent state

the whole panel is not reachable, also aren't the tools like pma. cli access to mysql only atm... how can this happen with just using the autoinstaller of imscp, no manual edits.

how to purge a broken imscp installation on a running system ignoring these errors? i just want to purge it, the data is save on another system...

maybe an howto how to migrate/mirror an existing imscp installation to another server WITH changing parameters like IP hostname etc should be added to the wiki. when i am done, i am willing to write one but first i need to know how to solve this.
i found a post of an official in the forum who stated "dump "imscp" and user databases, copy /etc/imscp, /var/www/virtual, /var/mail/virtual and run auto-installer script. et voila" - nope, didn't work

After flushing /var/log/imscp and executing the cmd:

Quote

root@one:/var/log# perl /var/www/imscp/engine/imscp-rqst-mngr
=======================
Processing type Plugin.
Processing 1, Monitorix, toinstall. (1 of 2: remaining 1)
Processing 2, SpamAssassin, toinstall. (2 of 2: remaining 0)

[ERROR]

Plugin::SpamAssassin::_checkSaUser: /usr/bin/id: debian-spamd: No such user
Plugin::SpamAssassin::_checkSaUser: /usr/bin/id: debian-spamd: No such user
Plugin::SpamAssassin::_updateSpamassassinRules: Mär 26 23:17:02.585 [1832]
info: config: failed to parse line, skipping, in "/etc/spamassassin/sql.cf":
auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList
Mär 26 23:17:02.585 [1832] info: config: failed to parse line, skipping, in
"/etc/spamassassin/sql.cf": user_awl_dsn DBI:mysql:spamassassin:localhost:3306
Mär 26 23:17:02.585 [1832] info: config: failed to parse line, skipping, in
"/etc/spamassassin/sql.cf": user_awl_sql_username <spamassassinUSERNAME>
Mär 26 23:17:02.586 [1832] info: config: failed to parse line, skipping, in
"/etc/spamassassin/sql.cf": user_awl_sql_password <spamassassinPASSWORD>
sa-compile: not compiling; 'spamassassin --lint' check failed!

[ERROR]

main::_process: Error while processing 2, SpamAssassin, toinstall.
main::_process: See /var/log/imscp/Plugin_mngr_SpamAssassin.log for details.

Display More

ls -la /var/log/imscp (a lil bit after the cmd the backup cron ran but the logfile has 0bytes as u see)

Quote

root@one:/var/log/imscp# ll
insgesamt 116
drwx--xr-x 2 root root 4096 Mär 27 00:19 ./
drwxr-xr-x 31 root root 12288 Mär 26 23:15 ../
-rw-r----- 1 root root 10520 Mär 27 00:19 imscp-backup-all.log
-rw-r--r-- 1 root root 0 Mär 27 00:00 imscp-backup-all-mngr.log
-rw-r----- 1 root root 4791 Mär 27 00:00 imscp-del-tmp.log
-rw-r----- 1 root root 501 Mär 27 00:00 imscp-disable-accounts.log
-rw-r--r-- 1 root root 3329 Mär 27 00:00 imscp-dsk-quota.log
-rw-r--r-- 1 root root 12288 Mär 27 00:00 imscp-httpd-logs-mngr.log
-rw-r----- 1 root root 1799 Mär 26 23:17 imscp-rqst-mngr.log
-rw-r--r-- 1 root root 4684 Mär 27 00:00 imscp-srv-traff.log
-rw-r--r-- 1 root root 6298 Mär 27 00:00 imscp-vrl-traff.log
-rw-r----- 1 root root 300 Mär 27 00:00 mail.po.log
-rw-r----- 1 root root 300 Mär 27 00:00 mail.smtp.log
-rw-r----- 1 root root 11819 Mär 27 00:20 monitorix-plugin-cronjob.log
-rw-r----- 1 root root 15043 Mär 26 23:17 Plugin_mngr_Monitorix.log
-rw-r----- 1 root root 3790 Mär 26 23:17 Plugin_mngr_SpamAssassin.log

Display More

monitorix
is installed, spamassasin still in progress. seems the plugin is not
compatible with an ubuntu configured spamassasin.
but the important
part: wordpress is still listed as "install in progress". if i click on
it, an empty popup comes up with ok and cancel:

still the actions do not take place. is the software repository outdated atm and not supported or is my installation buggy?

Hi,

after fixing my setup with help from nuxwin i am getting more troubles. I tried to install some plugins and delete some unneeded stuff like IPs, subdomains, installed software (from rep), but all those deleted/edited entries are "in progress", but nothing ever happens.
I tried to look into the logfiles all i found was a lot of empty files (cencored):

Quote

root@one:/var/log/imscp# ll
insgesamt 3664
drwxr-x--- 3 root imscp 4096 Mär 26 21:10 ./
drwxr-xr-x 30 root root 12288 Mär 26 08:27 ../
-rw-r----- 1 root root 1949 Mär 26 10:03 Certificates_mngr_dmn.log
-rw-r----- 1 root root 2019 Mär 26 10:03 Certificates_mngr_sub.log
-rw-r----- 1 root root 18966 Mär 26 10:03 Domain_mngr_domain.tld.log
-rw-r--r-- 1 root root 102665 Mär 24 17:22 ftp_traff.log
-rw-r----- 1 root root 0 Jun 16 2013 Htgroup_mngr_statistics:2.log
-rw-r----- 1 root root 731 Mär 26 10:03 Htgroup_mngr_statistics:3.log
-rw-r----- 1 root root 733 Mär 26 10:03 Htusers_mngr_domain.tld.log
-rw-r----- 1 root root 3037328 Feb 7 07:18 imscp-apache-logger.stdout
drwxr-x--- 2 vmail mail 4096 Jun 16 2013 imscp-arpl-msgr/
-rw-r----- 1 root root 73 Mär 26 00:19 imscp-backup-all.log
-rw-r----- 1 root root 0 Mär 26 00:00 imscp-backup-all-mngr.log
-rw-r----- 1 root root 73 Mär 25 10:20 imscp-backup-imscp.log
-rw-r----- 1 root root 0 Mär 23 00:00 imscp-backup-imscp-mngr.log
-rw-r--r-- 1 root root 98480 Mär 26 10:03 imscp-build.log
-rw------- 1 root root 0 Feb 7 08:45 imscp_daemon-stderr.log.1391759100
-rw------- 1 root root 0 Feb 7 08:46 imscp_daemon-stderr.log.1391759206
-rw------- 1 root root 0 Feb 12 19:54 imscp_daemon-stderr.log.1392231258
-rw------- 1 root root 0 Feb 12 19:55 imscp_daemon-stderr.log.1392231312
-rw------- 1 root root 0 Feb 12 19:55 imscp_daemon-stderr.log.1392231317
-rw------- 1 root root 0 Feb 12 20:02 imscp_daemon-stderr.log.1392231726
-rw------- 1 root root 0 Feb 24 17:12 imscp_daemon-stderr.log.1393258372
-rw------- 1 root root 0 Mär 3 07:43 imscp_daemon-stderr.log.1393828982
-rw------- 1 root root 0 Mär 3 08:00 imscp_daemon-stderr.log.1393830031
-rw------- 1 root root 0 Mär 5 08:56 imscp_daemon-stderr.log.1394006219
-rw------- 1 root root 0 Mär 6 20:21 imscp_daemon-stderr.log.1394133714
-rw------- 1 root root 0 Mär 6 20:22 imscp_daemon-stderr.log.1394133736
-rw------- 1 root root 0 Mär 6 20:22 imscp_daemon-stderr.log.1394133764
-rw------- 1 root root 0 Mär 24 17:11 imscp_daemon-stderr.log.1395677510
-rw------- 1 root root 0 Mär 24 17:13 imscp_daemon-stderr.log.1395677623
-rw------- 1 root root 0 Mär 26 15:27 imscp_daemon-stderr.log.1395844072
-rw------- 1 root root 0 Mär 26 21:10 imscp_daemon-stderr.log.1395864614
-rw------- 1 root root 0 Feb 7 08:45 imscp_daemon-stdout.log.1391759100
-rw------- 1 root root 0 Feb 7 08:46 imscp_daemon-stdout.log.1391759206
-rw------- 1 root root 0 Feb 12 19:54 imscp_daemon-stdout.log.1392231258
-rw------- 1 root root 0 Feb 12 19:55 imscp_daemon-stdout.log.1392231312
-rw------- 1 root root 0 Feb 12 19:55 imscp_daemon-stdout.log.1392231317
-rw------- 1 root root 0 Feb 12 20:02 imscp_daemon-stdout.log.1392231726
-rw------- 1 root root 0 Feb 24 17:12 imscp_daemon-stdout.log.1393258372
-rw------- 1 root root 0 Mär 3 07:43 imscp_daemon-stdout.log.1393828982
-rw------- 1 root root 0 Mär 3 08:00 imscp_daemon-stdout.log.1393830031
-rw------- 1 root root 0 Mär 5 08:56 imscp_daemon-stdout.log.1394006219
-rw------- 1 root root 0 Mär 6 20:21 imscp_daemon-stdout.log.1394133714
-rw------- 1 root root 0 Mär 6 20:22 imscp_daemon-stdout.log.1394133736
-rw------- 1 root root 0 Mär 6 20:22 imscp_daemon-stdout.log.1394133764
-rw------- 1 root root 0 Mär 24 17:11 imscp_daemon-stdout.log.1395677510
-rw------- 1 root root 0 Mär 24 17:13 imscp_daemon-stdout.log.1395677623
-rw------- 1 root root 0 Mär 26 15:27 imscp_daemon-stdout.log.1395844072
-rw------- 1 root root 0 Mär 26 21:10 imscp_daemon-stdout.log.1395864614
-rw-r----- 1 root root 73 Feb 2 00:00 imscp-del-logs.log
-rw-r----- 1 root root 4640 Mär 26 21:00 imscp-del-tmp.log
-rw-r----- 1 root root 73 Mär 26 00:00 imscp-disable-accounts.log
-rw-r----- 1 root root 73 Mär 26 00:00 imscp-dsk-quota.log
-rw-r----- 1 root root 73 Mär 26 00:00 imscp-httpd-logs-mngr.log
-rw-r----- 1 root root 1508 Feb 7 07:00 imscp-iptables-input.log
-rw-r----- 1 root root 1509 Feb 7 07:00 imscp-iptables-output.log
-rw-r----- 1 root root 501 Mär 26 10:03 imscp-local-dns-resolver.log
-rw-r----- 1 root root 1881 Mär 26 10:03 imscp-net-interfaces-mngr.log
-rw-r----- 1 root root 0 Jun 16 2013 imscp_network.log
-rw-r----- 1 root root 0 Feb 7 08:46 imscp_pkt_mngr_engine.log
-rw-r----- 1 root root 73 Mär 23 00:01 imscp-rkhunter-addon.log
-rw-r----- 1 root root 6389 Mär 26 10:03 imscp-rqst-mngr.log
-rw-r----- 1 root root 16178 Mär 26 10:03 imscp-set-engine-permissions.log
-rw-r----- 1 root root 14134 Mär 26 10:03 imscp-set-gui-permissions.log
-rw-r--r-- 1 root root 118211 Mär 26 10:03 imscp-setup.log
-rw-r----- 1 root root 4684 Mär 26 21:00 imscp-srv-traff.log
-rw-r----- 1 root root 3439 Mär 26 10:03 imscp_sw_mngr_engine
-rw-r----- 1 root root 6298 Mär 26 21:00 imscp-vrl-traff.log
-rw-r----- 1 root root 1716 Mär 26 10:03 Ips_mngr.log
-rw-r----- 1 root root 5101 Mär 26 10:03 Mail_mngr_abuse@domain.tld.log
-rw-r----- 1 root root 14831 Mär 26 10:03 Mail_mngr_bernhard.hein@domain.tld.log
-rw-r----- 1 root root 14440 Mär 26 10:03 Mail_mngr_dropbox@domain.tld.log
-rw-r----- 1 root root 0 Feb 12 20:02 Mail_mngr_haeiks@domain.tld.log
-rw-r----- 1 root root 5101 Mär 26 10:03 Mail_mngr_postmaster@domain.tld.log
-rw-r----- 1 root root 14699 Mär 26 10:03 Mail_mngr_s.b@domain.tld.log
-rw-r----- 1 root root 15232 Mär 26 10:03 Mail_mngr_s.bb@domain.tld.log
-rw-r----- 1 root root 15096 Mär 26 10:03 Mail_mngr_s@domain.tld.log
-rw-r----- 1 root root 15530 Mär 26 10:03 Mail_mngr_ss.b@domain.tld.log
-rw-r----- 1 root root 14959 Mär 26 10:03 Mail_mngr_service@domain.tld.log
-rw-r----- 1 root root 5101 Mär 26 10:03 Mail_mngr_webmaster@domain.tld.log
-rw-r----- 1 root root 816 Mär 26 21:00 mail.po.log
-rw-r----- 1 root root 816 Mär 26 21:00 mail.smtp.log
-rw-r----- 1 root root 0 Jun 16 2013 NetCard_mngr_delete.log
-rw-r----- 1 root root 0 Jun 16 2013 NetCard_mngr_toadd.log
-rw-r----- 1 root root 0 Sep 7 2013 Subdomain_mngr_base.log
-rw-r----- 1 root root 0 Sep 1 2013 Subdomain_mngr_blog.log
-rw-r----- 1 root root 10453 Mär 26 10:03 Subdomain_mngr_chris.log
-rw-r----- 1 root root 0 Sep 7 2013 Subdomain_mngr_filebase.log
-rw-r----- 1 root root 0 Sep 8 2013 Subdomain_mngr_forum.log
-rw-r----- 1 root root 0 Feb 12 19:55 Subdomain_mngr_maxpower.log
-rw-r----- 1 root root 5238 Mär 26 10:03 Subdomain_mngr_monitorix.log
-rw-r----- 1 root root 5138 Mär 26 10:03 Subdomain_mngr_munin.log
-rw-r----- 1 root root 14279 Mär 26 10:03 Subdomain_mngr_owncloud.log
-rw-r----- 1 root root 10321 Mär 26 10:03 Subdomain_mngr_sa.log
-rw-r----- 1 root root 0 Feb 12 19:55 Subdomain_mngr_seafile.log
-rw-r----- 1 root root 0 Jun 18 2013 Subdomain_mngr_test.log
-rw-r----- 1 root root 0 Sep 6 2013 Subdomain_mngr_typo3.log
-rw-r----- 1 root root 0 Feb 12 19:54 Subdomain_mngr_ultitrack.log
-rw-r----- 1 root root 2352 Mär 26 10:03 User_mngr_domain.tld.log

Display More

debug mode is enabled in imscp.conf
All the daemon logfiles are empty but the timestamps fit to my working time. There are older daemon errors too which i connect to earlier software installs/deinstall from the repository as i found "woltlab" and "wordpress" still stuck on "in progress" after i thought i deleted them back then.

in fact it seems the daemon is not working properly. without the logfiles it's very difficult to get any clue where to start digging. indeed i got none...

EDIT:
i found another hint something is wrong, the software repository version is outdated too, refreshing doesn't change anything.
Last Web software repository update 2012-06-28 10:17:11

sorry if i posted in the wrong subforum as i started writing without realizing this could be an older problem never being revealed.

Rerunning Autoinstaller -d using the right dns setting (not bind9, but external) fixed the problem. THX for the great support!

Quote from Nuxwin

Hello ;

You are using an exotic configuration so you should normally know how to manager.. Whatever, send me your teamviewer IDS.

i sent you the tv credentials.

it was working like a charm before, i don't really know what changed with the update to cause this problem. hope we can fix it

Quote from Nuxwin

Hello ;

Check your /etc/apache2/sites-availables/00_nameserver.conf file, which must contain the NameVirtualHost directives for your IPs (at bottom) such as

NameVirtualHost IP:80

i tried it, doesnt work. the server is behind a NAT device (router) and has an internal and external ip. i configured the hostname to be a subdomain of my domain pointing at my external ip address.

is it really
NameVirtualHost externalIP:80
NameVirtualHost externalIP:443

or as it was when i started editing
NameVirtualHost internalIP:80
NameVirtualHost internalIP:443

The Virtual Hosts are listening to the internal IP address as well.
I have teamviewer if u wanna have a look

as i said, all other sites are ok, just the panel. why should it be the nameserver config to solve that issue?