TIPS sysadmin upgrade to v .20

[Hyksos]

ariban

post the result of "cat /etc/httpd/conf.d/schmoozecom.conf"

Listen 9082
<VirtualHost *:9082>
DocumentRoot /var/www/html/aastra/
</virtualhost>
Listen 9084
<VirtualHost *:9084>
DocumentRoot /var/www/html/restapps/
</virtualhost>
Listen 9085
<VirtualHost *:9085>
DocumentRoot /var/www/html/restapi/
</virtualhost>
Listen 9081
<VirtualHost *:9081>
DocumentRoot /var/www/html/recordings/
</virtualhost>
Listen 9080
<VirtualHost *:9080>
DocumentRoot /var/www/html/
</virtualhost>
Listen 9083
<VirtualHost *:9083>
DocumentRoot /tftpboot/
</virtualhost>

Use the nano program to edit the file: "nano /etc/httpd/conf.d/schmoozecom.conf"
and make it:
Listen 82
<VirtualHost *:82>
DocumentRoot /var/www/html/aastra/
</virtualhost>
Listen 84
<VirtualHost *:84>
DocumentRoot /var/www/html/restapps/
</virtualhost>
Listen 85
<VirtualHost *:85>
DocumentRoot /var/www/html/restapi/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/recordings/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /tftpboot/
</virtualhost>

 

[Hyksos]

BTW, I don't use that module so I can't even test or follow what's the goal here, but this seem weird and I don't quite get it.

Where are all those virtual hosts coming from? With different ports by default upon upgrade of the sysadmin module?
It seems convoluted to me to have apache listen on all those incremental ports "in case" people want to use them?
I guess my question is why is it defaulting to the creation of all those virtual hosts on different ports if 99% of people won't use or need those. Does each have a disable function in the GUI? and shouldn't it be disabled by default?

In post 16 of this thread freepbx.org/forum/general-help/web-gui-broken-after-module-update

The guy had a perfectly functional install according to him and ended with a bunch of virtual hosts in the new file.
He also posted a screenshot (That's a guy who knows how to post...)
In which I can see the virtual host *:80 for /var/www/html
is called admin control panel... Not true, it's for the entirety of the html folder not for the control panel.

Of course it has to be for /html else if it would be for /admin it would break everything outside of /admin for port 80... not good
My point is that it's called admin control panel in the gui.. weird and confusing. Looking at it somebody would think that it will only give access to the control panel.. and it's not true at all, it's more an overarching virtual host serving the whole /html folder, including what's covered by the other virtual hosts.
Some users could put this one to port X lets say 80. Then put the other ones to YZX, different than 80 and go away thinking his config will only allow admin control panel on port 80. That's what the GUI is saying..

Also, no disable? why force a ton of apache listen in the setup? With the accompanying warning about non existent folder and potential for port conflicts and misunderstanding? I just though this module was to help sys administration not exclusively but mainly for users who don't have the knowledge to manage those things themselves in the underlying OS.

Anyway, just trying to help but this whole thing seem circonvulated a bit. I hope it's constructive and sorry for speaking without having the actual module Take it all with a grain of salt.

wardmundy You should try to check what it does with travelin man if it uses port 83, because under this new update, port 83 becomes the "http provisioning port" virtual host. If you already have listen 83 somewhere else (I don't use travelin man) people will end up with some "couldn't not bind to socket"...
(I know phoneguy said they ware taking it into account, I'm just saying we should test because if they're checking in /etc/httpd/conf/httpd.conf, that's not the only place to look for conflicting listen..)

Does it also check for /etc/httpd/conf.d/my_very_own_.conf and does it follow all the includes in all the files to find out _ALL_ the "listen" I could have everywhere for other applications? I don't know

 

[phoneguy]

All of those ports are managed in sysadmin. Each port has a specific function. Port 80 or whatever your default port you had is for the whole /var/www/html directory.

Then their are ports for different directories that you can also disable. The different ports are for the following directories or features.

* Gives you access to the aastra xml directory only
* Gives you access to the ARI only
* Gives you access to /tftpboot directory for http provisioning for phones that you want to pull configs over http
* The other 2 ports are being announced next week at Astricon some neat cool new things.

Once again all these can be controlled and disabled from system admin.

 

[phoneguy]

Also we start at your default port usually 80 and increment 1 port for each folder. We do a netstat to make sure the port is not in use before assigning it so we dont use a port that is in use somewhere else in some custom config file or custom include from httpd.conf.

 

[It's all good]

I am experiencing this as well. I don't have a /etc/httpd/conf.d/schmoozecom.conf.

• System Admin2.11.0.19Schmoozecom.comDisabled; Pending upgrade to 2.11.0.23

 

[edisoninfo]

I am experiencing this as well. I don't have a /etc/httpd/conf.d/schmoozecom.conf.

• System Admin2.11.0.19Schmoozecom.comDisabled; Pending upgrade to 2.11.0.23

Mine is now stuck in this same place

 

[DaveDog]

Mine is now stuck in this same place

Ditto

 

[kenn10]

Same here. I waited until it appeared that the module had the latest bugs worked out but I guess that wasn't the case. I would consider uninstalling and reinstalling the module but I don't know what effect that would have on my licensed modules. I'll wait to see what Tony has to say.

Please wait while module actions are performed
2.6.1 123_centos6 ERROR: Unable to install sysadmin. The sysadmin RPM you have installed is too old. Please update the sysadmin rpm via the command line, using yum install sysadmin
Error(s) installing sysadmin:
 
    Failed to run installation scripts
 
 
Return

 System Admin 2.11.0.19 Schmoozecom.com Disabled; Pending upgrade to 2.11.0.23

 

[Hyksos]

Linux cli:
"yum list installed sysadmin"
(store for future reference and for posting here)
"yum list available sysadmin"
(store for future reference and for posting here)
"yum install sysadmin"
(store for future reference and for posting here)
"/var/lib/asterisk/bin/module_admin showupgrades | grep sysadmin"
(store for future reference and for posting here)
"/var/lib/asterisk/bin/module_admin upgrade sysadmin"
(repeat until showupgrades | grep sysadmin shows no more updates, I don't know if it jumps to latest...)
(store for future reference and for posting here)
"amportal a r"
(store for future reference and for posting here)
"service httpd restart"
(store for future reference and for posting here)
(is it just saying "OK" and maybe warning... that's ok too.)
Test the GUI, if it works go into sysadmin and check the new port management interface, you should have that.

Still no GUI on port 80?
"cat /etc/httpd/conf/httpd.conf | grep 80"
(store for future reference and for posting here)
You should have a #listen 80 or ##listen 80.
"cat /etc/httpd/conf.d/schmoozecom.conf"
should contain something like:

Listen 82
<VirtualHost *:82>
DocumentRoot /var/www/html/aastra/
</virtualhost>
Listen 84
<VirtualHost *:84>
DocumentRoot /var/www/html/restapps/
</virtualhost>
Listen 85
<VirtualHost *:85>
DocumentRoot /var/www/html/restapi/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/recordings/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /tftpboot/
</virtualhost>

if not:
"nano /etc/httpd/conf.d/schmoozecom.conf"
and edit it so it looks like that or create it and make it look like that.
"service httpd restart"
(store for future reference and for posting here)
You should get only "OK" and warnings.
Does the GUI work on port 80?
Make sure your sysadmin module now contain the port management stuff in the GUI. (meaning you have the latest)

If something is wrong, use the output obtained to post the complete before-while-after of your system.
Maybe I'm wrong, but I think the FreePBX people are not looking into that anymore. You guys just need to read the thread and the link to freepbx forum and report the state of everything related to the problem if you want help with it.

Same here, same here, same here won't cut it now.

*Not trying to sound like FreePBX _should_ look into it more, I meant that waiting is not a good solution since actions are required on your machines before it can work.

 

[sko001]

I did the uninstall and then had to reinstall to v23 through the command prompt. That seemed to give a file system error, but back into the web gui allowed me to 'apply config' anyway. It had no effect on my licensed module (extension routing), which also kept working while sysadmin was uninstalled.

I used

rpm -Uvh http://yum.schmoozecom.net/schmooze-commercial/6/i386/RPMS/sysadmin/sysadmin-2.6.1-158_centos6.noarch.rpm

Hope this helps.

 

[It's all good]

rpm -Uvh http://yum.schmoozecom.net/schmooze-commercial/6/i386/RPMS/sysadmin/sysadmin-2.6.1-158_centos6.noarch.rpm
.

Thank you. This worked for me.

 

[ariban]

now the error came back, it was working fine.
the latest system admin when i try to upgrade to .24 from .23 i get the error cant install, and it disabled it pending update.
then i uninstalled it and now i am locked out of my admin ui again and cant access any setting.
here are all the results that i posted last time, can anyone help with this??

 

[ariban]

grep 80 /etc/httpd/conf/httpd.conf
##Listen 12.34.56.78:80
#Listen 80
#Listen 9080
ServerName 192.168.1.126:80
#NameVirtualHost *:80
# (e.g. :80) if mod_ssl is being used, due to the nature of the
#<VirtualHost *:80>
WARNING: Always run Incredible PBX behind a secure hardware-based firewall.
root@pbx:~ $ ls /etc/httpd/conf.d/
perl.conf README ssl.conf TestSSLServer.jar welcome.conf
php.conf schmoozecom.conf ssl.conf.old ward174.txt wsgi.conf
WARNING: Always run Incredible PBX behind a secure hardware-based firewall.
root@pbx:~ $ cat /etc/httpd/conf.d/schmoozecom.conf

Listen 82
<VirtualHost *:82>
DocumentRoot /var/www/html/aastra/
</virtualhost>
Listen 84
<VirtualHost *:84>
DocumentRoot /var/www/html/restapps/
</virtualhost>
Listen 85
<VirtualHost *:85>
DocumentRoot /var/www/html/restapi/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/recordings/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /tftpboot/
</virtualhost>

 

[ariban]

i also get this error when running service httpd restart

service httpd restart
Stopping httpd: [FAILED]
Starting httpd: Warning: DocumentRoot [/var/www/html/aastra/] does not exist
Warning: DocumentRoot [/var/www/html/restapps/] does not exist
Warning: DocumentRoot [/var/www/html/restapi/] does not exist
[Thu Oct 17 15:50:03 2013] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
[Thu Oct 17 15:50:03 2013] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
[FAILED]
WARNING: Always run Incredible PBX behind a secure hardware-based firewall.

 

[ariban]

also teh status shows apache offline

 

[ariban]

ok this is what i did to fix it.
i edited /etc/httpd/conf.d/schmoozecom.conf to be the following
Listen 83
<VirtualHost *:83>
DocumentRoot /var/www/html/recordings/
</virtualhost>
Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/
</virtualhost>
Listen 9080
<VirtualHost *:9080>
DocumentRoot /tftpboot/
</virtualhost>

then i ran service httpd restart and it started properly and now i can access teh admin GUI.

if this ok what i did?