unable to start apache as process/dameon

[Tapas Mishra]

On Wed, Mar 30, 2011 at 4:52 PM, Colin Law <clanlaw at googlemail.com> wrote:
> On 30 March 2011 12:11, Tapas Mishra <mightydreams at gmail.com> wrote:
>>
>> Here is one thing I found which made all things work I found in
>> /etc/init.d/ directory there are following files apache apache2.1 and
>> apache2.2 I remember long time back when I had installed it was only
>> apache but surprisingly I find these two files apache2.1 and apache2.2
>> also. Now when I did /etc/init.d/apache2.2 start then it started
>> working but I correctly remember I had not created apache2.1 or
>> apache2.2 or apache either so what could be the reason for existence
>> of 2 more files apache2.2 and apache2.1 apart from apache I was trying
>> to start service apache2 start and it was not working until I went to
>> /etc/init.d/ directory and noticed the presence of 3 files with name
>> apache and using one of them had worked.
>
> I think you would save both yourself and others a significant amount
> of time if you kept better notes on what you have done to each of your
> machines.  I find Tomboy Notes useful for this.  This is not the first
> time that you have asked for help and it turned out that the machine
> was not setup the way you remembered it was.
>
> Colin
>
>> ----------

daemon.log
http://pastebin.com/w1XMhNHL
syslog
http://pastebin.com/RdN6bjUm
/var/log/apt/term.log.1.gz
http://pastebin.com/cGi1a3BM

/var/log/apt/term.log.2.gz
http://pastebin.com/riYcXDFY

/var/log/apt/term.log
http://pastebin.com/1YicC1Cv

/var/log/apt/history.log.2.gz
http://pastebin.com/hZFib5Xh

/var/log/apt/history.log.1.gz
http://pastebin.com/yE3XK222

/var/log/apt/history.log
http://pastebin.com/XgKekqsg


the entries from 30th march on both the links are the ones which some
one might be willing to look.
My problem is solved as I mentioned in my previous message that there
were 2 extra files with name apache present in
/etc/init.d directory and using one of them was what had worked,but I
want to investigate this issue further as why did I needed to do this
? What was the reason that another file apache2.2. was present in
/etc/init.d and using that had worked and not /etc/init.d/apache2 .
My guess is some update might have over written (but I am not having
any facts to support my argument)
let me know what do I investigate ?Or some one can point to some thing
by looking at any other log even I will post.
Because this over writing or creation of files did not happened in the
virtual machines which were also lucid servers on this machine where I
reported this problem.