Author Topic: [solved] Stuck on first boot after fresh installation 4.2  (Read 4233 times)

Shugarie

  • Zen Apprentice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
[solved] Stuck on first boot after fresh installation 4.2
« on: February 02, 2017, 02:53:51 pm »
Hello everybody,

I'm quite new here and I discovered recently Zentyal. I tried the version 5, but it missed something for me : openchange, so no "exchange service".

So I decided to test the 4.2 version. And I got a real problem with that, after using the offcials cd to install, it boots but then i'm stuck on the screen "installing core packages ... please wait" and nothing happen (already waited more than 24h).

I've already try to follow different "how to", official or no official, tried the version 4, 4.1 too, same thing.

And if I reboot my machine during this screen, it boot normally, but I can't access to the webadmin interface.

Then I tried to install in package mode, version 4, 4.1 and 4.2. Followed clearly the zentyal wiki, and then, I have a problem with zentyal-core installation. It's saying that there is no ebox daemon.

Tried all this on : VMWARE Workstation ans HYPER-V

I can't understand what's goin on ? What I am doing wrong !?
« Last Edit: February 17, 2017, 10:10:41 am by Shugarie »

Shugarie

  • Zen Apprentice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: Stuck on first boot after fresh installation 4.2
« Reply #1 on: February 02, 2017, 04:32:14 pm »
This is what I got in my /var/log/zentyal/zentyal.log

2017/02/02 14:34:55 ERROR> Service.pm:76 EBox::Service::running - No such daemon: ebox.redis at No such daemon: ebox.redis at /usr/share/perl5/EBox/Service.pm line 76
EBox::Service::running('ebox.redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 540
EBox::Config::Redis::_initRedis('EBox::Config::Redis=HASH(0x3c61ce8)') called at /usr/share/perl5/EBox/Config/Redis.pm line 62
EBox::Config::Redis::_new('EBox::Config::Redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 92
EBox::Config::Redis::instance('EBox::Config::Redis') called at /usr/share/perl5/EBox/Module/Config.pm line 47
EBox::Module::Config::_create('EBox::GlobalImpl', 'name', 'global', 'printableName', 'global') called at /usr/share/perl5/EBox/GlobalImpl.pm line 71
EBox::GlobalImpl::_new_instance('EBox::GlobalImpl') called at /usr/share/perl5/Class/Singleton.pm line 58
Class::Singleton::instance('EBox::GlobalImpl') called at /usr/share/perl5/EBox/Global.pm line 38
EBox::Global::new('EBox::Global', undef) called at /usr/share/perl5/EBox/Global.pm line 56
EBox::Global::getInstance('EBox::Global') called at /usr/share/zentyal/sudoers-friendly line 40
2017/02/02 14:45:36 ERROR> Service.pm:76 EBox::Service::running - No such daemon: ebox.redis at No such daemon: ebox.redis at /usr/share/perl5/EBox/Service.pm line 76
EBox::Service::running('ebox.redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 540
EBox::Config::Redis::_initRedis('EBox::Config::Redis=HASH(0x3070178)') called at /usr/share/perl5/EBox/Config/Redis.pm line 62
EBox::Config::Redis::_new('EBox::Config::Redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 92
EBox::Config::Redis::instance('EBox::Config::Redis') called at /usr/share/perl5/EBox/Module/Config.pm line 47
EBox::Module::Config::_create('EBox::GlobalImpl', 'name', 'global', 'printableName', 'global') called at /usr/share/perl5/EBox/GlobalImpl.pm line 71
EBox::GlobalImpl::_new_instance('EBox::GlobalImpl') called at /usr/share/perl5/Class/Singleton.pm line 58
Class::Singleton::instance('EBox::GlobalImpl') called at /usr/share/perl5/EBox/Global.pm line 38
EBox::Global::new('EBox::Global', undef) called at /usr/share/perl5/EBox/Global.pm line 56
EBox::Global::getInstance('EBox::Global') called at /usr/share/zentyal/sudoers-friendly line 40
2017/02/02 16:17:06 ERROR> Service.pm:76 EBox::Service::running - No such daemon: ebox.redis at No such daemon: ebox.redis at /usr/share/perl5/EBox/Service.pm line 76
EBox::Service::running('ebox.redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 540
EBox::Config::Redis::_initRedis('EBox::Config::Redis=HASH(0x47a6560)') called at /usr/share/perl5/EBox/Config/Redis.pm line 62
EBox::Config::Redis::_new('EBox::Config::Redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 92
EBox::Config::Redis::instance('EBox::Config::Redis') called at /usr/share/perl5/EBox/Module/Config.pm line 47
EBox::Module::Config::_create('EBox::GlobalImpl', 'name', 'global', 'printableName', 'global') called at /usr/share/perl5/EBox/GlobalImpl.pm line 71
EBox::GlobalImpl::_new_instance('EBox::GlobalImpl') called at /usr/share/perl5/Class/Singleton.pm line 58
Class::Singleton::instance('EBox::GlobalImpl') called at /usr/share/perl5/EBox/Global.pm line 38
EBox::Global::new('EBox::Global', 1) called at /usr/share/perl5/EBox/Global.pm line 56
EBox::Global::getInstance('EBox::Global', 1) called at /usr/share/zentyal/manage-logs line 24
eval {...} at /usr/share/zentyal/manage-logs line 23
2017/02/02 16:22:44 ERROR> Service.pm:76 EBox::Service::running - No such daemon: ebox.redis at No such daemon: ebox.redis at /usr/share/perl5/EBox/Service.pm line 76
EBox::Service::running('ebox.redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 540
EBox::Config::Redis::_initRedis('EBox::Config::Redis=HASH(0x2161818)') called at /usr/share/perl5/EBox/Config/Redis.pm line 62
EBox::Config::Redis::_new('EBox::Config::Redis') called at /usr/share/perl5/EBox/Config/Redis.pm line 92
EBox::Config::Redis::instance('EBox::Config::Redis') called at /usr/share/perl5/EBox/Module/Config.pm line 47
EBox::Module::Config::_create('EBox::GlobalImpl', 'name', 'global', 'printableName', 'global') called at /usr/share/perl5/EBox/GlobalImpl.pm line 71
EBox::GlobalImpl::_new_instance('EBox::GlobalImpl') called at /usr/share/perl5/Class/Singleton.pm line 58
Class::Singleton::instance('EBox::GlobalImpl') called at /usr/share/perl5/EBox/Global.pm line 38
EBox::Global::new('EBox::Global', 1) called at /usr/share/perl5/EBox/Global.pm line 56
EBox::Global::getInstance('EBox::Global', 1) called at /usr/share/perl5/EBox/Util/Init.pm line 62
EBox::Util::Init::checkModule('webadmin') called at /usr/share/perl5/EBox/Util/Init.pm line 112
EBox::Util::Init::moduleAction('webadmin', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 253
EBox::Util::Init::moduleRestart('webadmin') called at /etc/init.d/zentyal line 59
main::main at /etc/init.d/zentyal line 80

pcready.cl

  • Zen Samurai
  • ****
  • Posts: 286
  • Karma: +13/-1
  • Zentyal Installer in Chile
    • View Profile
    • PC Ready Chile SpA
Re: Stuck on first boot after fresh installation 4.2
« Reply #2 on: February 06, 2017, 08:55:58 am »
same here!  :o
Email: contacto@pcready.cl
Teléfono: (+56 32) 314 0883
Skype: pcready.cl
Web: https://www.pcready.cl

Sycoriorz

  • Zen Apprentice
  • *
  • Posts: 10
  • Karma: +1/-0
    • View Profile
Re: Stuck on first boot after fresh installation 4.2
« Reply #3 on: February 06, 2017, 02:19:31 pm »
Hello Shugarie,

i had the same problem like you. I tried to install zentyal 4.1 in vbox. The system stuck after installation reboot by zentyal core packages.
I found following solution.
Plugoff the network wire before reboot.
Zentyal tries to connect the network and abort this after 60 seconds. Then the core will install without any troubles. After that you can plug in the network wire and everything run as needed.

Regards

Shugarie

  • Zen Apprentice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: Stuck on first boot after fresh installation 4.2
« Reply #4 on: February 06, 2017, 03:48:14 pm »
Man, what can I say more than I love you <3 ?

For those who where blocked like me on this. After installation, at the end, unplug (virtually or really) the network then reboot. The machine gonna boot up normally, then plug the network again and, important, lauch an apt-get update before installing the package, if you don't do that, you gonna be stuck again.

Thank you very much Sycoriorz.

thxer

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Stuck on first boot after fresh installation 4.2
« Reply #5 on: February 10, 2017, 10:41:35 am »
Hello,

Package Zentyal-core                          4.2.3 , doesn't work.

But a script : /usr/share/zenbuntu-core/core-install do an apt-get update and install the 4.2.3 version.

So if you unplug network the init script /usr/share/zenbuntu-core/core-install cant' download zentyal-core 4.2.3 and install 4.2.2 wich work fine.

--
Note i think the problem will be solved beacause : zentyal-core_4.2.4_all.deb 10-Feb-2017 01:25 
Come to day, it's seems to be a patch.

Have a nice day.



sheshman

  • Zen Apprentice
  • *
  • Posts: 34
  • Karma: +1/-0
    • View Profile
Re: Stuck on first boot after fresh installation 4.2
« Reply #6 on: March 09, 2017, 11:39:45 am »
Hello Shugarie,

i had the same problem like you. I tried to install zentyal 4.1 in vbox. The system stuck after installation reboot by zentyal core packages.
I found following solution.
Plugoff the network wire before reboot.
Zentyal tries to connect the network and abort this after 60 seconds. Then the core will install without any troubles. After that you can plug in the network wire and everything run as needed.

Regards

I love you man, you saved my day.  :-* :-* :-* :-* :-*