Welcome Guest. Please Login or Register  


You are here: Index > Softaculous Inc. > News and Announcements > Topic : AMPPS 2.1

2


Threaded Mode | Print  

AMPPS 2.1
Pixelate
Group: Member
Post Group: Newbie
Posts: 24
Status:
Is there a way for me to get the mysql databases out so I can do a fresh install of AMPPS. Maybe a fresh install will fix the port 80 issue?
IP: --   

AMPPS 2.1
Pixelate
Group: Member
Post Group: Newbie
Posts: 24
Status:
It looks like I'm going to have to go back to MAMP if I can't resolve this problem.
IP: --   

AMPPS 2.1
Pixelate
Group: Member
Post Group: Newbie
Posts: 24
Status:
What files do I move if I use a 2.0 install to keep the database files that I previously installed.

They were originally used on a 2.0 install and then today  I did the 2.1 update, so now I want to go back to 2.0.
IP: --   

AMPPS 2.1
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Please open a ticket. We will upgrade it for you.
http://www.ampps.com/support

-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

AMPPS 2.1 -- SQLiteManager/PHP version issue
--marc
Group: Member
Post Group: Newbie
Posts: 11
Status:
When the PHP Version is set to PHP 5.5, then clicking the 'SQlite Manager' at http://localhost/sqlite/ presents an error page which states:
Code
"Strict Standards: Non-static method sqlite::getDbVersion() should not be called statically, assuming $this from incompatible context in /Applications/AMPPS/SQLiteManager/include/SQLiteAutoConnect.class.php on line 12"


This is apparently a known bug with a 1-line fix ...
  --> http://sourceforge.net/p/sqlitemanager/bugs/56/
Code
/include/sqlite.class.php
  before: function getDbVersion($fullPath){
  after: public static function getDbVersion($fullPath){


Alternately, switch the PHP Version to PHP 5.3 and the error goes away.
IP: --   

AMPPS 2.1
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Quote From : --marc September 27, 2013, 11:46 pm
When the PHP Version is set to PHP 5.5, then clicking the 'SQlite Manager' at http://localhost/sqlite/ presents an error page which states:
Code
"Strict Standards: Non-static method sqlite::getDbVersion() should not be called statically, assuming $this from incompatible context in /Applications/AMPPS/SQLiteManager/include/SQLiteAutoConnect.class.php on line 12"


This is apparently a known bug with a 1-line fix ...
  --> http://sourceforge.net/p/sqlitemanager/bugs/56/
Code
/include/sqlite.class.php
  before: function getDbVersion($fullPath){
  after: public static function getDbVersion($fullPath){


Alternately, switch the PHP Version to PHP 5.3 and the error goes away.


Okay. Thanks for reporting.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

AMPPS 2.1
dmuch
Group: Member
Post Group: Newbie
Posts: 1
Status:
I also have this problem after update:

"The Apache start button can be clicked but then it doesn't change state. Apache doesn't show as started and 'http://localhost/ampps' etc. don't work".

Apache error log files:
[Sat Sep 28 15:26:19 2013] [warn] mod_wsgi: Compiled for Python/2.7.5.
[Sat Sep 28 15:26:19 2013] [warn] mod_wsgi: Runtime using Python/2.7.2.
[Sat Sep 28 15:26:42 2013] [warn] mod_wsgi: Compiled for Python/2.7.5.
[Sat Sep 28 15:26:42 2013] [warn] mod_wsgi: Runtime using Python/2.7.2.

How to fix the problem?
IP: --   

AMPPS 2.1
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Quote From : dmuch September 28, 2013, 2:36 pm
I also have this problem after update:

"The Apache start button can be clicked but then it doesn't change state. Apache doesn't show as started and 'http://localhost/ampps' etc. don't work".

Apache error log files:
[Sat Sep 28 15:26:19 2013] [warn] mod_wsgi: Compiled for Python/2.7.5.
[Sat Sep 28 15:26:19 2013] [warn] mod_wsgi: Runtime using Python/2.7.2.
[Sat Sep 28 15:26:42 2013] [warn] mod_wsgi: Compiled for Python/2.7.5.
[Sat Sep 28 15:26:42 2013] [warn] mod_wsgi: Runtime using Python/2.7.2.

How to fix the problem?


Hi,

From which version did you upgrade ampps?
Please open a ticket. we will look into it.

Try resorting default configuration. If you haven't made any changes in conf file.

-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

AMPPS 2.1
Tschoepler
Group: Member
Post Group: Newbie
Posts: 2
Status:
Same here. Updated today. I was able to run AMPPS and the server, even logged into the admin-panel & phpmyadmin-panel but then suddenly got a 404 and couldn't get Apache to run anymore. Same error messages. I checked ports and there is nothing on 80 or 443. Killed all httpd and made a restart etc. Nothing helped so far. The strange thing is that it worked after updating and I can't figure out what made it "crash".
IP: --   

AMPPS 2.1
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

We are doing some minor changes in Apache and PHP Configuration while upgrading. We take a backup of conf files first before modifying ( located at AMPPS/conf/httpd.conf-***.bak ), so in case Apache fails to start after a change we can restore the old conf file back and do the changes manually.

You can refer this wiki for the changes in the conf files:
http://www.ampps.com/wiki/Upgrading_AMPPS#Troubleshooting_and_FAQ_2

You can always open a ticket if you are facing any issues. We will look into it. :)


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

AMPPS 2.1
Tschoepler
Group: Member
Post Group: Newbie
Posts: 2
Status:
Going back to the backed up file didn't help. I ran "/Applications/AMPPS/apache/bin/httpd" and this is what it spits out.

Applications/AMPPS/apache/bin/httpd
[Mon Sep 30 09:40:16 2013] [warn] NameVirtualHost 127.0.0.1:443 has no VirtualHosts
(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

There is one more thing I recognized: I can run "sudo apachectl start" which also switches the buttons in AMPPS.app ("Start" grayed out, "Stop" and "Restart" saturated. Of course this doesn't help fixing the problem as it is OSX's Apache running but maybe it helps in tracking down the problem.

Thanks
IP: --   

AMPPS 2.1
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Quote From : Tschoepler September 30, 2013, 7:49 am
Going back to the backed up file didn't help. I ran "/Applications/AMPPS/apache/bin/httpd" and this is what it spits out.

Applications/AMPPS/apache/bin/httpd
[Mon Sep 30 09:40:16 2013] [warn] NameVirtualHost 127.0.0.1:443 has no VirtualHosts
(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

There is one more thing I recognized: I can run "sudo apachectl start" which also switches the buttons in AMPPS.app ("Start" grayed out, "Stop" and "Restart" saturated. Of course this doesn't help fixing the problem as it is OSX's Apache running but maybe it helps in tracking down the problem.

Thanks


Hi,

Sorry AMPPS does not have its own command line interface yet. You can start/stop the service from the GUI only.

"sudo apachectl start" will start the bundled apache which comes with mac.

Quote

(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

Sorry. Run it again with the "sudo" ahead of the command. i.e
Code
sudo /Applications/AMPPS/apache/bin/httpd


Please open a ticket, we will look into it. :)


Edited by tidus : September 30, 2013, 7:57 am

-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

AMPPS 2.1
ta6hbe
Group: Member
Post Group: Newbie
Posts: 4
Status:
Quote From : Pixelate September 26, 2013, 7:34 pm
[Thu Sep 26 12:33:53 2013] [warn] NameVirtualHost 127.0.0.1:443 has no VirtualHosts
(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs


Hello, I think you have to issue the command with sudo in front to run as root. I.e:
sudo /Applications/AMPPS/apache/bin/http.
IP: --   

AMPPS 2.1
ta6hbe
Group: Member
Post Group: Newbie
Posts: 4
Status:
I am having the same problem here. After updating to latest version, when I try to start Apache from the GUI by clicking the start button, start button becomes inactive (greyed out) then back to active again. Apache is not started and in the error log I get:

Code

[Tue Oct 01 11:04:06 2013] [warn] mod_wsgi: Compiled for Python/2.7.5.
[Tue Oct 01 11:04:06 2013] [warn] mod_wsgi: Runtime using Python/2.7.2.


When I run
Quote
sudo /Applications/AMPPS/apache/bin/httpd
I get:

Code

Could not reliably determine the server's fully qualified domain name, using computername.local for ServerName
in the terminal line.

Has there been any update in this at all? Appreciate your help.
Kind regards
IP: --   

AMPPS 2.1
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Can you Restore Default Configuration from Ampps Application ?


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

« Previous    Next »

Threaded Mode | Print  

2


Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is March 19, 2024, 3:13 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.048