Project

General

Profile

Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise

Added by xek on 3 months ago

I have been a FreePBX user for years. I am really wanting to try out WAZO.

I installed using wazo-latest-amd64.iso today, and I cannot access the WEB UI

I found this thread: https://projects.wazo.community/boards/1/topics/9546

So I installed picking language French, and mirror France, however this did not resolve anything.

What logs or commands should I be looking at? I appreciate any help, thank you.

Also, this is not a certificate error, it is a "Unable to connect" error. Almost as if the web service is not even running.

Also, I see that I can install from install script instead of iso: http://documentation.wazo.community/en/stable/installation/installsystem.html

I will give that a try today.


Replies (13)

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by xek on 3 months ago

Just tried the install script using latest debian stretch netboot:
http://ftp.nl.debian.org/debian/dists/stretch/main/installer-amd64/current/images/netboot/

No Luck running the installer script either, seems packages that the installer script used to use are no longer available on latest debian stretch.
I guess this means that the installer script is not kept up to date, maybe the ISO would be the better install method, but as I said earlier, no webui following fresh install when using the ISO.

Any help appreciated, let me know if there is any further information required. Thank you.

apt-get install software-properties-common

wget http://mirror.wazo.community/fai/xivo-migration/wazo_install.sh

chmod +x wazo_install.sh

./wazo_install.sh

Add mirrors informations
--2018-07-15 14:30:12--  http://mirror.wazo.community/wazo_current.key
Resolving mirror.wazo.community (mirror.wazo.community)... 52.3.59.59
Connecting to mirror.wazo.community (mirror.wazo.community)|52.3.59.59|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1722 (1.7K) [application/octet-stream]
Saving to: ‘STDOUT’

-                                                          100%[========================================================================================================================================>]   1.68K  --.-KB/s    in 0s      

2018-07-15 14:30:12 (147 MB/s) - written to stdout [1722/1722]

OK
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Get:2 http://mirror.wazo.community/debian phoenix-stretch InRelease [3,779 B]                                                      
Ign:3 http://ftp.us.debian.org/debian stretch InRelease                                                                            
Hit:4 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:5 http://ftp.us.debian.org/debian stretch Release                    
Get:6 http://mirror.wazo.community/debian phoenix-stretch/main amd64 Packages [58.1 kB]
Fetched 61.9 kB in 0s (103 kB/s)                             
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  xivo-dist
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,776 B of archives.
After this operation, 24.6 kB of additional disk space will be used.
Get:1 http://mirror.wazo.community/debian phoenix-stretch/main amd64 xivo-dist all 18.03~20180219.154539.72b3be5.deb9 [3,776 B]
Fetched 3,776 B in 0s (20.7 kB/s)    
Selecting previously unselected package xivo-dist.
(Reading database ... 27285 files and directories currently installed.)
Preparing to unpack .../xivo-dist_18.03~20180219.154539.72b3be5.deb9_all.deb ...
Unpacking xivo-dist (18.03~20180219.154539.72b3be5.deb9) ...
Setting up xivo-dist (18.03~20180219.154539.72b3be5.deb9) ...
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.us.debian.org/debian stretch InRelease                  
Hit:3 http://mirror.wazo.community/debian phoenix-stretch InRelease      
Hit:4 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:5 http://ftp.us.debian.org/debian stretch Release
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  postfix-sqlite ssl-cert
Suggested packages:
  procmail postfix-mysql postfix-pgsql postfix-ldap postfix-pcre postfix-lmdb sasl2-bin dovecot-common resolvconf postfix-cdb mail-reader ufw postfix-doc openssl-blacklist
The following NEW packages will be installed:
  postfix postfix-sqlite ssl-cert
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,776 kB of archives.
After this operation, 4,442 kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian stretch/main amd64 ssl-cert all 1.0.39 [20.8 kB]
Get:2 http://ftp.us.debian.org/debian stretch/main amd64 postfix-sqlite amd64 3.1.8-0+deb9u1 [318 kB]
Get:3 http://ftp.us.debian.org/debian stretch/main amd64 postfix amd64 3.1.8-0+deb9u1 [1,437 kB]
Fetched 1,776 kB in 4s (431 kB/s)    
Preconfiguring packages ...
Selecting previously unselected package ssl-cert.
(Reading database ... 27297 files and directories currently installed.)
Preparing to unpack .../ssl-cert_1.0.39_all.deb ...
Unpacking ssl-cert (1.0.39) ...
Selecting previously unselected package postfix-sqlite.
Preparing to unpack .../postfix-sqlite_3.1.8-0+deb9u1_amd64.deb ...
Unpacking postfix-sqlite (3.1.8-0+deb9u1) ...
Selecting previously unselected package postfix.
Preparing to unpack .../postfix_3.1.8-0+deb9u1_amd64.deb ...
Unpacking postfix (3.1.8-0+deb9u1) ...
Setting up ssl-cert (1.0.39) ...
Processing triggers for systemd (232-25+deb9u4) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up postfix-sqlite (3.1.8-0+deb9u1) ...
grep: /etc/postfix/dynamicmaps.cf: No such file or directory
Adding sqlite map entry to /etc/postfix/dynamicmaps.cf
Processing triggers for rsyslog (8.24.0-1) ...
Setting up postfix (3.1.8-0+deb9u1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service → /lib/systemd/system/postfix.service.
Adding group `postfix' (GID 112) ...
Done.
Adding system user `postfix' (UID 107) ...
Adding new user `postfix' (UID 107) with group `postfix' ...
Not creating home directory `/var/spool/postfix'.
Adding group `postdrop' (GID 113) ...
Done.
setting myhostname: wazo.mydomain
setting alias maps
setting alias database
changing /etc/mailname to  xivo-clients.proformatique.com
setting myorigin
setting destinations: xivo-clients.proformatique.com, $myhostname, wazo.mydomain, localhost.mydomain, localhost
setting relayhost: 
setting mynetworks:  127.0.0.0/8
setting mailbox_size_limit:  0
setting recipient_delimiter:  +
setting inet_interfaces: all
setting inet_protocols: all
/etc/aliases does not exist, creating it.
WARNING: /etc/aliases exists, but does not have a root alias.

Postfix (main.cf) is now set up with a default configuration.  If you need to 
make changes, edit /etc/postfix/main.cf (and others) as needed.  To view 
Postfix configuration values, see postconf(1).

After modifying main.cf, be sure to run 'service postfix reload'.

Running newaliases
Processing triggers for systemd (232-25+deb9u4) ...
Processing triggers for rsyslog (8.24.0-1) ...
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package dahdi-linux-modules-4.9.0-7-amd64
E: Couldn't find any package by glob 'dahdi-linux-modules-4.9.0-7-amd64'
E: Couldn't find any package by regex 'dahdi-linux-modules-4.9.0-7-amd64'
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package dahdi-linux-modules-4.9.0-7-amd64
E: Couldn't find any package by glob 'dahdi-linux-modules-4.9.0-7-amd64'
E: Couldn't find any package by regex 'dahdi-linux-modules-4.9.0-7-amd64'
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xivo-base : Depends: wazo-auth but it is not going to be installed
             Depends: wazo-service but it is not going to be installed
             Depends: wazo-webhookd but it is not going to be installed
             Depends: xivo-confd but it is not going to be installed
             Depends: xivo-ctid-ng but it is not going to be installed
             Depends: xivo-dird but it is not going to be installed
             Depends: xivo-manage-db but it is not going to be installed
             Depends: xivo-websocketd but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xivo : Depends: xivo-base (= 14:18.03~20180212.153210.c5ff859.deb9) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
./wazo_install.sh: line 65: xivo-service: command not found

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by xek on 3 months ago

I actually ran into similar problems with FreePBX install script.

It seems to me that if the install script is not going to be kept up to date to reflect available packages in the official debian repository, that maybe WAZO/FreePBX should maintain a PPA with all packages that the installer might require.

This way the installer script should always work, long as nothing too major changes in the distro.

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by Sylvain Boily 3 months ago

Looks like a depends issues. Is it fresh installation of Debian 9 ?
On your log we see some wazo packages won't to be installed.
For the iso I'm don't know without any logs. How and where did you install the soft?

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by xek on 3 months ago

Hello and thanks for the reply.

1. Yes Fresh install for both the ISO and installer attempts.

For the install where I attempted to use Debian, and run the install script, it was a fresh install (only hours ago) and the netboot image was used: http://ftp.nl.debian.org/debian/dists/stretch/main/installer-amd64/current/images/netboot/

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.5 (stretch)
Release: 9.5
Codename: stretch

On the ISO install let me know what logs would be useful,will get them to you ASAP, the ISO was downloaded from http://mirror.wazo.community/iso/wazo-latest-amd64.iso then put on USB key, then installed to a spare Dell PC that I have. (amd64)
I know for the ISO, everything appeared to install without issue, it was just that I could not access the WEBUI to finish up the install and config.

Thanks for the reply, I appreciate it :)

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by xek on 3 months ago

Looks like the ISO install had a similar issue, I think I found the log that has the good info /var/log/installer/syslog

tail -n 50 /var/log/installer/syslog

xivo : Depends: xivo-base (= 14:18.03~20180212.153210.c5ff859.deb9) but it is not going to be installed

Jul 15 23:21:18 in-target: 25300 files and directories currently installed.)^M
Jul 15 23:21:18 in-target: Preparing to unpack .../xorg/x11-common_7.7+19_all.deb ...^M
Jul 15 23:21:18 in-target: Unpacking x11-common (1:7.7+19) ...^M
Jul 15 23:21:18 in-target: Processing triggers for systemd (232-25+deb9u4) ...^M
Jul 15 23:21:18 in-target: Setting up x11-common (1:7.7+19) ...^M
Jul 15 23:21:19 in-target: debconf: unable to initialize frontend: Passthrough^M
Jul 15 23:21:19 in-target: debconf: (Failed to open fd 3: Bad file descriptor at (eval 17) line 3.)^M
Jul 15 23:21:19 in-target: debconf: falling back to frontend: Noninteractive^M
Jul 15 23:21:19 in-target: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults^M
Jul 15 23:21:19 in-target: Running in chroot, ignoring request.^M
Jul 15 23:21:19 in-target: invoke-rc.d: policy-rc.d denied execution of start.^M
Jul 15 23:21:19 in-target: Processing triggers for systemd (232-25+deb9u4) ...^M
Jul 15 23:21:19 in-target: Reading package lists...
Jul 15 23:21:19 in-target: 
Jul 15 23:21:19 in-target: Building dependency tree...
Jul 15 23:21:19 in-target: 
Jul 15 23:21:19 in-target: Reading state information...
Jul 15 23:21:19 in-target: 
Jul 15 23:21:20 in-target: Some packages could not be installed. This may mean that you have
Jul 15 23:21:20 in-target: requested an impossible situation or if you are using the unstable
Jul 15 23:21:20 in-target: distribution that some required packages have not yet been created
Jul 15 23:21:20 in-target: or been moved out of Incoming.
Jul 15 23:21:20 in-target: The following information may help to resolve the situation:
Jul 15 23:21:20 in-target: 
Jul 15 23:21:20 in-target: The following packages have unmet dependencies:
Jul 15 23:21:20 in-target:  xivo : Depends: xivo-base (= 14:18.03~20180212.153210.c5ff859.deb9) but it is not going to be installed
Jul 15 23:21:20 in-target: E
Jul 15 23:21:20 in-target: : Unable to correct problems, you have held broken packages.
Jul 15 23:21:20 in-target: Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Jul 15 23:21:20 in-target: Ign:2 http://ftp.us.debian.org/debian stretch InRelease
Jul 15 23:21:20 in-target: Hit:3 http://ftp.us.debian.org/debian stretch-updates InRelease
Jul 15 23:21:20 in-target: Hit:4 http://ftp.us.debian.org/debian stretch Release
Jul 15 23:21:20 in-target: Reading package lists...
Jul 15 23:21:21 in-target: 
Jul 15 23:21:21 in-target: invoke-rc.d: unknown initscript, /etc/init.d/dahdi not found.
Jul 15 23:21:21 in-target: /usr/local/simple-cdd/xivo.postinst: 55: /usr/local/simple-cdd/xivo.postinst: dahdi_genconf: not found
Jul 15 23:21:21 finish-install: Finished running simple-cdd profile post-install scripts
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/15cdrom-detect
Jul 15 23:21:22 cdrom-detect: Unmounting and ejecting '/dev/sdb1'
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/20final-message
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/30hw-detect
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/50config-target-network
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/55netcfg-copy-config
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/60cleanup
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/65partman-md
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/70mtab
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/90base-installer
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/90console
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/94random-seed
Jul 15 23:21:22 finish-install: info: Running /usr/lib/finish-install.d/94save-logs

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by xek on 3 months ago

Is there a way to run the installer, so that it knows I do not care about DAHDI?

I do not have a need for Dahdi

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by François Blackburn 3 months ago

Yeah it looks like a packaging conflict with the new debian version released July 14th, 2018

https://www.debian.org/News/2018/20180714

We are working on it

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by François Blackburn 3 months ago

It should be fixed now.

An ISO install without internet would probably have worked.
But with internet or with the script, a dependency conflict occured.

When the refactor of the administration interface will be done, the dahdi module will no longer be needed (using only confbridge instead of meetme) and a part of the problem will be solved.

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by xek on 3 months ago

Thanks so much! I appreciate the reply. I figured you guys were working on it.

I am going to give it a try today soon as I have the time, also thanks for the tip on unplugging the internet! I will keep that in mind if I ever have troubles in the future.

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by Wade Weppler 2 months ago

Issue still seems to exist with the latest ISO unless I'm missing something?

Tried an install today with an ISO download today and no web interface (ie. no wazo packages installed).

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by Tyler K 2 months ago

I too am having an issue with the latest (and earlier) ISOs. No Wazo packages, no Apache. I have ran the install script on top of an 18.02 install and it appeared to work, but have yet to confirm.

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by Wade Weppler 2 months ago

Was able to run the wazo installation script after the Wazo ISO was installed. All seems to be well... Didn't investigate further, so not sure why packages aren't installing through the ISO. Tried 3 separate times and got the same results.

RE: Fresh install wazo-latest-amd64.iso cannot access webui after install, please advise - Added by Tyler K 2 months ago

Yeah, I decided to continue on the install that I ran the script on and all seems well. Haven't established lines, phones, trunks and all that jazz... but I'm logged in, it now reports 18.03, and all settings verified successfully at the end of the wizard.

Good luck, hope all works out.

    (1-13/13)