my time with debian has been interesting ive learned alot... but my blood pressure has also went through the bloody roof.

I have a deadline of March 27th 2004 to get a webserver up that displays a working version of a website i making for a customer. I have easily 2-3 days of coding left (assuming all goes to plan) .... and very little time to dick around with linux and its counterparts.

i need a webserver that has php and mysql working. I have a gut feeling that php is working (at least it use to) . mysql is giving me this problem


me@MyAgony:~$ mysql
ERROR 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/
mysqld.sock' (111)
me@MyAgony:~$


when i go to the folder that the error specifies there is nothing there... whats up with that??


i know beggers cant be choosers but i would love to have mysql 4.0.17 on this baby but i can settle for the 3.2 that came with debain 3 (the current os) if thats what will work.

all i need is the dameon to start up and im set b.c i can connect to it through sqlYog from my windows machine.

if it isnt possible to get this problem fixed i will have to install windows server 2003 on the machine and once that happens there is little chance debian will ever go back on it



thanks,
race

# /etc/init.d/mysql start

With great respect, I think you are very brave to setup an unknown system for a webserver especially when it comes to later admin. Linux is very different to M$ in approach and needs a lot of work as you are finding out. The big plus in my book is that networking is much easier than M$.

nevermind, thought it was a problem with debian itself

alright so at least i can now verify that mysql is working (i can go to etc/init.d and then type mysql ). during the reinstall i hit yes when it asked to start at boot time.


but i think i have a firewall problem now... because even after a restart i still cant remote access my database. even when i try to access it when im logged onto the linux box.

me@MyAgony:~$ telnet localhost 3306
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

according to my calculations i should only have ipchains installled

MyAgony:/home/me# dpkg -l | grep fire
ii ipchains 1.3.10-15 Network firewalling for Linux 2.2.x
ii xfwp 4.1.0-16woody3 X firewall proxy server
MyAgony:/home/me#

because i just unistalled xfwp which took with it the "x-window-system" and i still have the problem.

so where good begginer tutorial for ipchains... ive seen tutorials for this stuff before and i was amazed at how complex it is to configure.

Do you have a telnet server running on your local machine ? If not, then of course you can't telnet to yourself .

Remotely access the sql is disabled by default I believe. Usually people run the webserver and write script that connects to the sql server on that machine. Then have others connect to the webserver to display pages.

yeah i got telnetd running (its about the easiest thing i think ive installed on the box)

which file do you have to change to allow remote access?

Check your my.cnf file in /etc/mysql and comment out "skip-networking"

Incorrect. You can reach many services that do not involve logging in, such as mail, http, ssh, ftp, irc, and mysql, without having an in.telnetd. (whether this is a good way to use them is another issue, but I think the OP was performing a basically sound diagnostic.)

ok so now it accepts remote access BUT it wont let you login. for example i use SQLyog to access my databases. its easier than the command line bs. and when i type in the address it gives me and error " you cant access this computer" or something along those lines. the same happens when i telnet to the port.

i get this error:?Host 'j24.rh.rit.edu' is not allowed to connect to this MySQL server

secondly. there are two passwords and usernames. one that was created by debian in the debian.cnf file and the second in the my.cnf. which one is the valid one?????

Have you tried the actual IP (192.168.1.1 for instance) instead of localhost (127.0.0.1), because telnetd might not be bound to localhost, but to the NIC.

Good luck.

Check the host value for the username that you are trying to connect remotely with. It might be set to localhost, restricting any remote access for that username. You can set it to % to allow remote login from any address to test it.