Hello everyone, I need to setup "LAMP" platform on a 'localhost'for two php based applications: * eZ publish Content Management System * TNG - The Next Generation of Genealogy Sitebuilding With Suse Linux 9.1 Pro YaST2 I have already the rpms by default: * Apache 2.0.49 * MySQL 4.0.18 * PHP 4.3.4 * phpMyAdmin 2.5.6 While the Suse Administration manual contains a chapter on Apache web server setup, there is not a word about MySQL or phpMyAdmin. I could neither find procedures for it in the Suse support knowledge database. (There is however another howto for building a LAMP server from scratch (source code) on Redhat at http://www.lamphowto.com/ but I think it ought to be possible to use the Suse rpm packages). Therefore I wonder: - what is really done (installed, set up) during the default MySQL installation? - what is the suggested way to continue and finish the setup of database(s) and user(s)? - how to test the default and new setup? - phpMyAdmin is not found in the program menu, possibly how to start and run it? Regards, Terje J. Hanssen
On Sunday 10 April 2005 8:40 am, Terje J. Hanssen wrote:
Hello everyone,
I need to setup "LAMP" platform on a 'localhost'for two php based applications: * eZ publish Content Management System * TNG - The Next Generation of Genealogy Sitebuilding
With Suse Linux 9.1 Pro YaST2 I have already the rpms by default: * Apache 2.0.49 * MySQL 4.0.18 * PHP 4.3.4 * phpMyAdmin 2.5.6
While the Suse Administration manual contains a chapter on Apache web server setup, there is not a word about MySQL or phpMyAdmin. I could neither find procedures for it in the Suse support knowledge database. (There is however another howto for building a LAMP server from scratch (source code) on Redhat at http://www.lamphowto.com/ but I think it ought to be possible to use the Suse rpm packages).
Therefore I wonder: - what is really done (installed, set up) during the default MySQL installation? - what is the suggested way to continue and finish the setup of database(s) and user(s)? - how to test the default and new setup? - phpMyAdmin is not found in the program menu, possibly how to start and run it?
Everything you need to know was installed on your system, read the following; /usr/share/doc/packages/mysql/manual.txt /usr/share/doc/packages/mysql/README /usr/share/doc/packages/mysql/README.SuSE /usr/share/doc/packages/phpMyAdmin/Documentation.txt /usr/share/doc/packages/php4/README.SuSE Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.14-default x86_64
Scott Leighton wrote:
On Sunday 10 April 2005 8:40 am, Terje J. Hanssen wrote:
With Suse Linux 9.1 Pro YaST2 I have already the rpms by default: * Apache 2.0.49 * MySQL 4.0.18 * PHP 4.3.4 * phpMyAdmin 2.5.6
Therefore I wonder: - what is really done (installed, set up) during the default MySQL installation? - what is the suggested way to continue and finish the setup of database(s) and user(s)? - how to test the default and new setup? - phpMyAdmin is not found in the program menu, possibly how to start
and
run it?
Everything you need to know was installed on your system, read the following; /usr/share/doc/packages/mysql/manual.txt /usr/share/doc/packages/mysql/README /usr/share/doc/packages/mysql/README.SuSE /usr/share/doc/packages/phpMyAdmin/Documentation.txt /usr/share/doc/packages/php4/README.SuSE
Scott,
Thank you for the documentation tip.
What I have tried is the following two steps:
1) I wish automatically start of MySQL at bootup, and created a symbolic
link according to the /usr/share/doc/packages/mysql/README.SuSE:
# /sbin/insserv /etc/init.d/mysql
I rebooted but I'm not sure MySQL started as it should
2) According to eZ publish's first installation procedure, I tried to
login as root (to create a database next), but got the following error:
# mysql -u root -p
On Sunday 10 April 2005 12:53 pm, Terje J. Hanssen wrote:
What I have tried is the following two steps:
1) I wish automatically start of MySQL at bootup, and created a symbolic link according to the /usr/share/doc/packages/mysql/README.SuSE:
# /sbin/insserv /etc/init.d/mysql I rebooted but I'm not sure MySQL started as it should
Try rcmysql status to see if it is up and running.
2) According to eZ publish's first installation procedure, I tried to login as root (to create a database next), but got the following error:
# mysql -u root -p
Enter password: ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) What can be wrong here? Has e.g MySQL's internal database (mysql) been set up is it should during the installation? Is there any users set up and possibly is there already a default root password?
Sounds like it is not running. It installs with no root password, so unless you changed it, you should be able to simply type #mysql as root and access the db. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.14-default x86_64
Scott Leighton wrote:
Sounds like it is not running. It installs with no root password, so unless you changed it, you should be able to simply type
#mysql
as root and access the db.
Still the same error occures: # mysql ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) I verified that '/var/lib/mysql/mysql.sock' did not exist. Below is however the content of /var/lib/mysql/mysqld.log *) And where is e.g. the boot log file located to verify the messages I saw regarding startup of MySQL? Have I missed some steps that need to done after the Yast2 installation? Can possibly phpMyAdmin be used for this troubleshooting? Terje *) # cat /var/lib/mysql/mysqld.log 050410 20:54:09 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 050410 20:54:10 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 050410 20:54:11 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 050410 20:54:12 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 050410 20:54:15 InnoDB: Started 050410 20:54:15 Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't exist 050410 20:54:15 Aborting 050410 20:54:15 InnoDB: Starting shutdown... 050410 20:54:19 InnoDB: Shutdown completed 050410 20:54:19 /usr/sbin/mysqld-max: Shutdown Complete 050410 20:54:19 mysqld ended
On Sunday 10 April 2005 1:30 pm, Terje J. Hanssen wrote:
Scott Leighton wrote:
Sounds like it is not running. It installs with no root password, so unless you changed it, you should be able to simply type
#mysql
as root and access the db.
Still the same error occures:
# mysql ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
I verified that '/var/lib/mysql/mysql.sock' did not exist. Below is however the content of /var/lib/mysql/mysqld.log *) And where is e.g. the boot log file located to verify the messages I saw regarding startup of MySQL?
Have I missed some steps that need to done after the Yast2 installation? Can possibly phpMyAdmin be used for this troubleshooting?
Terje
*) # cat /var/lib/mysql/mysqld.log 050410 20:54:09 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 050410 20:54:10 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 050410 20:54:11 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 050410 20:54:12 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 050410 20:54:15 InnoDB: Started 050410 20:54:15 Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't exist 050410 20:54:15 Aborting
050410 20:54:15 InnoDB: Starting shutdown... 050410 20:54:19 InnoDB: Shutdown completed 050410 20:54:19 /usr/sbin/mysqld-max: Shutdown Complete
050410 20:54:19 mysqld ended
I dunno, it looks like maybe a bad install. Almost like your db didn't get built. When the RPM is installed, it is supposed to run /usr/bin/mysql_install_db which creates the basic db at /var/lib/mysql/mysql Do a dirlist of /var/lib/mysql/mysql and see if you have a bunch of table files there. If you don't, then I have no clue what is going on, I'd probably try running /usr/bin/mysql_install_db to see if that solves it. Also, what is in your /etc/my.cnf configuration file? Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.14-default x86_64
The Sunday 2005-04-10 at 22:30 +0200, Terje J. Hanssen wrote:
Still the same error occures:
# mysql ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
You need to run "rcmysql status" ar root to see if the service is running.
I verified that '/var/lib/mysql/mysql.sock' did not exist. Below is however the content of /var/lib/mysql/mysqld.log *) And where is e.g. the boot log file located to verify the messages I saw regarding startup of MySQL?
/var/log/boot.msg (and .omsg for the previous one).
Have I missed some steps that need to done after the Yast2 installation? Can possibly phpMyAdmin be used for this troubleshooting?
The first time you run ""rcmysql start" it should create the initial database with the proper permissions. That's the theory :-) You could try deleting the files and retry. :-? -- Cheers, Carlos Robinson
On Monday 11 April 2005 02:25, Carlos E. R. wrote:
The Sunday 2005-04-10 at 22:30 +0200, Terje J. Hanssen wrote:
Still the same error occures:
# mysql ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Sorry to come late into the thread but are you a client on a lan with a server or is it a standalone box? If the system administrator hasn't granted you permission to access databases then you'll not be able to connect. If you are the administrator I think at this stage that you should delete /var/lib/mysql then uninstall mysql server using yast, reinstall mysql server and follow the instructions which appear on screen when you type rcmysql start. Do _exactly_ what it tells you to do after that, cryptic as it is. Cheers, Steve.
I think I found some of the problem and (partly) solved it. For one or another reason (ADSL router, Ethernet switch or ISP dns), the dhcp doesn't look to provide a properly hostname in the initial boot process. When I manually configured my Ethernet interface with Yast2 and put in the right hostname (default was linux) and rebooted, then the internal mysql internal database was set up during startup. Then I also was able to create a root password for mysql, log in as root and create a database for eZ publish. I unpacked eZ publish to /home/terje/public_html which created a folder ezpublish-3.5.1. However I got "connection refused" again when trying this url in Mozilla: http://localhost/~terje/public_html/ezpublish-3.5.1/index.php Is this a wrong url and how does I possibly verify if this directory really is web-served? I checked with Yast2 System>Run level editor that mysql was running. However, Apache2 was not running and I enabled it. But still I am not able to start the eZ publish wizard. Suggestion? Terje
On Sunday 10 April 2005 5:38 pm, Terje J. Hanssen wrote:
I think I found some of the problem and (partly) solved it. For one or another reason (ADSL router, Ethernet switch or ISP dns), the dhcp doesn't look to provide a properly hostname in the initial boot process. When I manually configured my Ethernet interface with Yast2 and put in the right hostname (default was linux) and rebooted, then the internal mysql internal database was set up during startup.
Then I also was able to create a root password for mysql, log in as root and create a database for eZ publish. I unpacked eZ publish to /home/terje/public_html which created a folder ezpublish-3.5.1. However I got "connection refused" again when trying this url in Mozilla: http://localhost/~terje/public_html/ezpublish-3.5.1/index.php
Is this a wrong url and how does I possibly verify if this directory really is web-served?
I checked with Yast2 System>Run level editor that mysql was running. However, Apache2 was not running and I enabled it. But still I am not able to start the eZ publish wizard. Suggestion?
Try something simpler to make sure that you have Apache, PHP and mysql all working. Put a simple index.html file in your ~/public_html folder and see if you can browse to it at http://localhost/~terje/public_html/index.html Once you get that much working, then move on to the harder things like EZ Publish. You are trying to do too much at once. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.14-default x86_64
Scott Leighton wrote:
Try something simpler to make sure that you have Apache, PHP and mysql all working. Put a simple index.html file in your ~/public_html folder and see if you can browse to it at http://localhost/~terje/public_html/index.html
If you point your brouwer at http://localhost/~terje, you will get the file /home/terje/public_html/index.html. If you specify the extra public_html, of course this is not found, since that directory will not exist (by default, unless you created it in public_html of course) -- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
Apache web service: 1) I copied index.php to my "public_html" and tried http://localhost/~terje/index.php but this resulted in error messages: Mozilla: "!The connection was refused when attempting to contact localhost." Opera: "Could not connect to remote server. You tried to access the address http://localhost/~terje/index.php, which is currently unavailable." Konqueror: "An error occurred while loading http://localhost/~terje/index.php: Could not connect to host localhost" 2) With another test using http://localhost:8085/ displayed the "Test page for Apache Installation" telling on the first line: "If you can see this, it means that the installation of the Apache web server software on this system was successful. You may now add content to this directory and replace this page." 3) I also get this Apache test page displayed if I browse with the Konqueror file manager to file:/srv/www/htdocs/index.html.en 4) But if I try Konqueror with http://localhost/~htdocs/index.html.en nothing else than this is displayed; "An error occurred while loading http://localhost/~htdocs/index.html.en: Therefore I wonder 1) If the above directories really have become enabled "web-seviced" (published) by Apache, and if there is some tests to verify it? I have enabled the http service wiht Yast2, but which portnumber(s) has to be set for running from localhost? 2) Maybe "localhost" does not work because there still can be some missing regarding my dhcp, hostname or network configuration? (I notice a message "resolv.conf not found!" during the boot process.) Terje
On Monday 11 April 2005 2:12 pm, Terje J. Hanssen wrote:
Apache web service:
2) With another test using http://localhost:8085/ displayed the "Test page for Apache Installation" telling on the first line: "If you can see this, it means that the installation of the Apache web server software on this system was successful. You may now add content to this directory and replace this page."
That means you must have messed around with apache's configuration, you have it listening on port 8085. It is going to be real difficult for people here to help you if you leave out important details, you earlier told us you installed the three packages using Yast, Yast does not set apache to listen to port 8085. Suggest you give us _all_ the details on what you have changed if you expect help. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.14-default x86_64
participants (5)
-
Carlos E. R.
-
Koenraad Lelong
-
Scott Leighton
-
steve
-
Terje J. Hanssen