yum list sysadmin shows installed package sysadmin.noarch 2.6.1-153_centos6 and available package 2.6.1-155.
Schmoozecom.conf file is not found, at least not in that location.
I manually updated sysadmin module using your instructions, thank you :), and have version 2.11.0.20 running.
Still no luck loading the web utility.
I did from the CLI thanks to the directions provided by parnassus. Version 2.11.0.20 is installed.
What do logs (freepbx/full) say? did you managed to monitor them via a “tail -f” during your attempts (at least just to see if something has gone bad and was then reported)?
I’m not sure what they are supposed to say but I don’t see anything untoward, at least I think I don’t. I did not use ‘tail -f’.
I updated the latest 64bit version using the GUI and now dont have access to the GUI. Can you please give me detail steps as to how I can get back web access. I am new to this so please list as many details as possible. here are some details using ssh…
[root@clean ~]# yum list sysadmin
Loaded plugins: fastestmirror, kmod
Loading mirror speeds from cached hostfile
Installed Packages
sysadmin.noarch 2.6.1-155_centos6 @schmooze-commercial
[root@clean ~]# yum install sysadmin
Loaded plugins: fastestmirror, kmod
Loading mirror speeds from cached hostfile
Setting up Install Process
Package sysadmin-2.6.1-155_centos6.noarch already installed and latest version
Nothing to do
[root@clean ~]# 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
[Sat Oct 05 09:59:50 2013] [warn] default VirtualHost overlap on port 82, the first has precedence
[Sat Oct 05 09:59:50 2013] [warn] default VirtualHost overlap on port 81, the first has precedence
(98)Address already in use: make_sock: could not bind to address [::]:82
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
Just to keep these fora “clean” I think this problem would be better discussed in the “Distribution” forum, or perhaps the “commercial module” forum.
If we keep it here in “General Help” it might confuse those who just need “General Help”, no?
I think you have repeated entries in your schmoozecom.conf file. I’ve noticed sometimes that happens you have to manually repair it. Go to etc/httpd/conf.d/schmoozecom.conf and edit the file. I’d delete everything and add: Listen 80
<VirtualHost *:80>
DocumentRoot /var/www/html/
Then restart the httpd service. This should get you back into the GUI.
I tried the command you gave me however this is what I got
[root@clean ~]# etc/httpd/conf.d/schmoozecom.conf
-bash: etc/httpd/conf.d/schmoozecom.conf: No such file or directory
[root@clean ~]#
A log itself “says” nothing…A log doesn’t speak, It told you what’s happening (and what happened).
It’s up to you understand what (each line of) a specific log file reports while a system is running and performing (normal/not-normal/maintenance) operations.
If you do an update (as example, via GUI or via CLI) of a FreePBX module a log will be updated…in this case new lines will appear into /var/log/asterisk/freepbx.log so, supposing you’re trying to forcing an update of sysadmin module, if you run a:
cat /var/log/asterisk/freepbx.log|grep sysadmin
you will for sure find something relevant to sysadmin module (if anything really happened on it!).
As example I manually updated today sysadmin 2.11.0.21 to 2.11.0.23 via CLI and I found these lines on above log (trimmed) file:
[2013-Oct-06 10:29:27] [INFO] (bin/module_admin:575) - sysadmin 2.11.0.21 -> 2.11.0.23
Untaring..Module sysadmin successfully downloaded
[2013-Oct-06 10:29:49] [INFO] (sysadmin/install.php:21) - Successfully copied LoadLicenseIfExists.php.
[2013-Oct-06 10:29:50] [PHP-WARNING] (/var/www/html/admin/modules/sysadmin/install.php:178) - mkdir(): File exists
[2013-Oct-06 10:29:50] [INFO] (sysadmin/install.php:360) - checking for ftp_server field..already exists
[2013-Oct-06 10:29:50] [INFO] (sysadmin/install.php:376) - checking for tftp_server field..already exists
[2013-Oct-06 10:29:50] [INFO] (sysadmin/install.php:391) - checking for ups_enabled field..already exists
[2013-Oct-06 10:29:51] [INFO] (bin/module_admin:74) - Checking for abnormalcallvolume..No abnormalcallvolume found..Module sysadmin successfully installed
The tail -f command could be used to watch a log in live-mode from another shell…so from one shell (or from the GUI) you launch the update and from another one you watch the log populating.
You should have a basic knowledge of Linux command line…so if you want to cat the schmoozecom.conf file (AKA read the content of that file) you need to do:
cat /etc/httpd/conf.d/schmoozecom.conf
If it exists the command above will report you the content.
Writing what you wrote (in the way you wrote) is non sense.
If you want to list it use:
ls -la /etc/httpd/conf.d/schmoozecom.conf
A man ls or man cat will show you the manual pages of those two commands.
I agree with you, somebody should make the change to clear up things.
Also could be interesting to point out what is the situation up to know in order to let involved users to understand the issue and the solution.
Thanks for your help the GUI is back after editing the schmoozecom.conf file. Wow what a relief this saved me a 5 hour trip if I had to reload this box.
Hi Folks,
I’m still having issues. Two FreePBX boxes here and they’ve both got broken web GUI’s. I have updated the sysadmin module from the CLI (also the fax and backup modules while I was there) and have subsequently manually yum updated sysadmin to 2.6.1-158_centos6.
Oddly there is no schmoozecom.conf file on either box?
Not running the distro either…maybe that is part of the problem?? I need to keep digging, but any help appreciated!
TIA
In my case I just created a “schmoozecom.conf” file in /etc/httpd/conf.d/ and put the content in from the second half of chaser’s post above. It complained about some directories which weren’t there, but I clean that up now.
I can report that the web GUI is working again and my phones can now pickup XML do dah files I had in the http subdirectories as before.
Back to normal.
So what busted it???
No doubt the Schmooze people are going to hate me because I don’t run the distro. So I apologise completely in advance. But some questions…
-
Any idea why I didn’t have the schmoozecom.conf file? The systems are correctly licensed and up until now have been behaving nicely and all module upgrades have been pain free.
-
What module or script or other creates the various subdirectories under /var/html directory that I don’t have (nor need really, hence now commented out in the .conf file), such as /restapps and /restapi ?
Thanks again from the black sheep
You should really use the information that parnassus provided in post #16. What I posted was a work around to get the GUI working again. The info parnassus posted was from a good upgrade.
Go to the WebGUI and select System Admin from the Admin dropdown menu. On the RHS you should see a list of configurable system option. There should be one for Port Management. If you click on this, then you should see a list of configurable IP ports, and what they’re used for. Setting these ports will update the schmoozecom.conf file. The Admin Control Panel option should be set to 80 for normal web access to the GUI.
If the Port Management option isn’t there, then I’m guessing the sysadmin update hasn’t worked correctly, and you shouldn’t really be creating the schmoozecom.conf file. Instead, I’d suggest that you check the httpd.conf file in etc/httpd/conf/ and see if the Listen 80 line has been commented out (see my earlier post #10). If it has, then you may want to remove the leading #. However, what you don’t want to have is Listen 80 in both the httpd.conf file and the schmoozecom.conf file.
I’m sure Tony will correct me if I’ve given any bad advice!
I understand what a log file does and no there are no errors that I can see.
I still cannor acess the web interface for my server.
I guess I’ll have to reinstall it since there is no fix for this issue.
I do indeed have the port management options in System Admin, so it has installed correctly, but curiously neither of the boxes that have had the module updates have the schmoozecom.conf file - I had to create one in both cases.
Question is that a bug or just a peculiarity on my setups. Weird.
Good morning, I have followed the instructions here and when I try and do yum upgrade sysadmin I get the above error PYCURL ERROR 6 couldnt resolve host
any help would be greatly apprecaited
Thanks
Christian