Hauptmenü

installation problem of KIX2017 on Ubuntu 14.04

Begonnen von Nilufar, 18.07.2017 07:55:25

⏪ vorheriges - nächstes ⏩

Nilufar

Hi kix team! I just installed kix2017 and followed the given guide [/size]https://www.kixdesk.com/en/downloads/installationguides/debian-ubuntu.html[/font][/size] but i encountered the following error in the end:

Setting up kix (17.1.0-0) ...
installing framework
stopping MySQL server
mysql stop/waiting
increasing MySQL max_allowed_packet size
stopping MySQL server
stop: Unknown instance:
dpkg: error processing package kix (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up apache2-mpm-prefork (2.4.7-1ubuntu4.16) ...
Processing triggers for libc-bin (2.19-0ubuntu6) ...
Errors were encountered while processing:
kix
E: Sub-process /usr/bin/dpkg returned an error code (1)


Nilufar

#1
I also tried start mysql deamon by service mysql start and run apt-get install kix kix-mysql  again and this time it was successfull but when i want to check database there's no kix17 database created and get error in browser, though the installation was successfull

root@kixdesk:~# apt-get install kix-mysql kix
Reading package lists... Done
Building dependency tree
Reading state information... Done
kix is already the newest version.
kix-mysql is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 226 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up kix (17.1.0-0) ...
installing framework
preparing cronjobs
rebuilding config
deleting caches
activating cronjobs
restarting daemon
configuring apache webserver
Enabling site kix.
To activate the new configuration, you need to run:
  service apache2 reload
Module perl already enabled
Enabling module headers.
To activate the new configuration, you need to run:
  service apache2 restart
Considering dependency filter for deflate:
Module filter already enabled
Module deflate already enabled
Module mpm_event disabled.
To activate the new configuration, you need to run:
  service apache2 restart
Considering conflict mpm_event for mpm_prefork:
Considering conflict mpm_worker for mpm_prefork:
Enabling module mpm_prefork.
To activate the new configuration, you need to run:
  service apache2 restart
* Restarting web server apache2                                                                                                                                                                                                      [ OK ]
cleaning up


******************************************************************************
KIX has been successfully installed.
******************************************************************************

Error in browser:

Internal Server ErrorThe server encountered an internal error or misconfiguration and was unable to complete your request.[/size]
Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error.[/size]
More information about this error may be available in the server error log.[/size]Apache/2.4.7 (Ubuntu) Server at 10.10.10.133 Port 80

Nilufar

log files in /var/log/apache2/error_log

root@kixdesk:~# tail -f /var/log/apache2/error.log
   Module: Kernel::System::ObjectManager::_ObjectBuild Line: 239
   Module: Kernel::System::ObjectManager::Get Line: 182
   Module: Kernel::System::Web::InterfaceAgent::Run Line: 166
   Module: ModPerl::ROOT::ModPerl::Registry::opt_kix_bin_cgi_2dbin_index_2epl::handler Line: 31
   Module: (eval) (v1.99) Line: 206
   Module: ModPerl::RegistryCooker::run (v1.99) Line: 206
   Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 172
   Module: ModPerl::Registry::handler (v1.99) Line: 31


[Tue Jul 18 11:10:28.871551 2017] [:error] [pid 10064] The constructor of Kernel::System::DB returned undef. at /opt/kix/Kernel/System/ObjectManager.pm line 539.\n\tKernel::System::ObjectManager::_DieWithError('Kernel::System::ObjectManager=HASH(0xb7eef6f4)', 'Error', 'The constructor of Kernel::System::DB returned undef.') called at /opt/kix/Kernel/System/ObjectManager.pm line 239\n\tKernel::System::ObjectManager::_ObjectBuild('Kernel::System::ObjectManager=HASH(0xb7eef6f4)', 'Package', 'Kernel::System::DB') called at /opt/kix/Kernel/System/ObjectManager.pm line 182\n\tKernel::System::ObjectManager::Get('Kernel::System::ObjectManager=HASH(0xb7eef6f4)', 'Kernel::System::DB') called at /opt/kix/Kernel/System/Web/InterfaceAgent.pm line 166\n\tKernel::System::Web::InterfaceAgent::Run('Kernel::System::Web::InterfaceAgent=HASH(0xb8a0e040)') called at /opt/kix/bin/cgi-bin/index.pl line 31\n\tModPerl::ROOT::ModPerl::Registry::opt_kix_bin_cgi_2dbin_index_2epl::handler('Apache2::RequestRec=SCALAR(0xb830b17c)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 206\n\teval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 206\n\tModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb830b528)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 172\n\tModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb830b528)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31\n\tModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xb830b17c)') called at -e line 0\n\teval {...} called at -e line 0\n


Nilufar

Same error i get with postgresql, though i didn't get any errors while installation process and i cheked the log files of apache:



[Tue Jul 18 11:46:57.402893 2017] [:error] [pid 13696] The constructor of Kernel::System::DB returned undef. at /opt/kix/Kernel/System/ObjectManager.pm line 539.\n\tKernel::System::ObjectManager::_DieWithError('Kernel::System::ObjectManager=HASH(0xb88135b4)', 'Error', 'The constructor of Kernel::System::DB returned undef.') called at /opt/kix/Kernel/System/ObjectManager.pm line 239\n\tKernel::System::ObjectManager::_ObjectBuild('Kernel::System::ObjectManager=HASH(0xb88135b4)', 'Package', 'Kernel::System::DB') called at /opt/kix/Kernel/System/ObjectManager.pm line 182\n\tKernel::System::ObjectManager::Get('Kernel::System::ObjectManager=HASH(0xb88135b4)', 'Kernel::System::DB') called at /opt/kix/Kernel/System/Web/InterfaceAgent.pm line 166\n\tKernel::System::Web::InterfaceAgent::Run('Kernel::System::Web::InterfaceAgent=HASH(0xb8815ccc)') called at /opt/kix/bin/cgi-bin/index.pl line 31\n\tModPerl::ROOT::ModPerl::Registry::opt_kix_bin_cgi_2dbin_index_2epl::handler('Apache2::RequestRec=SCALAR(0xb80820d8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 206\n\teval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 206\n\tModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb881e55c)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 172\n\tModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb881e55c)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31\n\tModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xb80820d8)') called at -e line 0\n\teval {...} called at -e line 0\n

Richard Leis

Hello Nilufar,

was the MySQL Server already installed or did you install it with KIX?
Did you export the necessary variables before installation?
export KIXMYSQL_USER=<MySQL admin user>
export KIXMYSQL_PASSWORD=<MySQL admin password>


Can you provide me the installation Logs, too?
These are located in /opt/kix17/var/log/ .

Best regards

Richard