[Techtalk] Cannot get LAMP mysql or php to start

[Wim De Smet]

Hi,

On Sat, Jan 16, 2010 at 1:51 AM, Leslie MacDougall <lesmacdee at gmail.com> wrote:
> Crash as in total shutdown. It's an older machine, but one of the
> beauties of Linux is that it can run on an older machine :D As far as
> I can tell I somehow misplaced a couple of important files. I'm a
> little worried about the possibility of hardware problems - they'll be
> more expensive than reinstalling my OS!

A reinstall might sort it, it's just a guess because random shutdowns
like that are usually really rare (most software problems cannot
trigger that kind of thing). Hopefully it is indeed nothing like that,
but it could be an overheating problem. That would be able to cause
data corruption (by overheating the IDE bus) and a host of other
problems. If so, cleaning some dust out might be enough to make it
return back to normal.

> Thanks for all your help on this Wim - it is much appreciated. I see
> you are in Google Wave... are you an expert on that too? :)
> Regards, Leslie

No problem. I use google wave more as a glorified note taking app, so
not really an expert, no. :-)

regards,
Wim

> On Sat, Jan 16, 2010 at 12:50 AM, Wim De Smet <kromagg at gmail.com> wrote:
>> Hi,
>>
>> On Fri, Jan 15, 2010 at 11:52 AM, Leslie MacDougall <lesmacdee at gmail.com> wrote:
>>> Hi Wim, don't know if this helps:
>>>
>>>> dpkg -l gave:
>>>> ii mysql-client 5.1.30really5. MySQL database client (metapackage depending
>>>> ii mysql-client-5 5.1.30really5. MySQL database client binaries
>>>> ii mysql-common 5.1.30really5. MySQL database common files
>>>> ii mysql-server 5.1.30really5. MySQL database server (metapackage depending
>>>> ii mysql-server-5 5.1.30really5. MySQL database server binaries
>>>> ii mysql-server-c 5.1.30really5. MySQL database core server files
>>>
>>> I had the above result saved from a former email to a friend. Also
>>> results for the following if you want them.
>>
>> That's odd, from the other output I would've suspected those
>> mysql-server packages weren't installed at all. Looks like the status
>> file is broken then.
>>
>>> Unfortunately I cannot even open a terminal before my computer
>>> crashes. (I am sending this email from someone else's windows machine
>>> :'( !!)
>>> Any suggestions as to how I can get mine to stay on long enough to
>>> find and kill the configuration job?
>>
>> What exactly do you mean by "crash"? Shutdown, black screen, ...? Just
>> booting up your pc and logging in should work. That doesn't make dpkg
>> launch, so if any problem were related to that, you should at least be
>> able to login and open a terminal. The fact that you can't points to
>> some deeper issue. Perhaps your friend was right and it's a bit of a
>> lost cause, though if weirdness like this is happening I'm still
>> inclined to think there's a hardware problem somewhere. You could try
>> reinstalling in any case.
>>
>> regards,
>> Wim
>> _______________________________________________
>> Techtalk mailing list
>> Techtalk at linuxchix.org
>> http://mailman.linuxchix.org/mailman/listinfo/techtalk
>>
>